Hi everyone
I'm having some issues with a Seagate Momentus 4. The drive showed up with 0 as capacity in the BIOS. After looking this up, and although it seems there was no firmware update for that drive according to Seagate
it seems that it had the same firmware issues than the 7200.11.
So I tried the "0 LBA" procedure from here : http://www.msfn.org/board/topic/128807- ... 0011-hdds/That fixed the capacity. Drive now shows up in the BIOS with correct capacity, but BIOS recognition is unusually long and it looks like the drive is stuck in some sort of busy state. I also tried the BSY procedure from same link but it didn't fix anything. I can access the console fine though. Closest thing to seeing the files was connecting the drive in an USB enclosure. Led from the USB enclosure keeps blinking as if there's activity. Partitions may mount up in Windows and I sometimes can see the files but it just stays inaccessible.
Firmware info :
Code:
Package Version: HO077A.HPM1.CA0A09.0003HPM1, Package P/N: ---------, Package Builder ID: 84,
Package Build Date: 07/10/2009, Package Build Time: 14:17:45, Package CFW Version: HO07.HPM1.00179468.8400,
Package SFW1 Version: A788, Package SFW2 Version: ----, Package SFW3 Version: ----, Package SFW4 Version: ----
Controller FW Rev: 0A090001, CustomerRel: 0003, Changelist: 00179468, ProdType: HO07.HPM1, Date: 07/10/2009, Time: 141745, UserId: 00080603
Servo FW Rev: 6843
RAP FW Implementation Key: 0E, Format Rev: 3E03, Contents Rev: 67 15 04 05
If I press . in command line
Code:
Current R/W User LBA 00000000 LLL CHS 000000.0.0000 PLP CHS 000000.0.0000
R/W Status 1 R/W Error 00000080 Ready
Am I reading correctly that the LBA issue may not be fixed after all ?
If I do ^C to reset the drive, I get this in terminal before ^Zing :
Code:
Rst 0x10M
(P) SATA Reset
(H) SATA Reset
(H) SATA Reset
(H) SATA Reset
(H) SATA Reset
(H) SATA Reset
(H) SATA Reset
I understand you guys don't want to spoon fed the answers to everyone but I'd appreciate any hint in solving this. Thanks in advance.
0) REALLY BAD idea to apply the "internet supa-dupa one-fits-all" fix without knowing what was going on.
1) the drive is OEM.
2) The problem WAS elsewhere, to me.
3) It is very difficult to do things only with hyperterminal. Better say : hyperterminal helps but you should know what to do.