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
February 1st, 2011, 15:55
Hi all,
I have a ST3500418AS with FW of CC36 and Site of SU. The drive came in and it was diagnosed as standard busy FW issue. At first, drive would go ready after a long time but lose readiness when you try to access it. Now drive will not go ready at all, even when the PCB is disconnected from the drive. As such, I cannot repair the FW issue. I checked on Seagate's website and this model is eligible for a firmware upgrade. However, when I type in the serial it tells me that it isn't eligible. Any suggestions on how I can get this to go ready and fix the FW?
Thanks,
Dizi
February 1st, 2011, 15:58
AFAIK CC36 is not a drive afflicted by standard busy bug. Also busy bug = drive holds busy and you report that it it did go ready for you after some time initially. Looking at the terminal during that long init could have shed some light on what exactly was the drive doing. Do you have it ?
February 1st, 2011, 16:03
Alexii,
Unfortunately, I do not have that. Did not run the terminal log when we first plugged it in, as we were hoping to extract the customer's important data fast for them. While it did go ready, I have seen one or two drives go ready in the beginning and then contract the bug almost like a disease. Similarly, I have also seen drives need to be repaired two or three times in order to get all the data off. But I have never seen a drive locked up like this one is.
Dizi
February 3rd, 2011, 19:35
I've got almost the same problem with an ST3500418AS (9SL142-300, CC34, WU), except it never gets to Drive Ready, Drive Seek Complete. Also doesn't appear to be the standard 7200.11-esque BSY bug, so presumably this 7200.12 drive is stuck in BSY for a reason. Anyone able to shed some light on common causes with this drive family?
Powered by phpBB © phpBB Group.