Seagate 7200.12 1.5TB
ST1500DL003
Firmware: CC32

Data is critical.

Log from terminal:

Rst 0x40M
MC Internal LPC Process
User Data Base 00990110

MCMainPOR: Start:
MCInitialize: Start: Buffer Words VBM: 00000210
MCMainPOR: EXCEPTION: MC Init Fail. Feature disabled.
MCMainPOR: MCTBufferPtr->Header.MCStateFlagsDisc = E59FF018
MCMainPOR: MCTBufferPtr->Header.MCTStateFlags = 0000F018
MCMainPOR: MCStateFlags = 00000000

MCMainPOR: EXCEPTION: POR Failed General
No HOST FIS-ReadyStatusFlags 0002A1A5
ASCII Diag mode


F3 T>/1

F3 1>N1

Init SMART Fail
Rst 0x40M
MC Internal LPC Process
LED:000000BD FAddr:00004C51

[terminal hangs, restart of the terminal connection]

F3 T>V1
User Slip Defect List
log log log phys phys
LBA span cumm cyl hd sctr zn cyl sctr SFI PBA
0 0 0 0 0 0 0 0 0 A 0


Head 0: entries 1 slips 0
Head 1: entries 0 slips 0
Head 2: entries 0 slips 0
Head 3: entries 0 slips 0
Head 4: entries 0 slips 0
Head 5: entries 0 slips 0
Total Entries 1 Total Slips 0

F3 T>V2
System Slip Defect List
log log log phys phys
LBA span cumm cyl hd sctr zn cyl sctr SFI
0 0 0 0 0 0 0 21DCB 0 FFFFFFFF 0

3B41F B9E1 B9E1 0 1 0 1 20ED0 0 FFFFFFFF 46E00

7683E B9E1 173C2 0 2 0 2 20B28 0 FFFFFFFF 8DC00

B1C5D B9E1 22DA3 0 3 0 3 23037 0 FFFFFFFF D4A00

ED07C B9E1 2E784 0 4 0 4 1F824 0 FFFFFFFF 11B800

12849B B9E1 3A165 0 5 0 5 215FC 0 FFFFFFFF 162600

1638BA B9E1 45B46 120 0 0 6 21EEB 0 FFFFFFFF 1A9400

19ECD9 B9E1 51527 120 1 0 7 20FF0 0 FFFFFFFF 1F0200

1DA0F8 B9E1 5CF08 120 2 0 8 20C48 0 FFFFFFFF 237000

215517 B9E1 688E9 120 3 0 9 23157 0 FFFFFFFF 27DE00

250936 B9E1 742CA 120 4 0 A 1F944 0 FFFFFFFF 2C4C00

28BD55 B9E1 7FCAB 120 5 0 B 2171C 0 FFFFFFFF 30BA00


Head 0: entries 2 slips B9E1
Head 1: entries 2 slips 173C2
Head 2: entries 2 slips 173C2
Head 3: entries 2 slips 173C2
Head 4: entries 2 slips 173C2
Head 5: entries 2 slips 173C2
Total Entries C Total Slips 7FCAB

F3 T>V4

Reassigned Sectors List
Entries: 0000, Alts: 0000, Removed: 4011, Pending: 0000

Idx LBA PBA LLLCHS of LBA PLPCHS of PBA SFI Hours Msecs S
tatus BBM Mask
F3 T>V40

DiagError 00000007

[...terminal hangs...]

I did NOT try the following commands, because of the obvious danger:
F3 T>i4,1,22
F3 T>m0,6,2,,,,,22

Any help is appreciated.

Further investigations:

F3 T>/7

F3 7>X

Head 00 Resistance 0119
Head 01 Resistance 00E3
Head 02 Resistance 010F
Head 03 Resistance 010C
Head 04 Resistance 015F
Head 05 Resistance 00F6

Maybe this helps somebody to suggest me anything useful. Any others commands I could eventually execute?

Seems like a mechanical issue.
Drive is from an external enclosure? If yes, did it sustain a physical shock?

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

It was working fine for a long time. Just before it stopped working I had it connected through external USB adapter. It suffered no shock for sure.

Additional commands:

F3 1>N5
Att
Num Flgs normlzd worst raw
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000

F3 1>/2

F3 2>s0,0,22

F3 2>A
Current Addr Mode
PLP CHS Mode, Seq In
Hd 0 Cyls 000000 - 0396CB
Hd 1 Cyls 000000 - 039112
Hd 2 Cyls 000000 - 03773D
Hd 3 Cyls 000000 - 03BE15
Hd 4 Cyls 000000 - 035AC2
Hd 5 Cyls 000000 - 0390E6

All Addr Modes
User LBA Mode
LBAs 00000000 - 15EB6EDA
System LBA Mode
LBAs 00000000 - 002C7173
User LLL CHS and User LLP CHW Modes
Hd 0 Cyls 000000 - 038EBE
Hd 1 Cyls 000000 - 0388D8
Hd 2 Cyls 000000 - 036F39
Hd 3 Cyls 000000 - 03B5A5
Hd 4 Cyls 000000 - 035306
Hd 5 Cyls 000000 - 0388D0
System LLL CHS and System LLP CHW Modes
Hd 0 Cyls 000000 - 000210
Hd 1 Cyls 000000 - 000210
Hd 2 Cyls 000000 - 000210
Hd 3 Cyls 000000 - 000210
Hd 4 Cyls 000000 - 000210
Hd 5 Cyls 000000 - 000210
PLP CHS and PLP CHW Modes
Hd 0 Cyls 000000 - 0396CB
Hd 1 Cyls 000000 - 039112
Hd 2 Cyls 000000 - 03773D
Hd 3 Cyls 000000 - 03BE15
Hd 4 Cyls 000000 - 035AC2
Hd 5 Cyls 000000 - 0390E6

Buffer Sector Offset 00000000

F3 2>.
Current R/W User LBA 000000000000 LLL CHS 000000.0.0000 PLP CHS 000000.0.0000
R/W Status 1 R/W Error 00000080 Ready


F3 2>R0,1

F3 2>^X
ATA 15 Cmds
Ts(ms) dT(ms) Op Cnt LBA
0 99999999 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000

RW 32 Cmds
Ts(ms) dT(ms) xT(ms) Type Option Mode St EC Info
22410 99999999 12 02 002241 000000 1 00000080 XFR RD SYS LBA B 00000
0024705 L 000000CA BO 000000 BES 008EDCA.0092049.008EDCA
22429 19 271 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000
0028FF6 L 00000018 BO 000000 BES 008EDCA.05FFFFF.008EDCA
22700 271 2787 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000
0028FF6 L 00000001 BO 000000 BES 008EDCA.05FFFFF.008EDCA
25488 2788 394 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000
0064415 L 00000018 BO 000000 BES 008EDCA.05FFFFF.008EDCA
25882 394 2847 02 002241 000000 2 C3160080 XFR RD SYS LBA B 00000
0064415 L 00000001 BO 000000 BES 008EDCA.05FFFFF.008EDCA
28729 2847 390 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000
0026865 L 00000935 BO 000000 BES 005FA01.0084740.005FA01
29119 390 2848 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000
0026865 L 00000001 BO 000000 BES 005FA01.0084740.005FA01
31982 2863 279 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000
0061C84 L 00000935 BO 000000 BES 005FA01.0084740.005FA01
32261 279 2777 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000
0061C84 L 00000001 BO 000000 BES 005FA01.0084740.005FA01
35063 2802 19 02 002241 000000 1 00000080 XFR RD SYS LBA B 00000
002B877 L 00000190 BO 000000 BES 003E333.0044732.003E333
35084 21 8 02 005041 000000 1 00000080 XFR WR SYS LBA B 00000
002FD5D L 00000001 BO 000000 BES 003E033.003E072.003E033
35186 102 5 02 005041 000000 1 00000080 XFR WR SYS LBA B 00000
0028FDC L 00000008 BO 000000 BES 003E0F3.003E2F2.003E0F3
35192 6 9 02 005041 000000 1 00000080 XFR WR SYS LBA B 00000
00643FB L 00000008 BO 000000 BES 003E0F3.003E2F2.003E0F3
35202 10 408 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000
002FD3F L 00000051 BO 000000 BES 008EDCA.05FFFFF.008EDCA
35610 408 2838 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000
002FD41 L 00000001 BO 000000 BES 008EDCA.05FFFFF.008EE4A
38448 2838 395 02 002241 000000 2 C3160080 XFR RD SYS LBA B 00000
006B15E L 00000051 BO 000000 BES 008EDCA.05FFFFF.008EDCA
38843 395 2850 02 002241 000000 2 C3160080 XFR RD SYS LBA B 00000
006B17A L 00000001 BO 000000 BES 008EDCA.05FFFFF.008F4CA
41694 2851 2 02 005041 000000 1 00000080 XFR WR SYS LBA B 00000
0028FDC L 00000008 BO 000000 BES 003E0F3.003E2F2.003E0F3
41697 3 9 02 005041 000000 1 00000080 XFR WR SYS LBA B 00000
00643FB L 00000008 BO 000000 BES 003E0F3.003E2F2.003E0F3
41707 10 10 02 005041 000000 1 00000080 XFR WR SYS LBA B 00000
0028FDC L 00000008 BO 000000 BES 003E0F3.003E2F2.003E0F3
41717 10 10 02 005041 000000 1 00000080 XFR WR SYS LBA B 00000
00643FB L 00000008 BO 000000 BES 003E0F3.003E2F2.003E0F3
41737 20 0 47 000000 000000 1 00000080 DISC_SLIP
52603 10866 8 02 002241 000000 1 00000080 XFR RD SYS LBA B 00000
002BA07 L 00000180 BO 000000 BES 0032000.0037FFF.0032000
52613 10 11 02 002241 000000 1 00000080 XFR RD SYS LBA B 00000
002BB87 L 00000100 BO 000000 BES 0038000.003BFFF.0038000
52625 12 0 27 002241 000000 1 00000080 SND_SRV 516F 0000 0000
0000 0000 0000 0000 0000 0001 003B 00D0
0000 0000 0000 0007 00
03 F470 F930 3F39 0003 0000 0000 0000 0000 0000 0000 0000
52625 0 1 27 002241 000000 1 00000080 SND_SRV 0501 0000 0000
0000 0000 0000 0000 0000 0001 016C 00D0
016C 0000 0000 0007 00
03 F470 F930 3F39 0003 0000 0000 0000 0000 0000 0000 0000
52626 1 0 27 002241 000000 1 00000080 SND_SRV 0106 0000 0000
0000 0000 0000 0000 0000 0001 016C 00D0
016C 0000 0000 0007 00
03 F470 F930 3F39 0003 0000 0000 0000 0000 0000 0000 0000
52626 0 0 27 002241 000000 1 00000080 SND_SRV 0501 008F 0000
0000 0000 0000 0000 0000 0001 4E4D 00D0
4E4D 0000 0000 0007 00
03 F470 F930 3F39 0003 0000 0000 0000 0000 0000 0000 0000
206749 154123 20 00 002024 000000 1 00000080 SEEK RD USR SEC CH 000
000.0
206769 20 0 27 002024 000000 1 00000080 SND_SRV 0501 00B3 0000
0000 0000 0000 0000 0000 0001 E052 00D0
E052 0000 FFFD 3D5C 00
03 F470 F930 3F39 0003 0000 0000 0000 0000 0000 0000 0000
206769 0 0 27 002024 000000 1 00000080 SND_SRV 0101 E052 0000
0000 0000 0000 0000 0000 0001 5875 00D0
E052 0000 FFFD 3D5C 00
03 F470 F930 3F39 0003 0000 0000 0000 0000 0000 0000 0000
294713 87944 9 02 002221 000000 1 00000080 XFR RD USR LBA B 00000
0000164 L 00000001 BO 1000213 BES 00B7080.00E23C9.00B7080

So, does that mean I can read data from the given sector through terminal and that the reading at all is fine?
If so - maybe there you know any device/method to read by sectors, to save data?

[Previous post is waiting for moderator to be approved.]

No shock at all, I had it connected through USB adapter, some day it stopped working just like that. Maybe the voltage dropped abnormally?

Check the results on the heads test you posted! Do you see something standing out?
Also, why do you think the drive hangs randomly and mysteriously?

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

I think labtech is suggesting (reading through the lines because he cannot speak clearly) that you try to disable the faulty head but he is not able to tell you how to do it.

Thank you for the support.

According to head resistance - I can see the 5th head has significantly higher value than the others. Is that mean it's faulty? Is there any method to switch the particular head off? I don't have any other tool except USB-TTL. I found out:

"How to use the PC-3000 UDMA to recover data
The most frequent reasons of HDD damage:
- failure of one or more magnetic-resistance heads
...
If one of the magnetic heads is damaged, we can get data access through the remaining heads using “MR-Head Shift technology”. The damaged head is substituted by the adjacent correct magnetic head. It allows for keeping the integrity of the translated data and for reading big data volumes without having to exchange the head stack."

But sadly I don't have such a device.

Might anybody advise anything more please?

I honestly don't know the cause of the failure. With very small probability my child could have had the access the drive and had it dropped, I simply can't be sure.

Seagate 7200.12 has many defects and is not reliable at all, in fact Seagate is not reliable for me. The only HDD i had personally that failed were all Seagate's.
But it is well known that 7200.12 has many firmware bugs, you can see how many forum post there is about those series, and i've done one as well.

Your SMART values output is 00s across the board, did you clear the SMART on the drive?

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

At very first I tried, but (I supppose) with no success:

F3 1>N1

Init SMART Fail
Rst 0x40M
MC Internal LPC Process
LED:000000BD FAddr:00004C51

[terminal hangs]

After the restart of the terminal I executed N5 command and it showed that SMART is cleared.

I still think the main problem is mechanical, then firmware issues, likely bad sectors will be an issue as well, etc.
Don't see an easy way out for data recovery without advanced tools and experience.

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

I tried play with congen a bit (it's reversible) and checked if it's visible in MHDD, it's not, unfortunatelly.

I consider try regenerating translator with m0,2,2,,,,,22 (without erasing nrg-list with i4..), or m0,6,3,,,,,22. Is there any danger with regenerating?

Then clear SMART and the same basic congen commands, then MHDD check, then ddrescue.

What you guys think?

I agree with labtech, you must first deal with the physical before logical issues. If the data is of no value and you don't care that you are very likely going to destroy any chance of professional recovery (or make it very expensive), go for it. Otherwise stop screwing around and have it assessed by a professional lab before it is too late.

_________________
Luke
Recovery Force Data Recovery

Ooops, sorry, I missed this part.
No, that is not what I am suggesting. Just saying it is likely a faulty head.

But if I was, then, well, let's see..
Disabling a head won't provide access to all data. If imaging drive with one or more disabled heads, then we won't have a complete image, so no access to all data as well. Result = corrupt files

Okay...
choice 1: buy chip programmer, desolder your ROM, dump ROM and study Seagate ROM(s) until you are fed up losing hair from so much scratching by studying bytes in hex view and determine what is what and for which head and and then what bytes you need to modify to make it inactive/disabled
choice 2: find somebody who has a DR tool that does this, borrow or rent it and modify the ROM yourself once learning how to do
choice 3: if can't borrow or rent, then ask the guy to reverse engineer what the tool does by again studying ROM(s) and changes in hex (doubt he will do it for free OR provide the info for free as he is probably going bold as well by now if he pursued this (doubt it) and that hair is worth something to him)
choice 4: this is cheaply feasible potentially, buy programmer, desolder ROM, dump ROM, send it to somebody who is willing to do this for free or cheap, have them loaded in their tool, modify the ROM by disabling the agreed head(s), save it, then send it back to you, reprogram the ROM back to your EEPROM, then you resolder it, then test. Not working? Crap, have to this again all over...
choice 5: just buy the DR tool, which is not feasible, but let's say you do and you manage to disable to head(s). Then what? Still no files, as we are back at square one.
choice 6: if the drive supports it and it is possible, disable head from the terminal (not sure about this), but we will back at square one again.

Clear enough? I am sure there other more creative ways to do this, but this is all my brain has this afternoon.

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

I'm exhausted just reading that last post.

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company

Hey, it took a lot of exhaustion to learn without tools or make money to buy the tools you have now, no?

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

That's a YES.

_________________
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners