no boot after adding new hard drive

[eric freeland]

I am having this exact same problem! I have a 40Gb IBM
deskstar Hd, bought a new Western Digital 80Gb drive. I
installed the 80gb, formatted it to NTFS and cloned it
using the Data Lifeguard tools that came with the drive.

I then swapped drives around with the new drive as the
master and when it booted it booted off the old drive.
After re-formatting the new drive and using Ghost 7.5 to
clone the drive it was doing the same thing. I then took
the slave off and set the new drive as single master, and
it now boots up to the blue WinXp Login screen, but there
are no logon buttons nor does it go any further.

I would love to know what is happening here.

I have an AMD XP1900, Soyo KT333, 1Gb PC2700, and the
aforementioned 40gb IBM and new 80Gb Western Digital
drives.

The old drive was set up as FAT32, but I converted it to
NTFS prior to installing and cloning the new drive.

The system sees the new drive placed in the master
location, it recognizes it in BIOS, and I can see all the
files that have been cloned. It just won't boot from
that drive when it is set up as a single drive.

>-----Original Message-----
>I recently added a new hard drive as a slave, with the
>previous drive as master as before. After cloning the
>original drive to the new drive with Norton Ghost and
>removing the old drive, the computer starts booting,
>shows the XP logo, but never finishes booting. The same
>thing happens when I try to boot to Safe Mode or to
>Debugging mode. Any ideas, anyone?
>
>Mark
>.
>

[Lemon Jelly]

eric freeland - typed:
> I am having this exact same problem! I have a 40Gb IBM
> deskstar Hd, bought a new Western Digital 80Gb drive. I
> installed the 80gb, formatted it to NTFS and cloned it
> using the Data Lifeguard tools that came with the drive.
>
> I then swapped drives around with the new drive as the
> master and when it booted it booted off the old drive.
> After re-formatting the new drive and using Ghost 7.5 to
> clone the drive it was doing the same thing. I then took
> the slave off and set the new drive as single master, and
> it now boots up to the blue WinXp Login screen, but there
> are no logon buttons nor does it go any further.
>
> I would love to know what is happening here.
>
> I have an AMD XP1900, Soyo KT333, 1Gb PC2700, and the
> aforementioned 40gb IBM and new 80Gb Western Digital
> drives.
>
> The old drive was set up as FAT32, but I converted it to
> NTFS prior to installing and cloning the new drive.
>
> The system sees the new drive placed in the master
> location, it recognizes it in BIOS, and I can see all the
> files that have been cloned. It just won't boot from
> that drive when it is set up as a single drive.
>
>>-----Original Message-----
>>I recently added a new hard drive as a slave, with the
>>previous drive as master as before. After cloning the
>>original drive to the new drive with Norton Ghost and
>>removing the old drive, the computer starts booting,
>>shows the XP logo, but never finishes booting. The same
>>thing happens when I try to boot to Safe Mode or to
>>Debugging mode. Any ideas, anyone?
>>
>>Mark
>>.

Sounds like you missed the important step of rebooting your new h/d
without the old one still attached, then booting with it attached
afterwards. I prefer to have a 2nd h/d formatted as an extended
partition without an active volume. Try removing the old drive &
rebooting.
See if this MS KB article helps:
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q289/0/22.asp&NoWebContent=1
Same url:
http://tinyurl.com/f2u7
If you used the convert command to go from FAT to NTFS, check your
cluster size is the optimal 4k & not 512bytes! If it isn't, you will be
better off doing a fresh install using NTFS from the outset.
--
Paul

[eric freeland]

Thanks for the reply. I'll check my cluster size on both
drives when I get home this evening and see if they're the
same. I really wanted to avoid a total new install
because I have a ton of stuff on the drives I don't want
lost, not to mention the time it will take me to re-
configure it. Well I guess a working system with a better
drive will be better than nothing :D

Thanks and I'll let you know how it goes.

Eric

>-----Original Message-----
>eric freeland - typed:
>> I am having this exact same problem! I have a 40Gb IBM
>> deskstar Hd, bought a new Western Digital 80Gb drive. I
>> installed the 80gb, formatted it to NTFS and cloned it
>> using the Data Lifeguard tools that came with the drive.
>>
>> I then swapped drives around with the new drive as the
>> master and when it booted it booted off the old drive.
>> After re-formatting the new drive and using Ghost 7.5
to
>> clone the drive it was doing the same thing. I then
took
>> the slave off and set the new drive as single master,
and
>> it now boots up to the blue WinXp Login screen, but
there
>> are no logon buttons nor does it go any further.
>>
>> I would love to know what is happening here.
>>
>> I have an AMD XP1900, Soyo KT333, 1Gb PC2700, and the
>> aforementioned 40gb IBM and new 80Gb Western Digital
>> drives.
>>
>> The old drive was set up as FAT32, but I converted it to
>> NTFS prior to installing and cloning the new drive.
>>
>> The system sees the new drive placed in the master
>> location, it recognizes it in BIOS, and I can see all
the
>> files that have been cloned. It just won't boot from
>> that drive when it is set up as a single drive.
>>
>>>-----Original Message-----
>>>I recently added a new hard drive as a slave, with the
>>>previous drive as master as before. After cloning the
>>>original drive to the new drive with Norton Ghost and
>>>removing the old drive, the computer starts booting,
>>>shows the XP logo, but never finishes booting. The same
>>>thing happens when I try to boot to Safe Mode or to
>>>Debugging mode. Any ideas, anyone?
>>>
>>>Mark
>>>.
>
>Sounds like you missed the important step of rebooting
your new h/d
>without the old one still attached, then booting with it
attached
>afterwards. I prefer to have a 2nd h/d formatted as an
extended
>partition without an active volume. Try removing the old
drive &
>rebooting.
>See if this MS KB article helps:
>http://support.microsoft.com/default.aspx?
scid=http://support.microsoft.com:80/support/kb/articles/Q2
89/0/22.asp&NoWebContent=1
>Same url:
>http://tinyurl.com/f2u7
>If you used the convert command to go from FAT to NTFS,
check your
>cluster size is the optimal 4k & not 512bytes! If it
isn't, you will be
>better off doing a fresh install using NTFS from the
outset.
>--
>Paul
>
>
>.
>

[Thomas Wendell]

Boot from install CD. Go to recovery console (repair at first possible
place?). At prompt for which OS installation answer 1 and enter
At command prompt enter fixmbr (or fixboot). Try boot


--
Reply to group
=================================================
Most learned here on nntp://news.mircosoft.com
Helsinki, Finland (remove _SPAM)
(translations from FI/SE not always accurate)
=================================================




"eric freeland" > kirjoitti viestissä
...
> Thanks for the reply. I'll check my cluster size on both
> drives when I get home this evening and see if they're the
> same. I really wanted to avoid a total new install
> because I have a ton of stuff on the drives I don't want
> lost, not to mention the time it will take me to re-
> configure it. Well I guess a working system with a better
> drive will be better than nothing :D
>
> Thanks and I'll let you know how it goes.
>
> Eric
>
> >-----Original Message-----
> >eric freeland - typed:
> >> I am having this exact same problem! I have a 40Gb IBM
> >> deskstar Hd, bought a new Western Digital 80Gb drive. I
> >> installed the 80gb, formatted it to NTFS and cloned it
> >> using the Data Lifeguard tools that came with the drive.
> >>
> >> I then swapped drives around with the new drive as the
> >> master and when it booted it booted off the old drive.
> >> After re-formatting the new drive and using Ghost 7.5
> to
> >> clone the drive it was doing the same thing. I then
> took
> >> the slave off and set the new drive as single master,
> and
> >> it now boots up to the blue WinXp Login screen, but
> there
> >> are no logon buttons nor does it go any further.
> >>
> >> I would love to know what is happening here.
> >>
> >> I have an AMD XP1900, Soyo KT333, 1Gb PC2700, and the
> >> aforementioned 40gb IBM and new 80Gb Western Digital
> >> drives.
> >>
> >> The old drive was set up as FAT32, but I converted it to
> >> NTFS prior to installing and cloning the new drive.
> >>
> >> The system sees the new drive placed in the master
> >> location, it recognizes it in BIOS, and I can see all
> the
> >> files that have been cloned. It just won't boot from
> >> that drive when it is set up as a single drive.
> >>
> >>>-----Original Message-----
> >>>I recently added a new hard drive as a slave, with the
> >>>previous drive as master as before. After cloning the
> >>>original drive to the new drive with Norton Ghost and
> >>>removing the old drive, the computer starts booting,
> >>>shows the XP logo, but never finishes booting. The same
> >>>thing happens when I try to boot to Safe Mode or to
> >>>Debugging mode. Any ideas, anyone?
> >>>
> >>>Mark
> >>>.
> >
> >Sounds like you missed the important step of rebooting
> your new h/d
> >without the old one still attached, then booting with it
> attached
> >afterwards. I prefer to have a 2nd h/d formatted as an
> extended
> >partition without an active volume. Try removing the old
> drive &
> >rebooting.
> >See if this MS KB article helps:
> >http://support.microsoft.com/default.aspx?
> scid=http://support.microsoft.com:80/support/kb/articles/Q2
> 89/0/22.asp&NoWebContent=1
> >Same url:
> >http://tinyurl.com/f2u7
> >If you used the convert command to go from FAT to NTFS,
> check your
> >cluster size is the optimal 4k & not 512bytes! If it
> isn't, you will be
> >better off doing a fresh install using NTFS from the
> outset.
> >--
> >Paul
> >
> >
> >.
> >

[eric freeland]

I tried the repair installation last night. I used the=20
FIXBOOT and FIXMBR on the new drive XP install and it said=20
that it had a non-standard MBR. I went through with the=20
fix and it said fix was successful.

Upon reboot it recognized the drive and began to load=20
windows, but stopped and hung at the Blue XP login screen=20
with no login buttons. I let it sit for a good 20 minutes=20
to see if it would go further but nothing...

Tonight I will check to see if both are formatted with the=20
same NTFS Byte size clusters.
Thanks

>-----Original Message-----
>Boot from install CD. Go to recovery console (repair at=20
first possible
>place?). At prompt for which OS installation answer 1 and=20
enter
>At command prompt enter fixmbr (or fixboot). Try boot
>
>
>--=20
>Reply to group
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=

>Most learned here on nntp://news.mircosoft.com
>Helsinki, Finland (remove _SPAM)
>(translations from FI/SE not always accurate)
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=

>
>
>
>
>"eric freeland" > kirjoitti viestiss=E4
...
>> Thanks for the reply. I'll check my cluster size on=20
both
>> drives when I get home this evening and see if they're=20
the
>> same. I really wanted to avoid a total new install
>> because I have a ton of stuff on the drives I don't want
>> lost, not to mention the time it will take me to re-
>> configure it. Well I guess a working system with a=20
better
>> drive will be better than nothing :D
>>
>> Thanks and I'll let you know how it goes.
>>
>> Eric
>>
>> >-----Original Message-----
>> >eric freeland - typed:
>> >> I am having this exact same problem! I have a 40Gb=20
IBM
>> >> deskstar Hd, bought a new Western Digital 80Gb=20
drive. I
>> >> installed the 80gb, formatted it to NTFS and cloned=20
it
>> >> using the Data Lifeguard tools that came with the=20
drive.
>> >>
>> >> I then swapped drives around with the new drive as=20
the
>> >> master and when it booted it booted off the old=20
drive.
>> >> After re-formatting the new drive and using Ghost=20
7.5
>> to
>> >> clone the drive it was doing the same thing. I then
>> took
>> >> the slave off and set the new drive as single master,
>> and
>> >> it now boots up to the blue WinXp Login screen, but
>> there
>> >> are no logon buttons nor does it go any further.
>> >>
>> >> I would love to know what is happening here.
>> >>
>> >> I have an AMD XP1900, Soyo KT333, 1Gb PC2700, and the
>> >> aforementioned 40gb IBM and new 80Gb Western Digital
>> >> drives.
>> >>
>> >> The old drive was set up as FAT32, but I converted=20
it to
>> >> NTFS prior to installing and cloning the new drive.
>> >>
>> >> The system sees the new drive placed in the master
>> >> location, it recognizes it in BIOS, and I can see all
>> the
>> >> files that have been cloned. It just won't boot=20
from
>> >> that drive when it is set up as a single drive.
>> >>
>> >>>-----Original Message-----
>> >>>I recently added a new hard drive as a slave, with=20
the
>> >>>previous drive as master as before. After cloning=20
the
>> >>>original drive to the new drive with Norton Ghost and
>> >>>removing the old drive, the computer starts booting,
>> >>>shows the XP logo, but never finishes booting. The=20
same
>> >>>thing happens when I try to boot to Safe Mode or to
>> >>>Debugging mode. Any ideas, anyone?
>> >>>
>> >>>Mark
>> >>>.
>> >
>> >Sounds like you missed the important step of rebooting
>> your new h/d
>> >without the old one still attached, then booting with=20
it
>> attached
>> >afterwards. I prefer to have a 2nd h/d formatted as an
>> extended
>> >partition without an active volume. Try removing the=20
old
>> drive &
>> >rebooting.
>> >See if this MS KB article helps:
>> >http://support.microsoft.com/default.aspx?
>>=20
scid=3Dhttp://support.microsoft.com:80/support/kb/articles/Q2
>> 89/0/22.asp&NoWebContent=3D1
>> >Same url:
>> >http://tinyurl.com/f2u7
>> >If you used the convert command to go from FAT to NTFS,
>> check your
>> >cluster size is the optimal 4k & not 512bytes! If it
>> isn't, you will be
>> >better off doing a fresh install using NTFS from the
>> outset.
>> >--=20
>> >Paul
>> >
>> >
>> >.
>> >
>
>
>.
>