Oh, didn't realize that it was the Windows XP Repair Install that was
hanging too, I thought you simply had restored the Ghost image and it was
hanging on boot-up

More comments below...

Jim

"Neil Bradley" <nb_no_spam@synthcom.com> wrote in message
news:iLehf.2584$R42.608@trnddc01...
> 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.
>

Ugh.

> 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.
>

Ok, so then did the original Maxtor that now has marked bad sectors, are you
sure this boots? IOW, you're Ghosting it from the bad sector drive to the
new drive, but we don't know at this point if the bad sector drive is a good
source for Ghosting, correct? I mean, we're assuming here that it is, and
you merely Ghosted one to the other w/o ever testing the bootability of the
bad sector'd drive. It's important only to the extent that I'm trying to
determine if this is a problem w/ Ghost, OR, the source (i.e., bad sector
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).
>

Again, same issue. It's not clear if the *source*, based on the bad sector
drive, even boots! If it doesn't, Ghosting isn't the issue. (btw, by
Ghosting I assume you mean copy/clone from one HD to the other). On the
other hand, if the source HD does boot, then sure, this would point to the
Ghosting process. It may simply be that the copy/clone process was in
error. If so, I can suggest a work around using another tool.

> > 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