RAID clean,degraded and the first hd is now as "spare" one...

carmalao · Oct 31st 2022

On md0 I don't have enough space. The md0 has 2 WD RED 3tb, and the md1 has 2 WD RED 1tb.

I'll try tomorrow the solution and let you know. Thanks.

carmalao · Oct 31st 2022

OK, so:

Code

root@nas:~# mdadm --fail /dev/md1 /dev/sdc
mdadm: set /dev/sdc faulty in /dev/md1
root@nas:~# mdadm --remove /dev/md1 /dev/sdc
mdadm: hot removed /dev/sdc from /dev/md1

Then I wipe it out with OMV (in Storage, Disks).

Then I gave the add command and:

Code

root@nas:~# mdadm --add /dev/sdc /dev/md1
mdadm: /dev/sdc does not appear to be an md device

Ideas?

carmalao · Oct 31st 2022

NEWS: I used OMV to "repair" the array, and it proposed me to add the sdc disk and so now it added it and it is recovering... waiting for new news.

carmalao · Oct 31st 2022

And here are the news (I'm still laughing):

Code

    Version : 1.2
     Creation Time : Sat Dec 17 16:44:54 2016
        Raid Level : raid1
        Array Size : 976631360 (931.39 GiB 1000.07 GB)
     Used Dev Size : 976631360 (931.39 GiB 1000.07 GB)
      Raid Devices : 2
     Total Devices : 2
       Persistence : Superblock is persistent

       Update Time : Mon Oct 31 20:09:21 2022
             State : clean, degraded
    Active Devices : 1
   Working Devices : 2
    Failed Devices : 0
     Spare Devices : 1

Consistency Policy : resync

              Name : NAS:1
              UUID : be21a281:1f0e7f6d:4580c9f1:96b04695
            Events : 3668609

    Number   Major   Minor   RaidDevice State
       -       0        0        0      removed
       1       8       64        1      active sync   /dev/sde

       2       8       32        -      spare   /dev/sdc

Display More

So, I'm at the start point!

geaves · Oct 31st 2022

Quote from carmalao

mdadm --add /dev/sdc /dev/md1

That's the wrong way round remember post 5

Quote from carmalao

So, I'm at the start point!

Yes but no, the problem was with the wipe, I bet you chose quick/short, if you did the you'll have to do this again

Fail and remove the drive from the array, then do a secure wipe, this will take some time, then rather than from the cli, from the WebUI -> Raid Management, select the array and then recover a dialog should display with the secure wiped drive, select it and click OK

carmalao · Nov 1st 2022

Yes you have the reason. I made in that way... short way. I'll do as you wrote now. Just a moment.

****

18.06.... 3%... how long will it take for 1tb? For sure I will have to stop it. Is it safe to stop it?

****

18.21 I stopped it and redo all as the last time, I cannot go on with this loooooong wipe (67 hours remaining...). I will go on on the next weekend.

geaves · Nov 1st 2022

Try adding the drive anyway even though you stopped it, another user did this after only 1% and it worked, no idea why.

Quote from carmalao

I cannot go on with this loooooong wipe (67 hours remaining...)

what's powering it a mouse in a wheel, that's ridiculous for a 1TB drive

carmalao · Nov 2nd 2022

My mouse was tyred also... so I stopped and add the drive, nothing changed: it's as spare.

I'm looking for new drives. Or maybe I will change the others of other array into 4tb and so I'll cancel the array md1.

Thanks

Participate now!