Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
July 12th, 2011, 21:19
I have this problem Rst 0x08M on terminal ctrl+z does not work hdd is not detected by bios
The data is not important i want the hdd... if is possible
July 13th, 2011, 2:44
"Rst 0x08M" is normal
July 13th, 2011, 11:31
are you sure terminal set up is correct?
July 13th, 2011, 11:38
labtech wrote:are you sure terminal set up is correct?
If setup was wrong 'Rst 0x80' message will not appear
July 13th, 2011, 12:16
I while ago, I rigged together a RS232 adapter with wires for Rx Tx. I did not do a good job with the cables on it. As result, I was able to receive signal in terminal, but could not transmit anything.
Was thinking OP may have the same problem.
July 13th, 2011, 14:37
tx cable problem
now
Rst 0x08M
ASCII Diag mode
F3 T>
LED:000000CD FAddr:000068DB
LED:000000CD FAddr:000068DB
LED:000000CD FAddr:000068DB
LED:000000CD FAddr:000068DB
no commands are accepted
July 13th, 2011, 15:37
Hdd is busy all the time and not detected by bios
July 13th, 2011, 16:47
I have not seen this model drive before.
It is an F3 Seagate drive, thus likely a firmware issue.
Since I have not worked on a drive like this before, I am unable to recommend a particular solution, but it is possible that one of the more popular solutions is applicable here.
Suggest you dig deeper, study more the issue and possible solutions by reading materials online, forums, manuals, books, whatever.
You can contact Seagate manufacturer and see if this model drive was affected by any firmware bugs. You will need the S/N ready.
Not sure what information you have available or how experienced you are...
July 13th, 2011, 17:16
Analysis...analysis...ANALYSIS...
July 13th, 2011, 18:58
http://www.overclock.net/hard-drives-st ... -pics.htmlRst 0x08M
ASCII Diag mode
F3 T>/2
F3 2>Z
DiagError 00005014
F3 2>Z
HighPowerMode 0027
Spin Down Complete
Elapsed Time 0.083 msecs
F3 2>U
HighPowerMode 002F
ExecuteSpinRequest
Spin Up Complete
Elapsed Time 3.231 secs
F3 2>/1
F3 1>N1
Init SMART Fail
LED:000000CC FAddr:0024ECD9
LED:000000CC FAddr:0024ECD9
Rst 0x08M
ASCII Diag mode
F3 T>m0,2,2,0,0,0,0,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewr
ite Retries = 0000
Init SMART Fail
LED:000000CC FAddr:0024ECD9
LED:000000CC FAddr:0024ECD9
Hdd is working and detected by bios but now i have internal cache error....
July 13th, 2011, 20:07
Can you access LBAs? What tools are you using to access this drive?
July 13th, 2011, 20:45
deleted
July 13th, 2011, 23:52
labtech wrote:Can you access LBAs? What tools are you using to access this drive?
Only TMOS. I don't have any special tools pc3000 etc...
July 14th, 2011, 0:08
grigoreee wrote:http://www.overclock.net/hard-drives-storage/457286-seagate-bricked-firmware-drive-fix-pics.html
Rst 0x08M
ASCII Diag mode
F3 T>/2
F3 2>Z
DiagError 00005014
F3 2>Z
HighPowerMode 0027
Spin Down Complete
Elapsed Time 0.083 msecs
F3 2>U
HighPowerMode 002F
ExecuteSpinRequest
Spin Up Complete
Elapsed Time 3.231 secs
F3 2>/1
F3 1>N1
Init SMART Fail
LED:000000CC FAddr:0024ECD9
LED:000000CC FAddr:0024ECD9
Rst 0x08M
ASCII Diag mode
F3 T>m0,2,2,0,0,0,0,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewr
ite Retries = 0000
Init SMART Fail
LED:000000CC FAddr:0024ECD9
LED:000000CC FAddr:0024ECD9
Hdd is working and detected by bios but now i have internal cache error....
Then it is NOT working...
July 14th, 2011, 1:40
The internal cache is the ram chip on the controller? (H5DU6462CTR)
July 14th, 2011, 2:12
The problem was elsewhere, and you applied a random solution. That's all. If you really want to reuse the disk it takes more than just hyperterminal to make it work CORRECTLY again.
July 14th, 2011, 2:17
BlackST wrote:The problem was elsewhere, and you applied a random solution. That's all. If you really want to reuse the disk it takes more than just hyperterminal to make it work CORRECTLY again.
Bad solidering on ram chip.... Now is working ...
July 14th, 2011, 6:35
if it was the ram it didn't start at all neither was responsive on tml.
Powered by phpBB © phpBB Group.