Hello everyone.
I have a ST1000LM025/ HN-M101ABB USB 3.0 hard drive that failed recently (my personal drive, I'm not a professional).
Everything was working OK but when I plugged it the next day it wasn't recognized by any OS.
S.M.A.R.T. data shows nothing out of the ordinary (also short and long self-test don't report any error) but drive is inaccessible (IO error).
Here is what the linux syslog reports upon connection:
Code:
[ 6849.614270] sd 13:0:0:0: [sdf] 1953504688 512-byte logical blocks: (1.00 TB/931 GiB)
[ 6849.615382] sd 13:0:0:0: [sdf] Write Protect is off
[ 6849.615387] sd 13:0:0:0: [sdf] Mode Sense: 27 00 00 00
[ 6849.616492] sd 13:0:0:0: [sdf] No Caching mode page found
[ 6849.616497] sd 13:0:0:0: [sdf] Assuming drive cache: write through
[ 6849.655356] sd 13:0:0:0: [sdf] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 6849.655363] sd 13:0:0:0: [sdf] Sense Key : 0xb [current]
[ 6849.655367] sd 13:0:0:0: [sdf] ASC=0x0 ASCQ=0x0
[ 6849.655369] sd 13:0:0:0: [sdf] CDB:
[ 6849.655371] cdb[0]=0x28: 28 00 00 00 00 00 00 00 08 00
[ 6849.655381] blk_update_request: I/O error, dev sdf, sector 0
[ 6849.655385] Buffer I/O error on dev sdf, logical block 0, async page read
(The last 7 lines are repeated several times, and happen on any sector I try to access)
The drive appears to spin normally, and makes a few light clicking noises at start-up, so the heads appear to move too.
I was able to hack into the serial interface. Here is the log:
Code:
ActiveFW : 00
FWVer : 0001
SATA PLL cal done
DDR size detected = 8MB
DDR size detected = 8MB
*PAUNI_L2957*PA VID=0006 PN=0009 Rev=0002- PA_UNI Found
*PAUNI_L2957*PA VID=0006 PN=0009 Rev=0002- PA_UNI FoundU
S_0SHK NF Cal:27
SO_1
SPU@31'C,4683mV
IS=6
CLA ..36/54
HO..OK
HO RPM=1883 OK
AC 1697
ST..OK
mS1 00000003
GT:423
SC(L):4114/33
BE.N:16
LD..OK
SK C: 7444 H:0
Boot Sector Error! Take a default.
Loaded FIT ( 0: 0: 1)
CalibTable Loaded. Rev:0x1B
ResoTable Loaded. Rev:0x01
Bump Limit Loaded. Rev:0x01
RRO1xTable Loaded. Rev:0x01
Fw Active 00
Ovly loaded to 0x00014D00
Ovly loaded to 0x1002E408
FdtTable Loaded. Rev:0x02
Reading Serial Num Pass
Up MC
PwrOn RRO1x @ H0
Table) cos = -1605376, sin = 806144
Coeff) cos = -22945, sin = 12984
DiskSlip : 254 [SrvTrk]
DiskSlip : 258 [SrvTrk]
PwrOn RRO1x @ H2
Table) cos = -1548544, sin = 703744
Coeff) cos = -83700, sin = 149028
DiskSlip : 240 [SrvTrk]
DiskSlip : 260 [SrvTrk]
TgtCyl: 832
Hd: 0 Zn: 0 Avg.:- 88
TgtCyl: 266176
Hd: 0 Zn: 1 Avg.: 1125
SVCAL(0080,0000)-->PASS
RecordValid Ok : 0407E47D 0007E41D
ReadyTime = 4461207 us
ENG>mS1 00000003
SK C:161356 H:0
SC(U)..4114/114
UD..OK : 114
PK_4 C: 45 H:0
Do you see any errors in this output?
Heads map output:
Code:
ENG>DF 61 4
E:0001
ENG>
HeadsMap: 0000, Bad Head = 0000 =
R-List output:
Code:
Num Defects/Entries: 1
| 0 | FFFFFFFF8 | 3FFF | 00.00 |
Slip-List is very long, it has over 10000 items (factory defects?)
V-List has 2032 elements.
The Flash dump from Samsung SRT was filled with errors (apparently newer drives cannot be dumped by SRT through the serial port).
I would appreciate any help so I can maybe recover some of the data.
The drive is still under warranty so I don't intend to do anything too involved with it (yes I read the various warnings about trying to DIY the drive)
I would just like to see if you have any idea what might be going on with the drive, and if there's any way I could recover some data.
Thanks in advance
FAQ
Search
Login
Register
HDDGURU FILES
