Jim wrote:
> You lost me a bit, you say one of the mirrored pair is reformatted by
> accident, so it's useless. But then you say you repaired the other HD, and
> it runs fine. Then say you need to recover a Ghost image? I thought the
> other drive w/ bad sectors was repaired and good to go?

Sorry 'bout that - I kinda lost myself. ;-) Okay, here's how it shakes up:

RAID Array consisted of:
Maxtor 250G 7Y250(1) (bad)
Maxtor 250G 7Y250(2) (good)

The 7Y250(1) developed bad sectors. I removed 7Y250(1) and ran on the
7Y250(2). In prepping the drives to send back Maxtor, I accidentally
formatted the good drive rather than the bad drive.

So after the data was wiped out on the 7Y250(2) (good) drive, I decided
to go buy a 3rd drive - a Maxtor 250G 6Y250.

I first took the 250G 7Y250(1) (bad) and did a chkdsk /f /r to get
around the bad sectors. Then, I ghosted from the 7Y250(1) (bad) to the
new 6Y250 drive.

The 6Y250 drive is the drive that causes the aforementioned hang. I also
targeted a Western digital drive, the 7Y250(2) (good) drive, and another
Maxtor SATA drive - all of which hang at the same spot, so something in
the Ghosting process isn't working right, and that's with Ghost 10.

Is that any clearer? It's not a Ghost image, rather it's a ghosted image
(that is, it's not a Ghost image file).

> Anyway, if the Ghost'ed image is not booting, I suggest an XP repair
> install.

I tried that, and it gets to the "Installing Windows" item in the left
hand side of the screen and sits there - forever, with 29 minutes left
to go (and the system is still "live"). ;-(

-->Neil