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

WD10EACS Recovery?

March 8th, 2013, 2:13

Alright, I'm new here and after browsing and browsing I've decided to just join.

I've got a WD WD10EACS that has a burnt out section on the PCB, as it received a surge while running. Thankfully, the drive spins up and doesn't make any clicking noises indicating bad heads or anything. What I'd like to know is, can I swap in another PCB to revitalize this drive? I'm not worried about the data on it, as it was given to me in a tower with a bad motherboard/processor/psu because of said surge. Can I swap PCBs and format, or is this drive pretty much just dead?

Thank you.

Re: WD10EACS Recovery?

March 8th, 2013, 2:36

WD has adaptive on PCB and if you swap PCB you have to swap out the eprom on this one. But if it is not yours do not bother to buy a new PCB and move the ROM chip yourself. You will more than likely only have to invest a few bucks more to buy a brand new HDD which is better for you.

Re: WD10EACS Recovery?

March 8th, 2013, 2:39

That's what I kinda figured, I just wasn't sure. The burnt part is right next to the lower-left side of the PCB part number sticker/barcode, if that helps. I can upload pictures. PCB swapping won't help me? I'm not interested in the data on it, it was given to me by a friend.

Re: WD10EACS Recovery?

March 8th, 2013, 2:42

Here's the damage, if it helps.
Attachments
IMG_20130308_012026.jpg
IMG_20130308_011955.jpg

Re: WD10EACS Recovery?

March 8th, 2013, 3:22

Doesn't look burnt to me, just normal corrosion.

I think your problem is elsewhere, given that the drive spins and "sounds normal"

Either way, if data is not required then just toss the drive.

Re: WD10EACS Recovery?

March 9th, 2013, 0:32

Yes agree buy a new drive and toss this one.

Re: WD10EACS Recovery?

March 12th, 2013, 2:25

Ok, that's what I figured.

I thought it was burnt there because this was also in a RAID configuration with an identical drive, neither was recognized, and they both were damaged in the same spot, in the same way. Just strange to me.
Post a reply