Beiträge von QPlus7

    It means the array isn't start and assembled. Even if the array was showing up there, you created a new array and your data is gone (although maybe recovered by photorec).

    Given my current state of affairs, if I wanted to try PhotoRec should I create the array again and wait for it to finish resynching?


    cat /proc/mdstat shows nothing at all as of right now.

    Code
    root@omv:~# blkid
    /dev/sda1: PARTUUID="501ac000-c1cf-45db-999b-185ed0acd703"
    /dev/sdc1: PARTUUID="5626b318-e9f3-4deb-a216-01bbf4260cc7"
    /dev/sdb1: PARTUUID="b34a2f99-0f8b-4882-9c33-9dc301a5a0ca"
    /dev/sdd1: PARTUUID="78476d9c-d1ce-4e93-b280-11eb8eb18cd9"
    /dev/sde1: PARTUUID="853258a8-49b8-4e51-a049-0ca28e0d0182"
    /dev/sdf1: UUID="e1cc774b-91da-4293-b459-d1c6e5ae6a2e" TYPE="ext4" PARTUUID="7ca6db92-01"
    /dev/sdf5: UUID="e4068c38-130b-4afc-94b6-8413cc16b93d" TYPE="swap" PARTUUID="7ca6db92-05"


    I'm guessing this means, without a doubt, that my array is gone. <X<X<X

    Let me preface this by saying that I've been running OMV for about 2 years with a single R5 and NEVER had any problems.


    Within the last month, I've had 2 major issues when adding drives to an existing array. Onne (Raid5 Missing, File System Missing) forced me to build a new array on a clean OMV 3 install. For the past 2 years, I've been running OMV 2.


    After I built the new array I backed it up to an external drive and to B2(or at least some of the data to B2 - I'm still not 100% sure all the data copied over but that is a different story!.


    I moved (not copied) from the external back to the new array and all was great! I then went to add a new drive so I powered off the machine, plugged in the drive, powered it back on --- no array!


    I revisited the thread up top and tried to follow some of the same steps, only this time I created a new array. The new array started to resync right away so I felt pretty good thinking the data would come back. It completed and after about 2 hours, the first time, I was unable to mount the filesystem (did I overwrite it when I created the new array?). I did not touch anything with the filesystem in OMV. As a matter of fact, the original one still shows up in the GUI as "missing".


    I rebooted the machine at this point thinking it might let me mount the fs after a clean reboot - array is gone, again! I went through the same process and waited another 2 hours. Again, never touching the filesystem. Same thing.


    At this point, I started recovering data from my external drive to yet another external drive. I was able to recover some data, but I can tell its not all there. I'm about to start downloading data from B2 but that will be slow and expensive but whatever. I just want my data back!


    What am I doing wrong with OMV and arrays -- is my data gone after I created the new array?


    Thanks in advance!

    Well, I did just that. Once I added the new drive and added it to the array it started to resync. Once the resync finished it started to recover. After about 18 hours total, my array is now online and I have access to all my data!


    First order of business, transfer everything to backblaze and a 6TB drive!


    After that, I'll start my research into other alternatives.


    Hope this helps someone in the future!

    Ok, maybe it wasn't my last post - sorry. Just thought of something...


    Is it possible that the reshaping never finished [Reshape pos'n : 577431040 (550.68 GiB 591.29 GB)]? I'm thinking if I power down, plug in the 6th drive, boot the machine, stop md127, and then run mdadm --assemble --force /dev/md127 /dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sde that might do the trick?

    This is probably my latest update for the night as I think I've made progress and the array might be reshaping right now.


    I removed the 6th disk I added and ran the following:



    Following that, I did this:

    Code
    mkdir -p /mnt/md127
    
    
    mount /dev/md127 /mnt/md127


    At this point my console just has a blinking cursor as if it was doing something.


    I logged in to another session and ran cat /proc/mdstat but get the blinking cursor again.


    Before I tried to mount the array, I saw it mounted in the GUI when I clicked on RAID Management and it showed "clean,degraded".


    After I mounted it, I get "Loading..." when I click on RAID Management and File System.


    I'm hoping the array is reshaping and will just take some time but I'm not sure how I can confirm that other than just waiting it out.


    Attached is the latest dmesg.

    I bought a new 1TB drive and put it in along with the original drives and the previously "new" drive that was in. This info is from that setup:



    I think my array is still in tact. I'm a bit confused on the naming though: is it /dev/md0, /dev/md127, or /dev/R5Array?


    At this point, I'm getting desperate. I'm willing to work with someone remotely and pay for their time.

    That is not a good sign that cat /proc/mdstat doesn't return anything. You will through the right steps to fix it. Sounds like the system isn't stable or a drive is failing. Anything in dmesg?


    I would ask yourself two questions:
    1 - Do you really need raid? Raid isn't backup and there are other ways to pool drives.
    2 - Can you back up the array? Raid isn't backup.

    Thanks for the reply!


    1) Going forward, I don't care what the pooling method is but for now I need to recover the array/data if possible
    2) I'm aware a RAID doesn't provide backups but I was in the process of consolidating everything so I could take a backup. At this point, I have none, unfortunately.


    I've made some progress in troubleshooting, I think.


    I put the 2 drives that were in after I expanded and reshaped the array. The following information is with these 2 drives in:


    I restarted the box and went through the process in post #2. I now see the array in the GUI and the file system shows unmounted.


    If I click mount, how long should it take? I tried it again and it locks up and "cat /proc/mdstat" doesn't show anything and clicking on RAID Management or File System in the GUI shows a loading button and nothing else.


    What would be the best way to proceed from here?

    Well, a little more digging and I came up with this:


    Code
    root@omv:/# mdadm --stop /dev/md127
    mdadm: stopped /dev/md127


    Code
    root@omv:/# mdadm --assemble --force --verbose /dev/md0 /dev/sd[abcdef]
    mdadm: looking for devices for /dev/md0
    mdadm: no RAID superblock on /dev/sdc
    mdadm: /dev/sdc has no superblock - assembly aborted



    My array showed up and I tried to mount the file system. The system has now locked up and cat /proc/mdstat doesn't return anything.


    I'm going to leave it overnight and check it again the morning.

    Hello, all.


    I added a new drive (6 x 1Tb total drives now), expanded my array and then resized the file system. I lost network connectivity during the resize and had to reboot. Now it appears I've lost my array. Below is the output based on ryecoaaron request in his sticky thread:


    Code
    root@omv:~# cat /proc/mdstat
    Personalities : [raid6] [raid5] [raid4]
    md127 : inactive sdd[0] sdb[5] sda[3] sdf[2] sde[1]
    4883157560 blocks super 1.2
    
    
    unused devices: <none>


    Code
    root@omv:~# blkid
    /dev/sdd: UUID="c628d2a9-0132-5816-afb8-3a2e73031b40" UUID_SUB="e072462a-09bb-7769-b0cd-88f58f9bb5ca" LABEL="omv:R5Array" TYPE="linux_raid_member"
    /dev/sdb: UUID="c628d2a9-0132-5816-afb8-3a2e73031b40" UUID_SUB="b0bd798e-80b4-db90-4e35-5d832793fe30" LABEL="omv:R5Array" TYPE="linux_raid_member"
    /dev/sde: UUID="c628d2a9-0132-5816-afb8-3a2e73031b40" UUID_SUB="ea552547-e7ab-f516-5b71-5b6a5234da89" LABEL="omv:R5Array" TYPE="linux_raid_member"
    /dev/sdg1: UUID="1d42ce8e-7dca-4183-8723-926eafc7c182" TYPE="ext4"
    /dev/sdg5: UUID="7bbc0b57-05ef-4b1b-8d19-2e1a6c71d8b5" TYPE="swap"
    /dev/sdf: UUID="c628d2a9-0132-5816-afb8-3a2e73031b40" UUID_SUB="bbf79cbf-98e4-2acb-37f9-2301d9fe9c1d" LABEL="omv:R5Array" TYPE="linux_raid_member"
    /dev/sda: UUID="c628d2a9-0132-5816-afb8-3a2e73031b40" UUID_SUB="f092b520-1794-41f6-5ca7-33251544ddd9" LABEL="omv:R5Array" TYPE="linux_raid_member"




    Code
    root@omv:~# mdadm --detail --scan --verbose
    mdadm: cannot open /dev/md/R5Array: No such file or directory


    I've rebooted a few times but do not see the array in the GUI. See attachments for more details on Physical Disks, Raid Management, and File System screenshots.





    Any help is GREATLY appreciated.