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
July 26th, 2009, 23:03
hi forum
i am having some issues and wondering if anone can provide some info please re the above drive.
here is some histroy for this drive
initially drive cmes in and clicks loudly, spins up and then spins down , drive does not become ready and after about 30 seonds just switches off.
now i have an identical drive. with full DCM match forall characters
the donor drive all works perfectly well.
i tried to put the patient drive into kernel mode(odyssey family) but was getting error codes and drive could not enter kernel mode.
i tired a board swap and drive would always remian busy and kept on clicking and same thing after 30 seconds would just powr off.
i tried my patient board on the donor drivem drive only remains busy and did not id.
suspecting head issues i replaced the heads.
after replaing heads my patient drive clicks very softly 10 times psins up then spins down and then does this process again before switching off. once again any thing i try and do get the error essage
WD Techo ON Error Device Error Detected 51/04 (ABR)
i swapped heads back to the way they were originally,
so patient drive has patient heads, drive spins up, no clicking this time, and rive becoes ready , drive still keeps on spinning and remains spinning and sounds normal and healthy.
i tired entering WD utilty and it will not autodetect, i selected the family manually (odyssey) and get the same message again as above
WD Techo ON Error Device Error Detected 51/04 (ABR)
i again cant enter kernel mode or do anything with the drive.
drive id is not read, capacity is .49mb
heads test show no heads available for test
and get the below log for some other tests
WD Techo ON Error Device Error Detected 51/04 (ABR)
Reading service tracks
Into folder............................. : <HDD Profile>\Data\Tracks
Reading method.......................... : Composite reading
Cyl -1.................................. : Ok
Cyl -2.................................. : Ok
Cyl -3.................................. : Ok
Cyl -4.................................. : Ok
Cyl -5.................................. : Ok
Cyl -6.................................. : Ok
Cyl -7.................................. : Ok
Cyl -8.................................. : Ok
Cyl -9.................................. : Ok
Cyl -10................................. : Ok
Cyl -11................................. : Ok
Cyl -12................................. : Ok
Cyl -13................................. : Ok
Cyl -14................................. : Ok
Cyl -15................................. : Ok
Cyl -16................................. : Ok
Cyl -17................................. : Ok
Cyl -18................................. : Ok
Cyl -19................................. : Ok
Cyl -20................................. : Ok
Reading modules
Into folder............................. : <HDD Profile>\Data\Modules\
Reading method.......................... : Composite reading
Reading modules
Into folder............................. : <HDD Profile>\Data\Modules\
Reading method.......................... : Selected copies
View ROM information
ROM Read Error ROM I/O Request error Cmd sending error Device Error Detected 51/04 (ABR)
SA surface verification
There is no deskription of SA in the zone allocation table
any ideas will be greatly appreciated.
thank you in advance
July 26th, 2009, 23:53
1. There is no regualar safe mode on Odyssey family, that's why you get Techno On error. It is normal even for working drive
2. It is very possible that you drive has bad heads (it may not click which is also normal behavior for Odyssey drives)
3. Simple swapping heads usually doesn't work on WD drives because it's not that easy
4. As you can see you don't know much about WD drives and most likely you will not get free-step-by-step-guide-to-fix-your-drive here. To prevent further irritation and possible verbal diarrhea of some members of this forum I would suggest you send this hard case to experienced professional or DR company
July 27th, 2009, 0:27
Doomer
thank you for the answer
i have tried the head swap, i understand there is an alignment issue that has to be addressed with these drives.
i accept while i dont know everythign about WD drives and i was expecting an answer to ceom from someone suggesting take it to a pro or something along those lines, there comes a stage when we want to learn and need to learn on how to deal with these drives by ourselves and always giving it to a pro is not always going to be an answer.
i can tell you about some jobs i hav ehad that have been to a so called pro but thats another topic for another time, for now i simply wanted an indication of what i should be looking at, i dont expect a full answer telling me step by step buttons to press as this will not solve my problem or educate me further about drives.
if certain people on the forum have an issue with this post and they feel like having verbal diarrhea thats fine, they have the right to answer or not, completely up to them
thx
July 27th, 2009, 3:31
I see that it thinks it read the tracks successfully, is this actually the case?
Also,
verbal diarrhea
July 27th, 2009, 4:57
Hi
it actually read the tracks as per result shown
but failed on everything else
strange ?
Thx
July 27th, 2009, 6:08
Hi,
we can help in this recovery, in case you can outsource, PM me.
pepe
July 27th, 2009, 10:00
I really doubt it read tracks because it didn't even switch to Techno On mode
July 27th, 2009, 22:22
if it didnt read the tracks how else would the drive show the report that it has been read?
thx
July 28th, 2009, 0:58
Check the tracks it thinks it saved with a hex editor. Do they actually have information in them?
July 28th, 2009, 1:07
drccsc wrote:Check the tracks it thinks it saved with a hex editor. Do they actually have information in them?
all empty
July 28th, 2009, 1:10
So it didn't actually do anything after all.
Powered by phpBB © phpBB Group.