NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Failed Drive Replaced, Recync Complete, But Volume Is Still Degraded
My RN312 has been working fine for many years. Just recently, one of the 4TB WD Black drives indicated a failure. I removed the failed drive and replaced it with a newer 4TB WD Black drive with the...
BtrieveBill wrote:
I hesitate to do that because I'm not sure where the RN312 keeps its brain.
Everything is on the disks - config files are stored in the OS partition, any apps are installed to a hidden folder on the data volume.
BtrieveBill wrote:
The SMART data shows that the last failure on that drive was in 2022, but that it is showing 53 pending sectors
Personally I would have replaced that disk. Generally I consider replacement when the bad sectors move into the 20s.
BtrieveBill wrote:
I copied all of the data off of the volume to my new Synology NAS, so I have no fear of losing anything.
Good.
One option is to save the config files, do a clean install on new disks, and then restore the config. Personally I'd use Seagate Ironwolf or WD Red Plus. If you use desktop class drives, make sure they are not SMR. Most desktop drives in the 2-6 TB range are now SMR.
A second option is to try cloning the disk to a replacement drive. Then power up the NAS with that drive installed. Delete all the files and snapshots, and restore the files from the Synology. After that hot-insert a second drive (ideally new) and wait for it to sync. That would preserve your configuration and the OS partition (assuming they are not damaged).
Thanks for the speedy reply. The drive had come out of a working RN516 that was upgraded from 4TB drives to 6TB drives, and it had no issues in the RN516, which is why I saved it. I have dropped in another one of the drives, blanked it, and have started another re-sync. I will advise as to how that goes!
Luckily, this box is used mainly for backups of other data that is on my RN516 and my newer Synology, and the Synology has space to hold a complete backup of the RN312. So, in the worst case, I could wipe both drives and simply restore everything, but it would be nice if it worked as advertised.
FYI -- I had no problems formatting the drive on a computer. The second 4TB drive (also removed from the RN516 when upgraded) was blanked, formatted, and added to the array, but it resulted in the exact same result -- the resync completed and the drive was marked ONLINE, but the volume still shows as degraded. Additional suggestions?
Download the log zip, and then post the contents of mdstat.log here. That will let you know what isn't synced.
Here's the MDSTAT log as of today. Let me know what else you might need from that log package:
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md1 : active raid1 sdc2[1] sda2[0]
523264 blocks super 1.2 [2/2] [UU]
md127 : active raid1 sdc3[2](S) sda3[0]
3902166656 blocks super 1.2 [2/1] [U_]
md0 : active raid1 sdc1[1] sda1[0]
4192192 blocks super 1.2 [2/2] [UU]
unused devices: <none>
/dev/md/0:
Version : 1.2
Creation Time : Thu Aug 14 17:38:12 2014
Raid Level : raid1
Array Size : 4192192 (4.00 GiB 4.29 GB)
Used Dev Size : 4192192 (4.00 GiB 4.29 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistentUpdate Time : Sun May 5 12:43:17 2024
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0Consistency Policy : unknown
Name : 7c6eb546:0 (local to host 7c6eb546)
UUID : 50442d9b:0f704f29:e37cb92c:dd62d058
Events : 4407578Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 33 1 active sync /dev/sdc1
/dev/md/data-0:
Version : 1.2
Creation Time : Thu Aug 14 17:38:12 2014
Raid Level : raid1
Array Size : 3902166656 (3721.40 GiB 3995.82 GB)
Used Dev Size : 3902166656 (3721.40 GiB 3995.82 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistentUpdate Time : Sun May 5 00:58:35 2024
State : clean, degraded
Active Devices : 1
Working Devices : 2
Failed Devices : 0
Spare Devices : 1Consistency Policy : unknown
Name : 7c6eb546:data-0 (local to host 7c6eb546)
UUID : 7766d2a3:da14ec25:7560e15c:9ca8dff8
Events : 4164Number Major Minor RaidDevice State
0 8 3 0 active sync /dev/sda3
- 0 0 1 removed2 8 35 - spare /dev/sdc3
BtrieveBill wrote:
md127 : active raid1 sdc3[2](S) sda3[0]
3902166656 blocks super 1.2 [2/1] [U_]As you can see the array has one of the disks marked as a spare, so the resync did not complete properly.
The best thing to do next is remove the disk, and delete the partitions, and then reinsert it. If you can connect the disk to a Windows PC (either with SATA or a USB adapter/dock), then you can remove the partitions with the windows disk manager.
You do need to be careful to remove the correct disk. Look in disk info.log, and note the channel number and the serial number of sdc. Power down the NAS, and remove the drive (confirming that it's the correct one by checking the serial number).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
