HELP 48tb raid wont show up anymore

1st Official Post

    i have OMV 6, its been running fine for the last year, today my 48 tb raid is missing, it shows the directory as still there, but all the data is missing, and it doesn't show up i the raid anymore.


    I don't know what happened, or what to do about it.


    Raid Page


    File System


    Shared Folders

    • Official Post
    Thread
    Degraded or missing raid array questions
    If you have a degraded or missing raid array, please post the following info (in code boxes) with your question.

    Login as root locally or via ssh - Windows users can use putty:

    • cat /proc/mdstat
    • blkid
    • fdisk -l | grep "Disk "
    • cat /etc/mdadm/mdadm.conf
    • mdadm --detail --scan --verbose
    • Post type of drives and quantity being used as well.
    • Post what happened for the array to stop working? Reboot? Power loss?
    ryecoaaron

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


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


    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!



    Code
    root@OpenMediaVult:~# mdadm --detail --scan --verbose
mdadm: Unknown keyword INACTIVE-ARRAY
ARRAY /dev/md3 level=raid0 num-devices=2 metadata=1.2 name=2x4tb3 UUID=b7967fed:0172a102:2d7f5a7f:3b3c8615
devices=/dev/sda,/dev/sdd
ARRAY /dev/md2 level=raid0 num-devices=2 metadata=1.2 name=2x4tb2 UUID=f65108e0:9ef74a7a:bd4890f4:3b434279
devices=/dev/sdb,/dev/sde
ARRAY /dev/md1 level=raid0 num-devices=2 metadata=1.2 name=2x4tb1 UUID=2780e0b3:f8cdaf72:56e420c5:d9d08183
devices=/dev/sdf,/dev/sdm
INACTIVE-ARRAY /dev/md5 num-devices=7 metadata=1.2 name=Archive UUID=4ae4e034:54c4c2cd:8a9132af:c5db2629
devices=/dev/md1,/dev/md2,/dev/md3,/dev/sdh,/dev/sdi,/dev/sdj,/dev/sdk


    for the raid in question it was a mix of drives, but it was 8x 8tb drives setup in raid 10.

    most of them would have been Seagate BarraCuda ST8000DM004 8TB 5400 RPM 256MB Cache SATA 6.0Gb/s 3.5" Internal Hard Drive Bare Drive - OEM



    The only thing i did before this all went crashing down was mess with a network setting. I use ethtools to tell it to change from a network speed of 100mb/s to 1000mb/s to see if it would allow faster upload. (foolish i know was curious what would happen) then everything broke.

    • Official Post

    Did you really create three raid 0 arrays to create three "drives" big enough to put in your raid 10 array along with five real drives?

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


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


    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!

    • Official Post
    Quote from tookys

    yes, i needed everything to be 8tb to work, and i was wanting to take advantage of the drives i could.

    While it is possible to do this, I would never tell someone to create an array like that. Why do you need raid?


    You can try:

    mdadm --stop /dev/md5

    mdadm --assemble --force --verbose /dev/md5 /dev/md[123] /dev/sd[hijkl]

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


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


    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!

    Code
    root@OpenMediaVult:~# mdadm --assemble --force --verbose /dev/md5 /dev/md1 /dev/md2 /dev/md3 /dev/sdh /dev/sdi /dev/sdj /dev/sdk /dev/sdl
mdadm: Unknown keyword INACTIVE-ARRAY
mdadm: looking for devices for /dev/md5
mdadm: No super block found on /dev/sdl (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sdl
mdadm: /dev/sdl has no superblock - assembly aborted

    did i enter the code right?



    [EDIT]

    nvm, i did it wrong , looks like it worked

    • Official Post
    Quote from tookys

    did i enter the code right?

    If you would've cut and paste, it would have done the same thing as what you expanded it to.


    Quote from tookys

    did it wrong , looks like it worked

    Something seems to be wrong with sdl. So, it did assemble but you have a degraded array.

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


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


    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!

Participate now!

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

Register Yourself Login