File System Shows Unavailable and Not Mounted, but Online. Possible mount point failure

1st Official Post

    I am a linux novice so seeking help. I have a RAID 5 with 3 devices


    My file system is now showing online, but not mounted or available.



    The command line is showing group descriptors corrupted.


    I'm trying to resolve this and save my raid so I can view my files within the raid.


    Unsure what commands to run, if there is an auto fix.

  • votdev

    Approved the thread.

  • Falken1975

    Added the Label OMV 7.x

    I had to reinstall version 7 and then started having these errors, which resulted in not being able to view the shares in SMB or MiniDLA. The raid structure is several years old.

    Quote from Falken1975

    Any suggestions or something else that I could provide to help solve? Really need a solution.

    I don't use RAID but you can start by reading this:
    Degraded or missing raid array questions - RAID - openmediavault


    The usual advice here is to NOT use RAID unless you really know how to use it and/or recover it.

    Since you have it already, try to get the RAID working and make a full backup ASAP.

    Falken1975 Your first two screen shots + console messages re: "group descriptor corruption" show your MD RAID layer is healthy, but the EXT4 filesystem on the RAID is corrupted. The output of "findmnt" you posted shows filesystem on the MD RAID device "/dev/md0" has failed to mount, hence the filesystem is "missing" in the WebUI.


    I would double check the S.M.A.R.T states of the three drives in the array for any underlying disk faults. Running fsck on the corrupted EXT4 filesytem may or may not fix things, so be prepared to restore you data from a backup. If you don't have backups be prepared for data loss.

    Output of blkid:


    root@server-nas1:~# blkid

    /dev/sdd: UUID="8fa7f605-65ad-d874-b64b-39886f6f99d0" UUID_SUB="e4e2d02c-8a89-9458-e40c-269611d12d16" LABEL="NAS:VeridianRaid" TYPE="linux_raid_member"

    /dev/md127: LABEL="RaidFileSystem" UUID="7548a815-427e-45ec-9120-ad3e9fb5cff5" BLOCK_SIZE="4096" TYPE="ext4"

    /dev/sdb: UUID="8fa7f605-65ad-d874-b64b-39886f6f99d0" UUID_SUB="7acf759e-e8b2-ef1c-1951-1f70c11f1d20" LABEL="NAS:VeridianRaid" TYPE="linux_raid_member"

    /dev/sdc2: UUID="4f3f0a29-f9ef-4f42-a89a-12a583fe29c8" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="322e25e1-6453-462d-a10e-0c777706ac08"

    /dev/sdc3: UUID="3c2f017f-21b3-4937-bcf3-e9b453b6aba7" TYPE="swap" PARTUUID="d891083f-abeb-4359-97fd-85d0d70aacfb"

    /dev/sdc1: UUID="C142-7519" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="1c5c87db-c845-4902-8e8c-9607383ab69a"

    /dev/sda: UUID="8fa7f605-65ad-d874-b64b-39886f6f99d0" UUID_SUB="bf99b275-1a73-6c29-aae2-f5ac3ced2f02" LABEL="NAS:VeridianRaid" TYPE="linux_raid_member"



    Output of mount:


    root@server-nas1:~# mount

    sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)

    proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)

    udev on /dev type devtmpfs (rw,nosuid,relatime,size=3979944k,nr_inodes=994986,mode=755,inode64)

    devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)

    tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=801664k,mode=755,inode64)

    /dev/sdc2 on / type ext4 (rw,relatime,errors=remount-ro)

    securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)

    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)

    tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)

    cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)

    pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)

    efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)

    bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)

    systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=15291)

    hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)

    mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)

    debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)

    tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)

    configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)

    fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)

    ramfs on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)

    ramfs on /run/credentials/systemd-sysctl.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)

    ramfs on /run/credentials/systemd-tmpfiles-setup-dev.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)

    tmpfs on /tmp type tmpfs (rw,relatime,inode64)

    /dev/sdc1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)

    ramfs on /run/credentials/systemd-tmpfiles-setup.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)

    binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)

    sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)

    Output of fsck:


    root@server-nas1:~# fsck

    fsck from util-linux 2.38.1

    e2fsck 1.47.1-rc2 (01-May-2024)

    /dev/sdc2 is mounted.

    e2fsck: Cannot continue, aborting.

    You could run e2fsck -v /dev/md0 In this interactive mode you should get warnings if answering "yes" to any question would be dangerous to the filesystem and so you can then bail out of the check.


    I can only repeat that running a check on a corrupted EXT4 filesystem may or may not fix things, so be prepared to restore you data from a backup. If you don't have backups be prepared for data loss.

    Response when running e2fsck -v /dev/md0


    root@server-nas1:~# e2fsck -v /dev/md0

    e2fsck 1.47.1-rc2 (01-May-2024)

    e2fsck: No such file or directory while trying to open /dev/md0

    Possibly non-existent device?

    I ran the check and it worked. I did lose some info in a shared folder, but I can live with it. I do have a backup, but is some what outdated. Thanks all for the assistance.

  • Falken1975

    Added the Label resolved

Participate now!

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

Register Yourself Login