WD20EARX won't accept loader 11

[DataPros]

The failed drive is WD20EARX-00PASB0 (Sadle G6). It spins up, then stops and becomes ready to enter utility in Kernel Mode. I'm following procedure in PC3K manual exactly. LDR loading from file finds 11.rpm and 5C.rpm. 5C loads okay, but 11 fails after many tries/re-powers/start overs.

Can anyone help me with getting past this?

Thanks!
-PP

[jermy]

Sounds like heads problem

[DataPros]

Thanks Jeremy. There is no clicking while it's starting.
Are you saying the failure to write that module is due
to bad head(s)? I thought the modules are written to
firmware on the card. No?

The drive originally had a blown controller which was
replaced and the first 46% of the drive was imaged
perfectly! But, now this condition persists and I'm
hoping imaging can be completed after this procedure
(which is on Page 57 of the PC3K WD-Marvel manual)

-PP
=================================

[Amarbir[CDR-Labs]]

The failed drive is WD20EARX-00PASB0 (Sadle G6). It spins up, then stops and becomes ready to enter utility in Kernel Mode. I'm following procedure in PC3K manual exactly. LDR loading from file finds 11.rpm and 5C.rpm. 5C loads okay, but 11 fails after many tries/re-powers/start overs.

Can anyone help me with getting past this?

Thanks!
-PP

Well,
I hope when the drive had not died you kept a SA and Rom backup did you ? .If yes you can load Overlay Modules " I hate to call them loader " . The steps would be as following

1 : Start The Drive
2 : Load Overlay modules for servo 5c and general overlay 11 from saved files to ram of hdd
3 : Then load dir module

[jackass25]

The drive originally had a blown controller which was
replaced and the first 46% of the drive was imaged
perfectly! But, now this condition persists and I'm
hoping imaging can be completed after this procedure

If you image 46% of the drive with another replacement PCB (with ROM transference) and if now you can't copy any extra data and the drive isn't responding properly then either it have firmware issues like re-lo list issues (pending problem/slow problem or damaged modules) or more likely the heads have died.

Block SA access first and load the overlay when the SA access is already blocked. Hope that you have a backup of the firmware done prior to image.

If so :

- Block SA access by changing regions on ROM.
- Load overlay.
- Restore regions on RAM.
- Load DIR to RAM.
- Try to access modules/SA.

Hi mr Spildit....

this steps is work with SEDIV?
if yes coud you tell us the steps? thank you in advance....

[pcimage]

Head(s) have died.

[hddguy]

After loader loading in Kernel mode there will be options to modify map of heads in RAM which will help in cases where not all heads are failed and at least one SA head is active.

But, as already mentioned, it does look like some level of mechanical fault is present...