ST3320620AS BSY, BIOS Problem

[MioNudzik]

Hello

I have a problem with my HDD it’s”
Seagate 7200.10
320GB
S/N: 9QF6QWAD
ST3320620AS
P/N: 9BJ14G-308
FW: 3.AAK
DC: 08083
S.C.: TK
Chip: LSI TTB4398A0

A few days ago, HDD work and the next day it was detected by BIOS and Sys (win7 64bit) but I could’t access to files. After restarting, PC barely passed the POST and hung on system start up for some time. When I go to "My Computer" there was no partitions of ST3320620AS – Windows doesn’t detect it. I have checked this HDD on another PC and the same problem appeared.

The behavior of this HDD is the same as if he have a problem with BSY or SAMRT but it is detected by bios(320GB).

Month or two ago I Ihad a problem with a different HDD it was Seagate 7200.11 500GB. I fixed it by using the RS232->TLL terminal
http://sites.google.com/site/seagatefix/Home
ON ST3320620AS I tried to use
http://www.msfn.org/board/topic/133604-seagate-720010-hdds-how-to-fix-bsy-state-too/
http://web.archive.org/web/20100416080308/http://www.datarecoverystory.com/2009/07/typical-data-recovery-case-for-7200-9-and-7200-10/
but no result
Log from Terminal

Reset
8192k x 16 DRAM
GALAXY - 1_Disk S-7A 12-08-06_16:32

Buzz HM SFI
!
(P)SATA Reset
carve writes(H)SATA Reset
carve writesAT Er 00 Nwt Er 37 RdWr 0c74d.01.0006
ATA St 80 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: 97f29ff7 b8 97f29ff7.3.640 0000 005f 0000 0000
DiskAccess ReadSector EC=43 at 00c74d.01.0006

CE Log ErrCode=37 LBA=116afb24 Type=5 Add To Pending 116afb24
AT Er 00 Nwt Er 37 RdWr 0c74d.01.000a
ATA St 80 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: 9ff79ff7 b8 9ff79ff7.3.640 0000 005f 0000 0000
DiskAccess ReadSector EC=43 at 00c74d.01.000a

CE Log ErrCode=37 LBA=116afb28 Type=5 Add To Pending 116afb28
AT Er 00 Nwt Er 37 RdWr 0c74d.01.000b
ATA St 80 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: 9ff79ff7 b8 9ff79ff7.3.640 0000 005f 0000 0000
DiskAccess ReadSector EC=43 at 00c74d.01.000b

CE Log ErrCode=37 LBA=116afb29 Type=5 Add To Pending 116afb29
AT Er 00 Nwt Er 37 RdWr 0c74d.01.000e
ATA St 80 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: 9ff79ff7 b8 9ff79ff7.3.640 0000 005f 0000 0000
DiskAccess ReadSector EC=43 at 00c74d.01.000e

it goes to
T>

Does anyone know how to solve the problem with this HDD?
What does the LOG from terminal means?

Right now I’m trying to get new PCB mayby it helps.
I need to recover the date from this HDD.


Thanks in advance for your help

[northwind]

Looks like the pending bug to me.

[BlackST]

Being a GALAXY can be something worse.... precise diagnose is needed.

[MioNudzik]

After Seatool long test i got this.



BIOS and Seatool is deteting HDD and nowhere else.

[poehere]

From this log it is not busy error or 0 LBA error it is seeing correct drive, name and LBA. Problem is else where. Like BlackST said you need proprer diagnostics to fix this one. Sorry it can not be done with the BSY or 0 LBA fix on it.

[northwind]

I still insist that this COULD be the pending bug (not the bsy bug).

[MioNudzik]

http://www.hardmaster.info/eng/articles/20-01-2009.html

I think i have the same problem.

What are the costs of such repairs/data recover?

[pcimage]

I still insist that this COULD be the pending bug (not the bsy bug).

I Agree

[Nick_CT]

I still insist that this COULD be the pending bug (not the bsy bug).

+1

[drc]

With pending bug it would take a lot longer than 40 minutes to read 300 million LBAs (I'm assuming read scan starts at the beginning)

[Nick_CT]

I have a Nighthawk plus at the moment with pending bug and a bad head. On the bad head it will read a few LBAs per second for quite a while, then have a good burst of a few hundred thousand and then back to snails pace again, whilst started up with LDR. Funny little monster.

[poehere]

I still insist that this COULD be the pending bug (not the bsy bug).

I agree with you on this one. He said he tried to use the 0LBA and BSY fix and I said it is not this problem. It is another problem and another pending bug problem on this drive and he can not fix it the way he was trying to do it

[pcimage]

I still insist that this COULD be the pending bug (not the bsy bug).

I agree with you on this one. He said he tried to use the 0LBA and BSY fix and I said it is not this problem. It is another problem and another pending bug problem on this drive and he can not fix it the way he was trying to do it

Exactly so.

"Pending" bug is competely different to "BSY" or "LBA 0" and so the "one size fits all" Internet solutions will not fix this.

[northwind]

Exactly.

There is no DIY fix for the pending bug, and applying the bsy bug "internet fix" to these drives, can end up in quite a mess.

[labtech]

Nice catch drc. Always studying the details...

Need a good hardware imager to recover the data off this drive. A pro can help you out.

Should still be relatively low cost at this point if stop messing around with it.

[positivebit]

it's pending bug to me (+2)
ps. sometimes heads become extremely weak and need to be swapped also.

[northwind]

well it also took 36 minutes to read 62m LBA.