Front light blinking red and status Raid is degraded

[Glaven Clattuck]

Remove also the option missing (must be used only when you create a raid !)

Ok the we are

Code: Select all

[root@LaCie-5big ~]# mdadm --assemble --force --verbose /dev/md4 /dev/sdc2 /dev/sdb2  /dev/sdd2 /dev/sde2       
mdadm: looking for devices for /dev/md4
mdadm: /dev/sdc2 is identified as a member of /dev/md4, slot 1.
mdadm: /dev/sdb2 is identified as a member of /dev/md4, slot 3.
mdadm: /dev/sdd2 is identified as a member of /dev/md4, slot 2.
mdadm: /dev/sde2 is identified as a member of /dev/md4, slot 4.
mdadm: forcing event count in /dev/sdc2(1) from 2758623 upto 2758626
mdadm: no uptodate device for slot 0 of /dev/md4
mdadm: added /dev/sdd2 to /dev/md4 as 2
mdadm: added /dev/sdb2 to /dev/md4 as 3
mdadm: added /dev/sde2 to /dev/md4 as 4
mdadm: added /dev/sdc2 to /dev/md4 as 1
mdadm: /dev/md4 has been started with 4 drives (out of 5).


Code: Select all

[root@LaCie-5big ~]# cat /proc/mdstat                                                                   
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md4 : active raid5 sdc2[1](F) sde2[4] sdb2[2] sdd2[3]
      15619969024 blocks super 1.0 level 5, 64k chunk, algorithm 2 [5/3] [__UUU]
     
md3 : active raid1 sda5[0] sde5[1] sdc5[4] sdb5[3] sdd5[2]
      255936 blocks [5/5] [UUUUU]
     
md2 : active raid1 sda9[0] sde9[1] sdb9[4] sdc9[3] sdd9[2]
      875456 blocks [5/5] [UUUUU]
     
md1 : active raid1 sda8[0] sdb8[4] sdc8[3] sdd8[2] sde8[1]
      843328 blocks [5/5] [UUUUU]
     
md0 : active raid1 sde7[4] sdd7[3] sdc7[2] sdb7[1] sda7[0]
      16000 blocks [5/5] [UUUUU]
     
unused devices: <none>


[Jocko]

So sdc2 has a failure status.

Then stop the nas and restart it with the original disk (sda) but without sdc (middle disk).
Post the mdstat output.

[Glaven Clattuck]

So sdc2 has a failure status.

Then stop the nas and restart it with the original disk (sda) but without sdc (middle disk).
Post the mdstat output.

done

Code: Select all

[root@LaCie-5big ~]# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md4 : active raid5 sda2[0] sde2[4] sdb2[2] sdd2[3]
      15619969024 blocks super 1.0 level 5, 64k chunk, algorithm 2 [5/4] [U_UUU]
     
md3 : active raid1 sda5[0] sde5[1] sdb5[3] sdd5[2]
      255936 blocks [5/4] [UUUU_]
     
md2 : active raid1 sda9[0] sde9[1] sdb9[4] sdd9[2]
      875456 blocks [5/4] [UUU_U]
     
md1 : active raid1 sda8[0] sdb8[4] sdd8[2] sde8[1]
      843328 blocks [5/4] [UUU_U]
     
md0 : active raid1 sde7[2] sdd7[3] sdb7[1] sda7[0]
      16000 blocks [5/4] [UUUU_]
     
unused devices: <none>


Can i insert a new disk on middle position (slot n.3) and start the rebuild process?

obviously since I only have a new HD and I had cloned it with sda, I format it first and then insert it on slot 3.
Is it ok for you?

[Jocko]

No you can not do it directly as it is a cloned disk (sda2) and it will be rejected (detected as a raid member)

Then do an hot plug, wait around one minute to bring up it by the firmware (you can check that by running dmesg command) and run

Code: Select all

mdadm --zero-superblock /dev/sdc2
mdadm --manage /dev/md4 --add /dev/sdc2

Check all is ok

Code: Select all

cat /proc/mdstat
mdadm --detail /dev/md4

[Glaven Clattuck]

It's started

Code: Select all

[root@LaCie-5big ~]# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md4 : active raid5 sdc2[5] sda2[0] sde2[4] sdb2[2] sdd2[3]
      15619969024 blocks super 1.0 level 5, 64k chunk, algorithm 2 [5/4] [U_UUU]
      [>....................]  recovery =  0.4% (15749888/3904992256) finish=1252.9min speed=51732K/sec
     
md3 : active raid1 sda5[0] sde5[1] sdb5[3] sdd5[2]
      255936 blocks [5/4] [UUUU_]
     
md2 : active raid1 sda9[0] sde9[1] sdb9[4] sdd9[2]
      875456 blocks [5/4] [UUU_U]
     
md1 : active raid1 sda8[0] sdb8[4] sdd8[2] sde8[1]
      843328 blocks [5/4] [UUU_U]
     
md0 : active raid1 sde7[2] sdd7[3] sdb7[1] sda7[0]
      16000 blocks [5/4] [UUUU_]
     
unused devices: <none>


Code: Select all

[root@LaCie-5big ~]# mdadm --detail /dev/md4               
/dev/md4:
        Version : 1.0
  Creation Time : Tue Oct 28 21:06:48 2014
     Raid Level : raid5
     Array Size : 15619969024 (14896.36 GiB 15994.85 GB)
  Used Dev Size : 3904992256 (3724.09 GiB 3998.71 GB)
   Raid Devices : 5
  Total Devices : 5
    Persistence : Superblock is persistent

    Update Time : Thu Aug  3 20:45:46 2023
          State : clean, degraded, recovering
 Active Devices : 4
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 1

         Layout : left-symmetric
     Chunk Size : 64K

 Rebuild Status : 0% complete

           Name : (none):4
           UUID : ad468f58:53571e53:74558f1d:48545ec5
         Events : 2758718

    Number   Major   Minor   RaidDevice State
       0       8       18        0      active sync   /dev/sda2
       5       8       66        1      spare rebuilding   /dev/sdc2
       3       8       50        2      active sync   /dev/sdd2
       2       8        2        3      active sync   /dev/sdb2
       4       8       34        4      active sync   /dev/sde2


wait and hope

[Jocko]

Nice !

Indeed just waiting now ... :dry

[Glaven Clattuck]

however I first formatted the clone HD and to speed up the rebuild time I entered this command

echo "20000" > /proc/sys/dev/raid/speed_limit_min

normally this parameter is set to 1000 as a minimum and 200,000 as a maximum.
Reading around, changing the minimum parameter to 20,000 improves performance without running into danger.
The maximum should not be touched.

And in fact the estimated time to finish the reconstruction has been reduced.

cross finger

[Jocko]

:thumbup
Yes we use a similar trick on our firmware.

[Glaven Clattuck]

No way.
The rebuild operation is not successful, after so many hours it stops and as before, reports sdc2 as faulty.
I tried to start it again, but once again (this time much earlier) it stopped

[Jocko]

:fists
That means there is another faulty disk ! if you do not reboot the nas,it should have some information in dmesg output. So post:

Code: Select all

dmesg

Check if smartctl command is available with lacie firmware

Code: Select all

which smartctl