WD20EACS-11BHUB0 not initialized anymore under HDD ID PC3000
Posted: January 15th, 2013, 16:57
Hello I have a question about one data recovery which I`m doing today.
I`m newbie with PC3000 UDMA, our company has it from long time and now I`m assigned to work with it.
I was taking data out from WD20EACS-11BHUB0 and it was doing it right after successful SA Structure Test. The Drive ID was recognized and it was working fine, slow but fine. Because drive reaction time was very slow, and on every 4 green sectors I was getting 1 black. I decide to play with the Reading settings. I put big delays in reading sections, and skipped resetting the drive because it was very slow.
After a while properly scanning drive decide suddenly to get me Black Sectors in big columns. First I tought there are unreadable sectors but after several columns I've got suspicious.
I decide to stop the process and try to do reinitialize the drive and do the SA Structure Test again.
Turned OFF the drive, Turned ON, Waited until BSY goes OFF and then BAM, drive came with no ID and start knocking.
When I turn ON the power it starts Knocking for several seconds, then stops for several more. Then Knocking again.
PC3K is not recognizing the HDD ID anymore. In autodetect it finds the Family Sadle G6, Sectors, Cyl, Arc, Heads number, but not HDD ID so I cannot starts SA Structure Test.
I have Profile previously created. Also I still can open the Task in PC3K Explorer saved from previous scan.
(sorry for my lame explanations but I`m still newbie and don't know most of the terms)
In the PC3000 manual it say something about this case, that it can be caused by Disabling the heads without setting the LBA to proper size, but I didn't change the LBA size.
And they Offer to short circuit several test points/F23,F19/ on the PCB board, but cannot find them for my drive: WD20EACS-11BHUB0
If someone have explanation or ideas why suddenly it decide to react like this it will be grateful.
Regards
I`m newbie with PC3000 UDMA, our company has it from long time and now I`m assigned to work with it.
I was taking data out from WD20EACS-11BHUB0 and it was doing it right after successful SA Structure Test. The Drive ID was recognized and it was working fine, slow but fine. Because drive reaction time was very slow, and on every 4 green sectors I was getting 1 black. I decide to play with the Reading settings. I put big delays in reading sections, and skipped resetting the drive because it was very slow.
After a while properly scanning drive decide suddenly to get me Black Sectors in big columns. First I tought there are unreadable sectors but after several columns I've got suspicious.
I decide to stop the process and try to do reinitialize the drive and do the SA Structure Test again.
Turned OFF the drive, Turned ON, Waited until BSY goes OFF and then BAM, drive came with no ID and start knocking.
When I turn ON the power it starts Knocking for several seconds, then stops for several more. Then Knocking again.
PC3K is not recognizing the HDD ID anymore. In autodetect it finds the Family Sadle G6, Sectors, Cyl, Arc, Heads number, but not HDD ID so I cannot starts SA Structure Test.
I have Profile previously created. Also I still can open the Task in PC3K Explorer saved from previous scan.
(sorry for my lame explanations but I`m still newbie and don't know most of the terms)
In the PC3000 manual it say something about this case, that it can be caused by Disabling the heads without setting the LBA to proper size, but I didn't change the LBA size.
And they Offer to short circuit several test points/F23,F19/ on the PCB board, but cannot find them for my drive: WD20EACS-11BHUB0
If someone have explanation or ideas why suddenly it decide to react like this it will be grateful.
Regards