Sign in with
Sign up | Sign in
Your question

Dropped Drive, Trying to Use Linux to Fix

Last response: in Storage
Share
December 25, 2012 7:29:40 PM

Hey everyone, I Googled, I read for hours on end...I'm at a complete lost.
The gist of the story is I had an external hard drive knocked over by the cat. It's a Buffalo HD CXT1. It literally stood on its own and I guess my cat knocked it over somehow and now it won't work.

I tried recovery softwares without any luck. The warranty's over so I pried open the case and took the drive out. The drive itself is a Seagate Barracuda 7200.12

I connected it with a Sata-USB and a power source to Windows, it recognizes the bridge (I'm guessing that's what the SATA thing is?) But the drive itself does not show up in My Computer.

So then I switched to my EeePC (Asus 1015B Running Pepper Mint 3 Linux) and plugged the USB in.
When I go to file manager, I cannot see the drive mounted. When I go into Disk Utility, I can see the drive but I'm not really sure what I'm looking at.
Can someone teach me how to do this step by step or at least point me to a link of some sort? I'm very new to Linux and I really have no clue what I'm doing.

I don't care about getting a new drive, I care about the information on this current drive.
Please let me know if there's any information that you need!

Thanks ahead of time.

More about : dropped drive linux fix

December 26, 2012 4:31:16 PM

Quote:
As I know, the falling thing usually can do some damage to the hard drive in two ways: logical damage and physical damage.
The former one is fine for you still can recover your data at the aid of a third-party recovery freeware, which has successfully helped me to retrieve my files from a inaccessible drive.
The latter one is really bad. You’d better take it to a specialist or recovery company for as soon as possible.
You could try a checking tool to help you know how your drive is damaged, such as Seatool.
Good luck!


I ran Seatools and it failed, but it suggested to do the long generic test, which I tried to do, and that didn't work either.
Then I plugged it into the EeePC and ran the GSmartControl, the log is below:

smartctl 5.41 2011-06-09 r3365 [i686-linux-3.2.0-23-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.12
Device Model: ST31000528AS
Serial Number: 5VP6BTF4
LU WWN Device Id: 5 000c50 02a656bc8
Firmware Version: CC44
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Thu Dec 27 00:22:50 2012 CST
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
See vendor-specific Attribute list for marginal Attributes.

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: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 609) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
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: ( 200) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table 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 077 077 006 Pre-fail Always - 133182396
3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 70
5 Reallocated_Sector_Ct 0x0033 096 096 036 Pre-fail Always - 174
7 Seek_Error_Rate 0x000f 054 054 030 Pre-fail Always - 34361575940
9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 7871
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 70
183 Runtime_Bad_Block 0x0000 100 100 000 Old_age Offline - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 4914
188 Command_Timeout 0x0032 095 001 000 Old_age Always - 5781115307362
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 059 045 045 Old_age Always In_the_past 41 (Min/Max 31/41)
194 Temperature_Celsius 0x0022 041 055 000 Old_age Always - 41 (0 20 0 0)
195 Hardware_ECC_Recovered 0x001a 021 012 000 Old_age Always - 133182396
197 Current_Pending_Sector 0x0012 081 081 000 Old_age Always - 805
198 Offline_Uncorrectable 0x0010 081 081 000 Old_age Offline - 805
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 230188772236288
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 249351989
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 578007911

SMART Error Log Version: 1
ATA Error Count: 4873 (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 4873 occurred at disk power-on lifetime: 7871 hours (327 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 51 00 00 00 00 00 Error: UNC at LBA = 0x00000000 = 0

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 08 00 00 00 e0 00 00:25:39.590 READ DMA EXT
ef 03 46 00 00 00 a0 00 00:25:39.468 SET FEATURES [Set transfer mode]
00 00 00 00 00 00 00 04 00:25:39.180 NOP [Abort queued commands]
25 00 08 08 00 00 e0 00 00:25:36.402 READ DMA EXT
ef 03 46 00 00 00 a0 00 00:25:36.287 SET FEATURES [Set transfer mode]

Error 4872 occurred at disk power-on lifetime: 7871 hours (327 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 51 00 08 00 00 00 Error: UNC at LBA = 0x00000008 = 8

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 08 08 00 00 e0 00 00:25:36.402 READ DMA EXT
ef 03 46 00 00 00 a0 00 00:25:36.287 SET FEATURES [Set transfer mode]
00 00 00 00 00 00 00 04 00:25:36.083 NOP [Abort queued commands]
25 00 08 ff ff ff ef 00 00:25:33.134 READ DMA EXT
ef 03 46 00 00 00 a0 00 00:25:32.907 SET FEATURES [Set transfer mode]

Error 4871 occurred at disk power-on lifetime: 7871 hours (327 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 51 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 08 ff ff ff ef 00 00:25:33.134 READ DMA EXT
ef 03 46 00 00 00 a0 00 00:25:32.907 SET FEATURES [Set transfer mode]
00 00 00 00 00 00 00 04 00:25:32.869 NOP [Abort queued commands]
25 00 08 ff ff ff ef 00 00:25:29.942 READ DMA EXT
ef 03 46 00 00 00 a0 00 00:25:29.377 SET FEATURES [Set transfer mode]

Error 4870 occurred at disk power-on lifetime: 7871 hours (327 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 51 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 08 ff ff ff ef 00 00:25:29.942 READ DMA EXT
ef 03 46 00 00 00 a0 00 00:25:29.377 SET FEATURES [Set transfer mode]
00 00 00 00 00 00 00 04 00:25:28.665 NOP [Abort queued commands]
25 00 01 ff ff ff ef 00 00:25:25.821 READ DMA EXT
ef 03 46 00 00 00 a0 00 00:25:25.614 SET FEATURES [Set transfer mode]

Error 4869 occurred at disk power-on lifetime: 7871 hours (327 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 51 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 01 ff ff ff ef 00 00:25:25.821 READ DMA EXT
ef 03 46 00 00 00 a0 00 00:25:25.614 SET FEATURES [Set transfer mode]
00 00 00 00 00 00 00 04 00:25:25.393 NOP [Abort queued commands]
25 00 01 ff ff ff ef 00 00:25:22.632 READ DMA EXT
ef 03 46 00 00 00 a0 00 00:25:22.516 SET FEATURES [Set transfer mode]

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 7871 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.

My next try is to try using the gddrescue. Wish me luck!

m
0
l
December 26, 2012 5:17:12 PM

By the look of that error log, the drive was powered-up and being accessed when it was knocked-over; if so, the more you try to use/recover the drive the greater the damage will be; take it to a data recovery specialise and be prepared for a big bill.
m
0
l
Related resources
December 26, 2012 5:56:14 PM

you can try Easus for free, it will scan and tell you if it can recover data. you will need to purchase to recover the data but the scan is free.
m
0
l
a c 326 G Storage
December 27, 2012 5:07:30 AM

ISTM that no software will be able to retrieve any data from your drive. :-(

I suspect that the "ATA Error Count" of 4873 will consist mostly of UNC errors, ie UNCorrectable read errors.

The last 5 errors in the SMART log are due to failed READ DMA EXT commands. The first occurs at LBA 0 and is the result of attempting to read 8 sectors beginning with sector 0.

The second error occurs when attempting to read 8 sectors beginning with sector 8.

The last error is the result of an attempt to read 8 sectors beginning with sector 0x0FFFFFFF. This is the last sector before the 28-bit LBA limit.

Therefore ISTM that smartctl has performed a quick scan of the user area and hit UNC sectors on each occasion, in which case I suspect that you may get an UNC error for every sector. You could use a disc editor such as DMDE or HxD to verify whether you can read any sector.

HxD - Freeware Hex Editor and Disk Editor:
http://mh-nexus.de/en/hxd

DMDE (DM Disk Editor and Data Recovery):
http://softdm.com/download.html

The following error indicates that the drive failed an internal read test:

"Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed."

The following SMART attributes confirm that your drive is having read problems:

1 Raw_Read_Error_Rate 0x000f 077 077 006 Pre-fail Always - 133182396
5 Reallocated_Sector_Ct 0x0033 096 096 036 Pre-fail Always - 174
7 Seek_Error_Rate 0x000f 054 054 030 Pre-fail Always - 34361575940
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 4914
188 Command_Timeout 0x0032 095 001 000 Old_age Always - 5781115307362
197 Current_Pending_Sector 0x0012 081 081 000 Old_age Always - 805
198 Offline_Uncorrectable 0x0010 081 081 000 Old_age Offline - 805

The "ATA Error Count" of 4873 appears to match the Reported_Uncorrectable errors (4914).

A perfect score for the Raw_Read_Error_Rate attribute would be 120. Your normalised value of 77 would suggest that the drive has a serious problem (the raw value of 133182396 is actually a sector count, not an error count). According to my calculations, I believe that the drive has recorded about 10600 errored sectors while attempting to read the previous 133182396 sectors.

The Seek_Error_Rate corresponds to 8 seek errors in 1.8 million seeks, possibly recently recorded.

For an explanation of the above attributes, see http://www.users.on.net/~fzabkar/HDD/Seagate_SER_RRER_H...

I believe that the Current_Pending_Sector and Offline_Uncorrectable counts would be the result of SMART self tests or offline scanning. These are bad sectors that are waiting to be replaced.

The Command_Timeout value is 0x054205530562 in hexadecimal. ISTM that this number consists of three 16-bit components, namely 0x0542, 0x0553, and 0x0562. Therefore the total number of timeouts is probably of the order of 1378 (= 0x0562).
m
0
l
!