I have had a mergerfs pool since OMV5 (now OMV6) all working fine (rpi4 with 4 USB drives).
Since upgrade to OMV6 though, there is some strange behaviour:
After every reboot, the mergerfs pool is not available in File Systems.
I then have to go into Mergerfs Plugin and manually click "Restart pool", which gives a browser error (see below).
After that mergerfs is available in File Systems and I need to restart Docker and all works well.
Didn't we discuss this in your other thread already?
we never resolved it
If I can't reproduce it or figure out why from your info, I don't know what changes to make. Who else do you think is going to help/make changes? I'm not sure what starting a new thread will do to help.
Other users.
I run 2 rpi based servers and both show exactly the same issue.
I assume there are other Raspberry users who come across the same issue and I am curious what their findings are.
Isnt that the purpose of the forum?
Sure but we had all of the info/questions/investigation notes in the other thread.
I'm glad you have two that show the same issue but that doesn't help me. The mergerfs plugin has zero issues on my sata connected systems. I don't have a bunch of usb drives (none that are hard disks) and a lot of time to reboot a system waiting for failures. I know you want to blame me for changing from fstab to systemd but all fstab entries are converted to systemd.
If you and other users can figure it out, I will gladly make changes to the plugins.
Is there a way to insert delays into the boot sequence?
Sure but then any service that is waiting on the mergerfs pool (like docker for example) would fail. I don't consider this a solution though.
sudo systemctl edit srv-mergerfs-POOLNAME.mount
and add:
[Service]
ExecStartPre=/bin/sleep 30probably some creative way to do that but I cant think of a way right now. might as well add longer delay to docker.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!