ST8000DM004 Doesn't ID and stays BSY

[Protech]

Hi guys,

Have a ST8000DM004 here. Spins up and keeps going and no funny sounds. No ID and stays busy. The ACE blog for "No HOST FIS-ReadyStatusFlags" is only for non SMR drives so didn't want to go that route. Have attached the screen shot. can you please advise?

Thanks

Attachments

[Lukas]

The log provided probably concerns a problem with the Media Cache.
What help are you looking for?

[pepe]

no, it is related to a file containing a sequence of sysfiles, which could not be read during init.

[Protech]

no, it is related to a file containing a sequence of sysfiles, which could not be read during init.

let me give you a better picture. Drive stays BSY so I had to apply the NO HOST "BUSY" RDY in RAM solution to get it ready. Then it ID partially with capacity 0. I was able to read sys files 1B, 35, and 93 but 28 gives errors. Refreshing Utility status with ATA and Resources back up both gets the drive BSY again. I'm stuck guys.

Attachments

[pepe]

can you read 28 with ignoring errors? I don't mean forcing it through the 8MB but if there area only a few bads, it is still better than regen.

[Protech]

can you read 28 with ignoring errors? I don't mean forcing it through the 8MB but if there area only a few bads, it is still better than regen.

Noop, not able to read 28 in both ways. is Regen the only remaining way?

[pepe]

regen is pretty destructive when it comes to MC. Moreover, it might only solve the problem temporarily if heads cannot write properly. BTW, are u using native heads? If not, regen causes a big mess if not treated properly.
There are other ways, like regen it on a donor, but this though if you don't know how...
try reading 28 from StartSector+03E1 LBA to the end of the module, ie, if it starts at 0x10000, start reading at 0x103e1 to the last syslba of 28 with ignore errors. Save the result and send me to see if it can be used.
try both copies

pepe

[Protech]

regen is pretty destructive when it comes to MC. Moreover, it might only solve the problem temporarily if heads cannot write properly. BTW, are u using native heads? If not, regen causes a big mess if not treated properly.
There are other ways, like regen it on a donor, but this though if you don't know how...
try reading 28 from StartSector+03E1 LBA to the end of the module, ie, if it starts at 0x10000, start reading at 0x103e1 to the last syslba of 28 with ignore errors. Save the result and send me to see if it can be used.
try both copies

pepe

Heads are native. Haven't tried Regen so far, but for the life of me I couldn't figure out how to read the 28 just the way you asked...please help

[Protech]

regen is pretty destructive when it comes to MC. Moreover, it might only solve the problem temporarily if heads cannot write properly. BTW, are u using native heads? If not, regen causes a big mess if not treated properly.
There are other ways, like regen it on a donor, but this though if you don't know how...
try reading 28 from StartSector+03E1 LBA to the end of the module, ie, if it starts at 0x10000, start reading at 0x103e1 to the last syslba of 28 with ignore errors. Save the result and send me to see if it can be used.
try both copies

pepe

Heads are native. Haven't tried Regen so far, but for the life of me I couldn't figure out how to read the 28 just the way you asked...please help

Attachments

[pepe]

why over terminal? SATA?

[Protech]

This case has been solved and files have been recovered. Thank you so much Pepe

[pepe]

nice to know, thanks.