NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Disk in trouble?
Just spotted this in my user.log file:
Dec 16 01:57:54 NETGEAR_NAS RAIDiator: Detected increasing reallocated sector count on disk 1 [-1, 0]
Dec 16 01:57:54 NETGEAR_NAS RAIDiator: Reallocation event count: [-1, 0]
Dec 16 01:57:54 NETGEAR_NAS RAIDiator: Detected increasing spin retry count on disk 1 [-1, 0]
Dec 16 01:57:54 NETGEAR_NAS RAIDiator: Detected increasing end-to-end errors on disk 1 [-1, 0]
Dec 16 01:57:54 NETGEAR_NAS RAIDiator: Detected increasing command timeouts on disk 1 [-1, 0]
Dec 16 01:57:54 NETGEAR_NAS RAIDiator: Detected increasing pending sector count on disk 1 [-1, 0]
Dec 16 01:57:54 NETGEAR_NAS RAIDiator: Detected increasing uncorrectable errors on disk 1 [-1, 0]
Dec 16 01:57:54 NETGEAR_NAS RAIDiator: Current (temp, start_stop_cnt, power_on_hrs, power_cycle_cnt, load_cycle_cnt) = (-1, -1, -1, -1, -1)
Dec 16 01:57:55 NETGEAR_NAS RAIDiator: Detected increasing reallocated sector count on disk 1 [0, -1]
Dec 16 01:57:55 NETGEAR_NAS RAIDiator: Reallocation event count: [0, -1]
Dec 16 01:57:55 NETGEAR_NAS RAIDiator: Detected increasing spin retry count on disk 1 [0, -1]
Dec 16 01:57:55 NETGEAR_NAS RAIDiator: Detected increasing end-to-end errors on disk 1 [0, -1]
Dec 16 01:57:55 NETGEAR_NAS RAIDiator: Detected increasing command timeouts on disk 1 [0, -1]
Dec 16 01:57:55 NETGEAR_NAS RAIDiator: Detected increasing pending sector count on disk 1 [0, -1]
Dec 16 01:57:55 NETGEAR_NAS RAIDiator: Detected increasing uncorrectable errors on disk 1 [0, -1]
Dec 16 01:57:55 NETGEAR_NAS RAIDiator: Current (temp, start_stop_cnt, power_on_hrs, power_cycle_cnt, load_cycle_cnt) = (41, 65535, 33700, 56, 402537)
...and it's there a few times going back to July 22 2015. Is my Hard Disk #2 in trouble?
By the way does anyone know how to get the NAS to append the Year to the log date please?
Some of the fields are vendor-specific and w/o knowing the formatting are hard to interpret. But still some of the seagate stats look off (for instance a spin-up time of zero).
However, I think what might be happening in the logs is that the SMART query is failing (I believe the -1 is what the system returns on if the query times out).
Perhaps test it with seatools in a PC, and look at the stats there.
FWIW, the ST3000DM001 isn't the best choice for RAID - generally it is reported to have a high failure rate. Backblaze actually removed them from their disk arrays ( https://www.backblaze.com/blog/3tb-hard-drive-failure/ ). Seagate IronWolf drives or Western Digital Reds are better choices.
9 Replies
Replies have been turned off for this discussion
Normally you'd see real counts in these entries. Can you find the smart stats in the log? I don't have a v2, so I'm not certain on the file names. But there should be something like smart_history.log mdstat.log likely also has the SMART data.
If you can connect disk 1 to a windows PC, I suggest powering down the NAS and doing that. Then test it with the vendor's diagnostic - Lifeguard for Western Digital; Seagate for Seatools.
Or maybe just get a new disk for peace of mind.
mdstat.log looks like this:
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md2 : active raid5 sdb3[3] sda3[0] sdc3[2]
5851089408 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU]
md1 : active raid1 sdb2[3] sda2[0] sdc2[2]
524276 blocks super 1.2 [3/3] [UUU]
md0 : active raid1 sdb1[3] sda1[0] sdc1[2]
4193268 blocks super 1.2 [3/3] [UUU]
unused devices: <none>I assume the file disk_smart_2016_12_11.log is the one you want:
***** Disk SMART log from 2016/12/11 *****
***** Disk SMART log for channel 1 [sda] *****
smartctl 5.42 2011-10-20 r3458 [armv5tel-linux-2.6.31.8.nv+v2] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net=== START OF INFORMATION SECTION ===
Device Model: ST3000DM001-9YN166
Serial Number: S1F0ZG77
LU WWN Device Id: 5 000c50 052153bae
Firmware Version: CC4B
User Capacity: 3,000,592,982,016 bytes [3.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: ATA-8-ACS revision 4
Local Time is: Sun Dec 11 06:47:05 2016 WET
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: PASSEDGeneral 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: ( 584) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x3085) SCT Status supported.SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 155330688
3 Spin_Up_Time 0x0003 095 092 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 037 037 020 Old_age Always - 65535
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 67631345
9 Power_On_Hours 0x0032 062 062 000 Old_age Always - 33687
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 55
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 082 082 000 Old_age Always - 18
190 Airflow_Temperature_Cel 0x0022 058 054 045 Old_age Always - 42 (Min/Max 28/46)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 45
193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always - 400370
194 Temperature_Celsius 0x0022 042 046 000 Old_age Always - 42 (0 19 0 0 0)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 98779952847291
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 196094765418670
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 113996279583075SMART Error Log Version: 1
No Errors LoggedSMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 12970 -
# 2 Extended offline Interrupted (host reset) 00% 12699 -
# 3 Short offline Completed without error 00% 0 -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.
***** Disk SMART log for channel 2 [sdb] *****
smartctl 5.42 2011-10-20 r3458 [armv5tel-linux-2.6.31.8.nv+v2] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.netSmartctl open device: /dev/sdb failed: No such device or address
***** Disk SMART log for channel 3 [sdc] *****
smartctl 5.42 2011-10-20 r3458 [armv5tel-linux-2.6.31.8.nv+v2] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net=== START OF INFORMATION SECTION ===
Device Model: TOSHIBA DT01ACA300
Serial Number: 534R3ZAGS
LU WWN Device Id: 5 000039 ff4ca0f19
Firmware Version: MX6OABB0
User Capacity: 3,000,592,982,016 bytes [3.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: ATA-8-ACS revision 4
Local Time is: Sun Dec 11 06:47:15 2016 WET
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: PASSEDGeneral SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
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: (22078) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
SCT capabilities: (0x003d) 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 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0005 139 139 054 Pre-fail Offline - 72
3 Spin_Up_Time 0x0007 222 222 024 Pre-fail Always - 244 (Average 273)
4 Start_Stop_Count 0x0012 079 079 000 Old_age Always - 85472
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 124 124 020 Pre-fail Offline - 33
9 Power_On_Hours 0x0012 097 097 000 Old_age Always - 27019
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 26
192 Power-Off_Retract_Count 0x0032 046 046 000 Old_age Always - 65535
193 Load_Cycle_Count 0x0012 029 029 000 Old_age Always - 85480
194 Temperature_Celsius 0x0002 146 146 000 Old_age Always - 41 (Min/Max 14/49)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0SMART Error Log Version: 1
No Errors LoggedSMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 6295 -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.Hope that's correct. Thank you.
Some of the fields are vendor-specific and w/o knowing the formatting are hard to interpret. But still some of the seagate stats look off (for instance a spin-up time of zero).
However, I think what might be happening in the logs is that the SMART query is failing (I believe the -1 is what the system returns on if the query times out).
Perhaps test it with seatools in a PC, and look at the stats there.
FWIW, the ST3000DM001 isn't the best choice for RAID - generally it is reported to have a high failure rate. Backblaze actually removed them from their disk arrays ( https://www.backblaze.com/blog/3tb-hard-drive-failure/ ). Seagate IronWolf drives or Western Digital Reds are better choices.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
