Posts by igrnt

    I'm confused because it is listed in the omv.extras 3.x stable.
    I will try to install it without plugin

    This is probably because I ported to OMV 3 early on, in v3.something before some major change occurred in 3.somethingBigger.
    You should still be able to install mpd itself without the plugin, as that it just pure debian.

    That (just the 'listen: bind to 0.0.0.0:6600' message, nothing about missing audio outputs in the logs) sounds like it is working then - now you need to connect to http://x.x.x.x:8000/mpd.ogg to hear the stream (assuming you used the Arch Wiki example verbatim, i.e. with Ogg Vorbis output). But as I say, I have never used the httpd output module myself so have not tested.

    I just gave it a try and indeed it does something:

    Code
    $ mpd
    listen: bind to '0.0.0.0:6600' failed: Address already in use (continuing anyway, because binding to '[::]:6600' succeeded)
    output: No "audio_output" defined in config file
    output: Attempt to detect audio output device
    output: Attempting to detect a alsa audio device
    output: Successfully detected a alsa audio device

    This way I can connect to the server but there is no music available.
    As opposed to ALSA output, where music is available and playable but there is no sound (on the client, the server is headless/speakerless).

    That log output sounds like you don't have an audio output configured.


    In addition, your last line sounds like you are using MPD on the OMV server, with and MPD client on another machine, and you are expecting the audio to come out of the speakers on your client machine. That is not how MPD works - audio outputs are on the server, so obviously with a speakerless OMV machine, you will not hear any audio output. At least not with traditional outputs like ALSA.

    Depends what the exact error you are getting is.
    I have never used the http or shoutcast outputs with mpd, so am unable to advise, but it looks like a problem with mpd rather than the plugin, per se - are you able to get mpd working when configuring outside the plugin?

    It isn't yet compatible with OMV3, still to do I'm afraid. I haven't tried it with OMV3 myself, perhaps others have managed to get it working.

    Detection of RAID arrays on top of encrypted disks is problematic. I think you could use mdadm --scan to detect the RAID array after unlocking the disks, but it is far better instead to create the encrypted disk on top of the RAID array. Automatic RAID detection and assembly will then work much smoother.


    Do this:

    • Wipe disks
    • Create RAID array from raw disks
    • Create encrypted volume using RAID array
    • Unlock encrypted volume, add shared folders

    So this is the cause of your problem. Check 3. and 4. like it says. Then, what's your setup, version of OMV, etc?


    I just tested LUKS on partitions (OMV 2.1.29, LUKs plugin 2.1.2) and it works fine, as I described:

    • Create partitions with, e.g. fdisk on command line (/dev/sde1)
    • Install plugin, then create LUKS containers on command line, e.g. cryptsetup luksFormat /dev/sde1
    • Observe /dev/sde1 appears in Encryption plugin UI and can be unlocked, mounted, etc.

    So the reason your LUKS partition is not visible in the plugin is not because it is not a raw block device (that restriction is only for creating new LUKS devices via the web UI), it is because there is something missing from your OS so the plugin can't detect existing LUKS devices.

    It isn't already possible via the plugin UI, it operates like the OMV filesystem page, it only lists whole block devices as candidate devices.


    What is possible is that, just like if you want to partition the OS drive, you must do this via the command line. If you create a LUKS device in this way, it should be usable perfectly fine in the plugin UI.


    I think that since there is no UI for managing partitions in OMV, that it is fine to expect users to have to resort to the command line if they want to do this.

    No, it's not compatible with OMV 3 yet. I haven't the time to do it at the moment. Pull requests are welcome!


    Still not sure about the partition issue - data partitions on the OS drive is an unsupported feature in OMV anyway, so probably best left to the user to do via command line if they want to take this route.

    What about Support für Openmediavault 3.0.22? Could you do that? because i cant set it up with 3.0.13 anymore because the other plugins install 3.0.22 somehow. And i need your plugin to unlock the disks of my raid


    I hope you can do that sometime


    I plan to update the plugin when OMV 3 reaches beta/feature-stable status, which means currently that it doesn't work with the new datamodels introduced around 3.0.13-15. I haven't had time so far to look at that so I have no idea about it.

    I just finished setting this up on my system, all went without a hitch with 2X3TB Hard Drives (not in raid)


    But now I'm wondering since both drives have the same passphrase, if there's any way I could unlock both at once (i.e. enter the passphrase once rather than twice to make my life easier)?


    Not via the Web GUI, I'm afraid. Via the command line you could do this using key files. Unless you reboot your system often, you should only have to unlock infrequently, right?


    As an aside, unless you duplicated the header from one drive to the other, they actually have different encryption keys, despite having the same passphrase.


    The easiest solution to this is probably to do LUKS-on-RAID, rather than RAID-on-LUKS.


    I understand the USB Stick thing, but my problem ist, that i have for example my plex server running. So i stream media from everywhere and most times i am not at home. If any error occurs or power loss, i can't get my server up and running without vpn or i open a port for ssh to internet.


    Thats why i would like a lokal network solution. I want it in case my server gets stolen, the key is on another device. I think this could be secure way? like wget the key through LAN ftp after boot and unlock the device, mount them and then delete the file. Should be the same security as an usb stick, because my small odroid c2, where the key would be stored on, would be hidden well :-).


    I hope you understand what i mean, because i would really like to have an automated unlock method :-)


    I understand what you mean, but since it is not something I would use myself, it is not a priority for me to develop network-based unlocking. I am unlikely to do it, but a) never say never, and b) patches/code to implement this are certainly welcome.

    That is expected behaviour - how different services handle the presence or otherwise of paths at startup varies. Samba seems to work okay, for instance.
    I can look into having the plugin reload NFS though (check: does reloading nfs work, or must it be restarted?)

    You posted your mpd.conf once already, I don't understand what is now preventing you from doing that again, but unfortunately I'm unable to help you any further. I suggest you look for something else (subsonic?) or look into mpd for yourself.