I've got a 1-year old Maxtor sata diamondmax 10 200gb, model 6v200e0.
First let me say I do have 95% of drive backed up but there are a few thinges I would like to get if I can. Had no signs of possible failure and HD monitoring software said all was good.
As of now HD not seen in windows xp, during boot up the drive showes up but model # is different with 0GB. Unit spins but arm just moves back and forth (clicking sound)
Could this be firmware failure?, fried PCB?
Any ideas for recovery? swapping PCB?, swapping disk to different HD?, software?
Thanks for any help

First of all, try to swap pcb and check if behaviour of the drive is the same.

When you say the arm moves back and forth do you know this by opening the drive?

Also disk is reported in BIOS but may have a different name such as SABRE or similar. This happens when the firmware is damaged or cannot be read. You can try to change PCB but it sounds like you may have some damage to the reading heads. If the heads are damaged and your data is important it may be worth contacting a professional company for a quote on data recovery.

Thanks for your help.
Data isn't important just wanted to try something for fun if nothing else.
I have a bad habbit of having to figure things out myself. That nice bluish sticker that says void if removed turns clear with the words void on it if you tamper with it. good by warranty.....
Yes I did open it and I understand about dust. I made a so called clean room and looked in only long enough through the boot up. After boot, drive stops clicking.
If I swap PCB could there be a firmware issue?
I'm collecting ideas to try, drive is trash anyhow.

It could be firmware issues, on those drives wouldn't be the first time I would see that behaviour.

The fact during boot in bios the drive showes up as a diffeent name makes me think it's firmware but not sure how to fix.
If I switch PCB from same model and firmware isn't the same as original will it work?

hy,
An firmware for SABRE 6V200E0 ,have someone??
If yes give me please.
Thanks.

You need PC3000 to fix this problem - nothing you can do yourself.

Jon

_________________
http://www.datasaversllc.com