Hello all, thank you for the replies.
Changes to mod 32 are definitely saved when using the 'automatic' slow responding fault. Attempts have also been made to manually alter mod 32 and also use a donor mod 32. The changes are saved, but no difference is made to the performance of the drive. Attempts have also been made to solve the 'Slow Responding' in RAM as per :
http://blog.acelaboratory.com/pc-3000-f ... write.htmlI'll have a try with @lifeguarddubai suggestions of changing the soft/hard reset options. Information below about head-map issues.
It is worth noting that the service area reads at full speed. Normally when a HDD has a the 'slow responding' issue the ROM and SA read very slowly too. In this case only the LBA areas do. This potentially suggests that the fault does not relate to the 'slow responding' issue, but merely has symptoms that are very similar to it. Perhaps there is some sort of donor PCB compatibility issue or other fault. That being said the original USB based PCB was providing the same symptoms when used.
For reference
Patient PCB: 2060-800041-003 REV P1
Donor PCB: 2060-800022-001 REV P1
With respect to original drive failure - the user reported that the disk was slowing down/hanging. He kept trying to read from the disk, until the point where it was no longer detected by the computer. I admit this seems like as classic case of bad sectors leading to 'slow responding'.
Below I have copied some of my correspondence with Ace TS on actions performed which they requested so you all have an idea of what tests have been performed.
Finally, I've left the drive reading for a day - 5GB of data was recovered (no read errors) at the 64Kb/s. As you can probably guess the owner of the HDD has a large amount of data on the disk otherwise I would simply 'wait it out'. Time to completion for imaging would be 200+ days.
Best regards,
John
------
Ace TS correspondence:Trying what you suggested:
Mod 02 from head 0 was read. The specified area was filled with "00" to the end of the module. I have attached a screenshot so you can check that I have chosen the correct start point.
The "CS recalc" function was run.
The new altered module was written back to head 0 and 1.
HDD was powered off.
When HDD was powered on, there were two loud clicks and HDD went to ERR. With soft / hard reset it is possible to get to RDY. When entering Utility in kernel model a Debug Stop code is shown. See attached screen shot.
Finally, when SED mode is turned off in "HDD ID"and I try to create a head-map in DE I get the following error: Error execute=LBA->CHS conversion error (0) Device Error Detected: "VSC ERR UNSUP ACTION CODE"----
And then for some further attempts:
Donor 02 mod from an exact match donor HDD was written to both head 0 and 1 using ABA.
• HDD was powered off, then on. Module 02 access is on in the ROM, but SED it turned off.
• On power on the HDD identifies with the donor 02 mod's serial number.
There are no changes to the HDD performance:
• It was possible to read all firmware modules at normal speed. The module read speed is normally effected when there is the 'slow responding fault'.
• When reading (encrypted) data in DE, the read speed is still 64kb/s
• Using the 'solve slow responding' function with donor mod 02 does not improve the performance.
• I have written the patient mod 02 back to the drive (copies 0 and 1)
• I have checked the SATA cable and replaced. Disk imaging performance is the same (64kb/s) when tested on DeepSpar Disk Imager too.
It is not possible to create a Headmap in DE, or use the "RAM head map editing" function. This model of HDD is 'SpyGlass', but in utility the closest match in Utility is to use 'Pebble Beach'. I presume this is why it is not possible to create a head map, or edit head functions? From the tests I have made on different LBA values, all the heads appear to be work, and are reading at 64kb/s.
_________________
CDR - Manchester Data Recovery Services
0161 408 4857
http://www.cheadledatarecovery.co.uk/