Cannot boot even after OS reinstalled - SMART log included

Questions about hardware,drivers and peripherals
Forum rules
Before you post please read how to get help

Cannot boot even after OS reinstalled - SMART log included

Postby CoyoteScofflaw on Mon Dec 03, 2012 6:39 pm

Hello. My computer has significantly slowed down. Before I realized this I had tried reinstalling LM13 & LM 14. Could boot into all of them at first, but it's gotten significantly worse to the point of LM13 Cinnamon x64 going straight into grub rescue with no way to boot into windows either. I think my HD may be busted or busting rapidly. I've posted the log of a SMART scan of the HD with some errors I cannot interpret.

Thank you.

smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.5.0-17-generic] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MK..59GSXP (Adv. Format)
Device Model: TOSHIBA MK5059GSXP
Serial Number: 32U1C5LHT
LU WWN Device Id: 5 000039 3e3310b2c
Firmware Version: GN003J
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Dec 3 21:39:56 2012 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: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 89) The previous self-test completed having
the electrical element of the test
failed.
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: ( 192) 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 097 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 - 2091
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 861
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 10504
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 097 097 000 Old_age Always - 1519
10 Spin_Retry_Count 0x0033 117 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 753
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 696
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 102
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 7164
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 23 (Min/Max 13/43)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 657
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 616
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 8216
222 Loaded_Hours 0x0032 097 097 000 Old_age Always - 1276
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 - 306
240 Head_Flying_Hours 0x0001 001 001 001 Pre-fail Offline FAILING_NOW 8

SMART Error Log Version: 1
ATA Error Count: 2156 (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 2156 occurred at disk power-on lifetime: 1518 hours (63 days + 6 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 02 58 61 46 62 Error: UNC at LBA = 0x02466158 = 38166872

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 00 58 61 46 40 08 1d+00:41:07.715 READ FPDMA QUEUED
60 08 00 50 61 46 40 08 1d+00:41:07.714 READ FPDMA QUEUED
60 08 00 48 61 46 40 08 1d+00:41:07.070 READ FPDMA QUEUED
60 08 00 40 61 46 40 08 1d+00:41:06.914 READ FPDMA QUEUED
60 08 00 38 61 46 40 08 1d+00:41:06.914 READ FPDMA QUEUED

Error 2155 occurred at disk power-on lifetime: 1518 hours (63 days + 6 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 02 68 ff d1 68 Error: UNC at LBA = 0x08d1ff68 = 147980136

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 00 68 ff d1 40 08 1d+00:40:36.956 READ FPDMA QUEUED
60 08 00 98 57 d1 40 08 1d+00:40:36.782 READ FPDMA QUEUED
60 08 00 68 56 d0 40 08 1d+00:40:36.769 READ FPDMA QUEUED
60 08 00 10 f8 69 40 08 1d+00:40:36.766 READ FPDMA QUEUED
60 08 00 80 f7 69 40 08 1d+00:40:36.758 READ FPDMA QUEUED

Error 2154 occurred at disk power-on lifetime: 1518 hours (63 days + 6 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 02 68 e4 39 6a Error: WP at LBA = 0x0a39e468 = 171566184

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 08 20 50 cc 66 40 08 1d+00:40:18.071 WRITE FPDMA QUEUED
61 10 18 c0 e2 06 40 08 1d+00:40:18.071 WRITE FPDMA QUEUED
61 08 10 b0 95 67 40 08 1d+00:40:18.071 WRITE FPDMA QUEUED
61 10 08 90 95 67 40 08 1d+00:40:18.071 WRITE FPDMA QUEUED
60 08 00 68 e4 39 40 08 1d+00:40:17.290 READ FPDMA QUEUED

Error 2153 occurred at disk power-on lifetime: 1518 hours (63 days + 6 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 02 68 e4 39 6a Error: UNC at LBA = 0x0a39e468 = 171566184

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 00 68 e4 39 40 08 1d+00:40:08.618 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 1d+00:40:08.618 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 1d+00:40:08.618 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 1d+00:40:08.617 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 1d+00:40:08.617 SET FEATURES [Set transfer mode]

Error 2152 occurred at disk power-on lifetime: 1518 hours (63 days + 6 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 02 68 e4 39 6a Error: UNC at LBA = 0x0a39e468 = 171566184

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 00 68 e4 39 40 08 1d+00:40:04.187 READ FPDMA QUEUED
60 08 00 60 e4 39 40 08 1d+00:39:58.829 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 1d+00:39:58.828 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 1d+00:39:58.828 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 1d+00:39:58.827 IDENTIFY DEVICE

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: electrical failure 90% 1519 0
# 2 Extended offline Aborted by host 90% 1494 -
# 3 Extended offline Aborted by host 90% 1493 -
# 4 Short offline Completed without error 00% 1493 -

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.
Last edited by CoyoteScofflaw on Tue Dec 04, 2012 6:18 pm, edited 1 time in total.
CoyoteScofflaw
Level 1
Level 1
 
Posts: 4
Joined: Sat Jul 21, 2012 1:26 pm

Linux Mint is funded by ads and donations.
 

Re: Cannot boot even after OS reinstalled - SMART log includ

Postby gnuuser on Mon Dec 03, 2012 8:07 pm

according to the smart data the drive is failing rapidly
here is a little trick you can try remove the drive and wrap it in paper towel place it in a ziplock bag and place in your freezer for 5 or 6 hours.
then install it back in the computer and immediately run your backup software this may allow you to save most or all of your data.
if the drive is still under warranty i suggest that you wipe the drive if it contains sensitive data before returning it for exchange
gnuuser
Level 1
Level 1
 
Posts: 17
Joined: Fri Nov 23, 2012 4:45 pm

Re: Cannot boot even after OS reinstalled - SMART log includ

Postby CoyoteScofflaw on Tue Dec 04, 2012 3:53 pm

Word. Thanks for the response. That's a damn shame. I managed to do a startup repair for Win7 and boot into that (where I'm posting from right now). It's running fairly slowly, but I was able to run a disk check from Advanced System Care v6. Posted below.

This is something that cannot be repaired from the computer then, eh?

Thanks,
Coyote

* * * * * * * * * * * * * * * * * * * * * *

Windows 7
English (United States)

C:\ Volume Label: ACER, File System: NTFS

Volume label is ACER.
Advanced SystemCare is verifying files (stage 1 of 3)...
239360 file records processed.
File verification completed.
144 large file records processed.
0 bad file records processed.
0 EA records processed.
44 reparse records processed.
Advanced SystemCare is verifying indexes (stage 2 of 3)...
Index entry etilqs_IeeekAAtFpFt9i6 in index $I30 of file 547 is incorrect.
Index entry ETILQS~1 in index $I30 of file 547 is incorrect.
Index entry CBS.log in index $I30 of file 1768 is incorrect.
Index entry CbsPersist_20121204194936.cab in index $I30 of file 1768 is incorrect.
Index entry CBSPER~4.CAB in index $I30 of file 1768 is incorrect.
Index entry CO94A5~1.REG in index $I30 of file 2033 is incorrect.
Index entry COBF3B~1.REG in index $I30 of file 2033 is incorrect.
Index entry COF32C~1.REG in index $I30 of file 2033 is incorrect.
Index entry components{5a905f39-333c-11e2-87a0-206a8a7f1966}.TxR.0.regtrans-ms in index $I30 of file 2033 is incorrect.
Index entry components{5a905f39-333c-11e2-87a0-206a8a7f1966}.TxR.1.regtrans-ms in index $I30 of file 2033 is incorrect.
Index entry components{5a905f39-333c-11e2-87a0-206a8a7f1966}.TxR.2.regtrans-ms in index $I30 of file 2033 is incorrect.
Index entry components{5a905f39-333c-11e2-87a0-206a8a7f1966}.TxR.blf in index $I30 of file 2033 is incorrect.
Index entry COMPON~3.BLF in index $I30 of file 2033 is incorrect.
Index entry 46dc78ec-5c64-4a07-9fe8-7e61574e7a43 in index $I30 of file 2809 is incorrect.
Index entry 46DC78~1 in index $I30 of file 2809 is incorrect.
Index entry TMP00000009283AE8F453058F89 in index $I30 of file 3375 is incorrect.
Index entry TMP000~1 in index $I30 of file 3375 is incorrect.
Index entry downloads.sqlite in index $I30 of file 43738 is incorrect.
Index entry DOWNLO~1.SQL in index $I30 of file 43738 is incorrect.
Index entry extensions.ini in index $I30 of file 43738 is incorrect.
Index entry EXTENS~1.INI in index $I30 of file 43738 is incorrect.
Index entry localstore.rdf in index $I30 of file 43738 is incorrect.
Index entry LOCALS~2.RDF in index $I30 of file 43738 is incorrect.
Index entry places.sqlite-shm in index $I30 of file 43738 is incorrect.
Index entry places.sqlite-wal in index $I30 of file 43738 is incorrect.
Index entry PLACES~2.SQL in index $I30 of file 43738 is incorrect.
Index entry PLACES~3.SQL in index $I30 of file 43738 is incorrect.
Index entry pluginreg.dat in index $I30 of file 43738 is incorrect.
Index entry PLUGIN~1.DAT in index $I30 of file 43738 is incorrect.
Index entry prefs.js in index $I30 of file 43738 is incorrect.
Index entry session.rdf in index $I30 of file 43738 is incorrect.
Index entry Cache in index $I30 of file 58287 is incorrect.
Index entry c23c8e9b1de10c2065901a2bc020917b8e6fc5133bd998193d23ee5a26c4f4ac_ff.sotp in index $I30 of file 58418 is incorrect.
Index entry c23c8e9b1de10c2065901a2bc020917b8e6fc5133bd998193d23ee5a26c4f4ac_key.itr in index $I30 of file 58418 is incorrect.
Index entry c23c8e9b1de10c2065901a2bc020917b8e6fc5133bd998193d23ee5a26c4f4ac_lp.act.xml in index $I30 of file 58418 is incorrect.
Index entry c23c8e9b1de10c2065901a2bc020917b8e6fc5133bd998193d23ee5a26c4f4ac_lpall.slps in index $I30 of file 58418 is incorrect.
Index entry c23c8e9b1de10c2065901a2bc020917b8e6fc5133bd998193d23ee5a26c4f4ac_lt.cac in index $I30 of file 58418 is incorrect.
Index entry C23C8E~1.CAC in index $I30 of file 58418 is incorrect.
Index entry C23C8E~1.ITR in index $I30 of file 58418 is incorrect.
Index entry C23C8E~1.SLP in index $I30 of file 58418 is incorrect.
Index entry C23C8E~1.SOT in index $I30 of file 58418 is incorrect.
Index entry C23C8E~1.XML in index $I30 of file 58418 is incorrect.
Index entry index.dat in index $I30 of file 59076 is incorrect.
Index entry ASCBackup32-2012-12-04(11-47-20).reg in index $I30 of file 61154 is incorrect.
Index entry ASD39D~1.REG in index $I30 of file 61154 is incorrect.
Index entry AS5B20~1.TXT in index $I30 of file 61188 is incorrect.
Index entry ASCLog-2012-12-04(11-47-20).txt in index $I30 of file 61188 is incorrect.
Error detected in index $I30 for file 66480.
Error detected in index $I30 for file 66480.
Error detected in index $I30 for file 66480.
Error detected in index $I30 for file 66488.
Error detected in index $I30 for file 66488.
Error detected in index $I30 for file 66488.
Error detected in index $I30 for file 66505.
Error detected in index $I30 for file 66505.
Error detected in index $I30 for file 66505.
Error detected in index $I30 for file 66506.
Error detected in index $I30 for file 66506.
Error detected in index $I30 for file 66507.
Error detected in index $I30 for file 66507.
Error detected in index $I30 for file 66507.
Error detected in index $I30 for file 66508.
Error detected in index $I30 for file 66508.
Error detected in index $I30 for file 66509.
Error detected in index $I30 for file 66509.
Error detected in index $I30 for file 66509.
Error detected in index $I30 for file 66512.
Error detected in index $I30 for file 66512.
Error detected in index $I30 for file 66516.
Error detected in index $I30 for file 66516.
Error detected in index $I30 for file 66517.
Error detected in index $I30 for file 66517.
Error detected in index $I30 for file 66517.
Index entry elemhide.css in index $I30 of file 71061 is incorrect.
Index entry 53778904a5b001d74a1903ed7eb5c3e8.png in index $I30 of file 98807 is incorrect.
Index entry 537789~1.PNG in index $I30 of file 98807 is incorrect.
Index entry journal7686C8AC in index $I30 of file 104372 is incorrect.
Index entry JOURNA~1 in index $I30 of file 104372 is incorrect.
287682 index entries processed.
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
CoyoteScofflaw
Level 1
Level 1
 
Posts: 4
Joined: Sat Jul 21, 2012 1:26 pm

Re: Cannot boot even after OS reinstalled - SMART log includ

Postby gnuuser on Wed Dec 05, 2012 8:08 pm

boot to dos mode and run chkdsk/f
this is the dos command to run checkdisk and the extension /f is the statement to six errors
this may repair the drive for you
if you can
download and burn a copy of hirens boot cd a9use the cd burning program that comes with it)
this utility /boot cd is free and has a lot of great tools to correct problems with drives
it also indludes the d-ban program (this program will wipe the drive if you need to do it)
it will clean a drive so completely that it is classed as forensically sterile
gnuuser
Level 1
Level 1
 
Posts: 17
Joined: Fri Nov 23, 2012 4:45 pm

Re: Cannot boot even after OS reinstalled - SMART log includ

Postby bigj231 on Wed Dec 05, 2012 9:37 pm

I have used the shelf in my chest freezer to hold the drive while I copied the data to another drive.
I would STRONGLY RECOMMEND replacing the drive with a new one as soon as possible. While you may "fix" it using a disk repair utility, it will most likely fail in short order. Your logs seem to point to a rapidly failing drive. A new drive is relatively cheap (you can get a 2TB desktop drive for under $100 US) and install will not take more than 10 minutes on most systems. You will also save yourself immeasurable heartache and stress.

Also, you can do most of the disk checking and recovery stuff from the Hirens CD (which isn't technically completely legal) on a Linux LiveCD (which is perfectly legal, and you already have one).

EDIT: I see you have a laptop from the drive specs. You can get a new 500GB bare drive for around $50 US. If you find an external drive cheaper than a bare drive, you can pull them apart and use the drive exactly the same as a boxed drive. I have done this for desktop systems, as the external drive was about $20 less than the bare drive, and it was the same exact hard drive inside.
Running on a 4-slot toaster @ 60Hz
User avatar
bigj231
Level 5
Level 5
 
Posts: 793
Joined: Fri Feb 26, 2010 10:16 am
Location: Middle of Nowhere


Return to Hardware Support

Who is online

Users browsing this forum: Google [Bot] and 9 guests