MergerFS stops the OMV 6 to continue boot.

1st Official Post

    Hi, I have configured mergerfs to mount 5 4tb drive. It is working with snapraid. Normally it works ok.
    However, if a file system error occurs during boot or the system fails to mount a drive, mergerfs makes the OMV to go for emergency mode.
    A ctrl+d and some sudo fsck fixes things most of the time.
    I am using no fail options for the drives. There is no such option for mergerfs sadly.
    Is there any way the system continues to GUI bypassing the maintenance mode. The system is really installed far from me and I can't do maintenance until it completes the boot sequence and connects to internet.
    Thanks.

  • chente

    Approved the thread.
    • Official Post

    While mergerfs doesn't support nofail, systemd mount (what the mergerfs plugin creates) should support it to not cause rescue mode. I haven't tried this because it is hard to simulate this problem. But it seems like you should fix the system since it is doing what it should - protecting your data.

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.4 | cterm 8.0 | borgbackup 8.1.6 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Thanks 1

    Thanks. I have fixed my drive problem for now.

    But this has happened before . What I only needed was to get out of emergency mode and run a fsck. The problem was someone had to connect keyboard and press ctrl d which would be highly inconvenient.

    I was thinking, if it would be possible to run mergers after network.online.

    The Mount file generated did put the omv to emergency mode I think.

    • Official Post
    Quote from sakib.buet51

    if it would be possible to run mergers after network.online.

    mergerfs waits on network-fs.target which would have to have network-online. But if the system goes into single user, it won't matter.


    Quote from sakib.buet51

    The Mount file generated did put the omv to emergency mode I think.

    You are correct. That is why I said to try adding nofail to the mergerfs pool options. According to the systemd.mount page, even though mergerfs doesn't do anything with nofail, it looks like systemd should.


    Quote

    With nofail, this mount will be only wanted, not required, by local-fs.target or remote-fs.target.

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.4 | cterm 8.0 | borgbackup 8.1.6 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Thanks 1

    Thanks again,
    I have configured it with nofail.
    In future, I will update the thread with the effect of no fail either as success or failure.

    So if I get a gui/ssh remote access with drive needing for fsck, it would be a success.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login