NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
nhasenoehrl
Oct 25, 2024Aspirant
ReadyNAS 104, Firmware 6.10.10, Resync failure
Hello everybody,
I took out one of my 6TB Hard Disks for maintenance the other three worked fine, but of course the system said "data DEGRADED". (If you wonder: By "maintenance" I mean running Spinrite 6.1 on it which worked very well, no problems there.) But when I put it back in it started Resync but failed somewhere at 30% or so. So I took it back out and formated it (on Win 11, via a docking station). Then I put it back in, now it started that whole lengthy resync process again. I hope it will work this time. Does the system expect an empty harddisk when it starts resync? If so, that might have been the reason for failing, since the old data were still on that disk. Any helpful ideas are welcome.
Thank you
Norbert
1 Reply
- StephenBGuru - Experienced User
nhasenoehrl wrote:
I took out one of my 6TB Hard Disks for maintenance the other three worked fine, but of course the system said "data DEGRADED".
Bad idea. If you want to test a disk out of the NAS, you should always power down the NAS before removing the disk, and keep it powered down until the disk is reinserted.
You can also test it in place, either using smartctl or the built-in disk test on the volume settings wheel (which also uses smartctl). You can also schedule the NAS maintenance tasks on that settings wheel.
nhasenoehrl wrote:
But when I put it back in it started Resync but failed somewhere at 30% or so. So I took it back out and formated it (on Win 11, via a docking station). Then I put it back in, now it started that whole lengthy resync process again. I hope it will work this time. Does the system expect an empty harddisk when it starts resync?
Since the NAS was running, the disk you removed was out of sync with the NAS when you reinserted it. So the NAS attempted to rebuild the contents of that disk from the parity blocks on the remaining disks - writing to every sector of the disk you reinserted. The system was NOT assuming the disk was empty.
If any of the remaining disks had failed during the resync process, you would have lost the entire volume.
You should download the full log zip, and look for disk errors during the resync that failed. The most likely scenario is that this was a write failure to the drive you removed/reinserted. FWIW, I've had disks that pass non-destructive read tests, but which fail a destructive write test (and vice versa). But it's best not to guess.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!