HDD GURU FORUMS

When starting out a repeated clank
I have access to the firmware I managed to make a image, after he starting LBA 63
After the first 10 Gb hard disk that can no longer get regular Clank.
Question would be if they can fix it? or the customer will be content with the data
Any advice is welcome.
Thanks

Terminal log:
CE Log ErrCode=43 LBA=37a66462 Type=5 Add To Pending 37a66462
AT Er 00 Nwt Er 43 RdWr 1ca9d.01.0004
ATA St 50 Er 00 Op ec a,0000/0/00,00 00 00
Niwot: 9ff79ff7 b8 9ff79ff7.3.642 0000 005f 0000 0000
$$SFI
AMR
$$SFI
AMR
DiskAccess ReadSector EC=43 at 01ca9d.01.0004

I'm not an expert but since nobody else answered ...
it seems like a bad sector on SA or a full Glist.
Any how you may be able to push the drive out of safe mode freez.by hard power reset while imaging(disable smart on bios ) and continue .
you may try to manually relocate the bad sector and regenerate the translator (how ever if it retrying on calibration the damage might be on servo/signal calibration sectors)
you may also try to set read retry to 0 and timeout to be very low. To avoid activation of the drive read error function
software glist emulator might also help
at the worst case disabling crc check also disables read error mechanism .
Its also possible to do selective file recovery

Terminal report you posted is small so difficult to tell but you possible have a pending bug, also '$' and 'AMR' errors are most likely related to Servo addressing errors. Maybe heads are not reading well, or platters are shifted slightly?

I see cases of eccentricity where certain areas can be read while others cant, most likely due to differences in density.

If you can provide more info about the failure and any repairs done, or even a longer terminal response you may get a better and more accurate reply.

As it stands it looks like you have both physical errors and maybe a pending bug.

The problem is almost certainly not related to defective blocks in SA or Glist or SMART.

The symptoms here should be properley adressed before attempting further work.

Attempting to recover this data without properley dealing with the problems corretly will only complicate things further.

thought he is saying that the first 10 GB of the drive is readable. The idea about full Glist was that it might cause translator failure pushing the drive into freez mode on first read error when trying to auto add to glist .Assuming pending problems are pending sectors .