Tag Archives: Translator

PC-3000 HDD. Seagate F3 arch. Manually Translator recovery procedure

A lot of times PC-3000 owners asked us about sharing step-by-step guide. One of the often problems on Seagate F3 architecture drives is a Translator problem. Usually we try to regenerate Translator automatically (by Translator regeneration and Recovery translator procedures). Basically … Continue reading

Posted in Data Extractor | Tagged , , , | 5 Comments

PC-3000 for HDD. Seagate F3. How to fix Init SMART Fail error

Hi Friends! How are you today? As you know SMART is very useful thing. It provides detailed infomation about Hard Drive. However SMART is broken too. Do you see this error? Init SMART Fail LED:000000CC FAddr:xxxxxxxx If yes then welcome … Continue reading

Posted in Articles, PC-3000 HDD | Tagged , , , , , , , , | 3 Comments

PC-3000 HDD. Seagate F3. How to fix translator issue caused by useless defects in Non-Resident G-list

Dear Users, you are often facing with a problem when on Seagate F3 drives you can read sectors in the beginning of the drive but from certain LBA the drive is filled with UNC error and in Data Extractor sectors … Continue reading

Posted in Articles, Data Extractor, PC-3000 HDD | Tagged , , , , , , , , , | 5 Comments

P-List and translator regeneration in WD Marvell drives

Hello friends! We are all know how to get the data if translator (31h module) is damaged: follow Work with Service Area->Translator regeneration menu. The utility fix the translator automatically using the P-List (33h module), and we’re able to read … Continue reading

Posted in Data Extractor | Tagged , | 5 Comments

PC-3000 for HDD. Seagate F3 utility. Translator recovering on Seagate F3 drives

The most popular problem of Seagate F3 drives it’s problem with Translator. Bassicaly such drives get access just to first part of users area, but the other part is unavailable for reading. Such behavior could be if Translation table have wrong defect … Continue reading

Posted in Articles, PC-3000 HDD, Video | Tagged , , | Leave a comment