Rosewood ST2000LM007 0 capacity

Moderator: Dmitriy_TS


Sam A
Newbie
Posts: 9
Joined: 31.08.16
Reputation: 0 / (0)

Rosewood ST2000LM007 0 capacity

Postby Sam A » 30.03.18, 00:43

IDs correctly but with 0 capacity.

Can backup all resources EXCEPT:

DTs

DT 0000 (Flash ROM), Read Adaptive Parameters File (RAP).............. : Error
Error : Error requesting command state "RD CP part" (ABR)


DT 0000 (RAM), Read Adaptive Parameters File (RAP).................... : Error
Error : Error requesting command state "RD CP part" (ABR)


(after working with an identical drive it looks like above is normal--just hadn't noticed it before)

Modules

Module 002B, R/W Operating Parameters (translator, etc)............... : Error
Error : Rq Rd Sys File part ID 2B, Offs 0x0 err! Tech state 0x72, 0x04440000


System Files

Sys File FC35E028(0), R/W Operating Parameters (translator, etc)...... : Error
Error : Rd SysF 3:28:0 (0/8000) err = 0x0000000E
Sys File FC35E028(1), R/W Operating Parameters (translator, etc)...... : Error
Error : Rd SysF 3:28:1 (0/8000) err = 0x0000000E



Unable to read SysFile 28 copy 0 or 1 in Service Information Objects via Terminal or ATA Indirect mode. No problem reading any other SysFile via Terminal or ATA Indirect mode.

11 entries in NRG list.

Edited SysFile 93 to turn off all but Media Cache.

Same exact results with donor heads.

Normally I would try translator regeneration but find numerous warnings against it for this model.

Any suggestions?


AJ2008
Posts: 1287
Joined: 25.11.08
Reputation: 10 / (98)

Re: Rosewood ST2000LM007 0 capacity

Postby AJ2008 » 03.04.18, 10:34

Module 002B and System files xxxxx028 are same module. Can you read any of 028 module with ignore read error option?

You will have to regen translator, but with this model MediaCache can store a lot of data that will not be accessible after clear translator as translator will not include MC data after rebuild which is why is important to try to back up as much of original translator module as possible. Try to preserve NRG defects also with a regeneration.


Sam A
Newbie
Posts: 9
Joined: 31.08.16
Reputation: 0 / (0)

Re: Rosewood ST2000LM007 0 capacity

Postby Sam A » 04.04.18, 17:11

Yes, tried ignore read error option on module 028. Between 028, 002B_0, and 002B_1 I was able to read all but the very top part of the file. When I selected "read by one sector" is when I had the best read of 002B (Thanks to Jared for the idea).

Things went downhill. Drive would ID but become bsy when trying to refresh modules list, restart autotune, etc.

Notified customer of risk, cleared Media Cache (allowed drive to refresh modules list, autotune, etc. again) and performed translator regen with NRG list. Had access to first 19 million sectors. Added first unreadable sector to slip list and was able to image rest of drive (probably got really lucky that I didn't have to add more entries...I was ready for quite a bit of work). Customer has reviewed recovery and he's sure nothing is missing. We can't figure out what might have been lost from Media Cache, if anything.


AJ2008
Posts: 1287
Joined: 25.11.08
Reputation: 10 / (98)

Re: Rosewood ST2000LM007 0 capacity

Postby AJ2008 » 04.04.18, 18:12

there is possibly a method to execute translator regeneration and stopping process before MC is affected - maybe it wont help, maybe it will I am not sure.

but since you have most data here and client seems happy, then this is a good result. I would be concerned that you have just 19,000,000 sectors read - this is approximately 9.5GB of sectors from a 2TB, but hopefully all important data was contained here :D


LarrySabo
Newbie
Posts: 24
Joined: 20.07.15
Reputation: 1 / (14)

Re: Rosewood ST2000LM007 0 capacity

Postby LarrySabo » 04.04.18, 20:30

Sam A wrote:Source of the post Had access to first 19 million sectors. Added first unreadable sector to slip list and was able to image rest of drive


AJ2008 wrote:Source of the post I would be concerned that you have just 19,000,000 sectors read


Sam A
Newbie
Posts: 9
Joined: 31.08.16
Reputation: 0 / (0)

Re: Rosewood ST2000LM007 0 capacity

Postby Sam A » 05.04.18, 05:10

AJ2008 wrote:Source of the post there is possibly a method to execute translator regeneration and stopping process before MC is affected


AJ--does this mean you've heard a rumor or do you know what the method is? Would you be willing to share?


jojo2012
New user
Posts: 52
Joined: 21.03.14
Reputation: 2 / (21)

Re: Rosewood ST2000LM007 0 capacity

Postby jojo2012 » 13.07.18, 18:44

Sam A wrote:Source of the post IDs correctly but with 0 capacity.

Can backup all resources EXCEPT:

DTs

DT 0000 (Flash ROM), Read Adaptive Parameters File (RAP).............. : Error
Error : Error requesting command state "RD CP part" (ABR)


DT 0000 (RAM), Read Adaptive Parameters File (RAP).................... : Error
Error : Error requesting command state "RD CP part" (ABR)


(after working with an identical drive it looks like above is normal--just hadn't noticed it before)

Modules

Module 002B, R/W Operating Parameters (translator, etc)............... : Error
Error : Rq Rd Sys File part ID 2B, Offs 0x0 err! Tech state 0x72, 0x04440000


System Files

Sys File FC35E028(0), R/W Operating Parameters (translator, etc)...... : Error
Error : Rd SysF 3:28:0 (0/8000) err = 0x0000000E
Sys File FC35E028(1), R/W Operating Parameters (translator, etc)...... : Error
Error : Rd SysF 3:28:1 (0/8000) err = 0x0000000E



Unable to read SysFile 28 copy 0 or 1 in Service Information Objects via Terminal or ATA Indirect mode. No problem reading any other SysFile via Terminal or ATA Indirect mode.

11 entries in NRG list.

Edited SysFile 93 to turn off all but Media Cache.

Same exact results with donor heads.

Normally I would try translator regeneration but find numerous warnings against it for this model.

Any suggestions?

Hi Sam, I have the same identical problem. Also the sys file 348 is unreadable.

You have solved with the regeneration of the translator taking into account the NRG list.
But I think the customer has more than 9GB of data as it was in your case, so I don't know what to do.


Sam A
Newbie
Posts: 9
Joined: 31.08.16
Reputation: 0 / (0)

Re: Rosewood ST2000LM007 0 capacity

Postby Sam A » 16.07.18, 04:08

jojo--please re-read my posts. I never stated that I was only able to image the first 9GB of data--another member mis-read my posts and stated this... and Larry has already pointed this out.


jojo2012
New user
Posts: 52
Joined: 21.03.14
Reputation: 2 / (21)

Re: Rosewood ST2000LM007 0 capacity

Postby jojo2012 » 16.07.18, 11:04

LarrySabo wrote:Source of the post
Sam A wrote:Source of the post Had access to first 19 million sectors. Added first unreadable sector to slip list and was able to image rest of drive


AJ2008 wrote:Source of the post I would be concerned that you have just 19,000,000 sectors read

Sam sorry, I had not seen this one. So with the translator regeneration and the addition of the first unread sectors to the Slip list you have solved the case....Good!

I played with another Rosewood and after translator regeneration into account the NRG list, it had the same entries (in my case 25) and the data was there with the complete structure. Only the Sys file 348 had a few bytes changed.

Thanks so much.....I'll let you know.

Jojo


Doomer
Newbie
Posts: 29
Joined: 24.06.14
Reputation: 1 / (12)

Re: Rosewood ST2000LM007 0 capacity

Postby Doomer » 16.07.18, 16:25

Sam A wrote:Source of the post Yes, tried ignore read error option on module 028. Between 028, 002B_0, and 002B_1 I was able to read all but the very top part of the file. When I selected "read by one sector" is when I had the best read of 002B (Thanks to Jared for the idea).

that's ok, you could have fixed the drive at this point
Sam A wrote:Notified customer of risk, cleared Media Cache (allowed drive to refresh modules list, autotune, etc. again) and performed translator regen with NRG list. Had access to first 19 million sectors.

And here you screwed up, big time
Sam A wrote: Added first unreadable sector to slip list and was able to image rest of drive (probably got really lucky that I didn't have to add more entries...I was ready for quite a bit of work).

You are very lucky

PS: if you ever read 2b/28 where first third/half of the module is unreadable you still can fix the drive w/o killing MC and regenerating translator. Ace TS should be able to help you.


Return to “Arch F3”

Who is online

Users browsing this forum: No registered users and 0 guests