7200.12 what's wrong?
January 10th, 2015, 14:15
Hi,
I need some help. I have this drive, somewhat slow to appear in BIOS but cannot be seen in Windows. MHDD detects it with some delay, also after pressing F2 it needs about 10 secs to id. SMART is tolerable and in terminal it outputs what should be expected.
Funny is MHDD lits HPA. The drive behaved normally until it happened and nobody played with it. So why can't I see the drive in windows device manager? Thanks for your advice.
According to Seagate, drive has 1,465,149,168 sectors, so do you think it has to do something with HPA? If I NHPA, it won't effect data, will it?
I need some help. I have this drive, somewhat slow to appear in BIOS but cannot be seen in Windows. MHDD detects it with some delay, also after pressing F2 it needs about 10 secs to id. SMART is tolerable and in terminal it outputs what should be expected.
- Code:
Rst 0x20M
Servo Processor Is Reset.
RW: Disc Ctlr Initialization Completed.
ExecuteSpinRequest
- Code:
(P) SATA Reset
- Code:
ASCII Diag mode
F3 T>
Funny is MHDD lits HPA. The drive behaved normally until it happened and nobody played with it. So why can't I see the drive in windows device manager? Thanks for your advice.
According to Seagate, drive has 1,465,149,168 sectors, so do you think it has to do something with HPA? If I NHPA, it won't effect data, will it?
- Attachments
-
- HDD2.JPG (56.47 KiB) Viewed 3850 times
-
- HDD1.JPG (52.54 KiB) Viewed 3850 times
Re: 7200.12 what's wrong?
January 10th, 2015, 14:58
Looks like it's failing rapidly.
If you don't need the data then bin it and buy a new one.
If you do need the data but it's not that important then you can try some DIY stuff like cloning with dd_rescue or media tooks pro and then using recovery software like getdataback or rstudio, AT YOUR RISK.
Or if the data is important to you, then seek professional help.
Good luck.
If you don't need the data then bin it and buy a new one.
If you do need the data but it's not that important then you can try some DIY stuff like cloning with dd_rescue or media tooks pro and then using recovery software like getdataback or rstudio, AT YOUR RISK.
Or if the data is important to you, then seek professional help.
Good luck.
Re: 7200.12 what's wrong?
January 11th, 2015, 7:16
Thank you for replying, at least the obvious was confirmed. 
Let me ask some questions:
1. V40 is empty. Will it hurt to try m0,2,2 and N1 in this order?
Or how can I diagnose it better?
3. It has CC46 fw. Do you recommend updating to CC49? Might solve some firmware issues? What are the odds it will finish successfully?
Prosoft was unable to copy anything, so drive must be brought into a better shape before trying to clone with free tools. (My route is DIY, as you might guess).
Let me ask some questions:
1. V40 is empty. Will it hurt to try m0,2,2 and N1 in this order?
Or how can I diagnose it better?
- Code:
F3 7>X
Head 00 Resistance 010A
Head 01 Resistance 0118
Head 02 Resistance 00B8
3. It has CC46 fw. Do you recommend updating to CC49? Might solve some firmware issues? What are the odds it will finish successfully?
Prosoft was unable to copy anything, so drive must be brought into a better shape before trying to clone with free tools. (My route is DIY, as you might guess).
- Attachments
-
V4.txt- G-List
- (25.59 KiB) Downloaded 527 times
Powered by phpBB © phpBB Group.