Best steps for Seagate Momentus Thin recovery

[posidon]

Hi all
I have got a critical case of Seagate Momentus thin ST500LM021 FW - 00045DM1 .
Disk has normal detection and I have backed up all modules / rom as well in pc3000 udma.
I am currently trying to image critical data folder , prior to that I have created Head Map in DE.
I am observing varied response from both heads in terms of data transfer speeds and bad sectors.
I want to know instead of imaging as it is , if some firmware repair may improve imaging speed ,
I dont want to take any chances .
Here is Terminal output --

tbg_n:0x0066
tbg_r:0x0057
RAP tbg_n:0x0067
RAP tbg_r:0x0022
RAP RegTBGN0x0067
RAP RegTBG0x4404
TBA0x000071CF
Update Channel
Start PVT recover
SP correction passed 0x01B30702[RA]!

Starting LBA of RW Request=01B307FD Length=00000020
ProcessRWError -Read- at LBA 01B30811 Sense Code=43110081
[ TRACK_OFFSET_RETRY PREAMP_FAST_RETRY SERVO_COAST_RETRY ]
vqvq[RA]!

Starting LBA of RW Request=01B3091D Length=00000020
ProcessRWError -Read- at LBA 01B30921 Sense Code=43110081
[ TRACK_OFFSET_RETRY PREAMP_FAST_RETRY SERVO_COAST_RETRY ]
vqvq[RA]!

Starting LBA of RW Request=01B30A1D Length=00000020
ProcessRWError -Read- at LBA 01B30A31 Sense Code=43110081
tbg_n:0x0066
tbg_r:0x0057
RAP tbg_n:0x0067
RAP tbg_r:0x0022
RAP RegTBGN0x0067
RAP RegTBG0x4404
TBA0x000071CF
Update Channel
Start PVT recover
SP correction passed 0x01B30A32[RA]!

I work mostly on DE level and dont know how to correctly interpret drives response and terminal output.
Earlier I am used to do Typical steps like NRG list clearing , smart reset etc.
But since Dr. Kiev and HPWlab has poined out risks in pressing commands in a hurry is Dangerous , I am not doing this routine and want to know how experts would have handled such case.
Thank You

[mr_spokk]

It's always a risk to do destructive commands, but a backup can help you out if things go bad. Did you backup necessary sys files as well?
I would try to clone the critical area first and use different timeout's and retries, looks like you have some bad sectors...but could be a weak head as well...so check for that also.

[posidon]

Hi mr_spokk
Thanks for your suggestions.
Yes as a rule I have made 2 backup copies of entire firmware modules ,sysfiles and rom
As of now I am not running any command except smart reset.

[athena]

I was having similar case , I erased NRG list , Alt list and erase smart. But original symptoms aggreavated and even restoring backup did not improve situation.
I think erasing NRG list and ALT list is equally dangerous .
If someone give details of crucial system files for each family ,that will be of immense help as Ace manuals are not updated and are not having information of individual sysfiles.
Something like this --

Attachments

Seagate Sysfiles.xlsx

(9.71 KiB) Downloaded 282 times

[Nick_CT]

Did you go to HDD ID settings in Seagate F3 utility and disable all background scanning and reallocation?

[posidon]

Hi Nick_CT
Thanks. Yes I have done that but unfortunately that has not improved situation.

[Nick_CT]

I would do as others suggested, change timeouts, low block size, read in reverse and get what you can off original heads, then do head swap. Either bad sectors, weak heads or a combination of both.