ST1000LM035 another problem with rosedwood family

[hamidbid]

Hi guys,

I have a ST1000LM035 after patch don't have to sa and terminal

In log window

HDD Redynes timeout (10000)
Family ID by HDD ID: A5
Selected family......................... : A5, Rosewood_A5
Model by ID............................. : ST1000LM035-1RK172

Loading default settings!
Use the options dialog to review and save utility settings.
Then press OK!


Family default settings loading!


Tech Key...
Error starting command "En Tech" (Drive is not ready)
Terminal : reply timeout error

I think pending sector
and what is about "MS Read Fails" ?
and why give message "Update Mask" after patch ?

Thanks for any new idea

Attachments

6794.txt

Terminal log window

(265.03 KiB) Downloaded 1106 times

[hamidbid]

Hi again
short terminal log
Boot 0x80M
Tech Unlock Handshake: 0x0791FB18
Reply:

Rst 0x80MSrv DETCR init 0x0000
(P) SATA Reset

RAW OFF
PASS
(DOS Table) Worst Count: 00000D40 At SU: 0000531A NT: 00000000 OT: 0000000E
(POR) Recover Secondary MCMT Opened Recovered
MS Read Fails: 0EEE17B0,000052E8
Update Mask - 000000000EEE17B0 - 00000001 - 00
Update Mask - 000000000EEE17B1 - 00000001 - 00
Update Mask - 000000000EEE17B2 - 00000001 - 00
Update Mask - 000000000EEE17B3 - 00000001 - 00
Update Mask - 000000000EEE17B4 - 00000001 - 00
Update Mask - 000000000EEE17B5 - 00000001 - 00
Update Mask - 000000000EEE17B6 - 00000001 - 00
Update Mask - 000000000EEE17B7 - 00000001 - 00
Update Mask - 000000000EEE17B8 - 00000001 - 00
Update Mask - 000000000EEE17B9 - 00000001 - 00
Update Mask - 000000000EEE17BA - 00000001 - 00
Update Mask - 000000000EEE17BB - 00000001 - 00
Update Mask - 000000000EEE17BC - 00000001 - 00
Update Mask - 000000000EEE17BD - 00000001 - 00
Update Mask - 000000000EEE17BE - 00000001 - 00
Update Mask - 000000000EEE17BF - 00000001 - 00
Update Mask - 000000000EEE17C0 - 00000001 - 00
Update Mask - 000000000EEE17C1 - 00000001 - 00
Update Mask - 000000000EEE17C2 - 00000001 - 00
Update Mask - 000000000EEE17C3 - 00000001 - 00
Update Mask - 000000000EEE17C4 - 00000001 - 00
Update Mask - 000000000EEE17C5 - 00000001 - 00
Update Mask - 000000000EEE17C6 - 00000001 - 00
Update Mask - 000000000EEE17C7 - 00000001 - 00
Update Mask - 000000000EEE17C8 - 00000001 - 00
Update Mask - 000000000EEE17C9 - 00000001 - 00
.
.
.
Update Mask - 000000000EEE5EB1 - 00000001 - 00
Update Mask - 000000000EEE5EB2 - 00000001 - 00
Update Mask - 000000000EEE5EB3 - 00000001 - 00
Update Mask - 000000000EEE5EB4 - 00000001 - 00
Update Mask - 000000000EEE5EB5 - 00000001 - 00
Update Mask - 000000000EEE5EB6 - 00000001 - 00
Update Mask - 000000000EEE5EB7 - 00000001 - 00
Update Mask - 000000000EEE5EB8 - 00000001 - 00
Update Mask - 000000000EEE5EB9 - 00000001 - 00
Update Mask - 000000000EEE5EBA - 00000001 - 00
Update Mask - 000000000EEE5EBB - 00000001 - 00
Update Mask - 000000000EEE5EBC - 00000001 - 00
Update Mask - 000000000EEE5EBD - 00000001 - 00
Update Mask - 000000000EEE5EBE - 00000001 - 00
Update Mask - 000000000EEE5EBF - 00000001 - 00
(MC POR Duration): 0000014E39
Intel 6G->3G
Send Status: COMRESET seen
CSpd= 3Gbps
(DOS) SU:0000E84B Ct:00000C6C Adjusted BRO: 0001DDC17B - 0001DDCD52
Starting LBA of RW Request=0001DDC17B Length=00000BD8
ProcessRWError -Read- at LBA 0001DDC17C Sense Code=43110081
Common path start quit now ProcessRC: 00000000,00000000ReadContinuous: 01DDC17C,0000017AUnrecovSectorCount:00FE,0179NumUDEs: 000000FE,00000179Passed: 00000080,0000012F,00000154Out:
SP Regen FAIL
SPRegen [0000|43110081] @LBA=0x01DDC17C
Setup currentretry count
Hd 0 Err Blk 1DDC17C BER pre -1.872396
Out:
Update Mask - 000000000EEE0BE0 - 00000008 - 00
Harden - 01DDC17C
InitiateMarkPendingReallocateRequest for disc_lba: 0001DDC17C CHS: 0000E84B.00.0001
Assert 741D - LBA 01DDC17C!

Starting LBA of RW Request=0001DDC17B Length=00000BD8
ProcessRWError -Read- at LBA 0001DDC182 Sense Code=43110081
Common path start quit now ProcessRC: 00000001,00000000ReadContinuous: 01DDC182,000002EFTotalEntries:0174 XfrLen:02EFUnrecovSectorCount:00FB,0173NumUDEs: 000000FB,00000173Failed: 40000087Out:
SP Regen FAIL
SPRegen [0000|43110081] @LBA=0x01DDC182
Setup currentretry count
Hd 0 Err Blk 1DDC182 BER pre -1.872482
Out:
Update Mask - 000000000EEE0C10 - 00000008 - 00
Harden - 01DDC182
InitiateMarkPendingReallocateRequest for disc_lba: 0001DDC182 CHS: 0000E84B.00.0007
Assert 741D - LBA 01DDC182!

Starting LBA of RW Request=0001DDC17B Length=00000BD8
ProcessRWError -Read- at LBA 0001DDC183 Sense Code=43110081

Thanks for new idea?

[hamidbid]

hi again

More description
After unlock in utility start (in PC3000 UDMA) near one minute later hard disk ready
next hdd Read HDD ID worked then push on utility start

in log window
Tech Key...
Error starting command "En Tech" (Drive is not ready)
Terminal : reply timeout error
don't have access terminal and also sa and hdd came busy

This problem has solution till now

appreciate for any answer
Thanks

[MindMergepk]

there is a solution
let me know if you need remote help.

[Orizarrb]

I had the similar case with same errors and asked ACE support to help me via teamviewer.
Not sure what they did, I remember they unlocked the drive first, it was too fast, but I read all data I need after that.

[hamidbid]

there is a solution
let me know if you need remote help.

Thanks ,I sent pm

[hamidbid]

I had the similar case with same errors and asked ACE support to help me via teamviewer.
Not sure what they did, I remember they unlocked the drive first, it was too fast, but I read all data I need after that.

thanks for answer,
Unfortunately , I don't have any support from two months ago

[hamidbid]

with Thanks Wasim,
I can get new idea , and tray many time and in last , I found solution

[mrdoktro]

Hi! Hamidbid did you find a solution?

[HDDscholar]

hamidbid, mrdoktro

This is not problem of this drive, from message you share, after you unlock the drive, PC3000 did not succeed to exchange command, maybe the bug of PC3000 or poor disk condition. ACE support just re-do the Handshake on Teamview after unlock, and you can get data, that would be the story, no big things.

Reminds! big things happen when you regenerate translator after above process, the link below list detail discussion about Rosewood drive translator issue,
for your reference https://forum.hddguru.com/viewtopic.php ... 10&start=0

Someone who attended Ace Labs conference in Las Vegas June 2018 said ACE had found Media Cache maybe the cause of this issue, but until now they have not release any solution. So be careful with translator of ST Rosewood for new engineers. Follow the tips from post do help you in future.

[MindMergepk]

Hi! Hamidbid did you find a solution?

can you share the terminal log ?

[manhcuongvn]

step 1 unlock techmode in rom
step 2 goto teminal backup 28, 93..etc
step 3 translator by command.
Step 4 change 93 module in ATA mode. and restat power
done. 100% success my case

[mrdoktro]

Hi MindMergepk. I had no problem with unlocking the disk. Only the first time I was recovering data from the rosewood disk. Some wrote that you can not touch the translator and SMART, and others that you have no choice but to regenerate the transistor, because the problem is in the system file 93, and without regeneration, you will not get access to this file. And so I did, first on an identical test disk and then on the target one. 99.5% of data recovered, 0.5% bad block.

[Lylor]

This problem caused by damage to Media Cache. You should repair it, because it has critical information for data recovery. The optimal way is to read MC system file with error ignoring re-read bad sectors (PC3000 allows to do that). Finally you combine good part of it with bad part together and write fixed in the drive. After repower you should get full sector access.

[HDDscholar]

step 1 unlock techmode in rom
step 2 goto teminal backup 28, 93..etc
step 3 translator by command.
Step 4 change 93 module in ATA mode. and restat power
done. 100% success my case

I followed your steps but failed. ended with LED, is there any misoperation? later I will update a video to show you.

@Lylor would u please specific more detail here about Media Cache, how to handle the situation.

[HDDscholar]

This problem caused by damage to Media Cache. You should repair it, because it has critical information for data recovery. The optimal way is to read MC system file with error ignoring re-read bad sectors (PC3000 allows to do that). Finally you combine good part of it with bad part together and write fixed in the drive. After repower you should get full sector access.

Pls see my operation, any suggestions? thanks in advance.
https://youtu.be/QgpAyz3iXd4

[northwind]

step 3 translator by command.

NO.
This will cause lost MC data.

[MindMergepk]

Hi MindMergepk. I had no problem with unlocking the disk. Only the first time I was recovering data from the rosewood disk. Some wrote that you can not touch the translator and SMART, and others that you have no choice but to regenerate the transistor, because the problem is in the system file 93, and without regeneration, you will not get access to this file. And so I did, first on an identical test disk and then on the target one. 99.5% of data recovered, 0.5% bad block.

well, I am glad you have recovered it.
You can count me with those guys who says never touch translator.

[Alikhan]

Media Cache has been repeatedly emphasized in topics about rosewood, however some technicians I know from DFL told me to ignore MC when dealing with LM, they even published a feature to fix partial sector access in their latest update. And allegedly there are numerous cases proven to be solved by their new feature. I just wonder if algorithm against ECC enables us to gain access to user data, why insist on working with MC? Even in ACE's free support blog, there are articles about recalculating translator after backup of vital sys files

[northwind]

I don't know about DFL, I know my own experience.

I have tested this with good drives; I've created folders and put files inside; worked with the drive for a while, then tinkered with it a bit to become unstable and then m0 the drive. The files were gone. I ran DMDE on the drive, the folders and files were nowhere to be seen. MFT entries were gone as well, the most recent ones. Regen'ing the translator will give you access to data, but you can lose a good 70GB of recent data.

So, whoever says to ignore MC is wrong, IMHO.