Boot stuck on WindowsXP Screen

[David]

I connected a new Western Digital harddrive to my system as a slave and used
WD Lifeguard tools to partition/format the new drive (being sure that it was
pointing at the new drive).

After running WD LIfeguard, I removed the slave (new WD drive), removed the
jumpers on the original drive, and attempted to reboot my computer (running
WinXp Home SP2). The boot process started, but stops on the second
WindowsXP screen (the blue one) and just sits there.

It was suggested that I use the WinXP Recovery Panel, then run chkdsk /p --
if that didn't work - try chkdsk /r. Ran both but neither worked.

Next, I connected an old backup drive as master and the problem harddrive as
slave and then rebooted. BIOS saw both drives but My Computer does not see
the problem harddrive. Soooooo, my previously good drive will now no longer
boot PLUS is not even seen by the system.

Any suggestions would be most appreciated.
Dave

 

[DatabaseBen]

access the bootup menu via f8 key and select bootlogging
option. then reboot and the log will begin to "log"

the above is a thought but
my suggestion would be to get the exact procedure
from microsoft.com knowledge database....

 

[Anna]

I connected a new Western Digital harddrive to my system as a slave and
used WD Lifeguard tools to partition/format the new drive (being sure that
it was pointing at the new drive).

After running WD LIfeguard, I removed the slave (new WD drive), removed
the jumpers on the original drive, and attempted to reboot my computer
(running WinXp Home SP2). The boot process started, but stops on the
second WindowsXP screen (the blue one) and just sits there.

It was suggested that I use the WinXP Recovery Panel, then run chkdsk
/p -- if that didn't work - try chkdsk /r. Ran both but neither worked.

Next, I connected an old backup drive as master and the problem harddrive
as slave and then rebooted. BIOS saw both drives but My Computer does not
see the problem harddrive. Soooooo, my previously good drive will now no
longer boot PLUS is not even seen by the system.

Any suggestions would be most appreciated.
Dave

Dave:
Just to gain a clear understanding of your situation & problem:

1. Your solely connected boot HDD containing the XP OS w/SP2 functioned
without any problems prior to your installing your new WD HDD. Is that
right? It booted without incident and functioned properly?

2. You then installed the new WD HDD as a slave to your Primary Master. You
partitioned/formatted it with the WD utility. Presumably you're planning to
use this new HDD as a backup/storage device and not a bootable drive, right?
This "slave" doesn't contain an operating system, right? It's just
partitioned & formatted and doesn't contain any data. Is that right?

3. You then uninstalled the slave HDD and for some reason removed the
jumpers on your boot HDD and the once-bootable drive now does not boot. (I
assume you tried booting a number of times but always with the same failed
results, right?) Why did you remove the jumpers from your boot drive? Is
that HDD a WD model and you were configuring it as Single? Is that the
reason? Isn't is still connected as Primary Master, no?

Possibly you'll have to run a Repair install on your boot drive but that's
not entirely clear at this point. I'm assuming that the drive is
non-defective and that you had no problems with it immediately prior to
installing your new HDD.

A side note...
In my opinion a user should not use a third-party program to
partition/format his or her HDD. And that is so even if such a utility is
provided by the manufacturer of the HDD. It's best to use the built-in Disk
Management utility included in the XP OS when the HDD is being installed as
a secondary drive or if the XP OS is being installed on the drive allow the
OS to perform the partitioning/formatting during the installation process.
Anna

 

[Mike Scirocco]

I connected a new Western Digital harddrive to my system as a slave and used
WD Lifeguard tools to partition/format the new drive (being sure that it was
pointing at the new drive).

After running WD LIfeguard, I removed the slave (new WD drive), removed the
jumpers on the original drive, and attempted to reboot my computer (running
WinXp Home SP2). The boot process started, but stops on the second
WindowsXP screen (the blue one) and just sits there.

<snip>

What happens when you replace the jumpers and reconnect the new WD
drive, making sure the jumpers are exactly as you had them during the
partitioning?

Also did you make sure your IDE cable is seated properly, maybe try
another cable?

 

[Dave]

Hi Anna,
Thanks for the response. In response to your questions:
1. Yes, the HDD worked fine before.
2. New Drive was partitioned/formatted with no other data.
3. NEw HD was removed -- old drive jumper removed as it was a "Single"
4. I tried "repair" - it didn't work.

I was later able to get my data off that drive. I installed an older
backup drive as Master, connected problem drive as Slave, went into
Device Management and changed "Drive Letters" on the problem drive
(???). That drive was then recognized --but still would not boot on
it's own. So, I transferred current My Documents and other data over to
lder drive. Now that I have a working drive with current data -- I used
Drive Image to copy the Drive and everything is back to normal.

Why it happended in the first place is beyond me. I've probably
formatted over 50 WD HDD this way and never had a problem before. Don't
know why it started now.

Dave