NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS Ultra 4 - The array is still in degraded mode
Hello just added two new 4 TB drive to my Ultra4; first drive loaded and sync correctly however after installing, test and sync the 2nd I'm now in Unprotected mode with the following messge: "RAID s...
dlavineway wrote:
I've tried posting the mdstat.log contents multiple time unfortunatly the post keeps disappearing, trying it as an attachment
Likely just caught in the spam filter.
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md4 : active raid5 sda5[0] sdb5[1] 976750784 blocks super 1.2 level 5, 64k chunk, algorithm 2 [2/2] [UU] md3 : active raid5 sda4[4] sdc4[3] sdd4[2] sdb4[5] 5860511616 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU] md2 : active raid5 sdd3[7] sdb3[5] sdc3[4] 2916119040 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/3] [_UUU] md1 : active raid1 sda2[6] sdb2[5] sdc2[4] sdd2[7] 524276 blocks super 1.2 [4/4] [UUUU] md0 : active raid1 sda1[6] sdb1[5] sdc1[4] sdd1[7] 4193268 blocks super 1.2 [4/4] [UUUU] unused devices: <none>
It looks like the problem is with md2 (and that you started off with a 4x1 TB array).
You could try
- removing the disk
- power down the NAS
- disconnect from the power main for a few minutes (maybe 15)
- reboot the NAS
- reinsert the disk.
Part of the rationale here is to clear out any bios state associated with the disk. Sometime the NAS drivers will declare a SATA bay down, and this should make sure it's up again.
I've tried posting the mdstat.log contents multiple time unfortunatly the post keeps disappearing, trying it as an attachment
dlavineway wrote:
I've tried posting the mdstat.log contents multiple time unfortunatly the post keeps disappearing, trying it as an attachment
Likely just caught in the spam filter.
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md4 : active raid5 sda5[0] sdb5[1] 976750784 blocks super 1.2 level 5, 64k chunk, algorithm 2 [2/2] [UU] md3 : active raid5 sda4[4] sdc4[3] sdd4[2] sdb4[5] 5860511616 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU] md2 : active raid5 sdd3[7] sdb3[5] sdc3[4] 2916119040 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/3] [_UUU] md1 : active raid1 sda2[6] sdb2[5] sdc2[4] sdd2[7] 524276 blocks super 1.2 [4/4] [UUUU] md0 : active raid1 sda1[6] sdb1[5] sdc1[4] sdd1[7] 4193268 blocks super 1.2 [4/4] [UUUU] unused devices: <none>
It looks like the problem is with md2 (and that you started off with a 4x1 TB array).
You could try
- removing the disk
- power down the NAS
- disconnect from the power main for a few minutes (maybe 15)
- reboot the NAS
- reinsert the disk.
Part of the rationale here is to clear out any bios state associated with the disk. Sometime the NAS drivers will declare a SATA bay down, and this should make sure it's up again.
It doesn't look like a dead bay issue, because all the other partitions of Drive 1 (sda) are included in their appropriate RAID groups.
I think you are going to find a bad sector on the drive. But why it wouldn't just re-allocate it and go on is a mystery.
If it still doesn't sync after you've done all StephenB has advised, I can give you SSH command for it to re-try adding the partition to the RAID. But it's probably unlikely that would be any more successful.
StephenB, your solution work; thank you very much
Sandshark wrote:
It doesn't look like a dead bay issue, because all the other partitions of Drive 1 (sda) are included in their appropriate RAID groups.
It didn't seem that likely to me either. But in the first post he said the drive was identified in web ui as dead - and it wasn't clear as to why. So I suggested the longer procedure.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
