Problem booting up with LUKS and UnionFileSystem

I'm using OMV5 + Luks + SnapRaid + Union/MergerFS and also had a problem of rebooting into emergency mode.

I hava managed to workaround this issue by adding "noauto" option in mergerfs entry in /etc/fstab. This disables the automatic mounting of mergerfs partition at boot (which cannot possibly succeed without unlocking Luks first) and causes OMV5 to reboot normally with GUI available. Then I unlock encrypted drives manually and, after that manually mount the mergerfs partition

mount /srv/random-mergerfs-uuid-copied-from-fstab

After that, shared folders immediately become available via SMB. Also, branches tab in UnionFS plugin gets updated automatically. I didn't test NFS, though. I don't mind doing manual actions after reboot because typing in Luks passphrase manually is required anyway. It would be nice if there was "mount UnionFS" button in GUI, though...

I run into the same problem after having a perfectly working UnionFS without LUKS i readded the UnionFS and applied encryption and now it's not working. i've tried peca89's solution "noauto" but still it boots into rec.mode. Does this work with MergeFS instead? How do I get past the error?

I have no idea, really. This is my first experience with OMV. I made it working without actual understanding of what's behind. For your reference, here is my fstab file:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdb1 during installation
UUID=373b353d-8628-438c-9f9f-6695718947a8 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sdb5 during installation
UUID=ef4b5e89-6564-46bd-a8a9-903cdd644cfd none            swap    sw              0       0
# >>> [openmediavault]
/dev/disk/by-label/data1        /srv/dev-disk-by-label-data1    ext4    defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
/dev/disk/by-label/data2        /srv/dev-disk-by-label-data2    ext4    defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
/dev/disk/by-label/parity        /srv/dev-disk-by-label-parity    ext4    defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
/srv/dev-disk-by-label-data1:/srv/dev-disk-by-label-data2        /srv/463f1db0-4d92-4076-a298-d082663c3a0c    fuse.mergerfs    defaults,noauto,allow_other,cache.files=off,use_ino,category.create=mfs,minfreespace=20G,fsname=pool1:463f1db0-4d92-4076-a298-d082663c3a0c,x-systemd.requires=/srv/dev-disk-by-label-data1,x-systemd.requires=/srv/dev-disk-by-label-data2    0 0
# <<< [openmediavault]

And the script I created and placed in /usr/local/bin to unlock all drives with the same password:

root@omv:~# cat /usr/local/bin/unlock-all.sh
#!/bin/bash

echo Enter password for unlocking all drives:
read -s lozinka

echo $lozinka | cryptsetup luksOpen /dev/sda sda-crypt;
echo $lozinka | cryptsetup luksOpen /dev/sdb sdb-crypt;
echo $lozinka | cryptsetup luksOpen /dev/sdc sdc-crypt;

#Mount all fstab entries except those with noauto option
mount -a
#Mount noauto entry manually
mount /srv/463f1db0-4d92-4076-a298-d082663c3a0c

Thanks peca89 ! I've managed to manually edit the fstab file so ignore mounting the encrypted mergeFS array and then i am manually decrypting and mounting it from the dashboard menu. Since I seldom restarts my server I have no problem with it but I hope this gets fixed in the near future.

Gnarf How are you exactly manually mounting the unionfs from the dashboard menu after you have manually decrypted the disks?

To mount from the dashboard was an overstatement. I use SSH, sorry for the typo.

Thanks peca89

The noauto worked only that when I now unlock the encrypted drives there broken. The fuse.mergerfs filesystem will not mount. It would really be become simpler if this was fixed in the future by the devs, because it really is a hassle when one cant properly restart the system.

The best solution is to include the encrypted volumes in your crypttab and add the initramfs option. This will bring up a password prompt at boot time for the volume so you can decrypt it.

sda-crypt /dev/sda none luks,initramfs

You can also refer to my post

LUKS + KeyFile + AutoMount? [SOLVED]

Zitat von ryecoaaron

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.

Is this something that can be implemented in the near future? Namely remove all the "x-systemd.requires" options from the union pools entry in fstab. And maybe a reload/check function for mergerfs so that all branches shows correct disks and not n/a without the need of modify mergerfs?

Zitat von Hylve

Is this something that can be implemented in the near future? Namely remove all the "x-systemd.requires" options from the union pools entry in fstab. And maybe a reload/check function for mergerfs so that all branches shows correct disks and not n/a without the need of modify mergerfs?

I've implemented the noauto and crypttab configuration. However do you know I can automount the union filesystem without having to enter cli everytime?