Raid Vanished

  • Hi, please forgive my english skills.
    I'm a newb and install an OMV home serveur with raid 5 (if I remember correctly)


    Yesterday I cut my Home Power Supply so the server shut down, when i turned it on once again, the boot messages was full of errors.


    One of them was:
    fsck.ext4: Unable to resolve 'UUID=0ba8ff35-ff8e-4416-8186-855a63544040'
    fsck died with exit status 8


    On my omv config page I have no more Raid listed, I still have my 3 physicall disks used to create the raid, and in my filesystem I have 1 filesystem listed, mounted, with status missing, and n/a to all other boxes.


    I tryed a fews things, more or less at random since I dind't know anything...
    for example:
    root@openmediavault:/media/0ba8ff35-ff8e-4416-8186-855a63544040# blkid
    /dev/sda1: UUID="0280a620-000a-47d3-8c3d-ed2d4f4d7e5a" TYPE="ext4"
    /dev/sda5: UUID="17dcbb16-973e-45e7-9d4b-3a014d5db305" TYPE="swap"
    /dev/sdb: UUID="b13d39a1-c47f-92d8-adbf-2a4e05ad6a85" LABEL="openmediavault:serveur" TYPE="linux_raid_member"
    /dev/sdd: UUID="b13d39a1-c47f-92d8-adbf-2a4e05ad6a85" LABEL="openmediavault:serveur" TYPE="linux_raid_member"
    /dev/sdc: UUID="b13d39a1-c47f-92d8-adbf-2a4e05ad6a85" LABEL="openmediavault:serveur" TYPE="linux_raid_member"


    I don't know what to look at or where to look at, I even don't know if I'm in the correcte subsection of the forum, my goal is to getmy files back from this raid since (of course...) I didn't have any back up of thoses files...
    If anybody as a clue, it will really help.
    I can provide any information you need if you asked.
    Best regards.

    • Offizieller Beitrag

    What is the output of: cat /proc/mdstat

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    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!

  • Zitat von "ryecoaaron"

    What is the output of: cat /proc/mdstat


    Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
    md0 : inactive sdb[0](S) sdc[2](S) sdd[1](S)
    8790796680 blocks super 1.2


    unused devices: <none>



    Thanks for your help.

    • Offizieller Beitrag

    Try:

    Code
    mdadm --stop /dev/md0
    mdadm --remove /dev/md0
    
    
    mdadm --assemble --run --force /dev/md0 /dev/sd[bcd]

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    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!

  • Zitat von "ryecoaaron"

    Try:

    Code
    mdadm --stop /dev/md0
    mdadm --remove /dev/md0
    
    
    mdadm --assemble --run --force /dev/md0 /dev/sd[bcd]



    Whow; it seems to start doing something in the right direction.



    In my omv gui I see my raid listed as clean/degraded, I still can't access my shared folder with other computer but it's a huge improvement.
    Yesterday on a French forum I tryed some things because of advices and remove one line in a mdadm conf because it was redondant as I was told. I don't know if that could explain the error opening /dev/md0.
    By the way, your avatar seems really appropriate :)

    • Offizieller Beitrag

    Post the output of cat /proc/mdstat now. It should be rebuilding even though one of your drives did not make it back into the array. You may have to zero the superblock on that drive.


    Little bit of Star Wars fan here :)

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    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!

  • here is the report:


    root@openmediavault:~# cat /proc/mdstat
    Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
    md0 : active (auto-read-only) raid5 sdb[0] sdc[2]
    5860530176 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [U_U]


    unused devices: <none>



    I'm a fan of R2D2 opening gates, reparing engines, pushing back aliens...
    I was just looking about translation of the star wars card game :)

    • Offizieller Beitrag

    Now add the missing drive back in:

    Code
    mdadm --zero-superblock /dev/sdd
    mdadm --add /dev/md0 /dev/sdd

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    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!

  • Zitat von "ryecoaaron"

    Now add the missing drive back in:

    Code
    mdadm --zero-superblock /dev/sdd
    mdadm --add /dev/md0 /dev/sdd



    Thanks I pasted the 2 lines at once, after that I try to copy paste one line after another, but I got some errors, I assumed the system proceeded the 2 commands the first time.The drive is added


    In my gui my raid is clean/degrade/recovering ()
    I don't have any %, I assume I must let it like that and don't click the "recover" tab.


    Thanks for helping.

    • Offizieller Beitrag

    Hope it works. You can check on progress with cat /proc/mdstat
    No need to click recover.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    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!

  • Zitat von "ryecoaaron"

    Hope it works. You can check on progress with cat /proc/mdstat
    No need to click recover.


    I track the % with the "detail" folder on the gui, it seems to work (6%)
    I assume once it's repaired I have to mounted it, or it will be mounted by itself?


    Anyway, if I have your postal adress I'll sent you a little something for your help.


    Thanks a lot R2 ;)

    • Offizieller Beitrag
    Zitat von "boudje"

    I track the % with the "detail" folder on the gui, it seems to work (6%)
    I assume once it's repaired I have to mounted it, or it will be mounted by itself?


    I think you have to mount it. I don't remember :)


    Zitat von "boudje"

    Anyway, if I have your postal adress I'll sent you a little something for your help.


    I appreciate the offer but no need :)

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    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!

  • Zitat von "ryecoaaron"


    I think you have to mount it. I don't remember :)



    I appreciate the offer but no need :)



    I'll go to bed, it's full night in France.


    I'll look at that raid tomorrow.


    I'll probably sleep a lot well than last night thanks to you. ;)

  • Bad news this morning:


    root@openmediavault:~# cat /proc/mdstat
    Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
    md0 : active raid5 sdd[3](S) sdb[0] sdc[2](F)
    5860530176 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/1] [U__]


    unused devices: <none>


    In my GUI the raid is listed as "failed"

    • Offizieller Beitrag

    That's bad. In the Messages log under System Logs, do you see any errors?

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    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!

  • I have pages of errors, many errors from type Buffer I/O errors on mdO
    Errors type /usr/sbin/cron mkgraph, etc


    I don't know how to provide you complete listing of errors and if you need it...

    • Offizieller Beitrag

    Unfortunately, if there are errors in that log, it usually is a bad sign and the hard drive might be going bad. It is still possible that it is a driver issue. What type of drives and motherboard are you using?

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    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!

  • Zitat von "ryecoaaron"

    Unfortunately, if there are errors in that log, it usually is a bad sign and the hard drive might be going bad. It is still possible that it is a driver issue. What type of drives and motherboard are you using?


    I use WD green 3TO and a G41M from MSI


    May be a HDD has some problems, I don't know how to test them.

  • I tryed a few software to recover data, and thoses softwares seems to find some datas: my img seems to be there, the software seems to find some folders, but I can't explore them.
    Moreover, the software can't recover various other kinds of files.
    It seems that my data are still on the drives, is there a way to explore those drives using a software or building the raid in a console? My filesystem is listed as missing once again in the OMV window.


    I don't care if I have to buy new disk to restore my datas or buy a software...

    • Offizieller Beitrag

    A new drive might help but you need to get two of those drives working in a raid 5 array again. I would boot systemrescuecd so you have the latest utilites and try the commands earlier in this thread again. Otherwise, you may need to take the drives to a data recovery place.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    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!

Jetzt mitmachen!

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