NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
One drive initially marked as failed, Resync now at 6.3% after 12 hours. What next? ReadyNAS Ultra 4
Decided to do some housekeeping and was deleting files from the Ultra 4 when I checked Frontview and found that one of the drives had been marked as having failed. I immediately shut down the NAS ...
Thank you for your quick response!
Here are the stats from Drive 4 (very similar to the others)
| SMART Attribute | |
| Spin Up Time | 0 |
| Start Stop Count | 3453 |
| Reallocated Sector Count | 0 |
| Power On Hours | 45055 |
| Spin Retry Count | 0 |
| Power Cycle Count | 315 |
| Runtime Bad Block | 0 |
| End-to-End Error | 0 |
| Reported Uncorrect | 0 |
| Command Timeout | 3 |
| High Fly Writes | 0 |
| Airflow Temperature Cel | 31 |
| G-Sense Error Rate | 0 |
| Power-Off Retract Count | 11 |
| Load Cycle Count | 3454 |
| Temperature Celsius | 31 |
| Current Pending Sector | 0 |
| Offline Uncorrectable | 0 |
| UDMA CRC Error Count | 0 |
| Head Flying Hours | 64265595669968 |
| Total LBAs Written | 412058933 |
| Total LBAs Read | 3157320595 |
| ATA Error Count | 0 |
No real changes that I see occuring for any of the disks.
Thanks again.
The only possible concern in the stats would be the command timeouts - and if they aren't increasing they aren't happening now.
Completion estimates for resync on the ultra/pro are often way off, but it should be farther along than 6% by now.
I think I'd let it complete if you can stand the poor performance.
You could of course pull drive 4, and the resync would stop. But I'd be more inclined to do that if we were seeing clear evidence that the drive was getting worse - and we aren't.
Ok. I will keep an eye on the SMARt status for the drives and check it again in a few hours. Hopefully the Resync speeds up a bit.
Thanks again for your advice!
Resync just finished. It seemed to go much faster after the files finished backing up. The SMART status of Disk 4 is now "OK" and there are no additional errors.
Really makes me wonder what may have caused the drive to be read as "failed." At this point do I just continue on as if nothing happened or replace the drive? Would there be any point in mounting the disk externally and running DiskWarrior to check the file system (would this be dangerous to the RAID arcitecture)?
You can't check the filesystem of a single drive in a RAID array. The data is striped across all the drives.
Maybe schedule a scrub. Resyncing the array wrote to every sector of the drive that's in the data array. A scrub would read all those sectors and verify RAID parity.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
