Switch to full style
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
Post a reply

WD2500JS recovery needed

June 8th, 2011, 18:55

This one is beyond my capabilities.

WD2500JS. The drive starts and I can do a SMART ATT and ID/EID (w/ MHDD). But when I try SCAN, I get one click on the RECAL and then the drive ABRTS on every sector.

Like other WD drives, the board on this one looks heat discolored in areas, and the foam under the PCB is brown near some components. But I've seen worse.

I think moving the ROM over to a new board is a lost cause. Why? Well, the drive powers up, spins, and is able to read enough of the firmware to get to the point where I can perform a SMART ATT and get reasonable output. It seems to me that, if the board can do all that, it isn't the board.

So it would seem to me to be either a firmware corruption issue, or a head issue. Neither of which I am able to address.

Or am I wrong?

Re: WD2500JS recovery needed

June 9th, 2011, 4:20

You are probably right.
If you want to be 100% sure, you can swap PCB + ROM and check the beahviour after.
If you have the same problems, that will be FW issue, or any heads or failed head.
It might still be possible to image from good heads or else replace them all.

Re: WD2500JS recovery needed

June 9th, 2011, 22:04

cgallery wrote:This one is beyond my capabilities.

WD2500JS. The drive starts and I can do a SMART ATT and ID/EID (w/ MHDD). But when I try SCAN, I get one click on the RECAL and then the drive ABRTS on every sector.

Like other WD drives, the board on this one looks heat discolored in areas, and the foam under the PCB is brown near some components. But I've seen worse.

I think moving the ROM over to a new board is a lost cause. Why? Well, the drive powers up, spins, and is able to read enough of the firmware to get to the point where I can perform a SMART ATT and get reasonable output. It seems to me that, if the board can do all that, it isn't the board.

So it would seem to me to be either a firmware corruption issue, or a head issue. Neither of which I am able to address.

Or am I wrong?

Would you like to send it in for a quote?
Post a reply