NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ATA Errors Not In System Log
Thought I'd comment on a curiosity that arose from a weird situation where a 516 spent 10+ hours syncing a drive replacing a missing member of a RAID6 array. But upon finishing it simply faulted it a...
The status log will record things when there has been a very significant amount of change.
The smart_history.log contains every change to key SMART values for every disk in the NAS.
So it was the new disk that you added that had ATA errors?
Well, according to the smart_history.log:
2016-12-29 02:01:14 ST4000DM000-1F2168 W300ADXP 0 0 0 0 0 9168 9168 0 2016-12-29 15:22:26 ST4000DM000-1F2168 W300ADXP 0 0 0 0 1 3312 3312 0 2016-12-29 16:35:21 ST4000DM000-1F2168 W300ADH6 0 0 0 0 1 0 0 12
I don't know what others might think, but I think 3000+ or 9000+ uncorrectable errors is probably a fair bet for having listed in the regular log display as "significant". ;) This was actually a drive that was previously in use in the 516 and later replaced with an 8TB disk in a newer deployment. But it certainly wasn't experiencing this sort of failure rate until very recently. Clearly, it is in bad shape and requires retirement.
What strikes me as odd is that I'd see all kinds of pop-up displays in the web UI /while/ these errors were building, and perhaps even get email notifications for them, but they don't apepar in the "Logs" display in the web UI? That's the head scratcher. Maybe there's a reason for it, but it seems like it'd be making difficult to see something really should be visible... if for no other reason than to allow someone to log in and see what's been going on at a glance if they get email notifications, and to corroborate the events without needing to download the logs .zip file.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
