Series of updates/LONG reboot, and now "Disks" and "File Systems", etc don't load

    Hi all,


    Just registered to post my first major issue with OMV. It'd been working smoothly and I use it for modest things, like SMB, Plex, and Wyze Bridge. It contains a ZFS pool of two 4 TB drives that I use for media files and a few external USB HDDs for backups. I try to be in the habit of applying updates as they come. Yesterday, I applied a bunch that appeared and they all seemed to go through ok, plus I did a reboot. Now, as in the subject line, my drives don't load at all in the GUI, nor file systems. They just indefinitely load. When I look at the SMB share, everything loads apart from the shared folder on the ZFS pool.


    What can I check to rule out any issues? I'd be surprised if it was a faulty drive in the ZFS pool as the drives are new/have a healthy SMART status, and all the issues started arising after the various updates I installed. The reboot also took a LONG time -- like 20+ minutes, in case that might provide a clue. There are also background tasks that I try to attach to but nothing appears.


    At a bit of a loss and don't want to mess with anything else at this time. I have a backup of the ZFS pool data, but yeah, happy to post any system details/logs etc that'd help diagnose the issue. Thanks in advance!

  • macom

    Approved the thread.

    Perhaps some clues in the boot logs:


    Quote from mh1983

    Here's my system kernel page, in case it helps:


    Select the Debian 6.1.31-amd64 and set it as Set boot.



    Reboot the system and see if everything works as before.



    On a side-note, the errors you posted is monit complaining about a missing NTFS drive:

    Quote from mh1983

    monit[459]: Filesystem '/srv/dev-disk-by-uuid-D69EE0029EDFD957' not mounted


    Did you removed any drive?

    Thanks for the suggestion. I'm trying this now.


    No, I didn't remove any drive. It's referring to a USB external HDD formatting with NTFS that's still attached to the system.

    Quote from mh1983

    Here's my system kernel page, in case it helps:


    Using the PVE kernel means you were using openzfs 2.2.7, switching to the debian kernel means using openzfs version 2.1.11


    If you had performed a zpool upgrade on your zfs pool while using openzfs 2.2.7 the your zfs pool would not import on the previous openzfs version.


    While I've not been able to reproduce it myself there is a question mark over a possible bug in the openmediavault-zfs plugin and pve kernel 6.11. ( see: RE: ZFS delete from GUI / zfs plugin fails always )


    What's your situation now re: zfs pool access?

    Sadly, I switched to Debian 6.1.0.31-amd64 as per suggestion above and system is not booting into web GUI now (or if it is, it's taking a really long time).

    Reboot seems to be stalled /hanging after I switched the kernel. Not sure what to do next.

    Quote from mh1983

    Reboot seems to be stalled /hanging after I switched the kernel. Not sure what to do next.

    Do you have a monitor attached to see what is going on?

    Quote from mh1983

    Not at this time, I'm afraid, and it's bit tricky to do without ripping out the server and relocating it

    That makes it difficult to know where it's blocking.


    The idea is to try other boot options, to see if any other works.

    Quote from mh1983

    Sadly, I switched to Debian 6.1.0.31-amd64 as per suggestion above and system is not booting into web GUI now (or if it is, it's taking a really long time).

    That's a one sign that OMV systemd services are failing to mount filesystems during boot. But in this case it's possible the that zfs-dkms has kicked in. It should get there eventually. Report back when you have OMV running and then you can run some checks.

    Quote from Soma

    That makes it difficult to know where it's blocking.


    The idea is to try other boot options, to see if any other works.

    Sorry, but I wouldn't suggest that for the moment. Having a monitor attached would make no difference until you boot OMV without the "quiet" kernel boot param which suppress console messages at boot time.

    Quote from Krisbee

    Sorry, but I wouldn't suggest that for the moment

    Well, i'm out of my league with ZFS.

    Just thought maybe a different kernel would boot.


    I'll take a step back for now.

    Quote from Soma

    Well, i'm out of my league with ZFS.

    Just thought maybe a different kernel would boot.


    I'll take a step back for now.

    It's not that is such a bad idea, except (A) I'd like to assess what's happened under the pve kernel if possible, and (B) each time the OP boots into a another debian kernel their system could get bogged down with a lengthy kernel module build.

    Quote from Krisbee

    That's a one sign that OMV systemd services are failing to mount filesystems during boot. But in this case it's possible the that zfs-dkms has kicked in. It should get there eventually. Report back when you have OMV running and then you can run some checks.

    Will do. It seems to be back online now. And the zfs pool access status is the same as before: I'm unable to access.

Participate now!

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

Register Yourself Login