NatureMadness Posted November 30, 2017 Share Posted November 30, 2017 I have a drive that is "offline" or Emulatede. The drive is only 5 month old. Is it dead/dying ? Attributes # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 1 Raw read error rate 0x000f 107 100 006 Pre-fail Always Never 169322588 3 Spin up time 0x0003 096 095 000 Pre-fail Always Never 0 4 Start stop count 0x0032 100 100 020 Old age Always Never 388 5 Reallocated sector count 0x0033 094 094 010 Pre-fail Always Never 7584 7 Seek error rate 0x000f 100 253 030 Pre-fail Always Never 4891968519021 9 Power on hours 0x0032 096 096 000 Old age Always Never 3785 (5m, 4d, 17h) 10 Spin retry count 0x0013 100 100 097 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 020 Old age Always Never 84 183 Runtime bad block 0x0032 093 093 000 Old age Always Never 7 184 End-to-end error 0x0032 100 100 099 Old age Always Never 0 187 Reported uncorrect 0x0032 088 088 000 Old age Always Never 12 188 Command timeout 0x0032 099 098 000 Old age Always Never 4295163907 189 High fly writes 0x003a 097 097 000 Old age Always Never 3 190 Airflow temperature cel 0x0022 091 058 045 Old age Always Never 9 (min/max 9/14) 191 G-sense error rate 0x0032 100 100 000 Old age Always Never 0 192 Power-off retract count 0x0032 100 100 000 Old age Always Never 35 193 Load cycle count 0x0032 099 099 000 Old age Always Never 2003 194 Temperature celsius 0x0022 009 042 000 Old age Always Never 9 (0 4 0 0 0) 197 Current pending sector 0x0012 095 095 000 Old age Always Never 880 198 Offline uncorrectable 0x0010 095 095 000 Old age Offline Never 880 199 UDMA CRC error count 0x003e 200 200 000 Old age Always Never 0 240 Head flying hours 0x0000 100 253 000 Old age Offline Never 153 (229 62 0) 241 Total lbas written 0x0000 100 253 000 Old age Offline Never 13962624088 242 Total lbas read 0x0000 100 253 000 Old age Offline Never 69442597629 Identity Title Information Device model: ST2000DM006-2DM164 Serial number: Z4Z7N6NR LU WWN device id: 5 000c50 0a255f3ab Firmware version: CC26 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: Not in smartctl database [for details use: -P showall] ATA version: ACS-2, ACS-3 T13/2161-D revision 3b SATA version: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local time: Thu Nov 30 11:10:14 2017 CET SMART support: Available - device has SMART capability. SMART support: Enabled SMART overall-health: Passed ATA Error Count: 12 (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 12 occurred at disk power-on lifetime: 3757 hours (156 days + 13 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 53 00 48 88 a0 04 Error: UNC at LBA = 0x04a08848 = 77629512 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 48 88 a0 e4 00 9d+23:22:25.721 READ DMA EXT 25 00 00 a8 36 60 e5 00 9d+23:22:25.713 READ DMA EXT 25 00 00 b8 6d 00 e5 00 9d+23:22:25.694 READ DMA EXT 35 00 00 48 86 a0 e4 00 9d+23:22:25.692 WRITE DMA EXT ef 10 02 00 00 00 a0 00 9d+23:22:25.692 SET FEATURES [Enable SATA feature] Error 11 occurred at disk power-on lifetime: 3757 hours (156 days + 13 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 53 00 e0 9b 0b 00 Error: UNC at LBA = 0x000b9be0 = 760800 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 20 e0 9b 0b e0 00 9d+23:22:20.073 READ DMA c8 00 20 00 cf 0e e0 00 9d+23:22:20.055 READ DMA b0 d1 01 01 4f c2 00 00 9d+23:22:13.805 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] b0 d0 01 00 4f c2 00 00 9d+23:22:13.680 SMART READ DATA ec 00 01 00 00 00 00 00 9d+23:22:13.666 IDENTIFY DEVICE Error 10 occurred at disk power-on lifetime: 3757 hours (156 days + 13 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 53 00 48 86 a0 04 Error: UNC at LBA = 0x04a08648 = 77629000 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 48 86 a0 e4 00 9d+23:22:08.077 READ DMA EXT 25 00 00 38 92 80 e4 00 9d+23:22:08.068 READ DMA EXT 25 00 00 48 98 e0 e4 00 9d+23:22:08.061 READ DMA EXT 25 00 00 80 86 00 e4 00 9d+23:22:08.005 READ DMA EXT 25 00 00 40 90 40 e4 00 9d+23:22:07.991 READ DMA EXT Error 9 occurred at disk power-on lifetime: 3647 hours (151 days + 23 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 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 c0 ff ff ff ef 00 5d+08:49:14.272 READ DMA EXT 35 00 40 ff ff ff ef 00 5d+08:49:14.269 WRITE DMA EXT 35 00 40 ff ff ff ef 00 5d+08:49:14.266 WRITE DMA EXT ef 10 02 00 00 00 a0 00 5d+08:49:14.256 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 5d+08:49:14.230 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] Error 8 occurred at disk power-on lifetime: 3647 hours (151 days + 23 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 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 5d+08:49:10.049 READ DMA EXT ef 10 02 00 00 00 a0 00 5d+08:49:10.039 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 5d+08:49:10.012 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 5d+08:49:10.012 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 5d+08:49:09.999 SET FEATURES [Set transfer mode] Quote Link to comment
JorgeB Posted November 30, 2017 Share Posted November 30, 2017 2 minutes ago, NatureMadness said: Is it dead/dying ? Yep, more dead than dying. Quote Link to comment
NatureMadness Posted November 30, 2017 Author Share Posted November 30, 2017 Just out of curiosity. How did you come to that conclusion? If i mount the drive outside the array i can read the data. The drive is still under warranty. But i get the feeling they wont take it, if they can "just" mount it and read data. Quote Link to comment
JorgeB Posted November 30, 2017 Share Posted November 30, 2017 Just now, NatureMadness said: But i get the feeling they wont take it A single pending sector is enough to qualify for an RMA, a failed SMART test is also enough, that disk should fail both the short and extended tests quickly. Quote Link to comment
BobPhoenix Posted December 1, 2017 Share Posted December 1, 2017 When I RMA'd a drive to WD one of the choices was "drive access is sluggish" in other words nothing obviously wrong showing in a smart report. So I don't think you have anything to worry about. Quote Link to comment
NatureMadness Posted December 1, 2017 Author Share Posted December 1, 2017 I will submit it for RMA, and post their response Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.