Beiträge von titango20

The previous thread previous thread talks about a boot problem with debian10, omv5 and cryptsetup. It closed with a temporary solution.

The solution works for boot process but not for system to work properly as mounting devices is not possible without the lines in fstab.

The previous thread mainly handles mergefs problems, so this thread might be good for my problem.

Problems for the solution (sry for double input)

• One of (temporary(?)) solutions for mergefs problem to not boot:

  adding no-fail (?) to /etc/fstab file. Well, omv5 does it already by default, so its just a check. If it works it would be a full solution in my opinion (=not temporary, but permament). Unfortunately it doesn't work for my system.

• other temporary solution:

  uncomment problem lines in /etc/fstab

  Temporary, because why should I "fix" a main file in debian thats finally handled by 3rd-party-system = omv.? Btw I need to activate lines after boot to be able to use the problem-drives. Otherwise system doesnt know them.

Sorry for losing main aspect of mergefs. I discriped my problem in referenced thread.

I will start a new thread here if you are more happy with that.

Thanks to geaves for clarification.

.

Thank you johnnyb

I experienced the same problem and solved it yesterday.

Commented out all drives in /etc/fstab (but not system drive xD) and my system booted as expected.

My drives are encrypted via luks plugin as well.

Running OMV5 with Debian 10.