All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 33 posts ]  Go to page 1, 2  Next
Author Message
 Post subject: RoseWood
PostPosted: February 22nd, 2018, 9:05 
Offline

Joined: October 21st, 2007, 8:48
Posts: 1283
Hello
ST1000LM035
SBM3
1 TB
The drive in topic shows correct ID, capacity and FW then stuck in busy and no user area access.
Terminal output:
Boot 0x80M
QB
Rst 0x80MSrv DETCR init 0x0000
(P) SATA Reset

RAW OFF
PASS
(DOS Table) Worst Count: 000015F4 At SU: 00004888 NT: 0000000A OT: 0000000E
(POR) Recover Secondary MCMT Opened Recovered
(MC POR Duration): 0000000146
Send Status: COMRESET seen
CSpd= 6Gbps
Update Mask - 0000000006196520 - 00000008 - 00
Update Mask - 0000000006196528 - 00000008 - 00
Update Mask - 0000000006196530 - 00000008 - 00
Update Mask - 0000000006196538 - 00000008 - 00
Update Mask - 0000000006196540 - 00000008 - 00
Update Mask - 0000000006196548 - 00000008 - 00
Update Mask - 0000000006196550 - 00000008 - 00
Update Mask - 0000000006196558 - 00000008 - 00
Update Mask - 0000000006196560 - 00000008 - 00
Update Mask - 0000000006196568 - 00000008 - 00
Update Mask - 0000000006196570 - 00000008 - 00
Update Mask - 0000000006196670 - 00000008 - 00
Update Mask - 0000000006196678 - 00000008 - 00
Update Mask - 0000000006196680 - 00000008 - 00
Update Mask - 0000000006196688 - 00000008 - 00
Update Mask - 0000000006196690 - 00000008 - 00
Update Mask - 0000000006196698 - 00000008 - 00
Update Mask - 00000000061966A0 - 00000008 - 00
Update Mask - 00000000061966A8 - 00000008 - 00
Update Mask - 00000000061966B0 - 00000008 - 00
Update Mask - 00000000061966B8 - 00000008 - 00
Update Mask - 00000000061966C0 - 00000008 - 00
Update Mask - 00000000061966C8 - 00000008 - 00
Update Mask - 00000000061966D0 - 00000008 - 00
Update Mask - 00000000061966D8 - 00000008 - 00
Update Mask - 00000000061966E0 - 00000008 - 00
Update Mask - 00000000061966E8 - 00000008 - 00
Update Mask - 00000000061966F0 - 00000008 - 00
Update Mask - 00000000061966F8 - 00000008 - 00
Update Mask - 0000000006196700 - 00000008 - 00
Update Mask - 0000000006196708 - 00000008 - 00
Update Mask - 0000000006196710 - 00000008 - 00
Update Mask - 0000000006196718 - 00000008 - 00
Update Mask - 0000000006196720 - 00000008 - 00
Update Mask - 0000000006196728 - 00000008 - 00
Update Mask - 0000000006196730 - 00000008 - 00
Update Mask - 0000000006196738 - 00000008 - 00
Update Mask - 0000000006196740 - 00000008 - 00
Update Mask - 0000000006196748 - 00000008 - 00
Update Mask - 0000000006196750 - 00000008 - 00
Update Mask - 0000000006196758 - 00000008 - 00
Update Mask - 0000000006196760 - 00000008 - 00
Update Mask - 0000000006196768 - 00000008 - 00
Update Mask - 0000000006196770 - 00000008 - 00
Update Mask - 0000000006196778 - 00000008 - 00
Update Mask - 0000000006196780 - 00000008 - 00
Update Mask - 0000000006196788 - 00000008 - 00
Update Mask - 0000000006196790 - 00000008 - 00
Update Mask - 0000000006196798 - 00000008 - 00
Update Mask - 00000000061967A0 - 00000008 - 00
Update Mask - 00000000061967A8 - 00000008 - 00
Update Mask - 00000000061967B0 - 00000008 - 00
Update Mask - 00000000061967B8 - 00000008 - 00
Update Mask - 00000000061967C0 - 00000008 - 00
Update Mask - 00000000061967C8 - 00000008 - 00
Update Mask - 00000000061967D0 - 00000008 - 00
Update Mask - 00000000061967D8 - 00000008 - 00
Update Mask - 00000000061967E0 - 00000008 - 00
Update Mask - 00000000061967E8 - 00000008 - 00
Update Mask - 00000000061967F0 - 00000008 - 00
Update Mask - 00000000061967F8 - 00000008 - 00
Update Mask - 0000000006196800 - 00000008 - 00
Update Mask - 0000000006196808 - 00000008 - 00
Update Mask - 0000000006196810 - 00000008 - 00
Update Mask - 0000000006196818 - 00000008 - 00
Update Mask - 0000000006196820 - 00000008 - 00
Update Mask - 0000000006196828 - 00000008 - 00
Update Mask - 0000000006196830 - 00000008 - 00
Update Mask - 0000000006196838 - 00000008 - 00
Update Mask - 0000000006196840 - 00000008 - 00
Update Mask - 0000000006196848 - 00000008 - 00
Update Mask - 0000000006196850 - 00000008 - 00
Update Mask - 0000000006196858 - 00000008 - 00
Update Mask - 0000000006196860 - 00000008 - 00
Update Mask - 0000000006196868 - 00000008 - 00
Update Mask - 0000000006196870 - 00000008 - 00
Update Mask - 0000000006196878 - 00000008 - 00
Update Mask - 0000000006196880 - 00000008 - 00
Update Mask - 0000000006196888 - 00000008 - 00
Update Mask - 0000000006196890 - 00000008 - 00
Update Mask - 0000000006196898 - 00000008 - 00
Update Mask - 00000000061968A0 - 00000008 - 00
Update Mask - 00000000061968A8 - 00000008 - 00
Update Mask - 00000000061968B0 - 00000008 - 00
Update Mask - 00000000061968B8 - 00000008 - 00
Update Mask - 00000000061968C0 - 00000008 - 00
Update Mask - 0000000006196BE8 - 00000008 - 00ProcessRC: 00000000,00000000ReadContinuous: 00C32D7E,00000258TotalEntries:0000 XfrLen:0258UnrecovSectorCount:0000,0000NumUDEs: 00000000,00000000Failed: 40000087Out:
SP Regen FAIL
SPRegen [0000|43110081] @LBA=0x00C32D7EOut:
SP Regen FAIL
SPRegen [0000|43110081] @LBA=0x00C32D7EOut:

Any suggestions?
Thanks in advance for any help.


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 23rd, 2018, 6:07 
Online
User avatar

Joined: December 8th, 2013, 4:48
Posts: 708
Location: Pakistan
can you access terminal Level T> ?

_________________
Data Recovery Pakistan


Top
 Profile  
 
 Post subject: Re: RoseWood recovery
PostPosted: February 23rd, 2018, 7:23 
Offline

Joined: February 8th, 2014, 8:08
Posts: 461
Location: Eastern Europe /recovering worldwide/
unknown wrote:
ST1000LM035
The drive in topic shows correct ID, capacity and FW then stuck in busy and no user area access.
Terminal output: ...

Classic - MC has failed. Could be due to defects or drive's inability to write.
Another possible option is reading issues.

Unless there were improper recovery attempts, which made the situation worse (not uncommon with the cases like this), chances are high that the data is recoverable.

_________________
• Remote RAID, NAS, SAN, VMware, DVR (CCTV), flash and tape recovery. Data recovery partnership and support.


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 23rd, 2018, 11:37 
Offline

Joined: October 21st, 2007, 8:48
Posts: 1283
MindMergepk wrote:
can you access terminal Level T> ?

Yes.


Top
 Profile  
 
 Post subject: Re: RoseWood recovery
PostPosted: February 23rd, 2018, 11:38 
Offline

Joined: October 21st, 2007, 8:48
Posts: 1283
Dmitri wrote:
unknown wrote:
ST1000LM035
The drive in topic shows correct ID, capacity and FW then stuck in busy and no user area access.
Terminal output: ...

Classic - MC has failed. Could be due to defects or drive's inability to write.
Another possible option is reading issues.

Unless there were improper recovery attempts, which made the situation worse (not uncommon with the cases like this), chances are high that the data is recoverable.

Didn't do anything to the drive yet. :)
Still trying to diagnose the problem.


Top
 Profile  
 
 Post subject: Re: RoseWood recovery
PostPosted: February 23rd, 2018, 11:48 
Offline
User avatar

Joined: August 15th, 2006, 3:01
Posts: 2540
Location: CDRLabs @ Chandigarh [ India ]
unknown wrote:
Dmitri wrote:
unknown wrote:
ST1000LM035
The drive in topic shows correct ID, capacity and FW then stuck in busy and no user area access.
Terminal output: ...

Classic - MC has failed. Could be due to defects or drive's inability to write.
Another possible option is reading issues.

Unless there were improper recovery attempts, which made the situation worse (not uncommon with the cases like this), chances are high that the data is recoverable.

Didn't do anything to the drive yet. :)
Still trying to diagnose the problem.


Well ,
Please make backup of imp sys files Before you start the show :mrgreen:

_________________
Regards
Amarbir S Dhillon , Chandigarh Data Recovery Labs
Logical,Semi Physical And Physical Data Recovery
Website-> http://www.chandigarhdatarecovery.com


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 23rd, 2018, 13:06 
Online
User avatar

Joined: December 8th, 2013, 4:48
Posts: 708
Location: Pakistan
unknown wrote:
MindMergepk wrote:
can you access terminal Level T> ?

Yes.


can help remotely if interested !

_________________
Data Recovery Pakistan


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 27th, 2018, 7:54 
Offline

Joined: October 21st, 2007, 8:48
Posts: 1283
I have backed up sys files and regen trans. The drive is stable now but with user area limit access to LBA 67000000.
tried to write back original translator but MRT doesn't support sys file/mods writing. :D

Any suggestions?
Thanks in advance


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 27th, 2018, 13:15 
Offline
User avatar

Joined: September 29th, 2005, 12:02
Posts: 3237
Location: Chicago
unknown wrote:
I have backed up sys files and regen trans.

awesome, you've done it

unknown wrote:
Any suggestions?

you can throw the drive away, then take a hammer and break you fingers and never do DR again.

_________________
https://www.linkedin.com/in/artemrubtsov/


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 27th, 2018, 13:25 
Offline

Joined: October 21st, 2007, 8:48
Posts: 1283
Doomer wrote:
unknown wrote:
I have backed up sys files and regen trans.

awesome, you've done it

unknown wrote:
Any suggestions?

you can throw the drive away, then take a hammer and break you fingers and never do DR again.

:lol: :lol: :lol:
Awesome advice indeed.


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 27th, 2018, 13:45 
Offline

Joined: October 21st, 2007, 8:48
Posts: 1283
But I think 1 failed DR case out of 10 success DR cases per week isn't deserve to break my fingers. :D


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 27th, 2018, 13:57 
Offline
User avatar

Joined: June 8th, 2006, 19:44
Posts: 2956
Location: Atlanta, GA
unknown wrote:
But I think 1 failed DR case out of 10 success DR cases per week isn't deserve to break my fingers. :D


Ask the client whose data didn't get recovered . . .


:mrgreen:

_________________
http://www.datasaversllc.com


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 27th, 2018, 14:02 
Offline

Joined: October 21st, 2007, 8:48
Posts: 1283
jono-ats wrote:
unknown wrote:
But I think 1 failed DR case out of 10 success DR cases per week isn't deserve to break my fingers. :D


Ask the client whose data didn't get recovered . . .


:mrgreen:

Until I backed up resources and recovery process didn't end yet, then the question can't be asked yet. :)


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 27th, 2018, 14:24 
Offline

Joined: October 16th, 2013, 13:21
Posts: 717
Location: Brazil
If you have backups, not all is lost.

Maybe we need to add to the usual instructions to backup modules first, the important part that is to know if one´s firmware tool can *write* those modules back.

Do you have another fw tool to try writing the modules back ?

Is it possible to write it back through terminal, even if it is to mean a lot of manual work ?


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 27th, 2018, 14:43 
Offline

Joined: October 21st, 2007, 8:48
Posts: 1283
rogfanther wrote:
If you have backups, not all is lost.

Maybe we need to add to the usual instructions to backup modules first, the important part that is to know if one´s firmware tool can *write* those modules back.

Do you have another fw tool to try writing the modules back ?

Is it possible to write it back through terminal, even if it is to mean a lot of manual work ?

A friend of mine has PC3K UDMA. We will try to write original resources back.
Thanks for reply :)


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 27th, 2018, 18:42 
Offline
User avatar

Joined: December 19th, 2006, 8:49
Posts: 9985
Location: Portugal
rogfanther wrote:
If you have backups, not all is lost.

Maybe we need to add to the usual instructions to backup modules first, the important part that is to know if one´s firmware tool can *write* those modules back.

Do you have another fw tool to try writing the modules back ?

Is it possible to write it back through terminal, even if it is to mean a lot of manual work ?


For this drive he would need ATA vendor specific commands in "Indirect Mode" (have more options then the "regular" ATA VSC to write sysfiles. I don't think MRT will work to write those sysfiles back.

Most likely the problem was media cache related. I would have started by attempting to disable it and relocation, etc on sysfile 93 or using congen. Re-set the media cache on rosewood might be dangerouse and you might loose considerable amount of data on that MC as well so if you can just image/clone the drive with congen / sysfile 93 manipulation the better.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 27th, 2018, 19:11 
Offline

Joined: October 21st, 2007, 8:48
Posts: 1283
(Patch ROM
Send handshake to access SA
Access SA and read backup of file 3_028_0
Next, run translator regeneration
Repower HDD and send handshake again
now try sector edit - if first and last LBA can be read, then you can recover now.

If last LBA cannot read, then write original 3_028_0 to module 2B in modules table)
This advice has given to me from a reputable member of this forum (all old members knows him perfectly )
So, I didn't recklessly regenerate translator before I took the advice to.


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 27th, 2018, 19:50 
Offline

Joined: October 16th, 2013, 13:21
Posts: 717
Location: Brazil
Spildit wrote:

For this drive he would need ATA vendor specific commands in "Indirect Mode" (have more options then the "regular" ATA VSC to write sysfiles. I don't think MRT will work to write those sysfiles back.



That´s why I said that maybe it is interesting to add to the usual recommendations for backing up modules to be sure that said modules can be written back, as a module that cannot be sent back to the hdd wouldn´t be much useful ..... Like, before changing things, make a backup and try to rewrite some not-important module back to the drive to see it the tool works.


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 28th, 2018, 0:03 
Offline

Joined: May 29th, 2011, 8:47
Posts: 102
Location: Russia
Spildit wrote:
ATA vendor specific commands in "Indirect Mode" (have more options then the "regular" ATA VSC to write sysfiles. I don't think MRT will work to write those sysfiles back.

You state as if you knew the way "indirect" mode works in pc3k :) Rosewood drives can NOT write sysfiles(FIDs). ATA modules CAN be written. The trick is made by pc3k to "deceive" a drive so that it thinks it writes a module but in fact it writes what we need.


Top
 Profile  
 
 Post subject: Re: RoseWood
PostPosted: February 28th, 2018, 15:47 
Offline
User avatar

Joined: December 19th, 2006, 8:49
Posts: 9985
Location: Portugal
Masterclass wrote:
Spildit wrote:
ATA vendor specific commands in "Indirect Mode" (have more options then the "regular" ATA VSC to write sysfiles. I don't think MRT will work to write those sysfiles back.

You state as if you knew the way "indirect" mode works in pc3k :) Rosewood drives can NOT write sysfiles(FIDs). ATA modules CAN be written. The trick is made by pc3k to "deceive" a drive so that it thinks it writes a module but in fact it writes what we need.


I don't "know" how PC-3000 implements the "indirect" mode because i did never bother to reverse it or sniff the commands.

As a matter of fact i don't have VSC for F3 arch drives as I'm not using neither recommending the use of that sort of junk.

But i do read the ACE forum.

http://forum.acelaboratory.com/viewtopi ... 52&p=33712

Dmitriy_TS wrote:
[post]33491[/post] Dear Amarbir,

Amarbir[CDR-Labs] wrote:
[post]33356[/post] Can You Explain Difference Between Direct ATA And Indirect ATA Mode ?


ATA direct mode uses three parameters to access the system file such as:
1. Volume
2. File ID
3. Copy

ATA indirect mode operates with more parameters and it is useful for some families: Wyatt, Brinks, Rosewood etc.


Dmitriy_TS wrote:
[post]33712[/post] Dear Amarbir,

Amarbir[CDR-Labs] wrote:
[post]33648[/post] Well ,
Understood This But Whats The Difference ?


For the drives where system files are read via ATA direct mode, you can read system file by typing volume, file id and copy of the file in the top sys files tab.
For the drives where system files are read via ATA indirect mode, you have to upload module and system files table in the utility and then check the box of the system file in the sys file tab to read file. You have to follow this procedure because of ATA indirect mode requires mode parameters (Volume, FileID, Copy and other). When you check the box you lay down system file parameters automatically.


But again i didn't bother to check it yet as "sniffing" commands on those Seagate F3 arch is the last of my priorities (i'm not using those drives) and also it have some extra difficulty as they are not regular ATA commands but instead they are send to the drive inside a buffer of data like on Marvell WD.

Maybe someday when i do get a decent LA and i do have time to play with it i may check it out to see what VSCs are used but again it's not on my top priority list of to-do things.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 33 posts ]  Go to page 1, 2  Next

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 28 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group