WD10EAVS

[pix]

Hi,
I have a WD10EAVS disk that stopped working. It was in a WD My Book mirror edition in raid 0 mode.
Now MyBook says that the disk isn't inserted. I tried it in another usb cabinet and it can't detect the device.
I connected in a PC and the bios can't detect it.

I thought that the board was broken, so I bought a donor disk. It's the same model (WD10EAVS) and it has the same board (2060-701590-000 REV A). The new disk is working.

Then I swapped the two boards, thinking that the old disk with the new board should work, but it doesn't. Then I tried the new disk with the old board, but it doesn't work too!
I tried to check information status with MHDD but I get the same message (photo shot attached) with both disks (old disk with new board and new disk with old board).
When I try MHDD with the new disk+new board, it can detect all the settings.

I think I'm missing something, but I don't know what

Do you have any advice or suggestion?

Attachments

[Alexii]

Heya m8. Well what you are saying that original mirror u changed and now the drives are striped right ? . Try connecting each one with their original PCBs to computer. If possible - record the sounds they make as you apply power to them. It will make remote diagnostics easier. In your situation we need both drives working to get the data. PS did u drop the caddy by any chance ?

[pix]

Yes, the disk are striped. The first one is broken, the second one is good. I bought a 3rd disk to use as donor.
The caddy didn't had any shock. It was working, and at a certain point I got many errors like "windows can't write file $....". At the next boot I couldn't read the data

I checked, the disk doesn't seem to produce any strange noise. Here there is the recording: http://www.mediafire.com/?28cpixfc3z941yg (I couldn't attach 3gp nor mp3)

[Alexii]

Cant tell anything from the sound unfortunately. Not loud enough. I wanted to hear the sound the heads make as they calibrate and try to init... So with original board that drive is not seen in MHDD right ? BTW straight PCB swaps very rarely work for WDs. U need to program the donor board to be compatible with the patient drive. In some cases it can be done by moving rom at location U12. If the rom at u 12 is not present - then special equipment is needed...
So any chance u can put original board on original drive and try to record the startup noise again ? Also can u give the full model number of the drive plz.

[positivebit]

The caddy didn't had any shock. It was working, and at a certain point I got many errors like "windows can't write file $....". At the next boot I couldn't read the data

Hi, i have just head swapped a WD same model like yours, with scratches from platters.
Your situation should be different, with right tools diagnose can be made properly, anyway i am 99% sure there many bad sectors on data area + maybe bad sectors on SA.
Is your data evaluable? if yes i wouldn't power on and off again, it can make difference between recovery or not, or at least other bad sectors can be growing and files recovery list can be smaller.

[pix]

Alexii, any suggestion on howto record the sound? I tried also with a stethoscope but without success I'll try this evening with a better microphone.
With the original board I can't even launch mhdd.
The bad disk serial is WCAU47560722
The donor disk serial is WCAU43725195

positivebit, the data in it is not essential, but I would prefer not to lose it

[Alexii]

Ok now... Ur drive is WD10EAVS-00D7B1 and belongs to Kermit family. Just to verify , the sound u provided was recorded from the bad drive with its original board correct ?

[pix]

The first sound was the bad drive with the other board.

Attached there is the sound of the bad disk with the original board: http://www.mediafire.com/?18ias89fhi37i1r

[Alexii]

hmm... cant say one way or the other. No clicks though. I cant tell if the heads are leaving parking or not though... Unscrew the bad PCB turn it around and tell me if there is a chip at position U12. I dont have a kermit handy so cant say if rom is embedded or not. If the position U12 is populated - u can try taking that chip and moving it to the donor board, then puting the donor board on ur drive and checking if u can see the data. Although at this time i will defiantly vote for the proper diagnostics...

[BlackST]

Scusate ma continuando cosi' si rischia di fare una ca....ta dietro l'altra.
Punto primo : ha smesso di funzionare MA continua a girare , da quel che sembra. Se e' cosi', il PCB puo' essere responsabile in un caso su 100 oppure c'e' un problema piu' complesso.
Punto secondo : cambiare un PCB cosi' com'e' non funziona (notato ?!) , fare strani cambi di ROM non porta a nulla se il problema NON e' li'.
Punto terzo : puo' benissimo essere un problema di firmware o mezzo fisico mezzo firmware e i sintomi sono ESATTAMENTE QUELLI.
Punto quarto : e' un RAID quindi una eventuale corruzione di uno dei dischi e' un problema (ammesso di ripararlo perfettamente).
L'unica cosa da fare e' una diagnosi seria con gli opportuni strumenti, che sfortunatamente non sono ne' gratis ne' "disponibili". Basta esperimenti.
C'e' di bello che se e' un problema di firmware tutti i dati possono essere ancora intatti, oppure si puo' risistemare , al limite (caso peggiore) riducendo di capacita' , per non buttare via il disco cosi' com'e' (che spreco!)
Ma non e' ne'' gratis ne' alla portata dell'utente finale.

Sorry, but going on this way leads to a neverending sequence of silly attempts.
First : drive not recognised BUT still spinning, at least that's what it seems.
If so, PCB is the culprit 1 out of 100, otherwise there's a more complex problem.
Second : straightforward swap of PCB leads to nothing (did you notice it ?), even ROM swap leads to nothing if the problem is not there.
Third : can perfectly be a mixed physical / firmware problem , giving out THESE EXACT SYMPTOMS.
Fourth : It's a RAID, so the corruption of one of the disks is another problem, assuming you can perfectly fix it.
The only thing to do is a diagnose with the appropriate tools, that unluckily are not for free neither... "available". Stop tinkering.
The only good thing is that , if it is a FW problem, all data is still safe and sound, or you can refurbish the disk , eventually (worst case) downsizing it, just to avoid discarding it (what a waste !).
But again, all this is not for free neither at reach of "average joe".