/srv/dev- ... is not a mountpoint. RAID1 not mountable? Dataloss? Help...

  • After upgrading and rebooting my RAID 1 stopped working. I got "Software Failure" after clicking on Storage. The command line tells me the group descriptors are corrupted, but the syslog shows some mismatch with the mountpoint. I don't understand if my Raid is gone or whats the problem. Can't access the Raid via smb,


    OMV6 on Proxmox with harddrive passthrough since 5 years...


    Some informations:


    Terminal:


    /etc/fstab:



    Code: cat /proc/mdstat
    cat /proc/mdstat
    Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] 
    md0 : active raid1 sdc[1] sdb[0]
          3906886464 blocks super 1.2 [2/2] [UU]
          bitmap: 0/30 pages [0KB], 65536KB chunk
    Code: mdadm --examine --brief --scan
    mdadm --examine --brief --scan
    ARRAY /dev/md/RedRaid  metadata=1.2 UUID=cd3cf365:95c40760:74b080e1:9ede0634 name=omv.local:RedRaid
    Code: blkid
    blkid
    /dev/sdc: UUID="cd3cf365-95c4-0760-74b0-80e19ede0634" UUID_SUB="44aa5744-4c01-7163-e93a-3a02560eb36c" LABEL="omv.local:RedRaid" TYPE="linux_raid_member"
    /dev/sdb: UUID="cd3cf365-95c4-0760-74b0-80e19ede0634" UUID_SUB="3169127b-6147-0151-4643-72425592e250" LABEL="omv.local:RedRaid" TYPE="linux_raid_member"
    /dev/sda1: UUID="91512fa9-66a6-4e0c-966f-ee484cf7882d" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="9cebf7d0-01"
    /dev/sda5: UUID="44aa4dfd-e989-4162-aa49-b4c7390b1107" TYPE="swap" PARTUUID="9cebf7d0-05"
    /dev/md0: LABEL="RedRaid" UUID="297ce47a-fa80-41f7-a8ff-f5662b8676aa" BLOCK_SIZE="4096" TYPE="ext4"
    /dev/sdd2: SEC_TYPE="msdos" UUID="78C8-F588" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI boot partition" PARTUUID="c4b7b64c-96b4-4b94-84a9-bb80b6ef09de"
    /dev/sdd3: BLOCK_SIZE="2048" LABEL="PVE" TYPE="hfsplus" PARTLABEL="HFSPLUS" PARTUUID="c4b7b64c-96b4-4b94-84a8-bb80b6ef09de"
    /dev/sdd1: PARTLABEL="Gap0" PARTUUID="c4b7b64c-96b4-4b94-84aa-bb80b6ef09de"
    /dev/sdd4: PARTLABEL="Gap1" PARTUUID="c4b7b64c-96b4-4b94-84af-bb80b6ef09de"
    Code: Syslog
    Sep  3 21:38:34 omv monit[895]: Filesystem '/srv/dev-disk-by-id-md-name-omv.local-RedRaid' not mounted
    Sep  3 21:38:34 omv monit[895]: 'filesystem_srv_dev-disk-by-id-md-name-omv.local-RedRaid' unable to read filesystem '/srv/dev-disk-by-id-md-name-omv.local-RedRaid' state
    Sep  3 21:38:34 omv monit[895]: 'filesystem_srv_dev-disk-by-id-md-name-omv.local-RedRaid' trying to restart
    Sep  3 21:38:34 omv monit[895]: 'mountpoint_srv_dev-disk-by-id-md-name-omv.local-RedRaid' status failed (1) -- /srv/dev-disk-by-id-md-name-omv.local-RedRaid is not a mountpoint


    • Offizieller Beitrag

    The array looks fine. What is the output of: sudo mount -a

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.2


    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!

    • Offizieller Beitrag

    sudo fsck.ext4 /dev/md0

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.2


    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!

    • Offizieller Beitrag

    Is it safe to do this without losing data?

    Hard to say if it is safe. You are definitely losing data. Just don't know what file that inode affects. On the other hand, it needs to be fixed. This is why backup is important. If you want to fix the filesystem, you should clear it.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.2


    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, it worked and data is still in place. Don't know if any files corrupted, but at least I can access them.


    One question: Is it possible for OMV to check (e.g. with fsck) a filesystem before it is mounted and the RAID tries to selfcheck?

    • Offizieller Beitrag

    Is it possible for OMV to check (e.g. with fsck) a filesystem before it is mounted and the RAID tries to selfcheck?

    Linux will do a filesystem check after so many times being mounted. You can unmount the filesystem and check it manually too.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.2


    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!

  • Niclas

    Hat das Label gelöst hinzugefügt.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!