NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Replacing failed disk in RN426
One day I rebooted my RN426, and one of my disks (disk4, Seagate 3TB) was not longer recognized, so the volume was marked as degraded. Rebooted again, and it came up, volume resynced, everything OK.
Next time, Disk 4 dropped and didn't come back on a reboot. So I bought a new HD (WD Red 8TB) to replace it. I popped in the disk, and.... nothing happened. The blue light comes on, indicating that the disk is in there, and it appears to be powered on (it's warm if I pull it out), but it doesn't show up in the volume page (not even as a disk at all, let alone as part of the array). Looks like the NAS doesn't even recognize the existence of the disk at all. Tried with a few different disks, in slots 4 and 5, and same problem. Disk looks fine if I pop it into an external enclosure and bring it up on my mac, but so does the old one.
What is going on here? Is it possible that I have some sort of hardware failure in my NAS, or perhaps there's a magic incantation I forgot to do?
9 Replies
Replies have been turned off for this discussion
Hardware failure is a possibility, but there are other possibilities.
Please send in your logs (see the Sending Logs link in my sig).
Please also go to System > Settings > Support, enable Secure Diagnostic Mode and PM (Private Message) me the 5-digit number you then get or include it on your email.
Do you see SMART errors for the old disk 4 in smart_history.log?
Logs sent.
The smart status looks a bit odd.
time model serial realloc_sect realloc_evnt spin_retry_cnt ioedc cmd_timeouts pending_sect uncorrectable_err ata_errors ------------------- -------------------- -------------------- ------------ ------------ -------------- ---------- ------------ ------------ ----------------- ---------- 2015-02-21 19:03:53 WDC WD20EARX-32PASB0 WD-XXXXXXXXXXXX -1 -1 -1 -1 -1 -1 -1 0 2015-02-21 19:03:53 ST3000DM001-1ER166 XXXXXRK -1 -1 -1 -1 -1 -1 -1 0 2015-02-21 19:03:53 ST3000DM001-1ER166 XXXXXPV -1 -1 -1 -1 -1 -1 -1 0 2015-02-21 19:03:53 ST3000DM001-1ER166 XXXXXXV -1 -1 -1 -1 -1 -1 -1 0 2015-02-21 19:05:41 WDC WD20EARX-32PASB0 WD-XXXXXXXXXXXX 0 0 0 -1 -1 0 0 0 2015-02-21 19:05:41 ST3000DM001-1ER166 XXXXXXRK 0 0 0 0 0 0 0 0 2015-02-21 19:05:41 ST3000DM001-1ER166 XXXXXXPV 0 0 0 0 0 0 0 0 2015-02-21 19:05:41 ST3000DM001-1ER166 XXXXXXXV 0 0 0 0 0 0 0 0 2017-02-22 19:34:04 WDC WD80EFZX-68UW8N0 XXXXXX4Y 0 0 0 -1 -1 0 0 0 2017-09-10 03:38:24 ST3000DM001-1ER166 XXXXXXPV 0 0 0 0 0 8 8 0 2017-10-04 18:03:51 ST3000DM001-1ER166 XXXXXXPV 0 0 0 0 0 0 0 2
However, the disk that failed is W500F7XV, and that's not the one that has errors reported for it. Disk *PV is still in there, and I've definitely scrubbed multiple times since 2017-10-04 without uncovering any data corruption. Potentially any errors it has are in sectors that didn't hold any data, or did the NAS manage to recover them silently from the other 3 drives at the time?
Your 3TB disks remaining in the NAS have been powered on for about 3.25 years. The ST3000DM001 has notoriously high failure rates when used in RAID arrays.
Your 8TB WD RED is a much better choice.
A few ATA errors in and of itself may not suggest that a disk is failing just yet, but if the count continues to increase rapidly or increases a lot that would suggest a problem.
Yes, definitely true. If I can now just get it to recognize the new Red, I'll be able to slowly swap out the seagates.
Also, something that didn't seem relevant, but I might as well put out there.
Not long before this had some general weirdness about not being able to remove an app (resilio sync), so I did what another forum post suggested (force reinstall the OS by "upgrading" to the existing version 3.9.3 using a downloaded zip archive), and it cleaned that much up at least. After that I was able to uninstall and upgrade the app no problem. However, I think it was at a reboot near that time that the disk4 dropped for good.
I've also noticed that disk4 tended to drop in restarts but not in shutdown-reboot cycles. Potentially something about spin up time perhaps? Sample size is small though, about 3 or so, so I'm not sure this is actually a real effect.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
