Solving Seagate Rosewood having Translator issue.

[darkforce1]

Well,

Seagate Rosewood drives are with firmware lock, the very first thing is to unlock; after that, we can not regenerate translator immediately, cuz that will lead to user sector access interruption and we can not restore the disk to the status before regenerating translator (but with backup of sys file, such attempt will have no threat to client data, we can still restore the disk to its original status).

The right procedures to fix Rosewood are:
1. Unlocking；
2. Backup firmwares especially sys file of 28 and 35;
3. Recalculate translator, and fix user sector access interruption (Restore the disk to its original status with the ablility of writing back sys file).

All who trying recalculate translator on modern seagate drives are amatours. They dont know how things is going in sa.
Translator isn't a couplrit . And you can't backup everything in SA due of bad sectors in specific modules responsible for user data access.

Agreed With Dr.

[reco]

Well,

Seagate Rosewood drives are with firmware lock, the very first thing is to unlock; after that, we can not regenerate translator immediately, cuz that will lead to user sector access interruption and we can not restore the disk to the status before regenerating translator (but with backup of sys file, such attempt will have no threat to client data, we can still restore the disk to its original status).

The right procedures to fix Rosewood are:
1. Unlocking；
2. Backup firmwares especially sys file of 28 and 35;
3. Recalculate translator, and fix user sector access interruption (Restore the disk to its original status with the ablility of writing back sys file).

All who trying recalculate translator on modern seagate drives are amatours. They dont know how things is going in sa.
Translator isn't a couplrit . And you can't backup everything in SA due of bad sectors in specific modules responsible for user data access.

The most important are sys file of 28 and 35, and if you can not backup modules due to bad sectors, you can also try to read via ABA method; if still not, please ask Jesus for help ：）

[drHDD]

So if I will give you rosewood with cleared SA and 28 and 35 from it - you will able to get access to all user files, right?

[reco]

So if I will give you rosewood with cleared SA and 28 and 35 from it - you will able to get access to all user files, right?

We are not near, if yes, I can try

Luckly, I have done some cases successfully, and yesterday, I fixed a customer case with sys 28 only;

Translator issue is complicated, there is no must success solution, but with backups, at least we restore to original status for future attempt.

[mrtpro]

I find a viedo in Youtube as below:
https://www.youtube.com/watch?v=7EL5PWOm-do&feature=youtu.be

[helpdisc]

man you work so fast, you found it minutes after you uploaded....bravo!

[MindMergepk]

Well,

Seagate Rosewood drives are with firmware lock, the very first thing is to unlock; after that, we can not regenerate translator immediately, cuz that will lead to user sector access interruption and we can not restore the disk to the status before regenerating translator (but with backup of sys file, such attempt will have no threat to client data, we can still restore the disk to its original status).

The right procedures to fix Rosewood are:
1. Unlocking；
2. Backup firmwares especially sys file of 28 and 35;
3. Recalculate translator, and fix user sector access interruption (Restore the disk to its original status with the ablility of writing back sys file).

and what if the sysfile 28 is corrupt which is some time the case ?

As many respected members mentioned this, regenerating translator is not a good solution to work with these drive, there are definitely other ways to solve most of the problem without touching the translators.

[darkforce1]

1 regenrate and have to add defect 8n defect list. Correct me i am wrong.

Vikas Seth

[reco]

man you work so fast, you found it minutes after you uploaded....bravo!

you are good, man!

@mrtpro, Ivy? or Wang? you guys are so fun, why do not you guys said that is your work directly? what you afraid for?

[reco]

Well,

Seagate Rosewood drives are with firmware lock, the very first thing is to unlock; after that, we can not regenerate translator immediately, cuz that will lead to user sector access interruption and we can not restore the disk to the status before regenerating translator (but with backup of sys file, such attempt will have no threat to client data, we can still restore the disk to its original status).

The right procedures to fix Rosewood are:
1. Unlocking；
2. Backup firmwares especially sys file of 28 and 35;
3. Recalculate translator, and fix user sector access interruption (Restore the disk to its original status with the ablility of writing back sys file).

and what if the sysfile 28 is corrupt which is some time the case ?

As many respected members mentioned this, regenerating translator is not a good solution to work with these drive, there are definitely other ways to solve most of the problem without touching the translators.

some case I encountered with good sys 28. What i suggested here before is in order to provided a manner to help Data recovery engineer to solved Rosewood hard drive translator issue temperately. The fact is my suggestions really works in some case.

There must be a way to solve this problem not by regenerating translator, either PC3K or MRT they had such solution at moment yet. It is nearly five months passed when ACE release 90G Media Cache theory in Vegas, I still take a sceptical eye on it.

[MindMergepk]

1 regenrate and have to add defect 8n defect list. Correct me i am wrong.

Vikas Seth

your method might work, i never used it like this.
There is definitely other and better way to deal with 28 sysfile corruption.