ST8000DM004-2CX188 V11

[Alandata Recovery]

   Model : ST8000DM004-2CX188
  Serial : ZCT27WSL
Firmware : 0001
Capacity : 0 MB ()

I have this drive. It was starting to have trouble reading and the customer kept replugging and then brought it in.

Sounds good - not crashed yet.

It came ready for me in universal utility and I read sector 0.

Then exitted and went to seagate util and it went BSY - I guess when reading ID.

Replugged it and this time it retried a bit and spun down - its right on the edge of no-ready.

I applied tech patch

I can get terminal

Got sysFile list with ^Y

Read all the critical sysfiles

1B 17A 28 35 93 348

There is about 12 entries in the NRGL

Depending what I do I start getting LED-BD messages.

There are warnings with rosewoods about regening the translator

editing the head map.

Normally with seagates

you untick the SMP

clear alt-list

clear smart

regen translator

and you are good.

I am unclear about whats safe to do with these....

Any advice?

Thanks

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Boot 0x0100MAF1120001    
SpinUp
TCC:001E

Trans
Tech Unlock Handshake: 0xCAF5D392
Reply:

Rst 0x0100MAF1120001    
(P) SATA Reset

   NVCScram Saved HB Size:020A
    LD: MD_Alloc:00000090 HB_Alloc:0000 MD_Alloc:80380000 HB_Alloc:8032 FlashRestorePowerDevReg 7E: 7001   PowerDevReg 7D: 0044 MD_Saved:00000090 HB_Saved:00000000 MD_CRC:3B4A
    PP: MD_Alloc:00016800 HB_Alloc:0000 FlashRestore
PVTSize: 0008B16C   CompSize: 000031E2   DeCompSize: 0008B16C MD_Saved:000031E2 HB_Saved:00000000 MD_CRC:E238
    MC: MD_Alloc:00003000 HB_Alloc:0000 FlashRestore
DataLength: 00000310 MD_Saved:00000310 HB_Saved:00000000 MD_CRC:4C0E    DataLength: 000031E2
DSP003F
2Sync:0 4............................................................................................................................................................................................................................................................................................................
 MCMainPOR: Start:
 Media Cache Data Base  03A3812AB0 ODUmpEndHostLba = 0005F526A8 IDUmpStartHostLba = FFFFFFFFFF
 Check MCMT Version: Current
 Secondary is latest! - 00000001
 Primary is obsolete
[MCMTW_DSW] Primary - 000A4392
MSPSequenceNumber(Disc) 001FF900
MSPSequenceNumber(MCMT) 001FF8FEMS UDE detect during recon   LPCDisc=00 4BE29CAD 0026
MS Read Fails: 5F14E568,0000DA00
Starting LBA of RW Request=00755F7B4F  Length=00001B40
ProcessRWError -Read-   at LBA 00755F7E41  Sense Code=43110081Out: [PRA]!

Starting LBA of RW Request=00755F7B4F  Length=00001B40
ProcessRWError -Read-   at LBA 00755F7E51  Sense Code=43110081Out: [PRA]!

Starting LBA of RW Request=00755F7B4F  Length=00001B40
ProcessRWError -Read-   at LBA 00755F9502  Sense Code=43110081Out: [PRA]!

 NECS: CorruptedSectorsRecon - Head:00000116 Tail:00012468
 LastWrittenDiscLBA : FFFFFFFFFFFFFFFF
 MCMainPOR: MediaCacheDiscStateFlags 0000002A  MCStateFlags 00000041
6Gb Max Speed lowered to 3Gb for Intel bug
Send Status: COMRESET seen
FIS34
ENP003F
2Sync:1 C
ASCII Diag mode

F3 T>
F3 T>
ASCII Online mode

Di 1D
TCC:0020 EMCDataErr:0000000F

[BRO - 0002] 005170BC34 - 005170D8E3 Extents - 0002 Blk - 00000990 D - 00000140
Common path start quit now Out:
LED:0x000000BD FAddr:0x00008046

PrgF
LED:0x000000BD FAddr:0x00008046

LED:0x000000BD FAddr:0x00008046

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

--

Alandata Data Recovery -  (949)287-3282  
"Cleanroom Data Recovery of RAID, VMware, NAS, Linux, Tape, Disk, Forensics"

www.alandata.com   www.alandataRecovery.com

[t...@desertdatarecovery.com]

Ace say that rebuilding the translator should not be done on Seagate SMR drives. They say as SMRs use a secondary translator the whole firmware is a different structure and Ace claim it can brick the drive. However I (and others) have done it for fun on donor Rosewood drives and it did not brick the drive. However I wouldn’t try it on a clients drive.

 

When Ace have logged in here to look at SMR drives, most of the time they do the standard 3 without rebuilding the translator.

 

Clear MCMT (you may loose data so is a last resort)

Clear slip list

And clear DOS tables.

 

Tim Homer - Lead Engineer

Desert Data Recovery

t...@desertdatarecovery.com

www.desertdatarecovery.com

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/CAH-%2BjWRKgausvDUwsbjgzKEzH%2Bgf5zuRm5oe5v36iBP33GUKDw%40mail.gmail.com.

[wayne horner]

thanks!

 should i also clear the USE media cache tick in the SP ?

write block ?

Alandata Data Recovery -  (949)287-3282  

"Cleanroom Data Recovery of RAID, VMware, Network Attached Storage, Linux, Tape, Disk, Forensics"

www.AlanData.com   www.AlanDataRecovery.com

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/059001d8b677%2489c3bea0%249d4b3be0%24%40desertdatarecovery.com.

[Desert Data Recovery]

You should always write block if possible. I have found unchecking MC in SMP causes more issues than it solves. 

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/CAJEn65rXs0eZZ02x_sbCOzOcD7he%3D53CwE2ARGi%3DDFzh-zajKg%40mail.gmail.com.

[wayne horner]

I cleared the smart

cleared the alt list and regened the translater

repowered and now I get read errors everywhere.

I wrote hte original 28 translator back

repowered

now its working pretty good..

weird is the drive acts like it gets a power off reset when reading certain areas.

I have to unlock the handshake

reupload the ram block

^R

to get it reading again..

Alandata Data Recovery -  (949)287-3282  
"Cleanroom Data Recovery of RAID, VMware, Network Attached Storage, Linux, Tape, Disk, Forensics"

www.AlanData.com   www.AlanDataRecovery.com

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/CAOasWzvS2Vn%2BnCi07_fhT9fvPi5wdUjxy26eJXm8hPN%3DOwB6zA%40mail.gmail.com.

[t...@desertdatarecovery.com]

“weird is the drive acts like it gets a power off reset when reading certain areas.”

 

I get that a lot with SMR drives, especially the WD Spyglass family after a head swap. As the FW is checking the resistance in the heads I think sometimes swapping from a good head to a dodgy head while imaging can cause the reset, I am guessing due to the FW. I have found imaging in PIO, using a smaller block size, or imaging head by head can help.

 

Tim Homer - Lead Engineer

Desert Data Recovery

t...@desertdatarecovery.com

www.desertdatarecovery.com

 

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/CAJEn65rkJxdCF4xcHS_7Z-BG%2B-xma7tjD5doW6_FWt%2BZJVkjow%40mail.gmail.com.