New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Does this mean the HDD is dead?
machine123
Member
Hello,
My server has become extremely unresponsive, luckily the OS is on an SSD which seems to be working fine, however one of the two HDDs in a raid 0 array are giving the following smartctl:
root@ubuntu:/mnt/data/local/post-processed# smartctl --all /dev/sdc
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-116-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 3.5" DT01ACA... Desktop HDD
Device Model: TOSHIBA DT01ACA200
Serial Number: 43I191BGS
LU WWN Device Id: 5 000039 ff3ceadd3
Firmware Version: MX4OABB0
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Fri Mar 2 20:31:10 2018 EST
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: (0x82) Offline data collection activity
was completed without error.
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: (15013) 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: ( 251) 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 - 71
3 Spin_Up_Time 0x0007 129 129 024 Pre-fail Always - 300 (Average 285)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 58
5 Reallocated_Sector_Ct 0x0033 087 087 005 Pre-fail Always - 129
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 126 126 020 Pre-fail Offline - 32
9 Power_On_Hours 0x0012 095 095 000 Old_age Always - 35036
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 57
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 154
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 154
194 Temperature_Celsius 0x0002 253 253 000 Old_age Always - 22 (Min/Max 10/42)
196 Reallocated_Event_Count 0x0032 032 032 000 Old_age Always - 1369
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 8
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 8
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 213898
SMART Error Log Version: 1
Warning: ATA error count 65535 inconsistent with error log pointer 1
ATA Error Count: 65535 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 65535 occurred at disk power-on lifetime: 26669 hours (1111 days + 5 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 70 fd 3f 67 03 Error: UNC at LBA = 0x03673ffd = 57098237
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
24 00 70 fd 3f 67 e0 00 14:49:10.637 READ SECTOR(S) EXT
c6 00 00 f8 3f 67 a0 00 14:49:10.584 SET MULTIPLE MODE
24 00 08 f5 3f 67 e0 00 14:49:07.386 READ SECTOR(S) EXT
24 00 08 55 52 b5 e0 00 14:49:07.367 READ SECTOR(S) EXT
24 00 80 dd c4 06 e0 00 14:49:07.327 READ SECTOR(S) EXT
Error 65534 occurred at disk power-on lifetime: 26669 hours (1111 days + 5 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 05 f8 3f 67 03 Error: UNC at LBA = 0x03673ff8 = 57098232
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
24 00 08 f5 3f 67 e0 00 14:49:07.386 READ SECTOR(S) EXT
24 00 08 55 52 b5 e0 00 14:49:07.367 READ SECTOR(S) EXT
24 00 80 dd c4 06 e0 00 14:49:07.327 READ SECTOR(S) EXT
24 00 78 d5 3c c2 e0 00 14:49:07.307 READ SECTOR(S) EXT
24 00 08 cd 3c c2 e0 00 14:49:07.222 READ SECTOR(S) EXT
Error 65533 occurred at disk power-on lifetime: 26669 hours (1111 days + 5 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 75 f8 3f 67 03 Error: UNC at LBA = 0x03673ff8 = 57098232
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
24 00 78 f5 3f 67 e0 00 14:49:03.263 READ SECTOR(S) EXT
34 00 08 15 c5 7d e0 00 14:49:03.262 WRITE SECTORS(S) EXT
24 00 78 65 c4 06 e0 00 14:49:03.242 READ SECTOR(S) EXT
24 00 78 55 3c c2 e0 00 14:49:03.222 READ SECTOR(S) EXT
34 00 08 4d 35 46 e0 00 14:49:03.220 WRITE SECTORS(S) EXT
Error 65532 occurred at disk power-on lifetime: 26658 hours (1110 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 70 fd 3f 67 03 Error: UNC at LBA = 0x03673ffd = 57098237
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
24 00 70 fd 3f 67 e0 00 03:09:38.444 READ SECTOR(S) EXT
c6 00 00 f8 3f 67 a0 00 03:09:38.373 SET MULTIPLE MODE
24 00 08 f5 3f 67 e0 00 03:09:35.146 READ SECTOR(S) EXT
24 00 28 5d de d1 e0 00 03:09:35.124 READ SECTOR(S) EXT
24 00 78 9d ec 56 e0 00 03:09:35.012 READ SECTOR(S) EXT
Error 65531 occurred at disk power-on lifetime: 26658 hours (1110 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 05 f8 3f 67 03 Error: UNC at LBA = 0x03673ff8 = 57098232
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
24 00 08 f5 3f 67 e0 00 03:09:35.146 READ SECTOR(S) EXT
24 00 28 5d de d1 e0 00 03:09:35.124 READ SECTOR(S) EXT
24 00 78 9d ec 56 e0 00 03:09:35.012 READ SECTOR(S) EXT
34 00 08 7d 4b ee e0 00 03:09:35.010 WRITE SECTORS(S) EXT
34 00 08 85 89 6a e0 00 03:09:35.009 WRITE SECTORS(S) EXT
SMART 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% 30239 -
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.
I have raised a ticket, however wanted to get you guys opinion if it's indeed a valid reason fro them to replace the hdd. Thanks
Comments
Not dead but dying
Yes, pretty much. It's on life support
Not as clear, as you see from the error log the latest UNC error was detected at hour 26669, while the latest SMART test was done on hour 30239 successfully.
Could be that all these bad sectors and remaps were done long ago and don't increase anymore, whereas the problem could be caused by the high UDMA_CRC_Error_Count, with which it's harder to say whether that's historical issues or current -- indicating a bad cable connection, either now or in the past. Does the number there increase? Do you see any errors in
dmesgwhile the server is being slow?Meanwhile, run a
smartctl -t long /dev/sdxand after a few hours check for results insmartctl -a. If that fails, it's a sure sign the disk is bad.On the other hand, regardless of what's the actual problem, any host should have no objections to replacing a disk with SMART in its current state. So you could just have it replaced and don't bother with further digging.
I would do as @rm_ says - run a long smart test and check the smart logs.
Attributes 5, 197 and 198 are all non-zero but pretty small. I think there's still decent life in the disk but only a full disk write test (or a disk wipe via hdparm) will confirm if that's the case. Usually there are a fairly decent number of spare sectors that come with the disk and it doesn't appear that you're running out of those as yet.
The old (~26k hours) UNC errors are all probably cabling/power issues and spurious from a disk health standpoint.
Disclaimer: we're all talking in probabilistic terms based on prior experience. What will happen in your specific case is anyone's guess.
Got it replaced, thanks for the help guys.