PC-3000 Forum

I have very curious case. It is ST31000333AS. It clicks several times (sounds very strange) and then comes to [DRD DSC] but when trying to access any sector it goes to [BSY DRD DSC] and then I get no response (even from terminal) unless I power cycle it. The same happens when I try 'Check heads' command (just BSY and getting timeout from terminal)

ID is being detected -
Model ST31000333AS
Serial: 5TE08DFP
Firmware: SD35
Capacity 931.51GB (1 953 525 168)

Terminal log from initialozation:

I do not know this new drives (F3 Arch.) so I co not know what could that be.
By the way it sounds I'd say there is something wrong with heads but could that be firmware problem? As far as I know it is one of affected drives but wouldn't like to mess it up. Any suggestions?

Regards,
Pawel.

seagate 1 TB have 8 head. I think there is must a dead head or more. but the active head still working.

I don't think so
new hdd ,head very new
alway show busy and 0 GB
IF can't repair , change good PCB
don't forget change ROM

sounds very strange
7200.11 always strange sound
ka kl !! ka kl !! ka kl !!

I was searching on Internet and all over there is a new procedure that has been posted for repairing these drives. I am not sure if it would work for you but you could try and go to HDDGuru and see the procedure. They claim that it will really repair these drives. I have never tested it or used it but take a look it might give you a starting point as to repairing your problem. Only a suggestion

poehere wrote:I was searching on Internet and all over there is a new procedure that has been posted for repairing these drives. I am not sure if it would work for you but you could try and go to HDDGuru and see the procedure. They claim that it will really repair these drives. I have never tested it or used it but take a look it might give you a starting point as to repairing your problem. Only a suggestion

http://forum.hddguru.com/tutorial-resol ... 11040.html

maybe this is you are talking about... You can give it a test...
post the result here

I have not successfully done this specific method, it involves shorting of the read channels inbetween the LED errors to gain temporary terminal access, never managed to get the terminal inbetween the errors myself.