Openmediavault is adding wrong UUID in FSTAB - System no longer boots

Hi everyone,

recently installed openmediavault on my debian machine.

It's running from a 1TB SSD which is encrypted.

I added 4 encrypted disks to the system, then installed the LUKS plugin + unionfs + snapraid and mounted my disks.

Adding an SMB share worked fine and i was able to copy files to my disks.

After a reboot, my system is no longer booting. When checking the fstab, the uuids added by OMV do not match the uuids I get when running blickid.

When booting, I now get a message telling me that there's a start job running for /dev/disk/by-uuid/<wrong uuids added by omv> + (after 90 sec of waiting for the start jobs): Time out waiting for device /dev/disk/by/uuid/<wrong uuid added by omv>, followed by "you are in emergency mode.

Why is OMV adding wrong uuids to /etc/fstab and how do i prevent this from happening again?

I've been able to boot by doing this:

For anyone facing the same problem, this is how you can boot again:

• at the grub prompt, hit "a" to append options
• add init=/bin/bash to the end of the kernel command line and press enter

The system will boot to a command line enter the following commands at the prompt

• mount -o remount,rw /
• nano /etc/fstab

Uncomment the wrong uuids by adding # to the beginning of the affected lines.

blkid <span style="font-family:Arial, Helvetica, sans-serif;">will give you the correct uuids</span>.

I can unlock the encrypted drives using the webui, but i can't use them as the entries are missing in the fstab (which makes sense as i've uncommented them).

blkid is now giving me a lot more uuids as well, now the encrypted disks are unlocked.

So it seems what happens is this: OMV is adding the uuids of the unlocked lvm/partition/disk? (i am not that versed in linux, i've set the disks up using the web ui). however, those are not available during boot, as the disks are locked. i am not prompted to unlock the disks during boot (prompt is coming up only for the encrypted boot drive, which works fine).
See attached screenshot. The upper uuid is available during boot, the lower one is added into the fstab.

okay, so switching to mergerfs fixes the problem as the unionfs-plugin is missing the necessary option to disable automounting.

Problem booting up with LUKS and UnionFileSystem

Zitat von ryecoaaron

You can add ,noauto to the options box on both plugins.

Oh. now that you mention it... I could have done that. I've instead added my /srv/dev/disks-by-uuis folders.