segate 7200.12 translation problem

[sigmaalv]

i have a seagate following model. its 7200.12

Model : ST3320613AS
Firmware : CC2J
Capacity : 298.09 GB (625 142 448).

###### i can read sectors from some regions in DE. but most of the sectors cannot read. i get following error on terminal

Starting LBA of RW Request=0CD8B2CF Length=FFFFFFFF
ProcessRWError -Read- at LBA 0CD8B2CF Sense Code=43110081
Unrecoverable Error Reported
Starting LBA of RW Request=0CD8B2D0 Length=FFFFFFFF
ProcessRWError -Read- at LBA 0CD8B2D0 Sense Code=C4090082
Unrecoverable Error Reported
Starting LBA of RW Request=0CD8B2D1 Length=FFFFFFFF
ProcessRWError -Read- at LBA 0CD8B2D1 Sense Code=C4090082
Unrecoverable Error Reported.

######if i select command to read " Avtice pc3000 Utility" with no to message " transfer data inspite of error" i can read the sectors.
but its very very slow ie 1sector/second. but not sure abt the integrity of data.

####### i did " recover translator command" . but i get following error

Switching Autoreassign OFF...
Obtaining Saved Mode Pages File information...
Reading Saved Mode Pages...
Parsing Saved Mode Pages...
SMP Dbl: 0x3C000317 - 0x037FF7FF (0x0000000F)

G-List erase...

Regenerate translator
Result............................................ : Ok

HDD ID reading...
Detecting defects hiding cmd type...
G-List erase...

Start scanning...
"Fork" searching: 0 - 625142447
Verification error 48-bit (UNC)
Translation "fork" direction detection ambiguity!
Correct it manually!
LBA : 85655454.

#### i added this sector 85655454 to defect list and saved . then run " recover translator" but still i get same error.

any solution? ace supports tried to solve this problem. but the could't . pls help me

with regards
sigmaalv

[labtech]

what is the customer's description of how this drive failed?

[Nick_CT]

If you look in the Seagate section of the ACE forum there is a solution for this problem.

[pcimage]

I had a similar case on a 1Tb 7200.12 that couldn't solve in time/cost for client, drive wouldn't go past a certain LBA.

Either manually or using UDMA "routine" with hundreds/thousands of defect relocations the bad spot hardly progressed at all.

Mind you, the one I had had been opened by the "local computer guy" (what the hell he was looking for in a drive that sounded normal and ID'd OK) and so was contaminated. Or maybe he had applied the "universal LBA0 fix" ( ) and fiddled more with the terminal commands.

Again using "read by utility" I could read random sectors all over the disk but very slowly.

In the end the case was abandoned as the time involved was clocking up, and it was only schoolwork on the drive so the cost would have been prohibitive.