Problem booting up with LUKS and UnionFileSystem

    • OMV 5.x (beta)
    • Problem booting up with LUKS and UnionFileSystem

      Hi there,

      I am pretty new to Raspberry and Linux stuff, please consider this.

      I'm having issues using a RPi4 with OMV5. When I mount my 2 encrypted drives and then reboot OMV, it takes a while because mounting the filesystem is timing out (obviously, because the drives are locked when rebooting the RPi). But the system boots and I can access the GUI. Then I unlock the drives and I can mount the filesystems in GUI. I added x-systemd.device-timeout to the drives in /etc/openmediavault/config.xml and then did omv-salt deploy run fstab to save this.

      After creating a pool with UnionFileSystem it mounts and shows it correctly in GUI. But after restarting OMV the RPi boots to emergency mode.

      I followed the instructions on this site at "4.1" but without SnapRaid.

      I don't know, how I show you the logfiles. If you need them, please tell me, how I can do that.

      I'm looking forward to your help. Thanks in advance!

      Best regards

      Edit: after deleting the entries in fstab it boots again, but I can't mount the pool. I got some logs, I hope it helps.
      Images
      • after restarting with pool.jpg

        964.83 kB, 1,920×1,440, viewed 56 times
      Files

      The post was edited 2 times, last by Final ().

    • Hi,

      I have the same issue using a similar setup with encrypted drives and unionfilesystem.
      In OMV4 this setup worked as expected, but in OMV5 the system boots into emergency mode.
      The cause for this behaviour seems to be additional configuration options in fstab written only by OMV5.

      I was able to work around this issue by manually removing all 'x-systemd.requires=...' options from the pools entry in fstab.
      The system then boots in normal mode. After unlocking and mounting all drives the pool seems to work fine. Only the branches tab in Union Fileystem usually shows no drive names which can be resolved by slightly modifying the pools configuration. Unfortunately saving the configuration overwrites fstab with the old settings.

      I appreciate the fact that OMV5 now at least checks if all drives are present, but this breaks setups with encrypted drives.
      Is there a way to change the default options?

      @Final Deleting only these options instead of the whole configuration might make the pool mount again.

      I hope this helps
    • Hello everyone,

      That's my 2nd try with OMV, so far I'm using unraid, but I'm looking for something light, like raspi 4

      And, I've same problem with unionfs
      How I can modify config.xml to remove "permanently" definition x-systemd.requires in fstab?
      Also there's problem with mounting unionfs even modyfing fstab
      I added noauto option to fstab, then manually mounted via shell by

      mount /srv/union-id

      even then, NFS doesn't worked well, directory mounted outside uniofs, lots of errors about missing ID, etc.
      So far unionfs can't work with luks
      (from my point of view, LUKS is "must have")
    • Joe Chip wrote:

      How I can modify config.xml to remove "permanently" definition x-systemd.requires in fstab?
      Change the options in the mntent section. If you edit the pool in the web interface, it will add them back though. I guess I could add a checkbox to disable them.
      omv 5.3.4 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.5
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Thx!

      I've done that again... and looks much better...
      Still have to mount filesystems, mount unionfs from shell (that's frustrating)
      So far NFS is working well, data is saved on unionfs folder (probably)

      but. still have error like

      Couldn't extract an UUID from the provided path '/export/union'.

      need to do some magic with configuration?

      Error #0:
      OMV\Exception: Couldn't extract an UUID from the provided path '/export/union'. in /usr/share/php/openmediavault/system/filesystem/backend/mergerfs.inc:96
      Stack trace:
      #0 /usr/share/php/openmediavault/system/filesystem/backend/mergerfs.inc(64): OMV\System\Filesystem\Backend\Mergerfs::extractUuidFromMountPoint('/export/union')
      #1 /usr/share/php/openmediavault/system/filesystem/filesystem.inc(904): OMV\System\Filesystem\Backend\Mergerfs->getImpl('240:480')
      #2 /usr/share/openmediavault/engined/rpc/sharemgmt.inc(158): OMV\System\Filesystem\Filesystem::getImplByMountPoint('/srv/6e164aa3-6...')
      #3 [internal function]: Engined\Rpc\ShareMgmt->enumerateSharedFolders(NULL, Array)
      #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      #5 /usr/share/openmediavault/engined/rpc/sharemgmt.inc(205): OMV\Rpc\ServiceAbstract->callMethod('enumerateShared...', NULL, Array)
      #6 [internal function]: Engined\Rpc\ShareMgmt->getList(Array, Array)
      #7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      #8 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getList', Array, Array)
      #9 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('ShareMgmt', 'getList', Array, Array, 1)
      #10 {main}
    • Joe Chip wrote:

      Couldn't extract an UUID from the provided path '/export/union'.

      need to do some magic with configuration?
      I don't know what is causing this. /export/union shouldn't be passed to the mergerfs backend. I also can't reproduce it.
      omv 5.3.4 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.5
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Joe Chip wrote:

      Are You using Rasberry installation, or intel based? maybe those problems are related to raspi build and not caused by any plugins?
      The plugin doesn't know/care what system it is running on.
      omv 5.3.4 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.5
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • I'm almost done :)

      So it's not raspi problem
      after few plugins updates, there's progress
      NFS works, /export is mapped properly on

      240:480 on /export/union type fuse.mergerfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other)

      for now just got error with editing shares

      "Couldn't extract an UUID from the provided path '/sharedfolders/union'."

      but there's definion in xml config
      Is something missing or just bug?


      <sharedfolder>
      <uuid>6bfa939b-dfe3-44b8-8614-5a7004cfd8f0</uuid>
      <name>union</name>
      <comment></comment>
      <mntentref>553826eb-d02e-457d-b98c-26c7e3752160</mntentref>
      <reldirpath>union/</reldirpath>
      <privileges>
      <privilege>
      <type>user</type>
      <name>proxmox</name>
      <perms>7</perms>
      </privilege>
      </privileges>
      </sharedfolder>
      </shares>
    • I'll answer to myself and all others intrested in using OMV with LUKS and unionfs,
      I can mount now all from from gui or shell

      Just created simple script for a little automation, it's easier to explain that way ;)

      Shell-Script

      1. #!/bin/bash
      2. # input passphrase for each disk
      3. cryptsetup luksOpen UUID=d4fafafb-2d6c-447d-8a27-ec80ef74024b 240
      4. cryptsetup luksOpen UUID=477ae786-cf19-4419-a57f-6be80c70d480 480
      5. # mount disks
      6. mount /srv/dev-disk-by-label-480/
      7. mount /srv/dev-disk-by-label-240/
      8. # mount unionfs and nfs share
      9. mount /srv/6e164aa3-6c7f-4e2c-9a00-cbe3d686dc1e/
      10. mount /srv/6e164aa3-6c7f-4e2c-9a00-cbe3d686dc1e/union/
      11. # restart nfs to refresh exports
      12. systemctl restart nfs-server.service
      Display All
    • Users Online 1

      1 Guest