Hi all,

ST9320423AS giving me some trouble. When it came in it would spin, give a few head knocks here and there, but stay spinning. Drive stays BSY.

The heads were swapped with a good donor set. Drive has same problem. Next up was to rule out PCB. Replacement with ROM swap was done and still same problem.

The drive spins up, gives a few knocks, sounds OK for a few seconds, a knock or two, quiet again for a while, another knock every now and then. Stays BSY. Can access terminal, level /2 etc.

Terminal commands are giving this error: DiagError 00005014

Rst 0x10M
ASCII Diag mode

F3 T>V40
LED:000000CC FAddr:0024E769
Rst 0x10M
ASCII Diag mode

F3 T>/2

F3 2>U

DiagError 00005014
F3 2>
LED:000000CC FAddr:0024E769
Rst 0x10M
ASCII Diag mode

F3 T>/2

F3 2>Z

DiagError 00005014
F3 2>
LED:000000CC FAddr:0024E769
Rst 0x10M
Rst 0x10M
ASCII Diag mode

F3 T>
ASCII Diag mode

F3 T>
LED:000000CC FAddr:0024E769
Rst 0x10M


Any ideas are most welcome. Symptoms are identical with new heads and PCB as they were when drive had native components.
Thanks.

_________________
Death is nothing, but to live defeated and inglorious is to die daily.
Data Recovery Cape Town

Do the donor's heads on your donor still work fine?

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

Yes, donor heads work in donor drive, patient heads also work in donor drive.

_________________
Death is nothing, but to live defeated and inglorious is to die daily.
Data Recovery Cape Town

Hi,
diag errors 0x5000 - 0x5FFF are Read/Write Errors, and 0x5014 is: "the R/W is not ready to accept requests".
looks like the drive stops before attempting to R/W, are you absolutely sure donor heads are compatible with patient?

Luca

_________________
Data Recovery pro in Italy
www.ultrarecovery.com

Compatibility looks OK if patient is good in donor

i didn't saw it

_________________
Data Recovery pro in Italy
www.ultrarecovery.com

Yes, donor is a good match. Donor images fine with patient heads, so it's not a compatibility issue.

_________________
Death is nothing, but to live defeated and inglorious is to die daily.
Data Recovery Cape Town

Experimenting lots of problems with a Barracuda Green series (ST1000DL002) with this same error due to what it seems the bugs running in the background...quite irritating as can't stop them from running.

I have noticed the error occurs the DiagError 00005014 occurs with any command issued at any level.
Suggestions are welcome, even with PM.

Thanks

Terminal:


Boot 0x20M
Spin Up[0x000246DF]
Trans.

Rst 0x20M
MC Internal LPC Process
Spin Up
(DOS) Table Read FAIL
DOS: MAGIC CONFIG NUMBER MISMATCH
(DOS) Requesting File Save

(DOS) Table Read FAIL
ASCII Diag mode

F3 T>
MediaPartition:

Host LBA Length Disc LBA Length Start Cyl Head
Media Partition 00000000 009999C0 00000000 00133338 00000000 00000000
MC 00000000 00989DC0 00000000 001313B8 00000000 00000000
MSP 009915C0 00000C00 001322B8 00000180 000003F2 00000000
User Partition 009999C0 00133338 000003FD 00000000

MCMainPOR: EXCEPTION: SIM aborted prior to MCMT read
MCMainPOR: EXCEPTION: POR Failed General
MCMainPOR: Feature Disabled...
ASCII Diag mode

F3 T>
ASCII Diag mode

F3 T>/2

F3 2>Z

DiagError 00005014
F3 2>[/b]

MSP MainPOR:
MSP Init Metadata
Buf Bytes/VBM 00000210 DBA Base 40000000
Metadata size in bytes 0040
Num Segments 0060
Logical Sector Alignment 00000000
MSP Reconstruction
MSP Read ScratchPad Section 0000 DiscLBA 001322B8 BlkSize 00000C00 Num Segments 00000060 DiscLba 001322B8 RW_RTL 000F4240
Starting LBA of RW Request=001322B8 Length=00000180
ProcessRWError -Read- at LBA 001322B8 Sense Code=43110081
ERC TO exceeded, orig value in us:FFFFFFFF
MSP LPCDiscXfrScratchPadSegment detected ERROR: StateFlags 00000600 DiscLBA 001322B8
MSP Reconstruction: EXCEPTION: Read ScratchPad Section 00000000
MSP Reconstruction: EXCEPTION: Read MSP Segment Error
Segment 0000StartLBA 009915C0 ErrorLBA 009915C0
Error in MSP Header
Continue MSP Read, PreError Segment Cnt0000
Num Segments 0060
No valid segments found
MSP Read ScratchPad Section 0001 DiscLBA 001322BC BlkSize 00000BE0 Num Segments 0000005F DiscLba 001322BC RW_RTL 000F4240
Starting LBA of RW Request=001322BC Length=0000017C
ProcessRWError -Read- at LBA 001322BC Sense Code=43110081
ERC TO exceeded, orig value in us:FFFFFFFF

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

Hi Nick_CT,

Can you try:
^ X

you get log with this commnad?

Yes, but then stuff still runs in the background and locks up with LED:000000BD FAddr:000058B3
Terminal:

F3 T>
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
41643 99999999 417 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000006B15E L 00000051 BO 000000 BES 00932CA.02932C8.00932CA
42060 417 99999999 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000006B15E L 00000001 BO 000000 BES 00932CA.02932C8.00932CA
44428 2368 8 02 005041 000000 1 00000080 XFR WR SYS LBA B 000000028FDC L 00000008 BO 000000 BES 0042123.0042322.0042123
44436 8 10 02 005041 000000 1 00000080 XFR WR SYS LBA B 0000000643FB L 00000008 BO 000000 BES 0042123.0042322.0042123
11379 4294934239 0 2F 000000 000000 1 00000080 SPN_UP NORMAL
11403 24 8 34 000000 000000 1 00000080 TCC 1
11412 9 8 02 002241 000000 1 00000080 XFR RD SYS LBA B 0000000246DF L 0000000C BO 000000 BES 00A750A.00A7809.00A750A
11420 8 415 02 002241 000000 2 C3160080 XFR RD SYS LBA B 00000002913D L 00000008 BO 000000 BES 004BFC0.004C23F.004BFC0
11835 415 2826 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000002913D L 00000001 BO 000000 BES 004BFC0.004C23F.004BFC0
14661 2826 417 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000006455C L 00000008 BO 000000 BES 004BFC0.004C23F.004BFC0
15078 417 2764 02 002241 000000 2 C3160080 XFR RD SYS LBA B 00000006455C L 00000001 BO 000000 BES 004BFC0.004C23F.004BFC0
17843 2765 8 02 005041 000000 1 00000080 XFR WR SYS LBA B 00000002913D L 00000001 BO 000000 BES 004BFC0.004BFFF.004BFC0
17852 9 9 02 005041 000000 1 00000080 XFR WR SYS LBA B 00000006455C L 00000001 BO 000000 BES 004BFC0.004BFFF.004BFC0
17862 10 10 02 005041 000000 1 00000080 XFR WR SYS LBA B 00000002913D L 00000008 BO 000000 BES 004BFC0.004C1BF.004BFC0
17872 10 10 02 005041 000000 1 00000080 XFR WR SYS LBA B 00000006455C L 00000008 BO 000000 BES 004BFC0.004C1BF.004BFC0
17882 10 418 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000002913D L 00000008 BO 000000 BES 004BFC0.004C23F.004BFC0
18300 418 2825 02 002241 000000 2 C3160080 XFR RD SYS LBA B 00000002913D L 00000001 BO 000000 BES 004BFC0.004C23F.004BFC0
21125 2825 417 02 002241 000000 2 C3160080 XFR RD SYS LBA B 00000006455C L 00000008 BO 000000 BES 004BFC0.004C23F.004BFC0
21542 417 2826 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000006455C L 00000001 BO 000000 BES 004BFC0.004C23F.004BFC0
24368 2826 406 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000002F98A L 00000001 BO 000000 BES 0063B01.0063B40.0063B01
24774 406 2834 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000002F98A L 00000001 BO 000000 BES 0063B01.0063B40.0063B01
27608 2834 408 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000006ADA9 L 00000001 BO 000000 BES 0063B01.0063B40.0063B01
28017 409 2833 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000006ADA9 L 00000001 BO 000000 BES 0063B01.0063B40.0063B01
30856 2839 408 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000002B877 L 00000190 BO 000000 BES 0042363.0048762.0042363
31265 409 2834 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000002B877 L 00000001 BO 000000 BES 0042363.0048762.0042363
34121 2856 406 02 002241 000000 2 43110081 XFR RD SYS LBA B 000000066C96 L 00000190 BO 000000 BES 0042363.0048762.0042363
34527 406 2835 02 002241 000000 2 43110081 XFR RD SYS LBA B 000000066C96 L 00000001 BO 000000 BES 0042363.0048762.0042363
37376 2849 9 02 005041 000000 1 00000080 XFR WR SYS LBA B 00000002FD5D L 00000001 BO 000000 BES 0042063.00420A2.0042063
37535 159 10 02 005041 000000 1 00000080 XFR WR SYS LBA B 000000028FDC L 00000008 BO 000000 BES 0042123.0042322.0042123
37545 10 10 02 005041 000000 1 00000080 XFR WR SYS LBA B 0000000643FB L 00000008 BO 000000 BES 0042123.0042322.0042123
37555 10 419 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000002FD3F L 00000051 BO 000000 BES 00932CA.02932C8.00932CA
37975 420 99999999 02 002241 000000 2 43110081 XFR RD SYS LBA B 00000002FD3F L 00000001 BO 000000 BES 00932CA.02932C8.00932CA

MSP MainPOR:
MSP Init Metadata
Buf Bytes/VBM 00000210 DBA Base 40000000
Metadata size in bytes 0040
Num Segments 0060
Logical Sector Alignment 00000000
MSP Reconstruction
Rst 0x20M
MC Internal LPC Process
Spin Up
LED:000000BD FAddr:000058B3

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

Can You read Mods?

No. No longer can access the drive/terminal once the LED:000000BD FAddr:000058B3 error throws.

Matter of fact, I only have terminal access for like 2-3 seconds, which allows me to throw a command (like I did with CTR x), and the bug I guess kicks in again, locking the terminal. Thereafter, the LED:000000BD FAddr:000058B3 shows and the terminal is unresponsive.

All this time the drive only stays busy, never gets ready. Never spin down.

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

Can you take a look to all HDD platters surfaces, maybe one (or moore) is badly.

All? How?

Top, nothing significant. Plus, If there was significant damage, then the drive would have likely spun down.

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

I think the problem maybe in any head.

Anybody have another way?

Thanks

PM sent

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

I should have started a new thread for this case at the time.

Anyway, I closed this case as unrecoverable. The patient's heads were indeed damaged based on tests on donor drive. The patient killed a couple of donor heads in recovery attempts.

Thanks for the PMs and help with ideas from other.

Learned few interesting things from this case.

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

Hi Dear Bro Labtech
Hi Have Solved More Then 6 Case 1 Bcoz Of Its Have Defrent Problem.
Contact Me On My MSN I Will Send You My Case Studies And Solution.
Dont Apply Any Translator Regenaration Command Other Wise Your Drive Stuck In Partial Sector Access Problem.
I Have Solve This Type Of Case Without Any Translator Command.

Yours Friend
Jignesh Pankhania

Dear Friend NickCT

Sorry To Say But Your Diagnotic Is Wrong Your Drive Have No Head Problem.
Look At Messege Its Give The LED:000000CC FAddr:0024E769 See And Thing When And Why This Error Comes.
You Change Head But Its Not Need Your Case Solved Without Change The Head.
If You Change 10 Donor Head Then Also Your Drive Not Fixed By Head Change.
Pm Me I Will Suggest If My Solution Work For You Then I Am Happy To Help You.
Sorry For My Bad English.

Yours Friend
Jignesh Pankhania

Heads were everything but fine or at least there was something else wrong.



The doubt is IF head swap procedure was totally flawless, assuming it was OK at this point the only thing that can tell is media analysis.