Seagate ST3320620AS not ready

[ccc]

Hi guru's

I have with me a seagate 7200.10 Sata drive, 320 Gb, with a very strage behavior. Drive is powering up properly, recalibrates and right after that start to do a sound like that when a bad sector has been encountered...no clicking no other sounds....only "crrr" for several times and after a while the sound is the same but it is a bit quickly compared with firsts sounds....I hope i've been clear enough .The big problem is some data is wanted from this hdd.

Ok.You will ask for terminal log.Here it is:

Reset4096k x 32 DRAM
GALAXY - 1_Disk S-6B 08-30-06_15:36

Buzz HM SFI
!
(P)SATA Reset
(H)SATA Reset
AT Er 00 Nwt Er 37 RdWr 144ef.00.0134
ATA St 50 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: 97f29ff7 b6 97f29ff7.3.640 0000 005f 0000 0000
DiskAccess ReadSector EC=43 at 0144ef.00.0134

CE Log ErrCode=37 LBA=1a72a1fa Type=5 Add To Pending 1a72a1fa
AT Er 00 Nwt Er 37 RdWr 144ef.00.0135
ATA St 50 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: 9ff79ff7 b6 9ff79ff7.3.640 0000 005f 0000 0000
DiskAccess ReadSector EC=43 at 0144ef.00.0135

CE Log ErrCode=37 LBA=1a72a1fb Type=5 Add To Pending 1a72a1fb

CE Log ErrCode=37 LBA=1a72a0c6 Type=6aAT Er 00 Nwt Er 37 RdWr 144f2.00.0387
ATA St 50 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: 97f29ff7 b6 97f29ff7.3.640 0000 005f 0000 006a
DiskAccess ReadSector EC=47 at 0144f2.00.0387

CE Log ErrCode=37 LBA=1a72b131 Type=5 Add To Pending 1a72b131

CE Log ErrCode=37 LBA=1a72adaa Type=6aAT Er 00 Nwt Er 37 RdWr 144f5.00.018e
ATA St 50 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: 97f29ff7 b6 97f29ff7.3.640 0000 005f 0000 006a
DiskAccess ReadSector EC=47 at 0144f5.00.018e

CE Log ErrCode=37 LBA=1a72bc1c Type=5 Add To Pending 1a72bc1c

CE Log ErrCode=37 LBA=1a72ba8e Type=6aAT Er 00 Nwt Er 37 RdWr 144f6.00.00e5
ATA St 50 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: 97f29ff7 b6 97f29ff7.3.640 0000 005f 0000 006a
DiskAccess ReadSector EC=43 at 0144f6.00.00e5

CE Log ErrCode=37 LBA=1a72bfbf Type=5 Add To Pending 1a72bfbf
AT Er 00 Nwt Er 37 RdWr 144f6.00.00e6
ATA St 50 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: 9ff79ff7 b6 9ff79ff7.3.640 0000 005f 0000 006a
DiskAccess ReadSector EC=47 at 0144f6.00.00e6

CE Log ErrCode=37 LBA=1a72bfc0 Type=5 Add To Pending 1a72bfc0

CE Log ErrCode=37 LBA=1a72beda Type=6aAT Er 00 Nwt Er 37 RdWr 144f8.00.03e2
ATA St 50 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: 97f29ff7 b6 97f29ff7.3.640 0000 005f 0000 006a
DiskAccess ReadSector EC=43 at 0144f8.00.03e2

....................................Starting from this it's very quick

CorrectWriteStart
AT Er 00 Nwt Er 22 RdWr 144fa.00.02e4
ATA St 50 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: 1a72d2ee 14 1a72d2ee.a.9d0 0001 3926 02e5 0000

CorrectWriteStart
AT Er 00 Nwt Er 22 RdWr 144fa.00.02e4
ATA St 50 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: 1a72d2ee 14 1a72d2ee.a.9d0 0001 3926 02e5 0000

CorrectWriteStart
AT Er 00 Nwt Er 22 RdWr 144fa.00.02e4
ATA St 50 Er 01 Op 00 0,0000/0/00,00 01 00
Niwot: 1a72d2ee 14 1a72d2ee.a.9d0 0001 3926 02e5 0000

and so on.....
Here is the complete log:

ST.log

(25.67 KiB) Downloaded 577 times

I want to mention that the 144xx cylinder is not in SA.SA is from 15CAA to 15E29 cylinder.
I can stop this messages only if I press Ctrl+z to go into terminal or with power off/on.What i have done so far:

In victoria for win i can scan in both modes , verify and read, and the messages stops.Same for mhdd or any other program that can do scan in lba. In terminal I can read and write in SA with head 0 ( i changed the age from 50 to 4f and viceversa, cleared smart and other nondestructive commands). So it looks that head 0 is ok.

I tryed some recovery/cloning programs , for win and for dos , but almost every program tell that the recovery/clone will take hundreds of days, because the program reads 256 sector and after that takes a pause of ~1 min , in this time the hdd shows those errors in terminal. Starting from "Correct write start" message the hdd is Busy and all programs are blocked.

Does anyone have any ideas how to make it stop to try to recover some files from it?

Any help will be much appreciated.

PS. Sorry for the long post but i wanted to be as clear as possible.

[dobrevjetser]

Hi CCC,

If you have pc3K UDMA, you can make a data copy with DE, using the option "use pc3k utility" and putting the baudrate at maximum.

Best regards,

Dobre

[ccc]

Hi Dobre

Thanks for reply......unfortunately i don't have PC3k UDMA. But from what u say i understand that the data can be copyed thru com port. Is this correct?

Rgds

[beto]

This is the typical Error on Barracuda Family DiskAccess ReadSector EC=43 , on this cases are a little choice or tried to get, sectors , using "hardware control" from the own MHA , or did a MHA swap,

Best Regards

[ccc]

Hi Beto

I know this is a tipical error on seagate but why right after power up starts to do like this?....looks like those errors are in a log or something because every time i power up it starts from the same point, mean from there: AT Er 00 Nwt Er 37 RdWr 144ef.00.0134....

Thanks
Rgds

[ccc]

Hi

Good news....All necessary data (about 9 Gb ) recovered.....And all of this without PCI or UDMA.

Only a lot of work in terminal ...and of course a little brain.

Thank you all who have replyed.

Rgds