Why does this happen

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Recently I used Norton ghost to transfer my OS from a smaller HD to a new
Raid setup. The problem seems to be that the computer won't boot in windows
without my original HD connected in my system. If my old HD is connected, the
system boots from the new raid drives but the drive letter is other than c:
and the old drive is the c: drive (which is no longer the the system drive)
all drives are Sata type. the the OS is Winxp hone edition.

what would be the reason for this?
 
You may need to change entries in the boot.ini file.
See your motherboard or raid card's Installation guide.

JS
 
A little more info I also tryed to put a fresh copy of XP on my raid setup
then I wanted to use XP's file tranfer wizard to transfer all my setting to
the new drive but agiang my orginal drive stayed C. I'm not looking to run
mulit. copies of Xp just put my old stuff on to the new drive.
 
Denprze said:
Recently I used Norton ghost to transfer my OS from a smaller HD to a new
Raid setup. The problem seems to be that the computer won't boot in
windows
without my original HD connected in my system. If my old HD is connected,
the
system boots from the new raid drives but the drive letter is other than
c:
and the old drive is the c: drive (which is no longer the the system
drive)
all drives are Sata type. the the OS is Winxp hone edition.

what would be the reason for this?
Click to expand...


Denprze:
Notwithstanding any problems involving your RAID setup - there's a good
chance this problem arose because (possibly) after you cloned the contents
of your "smaller" HD to a different HD, you booted without first
disconnecting the old HD from the system. In many (but not all) instances
doing so can cause future boot problems with the cloned drive - one of them
being what you're now experiencing, i.e., the system will boot *only* if
both drives are connected.

As I say, I'm not certain this is the precise cause of the problem you're
experiencing but it might be. If it is, the moral of the story is that after
one uses a disk imaging program to clone the contents of one HD to another,
it's important that the initial boot to the cloned HD following the disk
cloning operation be made with *only* that drive connected to the system.
Anna
 
Anna is right that if you boot into XP with both disks, one or both
disks get "corrupted" and you may no longer be able to boot from at
least one of them. I read somewhere it has something to do with having
2 disks with same ID (which would be the case after you clone) and XP,
not liking this, messes with registry entries to "fix" the issue.

As a follow on, when I want to have 2 such disks on-line at the same
time, I boot into Windows 2000 (from a different disk) and W2K seems to
handle the 2 XP disks fine (so you can copy files between the XP disks
etc).

You might also be able to put one of your XP disks as a second drive on
another networked computer and copy files over the network. (I have
only done this with W2K as the boot system on the networked computer
and I know that works fine - I don't know how it would work with XP as
the boot system - if the original problem is caused by identical drive
ID's, presumably a different computer should have a different ID on its
boot disk.)

I have all my disks (PATA and SATA) in drive caddies and this very much
helps when you want to mess around with your hard drives. I cloned my
main 60G PATA system onto a 250G SATA a couple of weeks ago (using
Ghost 2003) and the new 250G system booted up fine (I removed the
original 60G first!) and has been working great since.
 
Back
Top