NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
SMART disk errors or NO SMART disk errors?
I got an email this morning (generated 4 a.m.) from my ReadyNAS NV that said reallocated sector count on disk 1 has increased from 227 to 228. I've never received an error notice for this drive before so figured it must be failing quickly. I logged in to the ReadyNAS front end and checked the SMART status for the drive, and it reported there were no reallocated sectors for that drive (it should be noted that an identical drive in the enclosure is correctly reporting 10 reallocated sectors and has been for some time). So, which to believe? Running 4.1.9 and the drive is a Seagate ST31000528AS.
Thanks!
Thanks!
16 Replies
Replies have been turned off for this discussion
- Try clearing your web browser cache, closing your web browser, reopening Frontview and checking again.
Also download your logs (Status > Logs > Download all Logs) and look in the disk smart logs. - I just replaced the disk that was throwing these errors, and I'm still getting the smart disk error messages, with the count continuing from the same number before I replaced the drive. So, clearly something is messed up. Here's the code from the last error log for the channel in question:
***** Disk SMART log for channel 1 [hdc] *****
smartctl 5.42 2011-10-20 r3458 [padre-linux-2.6.17.14ReadyNAS] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: WDC WD10EFRX-68JCSN0
Serial Number: WD-WMC1U5213578
LU WWN Device Id: 5 0014ee 6029403a3
Firmware Version: 01.01A01
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Sun Sep 9 06:47:08 2012 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (13320) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 152) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x30bd) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 136 136 021 Pre-fail Always - 4191
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 6
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 466
10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 6
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 5
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 0
194 Temperature_Celsius 0x0022 111 105 000 Old_age Always - 32
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay. - Do you have any USB hard disks connected?
- I do. Two. Is there a way to tell which of these is producing the errors?
- One way is to connect them to a PC and use Acronis Drive Monitor (or other tools) to see the SMART stats. SMART data is tracked and kept by the drive itself, so it moves with the drive from system to system.
The "+" part of SMART+ is tracked and kept by the NAS (extended attributes section, and the ATA errors fail into this category). - I'll do that. Must be one of those USB drives acting up, as I can't see how the brand new drive on channel 1 would already be producing 250 sector reallocation errors. Of course, the downside is that I just replaced what was probably a perfectly fine drive. Suppose I can run disk tools on the two drives I removed to determine which one was actually bad (I know, I know: Always label the drives you remove from the NAS). Thanks, all, for the help.
I keep a spare on hand, since if a drive in the array goes bad, it is good to replace it promptly (since a second drive failure destroys the array). So maybe you should delete the partitions off the good drive (or zero it with Seatools) and keep it as a spare.nicheplayer wrote: ...Of course, the downside is that I just replaced what was probably a perfectly fine drive. Suppose I can run disk tools on the two drives I removed to determine which one was actually bad... StephenB wrote: So maybe you should delete the partitions off the good drive (or zero it with Seatools) and keep it as a spare.
That's a great idea; that's what I'll do. I just need to find some disk diagnostic tools that'll run on OSX.- If you are comfortable with shell commands you could SSH into the NAS and do:
cat /proc/mounts
to identify the USB disks then check the SMART stats using the smartctl command. mdgm wrote: then check the SMART stats using the smartctl command.
What's the usage of the smartctl command once I've identified the offending disk?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
