NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Drive in a Readynas 102 changing state from RESYNC to FAILED while resyncing.
Hi.
I've had some issues with my Readynas 102 recently.
It has two drives in raid, drive 2 have been giving early signs of age for quite some time.(Detected high command timeouts happening once or twice per year).
Yesterday the second drive failed, and I replaced it with a used, working drive that I pulled from a working Readynas 104.
I deleted all the partitions on the drive, before I installed it in the RN 102.
After about 5 hours, the resync operation completed, but the nas compained about the volume still being degraded.
I did a reboot, the NAS repeated the process, and the exact same thing happened after 5 hours.
I hot-swapped (pulled and re-installed) the drive, and it started over again.
At 17:54:24 today the drive failed, and at 17:54:37 the resync completed (!), still complaining about the volume being degraded.
This drive is still well within the warranty period, and has 0 smart-errors. This was something I knew from before,
but I confirmed it by first checking smart_history.log :
2018-04-10 20:41:36 WDC WD30EFRX-68EUZN0 WD-WCC4N5PNXT1N 0 0 0 -1 -1 0 0 0
and then I connected it to a pc running windows 10, checking with both speedfan and CrystalDiskInfo:
CrystalDiskInfo - seems fine to me?
Link to speedfan results: link: http://www.hddstatus.com/hdrepshowreport.php?ReportCode=11195176&ReportVerification=FDCAF8A2
Also, here's a screenshot of the log. Please ignore the line saying that the seagate-drive was re-installed, that was just me forgetting to unlock the drive before moving it.
I also checked the smart-info for the drive that I actually assumed was dead: Everything seemed fine. Havent run any benchmarks/stresstests on either of the drives, but I dont expect that to be nessesary on the WD RED 3TB drive, as it was working like a charm in the other nas.
11 Replies
Replies have been turned off for this discussion
It's possible that something is wrong with the SATA port on the RN102.
Though perhaps try yet-another-test of the disk with WDC's lifeguard program in the Windows PC. Perhaps try the write zeros test (which is destructive), as it is closer to what happens in the resync than the normal non-destructive tests.
Thanks for the reply.
I'll do some testing through the night and report back tomorrow. I'm starting of the drive that should be dead (according to the NAS),
considering that the WD RED 3TB was working fine until i installed it in the 2-bay NAS.
Do you have any suggestions on how to troubleshoot the S-ATA connectivity? Would it be safe to export the system drive, test the NAS with two other drives, then cold-import the original system-drive afterwards?Also, here's a large part of the DMESG output from earlier today, complaining about bad sectors on the WD RED drive, which Im pretty sure is 100% fine.
Danny2 wrote:
Do you have any suggestions on how to troubleshoot the S-ATA connectivity? Would it be safe to export the system drive, test the NAS with two other drives, then cold-import the original system-drive afterwards?Don't export anything. Just shut down the NAS, and remove the working drive (labeling it by slot).
Then try inserting the WDC drive into the same slot that the working drive is in, and do a factory default via the boot menu. If that install works, then run a disk test on the drive from the NAS volume settings wheel.
Then repeat that process, but putting the WDC drive into the other slot.
When you are done, you can power down, restore the working drive back into it's slot (leaving the other slot empty), and then power up.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
