I get the following error when I try to recover F3 translator...

[osity]

Seagate ST9500320AS
I have what seems to be a translator issue.
I tried to regen translator which completed but I could still not access sectors located at the end of the drive.
Afterwards, I tried to recover the translator and I get a lot of the following type of errors which continue seemingly forever:


Start scanning...
"Fork" searching: 0 - 976773167
HDD power supply switching OFF/ON...
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 422C:3:21E(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 422C:3:21E(1)! Tech state 0x72, 0x03110081
LBA : 123277186
"Fork" searching: 123277187 - 976773167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect 422C:3:26B(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect 422C:3:26B(1)! Tech state 0x72, 0x03110081
LBA : 123277263


Currently I can read first half of sectors but I get UNC error on the end part of the drive.
I'm guessing I have to manually update a list for a manual translator recovery attempt. I've never done this.

Can anyone point me in the right direction?

[DataMedics]

You need to let the forking run. It may seem like forever, I've had it run for 4 to 5 days at times.

[osity]

Lol.... I let it run for a whole day and then decided it was a waste of time. I'll let it run for days instead.

Thanks for the message of hope !

[DataMedics]

I'd still image it as far as you can first. Just in case the heads die during the process.

[Filipp_TS]

Hi all!
Another way is recover translator manually - you can contact Technical support: http://ts.acelab.eu.com/
http://blog.acelab.eu.com/7-known-s ... cally.html

[osity]

Under section "what can i do if recover translator doesnt work" it says: "2. Try tiny Non-resident G-list adjusting or at least remove manually all defects with all non-zero flags."
Were is “tiny Non-resident G-list adjusting”?

[osity]

Source of the post Hi all!
Another way is recover translator manually - you can contact Technical support:

I just renewed my TS contract to get help with Filipp's "recover translator manually" method mentioned above as I didn't want to wait weeks for forking. Filipp just did exactly what I had done and told me to wait however many days it takes.....

[DataMedics]

Source of the post

Source of the post Hi all!
Another way is recover translator manually - you can contact Technical support:

I just renewed my TS contract to get help with Filipp's "recover translator manually" method mentioned above as I didn't want to wait weeks for forking. Filipp just did exactly what I had done and told me to wait however many days it takes.....

And, I'm pretty sure I told you that a week ago too. Had you listened, it'd be done already.

[osity]

Data medics, It had ran for 3 days and it hadn't moved! This time around I started it at the last readable sector rather than the first sector so that should save a few days off the month I will likely have to wait!

[DataMedics]

In my experience it usually gets stuck in an area for a while and seems like it's not getting anywhere counting away one sector at a time. Then all of the sudden when you haven't been watching it a few days later, it's done.

[osity]

Well that certainly sounds like a nice scenario.

[DataMedics]

Don't worry, these don't come up often at all. I've only had to do this twice I think. The first time I almost gave up thinking it would never finish. The second time I got smart and started it right be for leaving for a four day weekend.

[osity]

lol... apparently it was memorable.

[osity]

I'm hoping I don't need the USB Terminal connected for this.... I need it on the other channel for other jobs.

[Amarbir[CDR-Labs]]

Hi Both Of You ,
One Observation i have had is that if one of the multiple heads are bad never do this as it senses all wrong info . I quick head swap and we are done