View previous topic :: View next topic |
Author |
Message |
Ottre Tux's lil' helper
Joined: 23 Dec 2012 Posts: 129
|
Posted: Mon May 02, 2016 6:09 am Post subject: Is this hard drive dead? |
|
|
Yesterday I picked up a MacBook a1181 that failed to boot OS X.
After figuring out how to get past the Select CD-ROM Boot Type screen, I managed to boot SystemRescueCD.
Here's the output from the smartctl long test:
Code: |
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.14.43-std453-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MK..55GSX
Device Model: TOSHIBA MK4055GSX
Serial Number: 89Q2C1UBT
LU WWN Device Id: 5 000039 1f33890c8
Firmware Version: FG011M
User Capacity: 400,088,457,216 bytes [400 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Mon May 2 04:50:22 2016 UTC
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: ( 41) The self-test routine was interrupted
by the host with a hard or soft reset.
Total time to complete Offline
data collection: ( 120) 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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 176) minutes.
SCT capabilities: (0x0039) 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 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1690
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 1269
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 260
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 2744
10 Spin_Retry_Count 0x0033 125 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1053
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 69
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 18087971
193 Load_Cycle_Count 0x0032 087 087 000 Old_age Always - 134964
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 27 (Min/Max 12/50)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 108
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 39
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 121
222 Loaded_Hours 0x0032 098 098 000 Old_age Always - 1119
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 330
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
ATA Error Count: 498 (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 498 occurred at disk power-on lifetime: 2738 hours (114 days + 2 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 0a 2e 16 70 43 Error: UNC 10 sectors at LBA = 0x0370162e = 57677358
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 30 08 16 70 40 00 00:02:10.164 READ DMA EXT
25 00 30 08 16 70 40 00 00:02:06.330 READ DMA EXT
25 00 30 08 16 70 40 00 00:02:02.490 READ DMA EXT
25 00 08 a0 81 1e 40 00 00:02:02.474 READ DMA EXT
25 00 30 08 16 70 40 00 00:01:58.641 READ DMA EXT
Error 497 occurred at disk power-on lifetime: 2738 hours (114 days + 2 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 0a 2e 16 70 43 Error: UNC 10 sectors at LBA = 0x0370162e = 57677358
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 30 08 16 70 40 00 00:02:06.330 READ DMA EXT
25 00 30 08 16 70 40 00 00:02:02.490 READ DMA EXT
25 00 08 a0 81 1e 40 00 00:02:02.474 READ DMA EXT
25 00 30 08 16 70 40 00 00:01:58.641 READ DMA EXT
2f 00 01 10 00 00 00 00 00:01:58.641 READ LOG EXT
Error 496 occurred at disk power-on lifetime: 2738 hours (114 days + 2 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 0a 2e 16 70 43 Error: UNC 10 sectors at LBA = 0x0370162e = 57677358
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 30 08 16 70 40 00 00:02:02.490 READ DMA EXT
25 00 08 a0 81 1e 40 00 00:02:02.474 READ DMA EXT
25 00 30 08 16 70 40 00 00:01:58.641 READ DMA EXT
2f 00 01 10 00 00 00 00 00:01:58.641 READ LOG EXT
60 08 90 a0 81 1e 40 00 00:01:54.575 READ FPDMA QUEUED
Error 495 occurred at disk power-on lifetime: 2738 hours (114 days + 2 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 0a 2e 16 70 43 Error: UNC 10 sectors at LBA = 0x0370162e = 57677358
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 30 08 16 70 40 00 00:01:58.641 READ DMA EXT
2f 00 01 10 00 00 00 00 00:01:58.641 READ LOG EXT
60 08 90 a0 81 1e 40 00 00:01:54.575 READ FPDMA QUEUED
60 30 88 08 16 70 40 00 00:01:54.567 READ FPDMA QUEUED
60 20 80 e8 15 70 40 00 00:01:54.542 READ FPDMA QUEUED
Error 494 occurred at disk power-on lifetime: 2738 hours (114 days + 2 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 41 8a 2e 16 70 63 Error: UNC at LBA = 0x0370162e = 57677358
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 90 a0 81 1e 40 00 00:01:54.575 READ FPDMA QUEUED
60 30 88 08 16 70 40 00 00:01:54.567 READ FPDMA QUEUED
60 20 80 e8 15 70 40 00 00:01:54.542 READ FPDMA QUEUED
60 20 78 c8 15 70 40 00 00:01:54.540 READ FPDMA QUEUED
60 30 70 98 15 70 40 00 00:01:54.529 READ FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended captive Interrupted (host reset) 90% 2738 -
# 2 Short offline Completed: read failure 00% 2738 20343600
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.
|
Can somebody confirm this drive is dead?
I'm not familiar with smartmontools. The last time I had a failed drive I used badblocks to diagnose it. |
|
Back to top |
|
|
vaxbrat l33t
Joined: 05 Oct 2005 Posts: 731 Location: DC Burbs
|
Posted: Mon May 02, 2016 7:15 am Post subject: ick |
|
|
200+ reallocated sectors but it's only been on for 2700+ hours. Compare with a drive on one of my boxes that's been running for almost an order of magnitude longer (see 9 Power_on_hours) and no reallocated sectors. OTOH notice that I've only power cycled my drive less than 30 times during its entire lifetime while your laptop has been cycled 1000+ times. That's the difference between a laptop drive which is constantly getting spun to conserve power versus a desktop that's kept running 24x7. For laptops, I'd recommand an ssd drive because of all of the bouncing around:
Code: | figo sddm # smartctl -a /dev/sdb
smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.1.15-gentoo-r1] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: HGST HDS724040ALE640
Serial Number: PK1334PBG8971S
LU WWN Device Id: 5 000cca 23dc3c59b
Firmware Version: MJAOA580
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon May 2 03:06:59 2016 EDT
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: ( 24) 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: ( 576) 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 137 137 054 Pre-fail Offline - 79
3 Spin_Up_Time 0x0007 185 185 024 Pre-fail Always - 418 (Average 417)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 28
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 121 121 020 Pre-fail Offline - 34
9 Power_On_Hours 0x0012 098 098 000 Old_age Always - 15471
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 28
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 664
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 664
194 Temperature_Celsius 0x0002 142 142 000 Old_age Always - 42 (Min/Max 15/60)
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 - 0
|
I wouldn't trust it for anything at this point. |
|
Back to top |
|
|
frostschutz Advocate
Joined: 22 Feb 2005 Posts: 2977 Location: Germany
|
Posted: Mon May 02, 2016 10:42 am Post subject: |
|
|
It's dead. Reallocated sectors, Pending sectors, error log entries that are very recent, read failure in selftest - which you should run regularly but didn't - set up smartmontools in the future. |
|
Back to top |
|
|
krinn Watchman
Joined: 02 May 2003 Posts: 7470
|
Posted: Mon May 02, 2016 10:45 am Post subject: |
|
|
Without even looking at any values...
Now that "in your mind" the drive "might be" dead, could you seriously keep trusting it?
I'm afraid, as long as your mind will have doubt, you won't be able to use it safely.
Even if anyone would tell you the drive is ok, will you trust that guy, it's your datas on it, not his.
Only one person here that could made my mind change on a disk status, NeddySeagoon, but even coming from him, i'm unsure it would make my mind change, just because if he say anything here i will see his signature with his quote "Computer users fall into two groups: those that do backups, those that have never had a hard drive fail."
So dead or not, you should change it, because anytime you will use your laptop, you'll be scare to save anything on it that might get lost.
As you see, it's not if it is really dead or not, it's just if you have faith or not in it ; and the answer is easy, if you ask us, it's because you have lost it already.
What is sure, with your disk_shift and g-sense value, the drive has taken a shock. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|