Drive recognized properly in BIOS. No clicking. Simply shows 0 lba just like the 7200.11 drives. I've done quite a few 7200.11's but this is the first Momentus drive I've had come in with these symptoms. Are the terminal commands the same for this drive? If they are different does someone mind passing along the commands to me? Please feel free to PM if you prefer.

Thanks!

can you post terminal log

_________________
ZeBong
" что случилось в России - останется в России "
" Россия еще раз"

It will have to be tomorrow. I don't have the drive with me right now. I had read somewhere, that the 7200.3 Momentus drives were having the same firmware glitch, which is why I asked. It appears to be exactly like the 0 lba issue with the 7200.11. The firmware is DE13.

I believe the failure that you see in the 7200.11 is not a new failure. It has been happening to seagate drives for some time, but the issue with the 7200.11 was that there was a bug n the firmware causing it to happen very often.


So it is possible to see this type of problem in all seagate drives, but it is just much much more common in the affected 7200.11 drives.

When I power up the drive, all I get in the terminal window is this:

Rst 0x10M

I can hit ctrl-z to enter level 2, but there really isn't much that comes up when the drive powers on. Even in PC3K, I get nothing on the terminal output.

This is normal output. F3 commands will work on this drive as it is F3. The standard command is non destructuve and can be applied to these disks with 0MB fault.

Is it the same command, or is there a different variation?

F3 T>m0,2,2,0,0,0,0,22

I am pretty sure the command listed above should regenerate the partition in this drive. However, this is the result I get:

DiagError 0000500E Process Defect List Error
R/W Sense 00000002, R/W Error 841C0087, List Offset 00000000, File Error 0000000
1

I am 99% sure that the command is different, and that you may have just made things much worse. Someone alittle more versed in Seagate commands will probably confirm, but I am very certain the regenerate command is different on this drive.



Regards,

Actually this wasn't done to the customer's drive. I have a practice drive here that I'm working with first just to see what kind of results I get.