View Full Version : ghost problems
jan smit
December 6th 03, 10:24 PM
Hi there,
I just cloned my XP Pro from a 80 gb IBM disk to a new 80 gb Seagate with
Ghost 2003.
I does boot but not further than the XP logo and than it hangs.
I tried a fixmbr but that one doesn't seem to work
Has anyone got any idea?
It's just a clone so it should work, uh?
Thanx,
JS
Joseph Conway \(MSFT\)
December 6th 03, 10:25 PM
Are the controllers different that these drives are on?
"jan smit" > wrote in message
...
> Hi there,
>
> I just cloned my XP Pro from a 80 gb IBM disk to a new 80 gb Seagate with
> Ghost 2003.
> I does boot but not further than the XP logo and than it hangs.
>
> I tried a fixmbr but that one doesn't seem to work
> Has anyone got any idea?
>
> It's just a clone so it should work, uh?
>
> Thanx,
> JS
>
>
I'm Dan
December 6th 03, 10:28 PM
"jan smit" > wrote:
> I just cloned my XP Pro from a 80 gb IBM disk to a new 80 gb Seagate with
> Ghost 2003.
> I does boot but not further than the XP logo and than it hangs.
>
> I tried a fixmbr but that one doesn't seem to work
> Has anyone got any idea?
>
> It's just a clone so it should work, uh?
Yes, but there's a couple issues with cloning. First, XP remembers what
disk it was on by recording in the registry a partition signature, which
will be different on a new disk. XP is fairly smart and can normally fix
itself in such a case, but sometimes you may need to force it to boot into
safe mode first so it can fix itself. If you ghosted your image to CD,
swapped disks, then restored from CD (i.e., never had both disks in at the
same time), this is normally the most you'd have to do.
Make sure you don't have the original disk still installed -- some people
try to leave it in as a slave drive -- because then XP will see that
partition signature it had previously remembered and get confused.
There may also be problems if you're trying to clone disk-to-disk from
within Windows. I haven't confirmed this, but I can envision problems if
the old XP is booted, it sees the new drive, records it's signature, and
assigns it a drive letter (let's say, D:) -- all before you get Ghost
running. After the clone is made and the new XP tries to boot, it sees
itself on a partition matching the new signature but it's registry remembers
that signature goes with a drive letter other than C:, and it gets confused.
(Actually, a brand new, unpartitioned/unformatted disk shouldn't get a drive
letter, but this is all avoidable anyway by running Ghost from its boot
floppy, not from Windows.)
Finally, Ghost may cause problems by trying to be too smart for itself. If
you install both disks and try to clone from master to slave, Ghost examines
your system and may make changes to the clone's boot.ini file to point to
the slave -- and then you no longer have a perfect clone. Unfortunately,
when you then remove the master and move the slave to master position, the
Ghost-modified boot.ini would then be incorrect. If that has happened, you
may need to edit your boot.ini back to what it was originally.
FYI, there should be a disk copying utility from Seagate (either supplied on
floppy with the new disk, or downloadable from their website) which is
intended exactly for the purpose you desire. It boots from floppy, makes a
straight clone, and without trying to be too smart. IMHO, it's a better way
to go than using Ghost.
jan smit
December 6th 03, 10:28 PM
Xref: kermit microsoft.public.windowsxp.hardware:128458
>
> FYI, there should be a disk copying utility from Seagate (either supplied
on
> floppy with the new disk, or downloadable from their website) which is
> intended exactly for the purpose you desire. It boots from floppy, makes
a
> straight clone, and without trying to be too smart. IMHO, it's a better
way
> to go than using Ghost.
`Thanks a lot Dan, you gave a lot of usefull information. But, just 5
minutes ago, the HD from which i was cloning, *REALLY* crashed
(skrrrrieeeeek it said)
well, all i've got right now is an exact copy on a seagate but it won't
boot.
perhaps if i get a new ibm deskstar and clone it back, then it will work?
Right now, i'm going to bump my head against the wall untill i fall asleep.
D*mn.....
JS
I'm Dan
December 6th 03, 10:28 PM
"jan smit" > wrote:
> `Thanks a lot Dan, you gave a lot of usefull information. But, just 5
> minutes ago, the HD from which i was cloning, *REALLY* crashed
> (skrrrrieeeeek it said)
>
> well, all i've got right now is an exact copy on a seagate but it won't
> boot.
>
> perhaps if i get a new ibm deskstar and clone it back, then it will work?
Not necessarily. Remember, there are situations where Ghost does not make
an *exact* copy, so all you're going to get is a clone of the non-working
copy.
You haven't said how you did the cloning . . . was it disk-to-disk? From
Windows or from a Ghost boot floppy? FAT32 or NTFS?
I suggest you install the Seagate as master, no slave, disconnect any
zip/jazz drives (to prevent them from getting the C: drive letter), and try
booting into safe mode (press F8 as soon as you hear the beep at the end of
the bios POST routine and before Windows starts loading). If it loads
successfully, then maybe you got XP to fix itself, so try rebooting back
into normal mode. If safe mode doesn't work, check your boot.ini file.
Post back if you need help with that.
NobodyMan
December 6th 03, 10:29 PM
On Fri, 16 May 2003 07:50:54 +0200, "jan smit" >
wrote:
>Hi there,
>
>I just cloned my XP Pro from a 80 gb IBM disk to a new 80 gb Seagate with
>Ghost 2003.
>I does boot but not further than the XP logo and than it hangs.
>
>I tried a fixmbr but that one doesn't seem to work
>Has anyone got any idea?
>
>It's just a clone so it should work, uh?
>
>Thanx,
>JS
>
Drive images (made with Ghost or DriveImage) are designed to be loaded
onto systems with identical hardware as the machine from which the
image was made. If you replaced your old drive with a new drive,
especially one from a different manufacturer, you may have shot
yourself in the foot.
Then again you may get lucky and get this to work.
I'm Dan
December 6th 03, 10:38 PM
"NobodyMan" > wrote:
> >I just cloned my XP Pro from a 80 gb IBM disk to a new 80 gb Seagate with
> >Ghost 2003.
> >I does boot but not further than the XP logo and than it hangs.
> >
> >I tried a fixmbr but that one doesn't seem to work
> >Has anyone got any idea?
> >
> >It's just a clone so it should work, uh?
>
> Drive images (made with Ghost or DriveImage) are designed to be loaded
> onto systems with identical hardware as the machine from which the
> image was made. If you replaced your old drive with a new drive,
> especially one from a different manufacturer, you may have shot
> yourself in the foot.
>
> Then again you may get lucky and get this to work.
You don't need to be lucky; it works just fine. Yes, major hardware
changes -- such as a mainboard -- can be dicey, but a hard drive swap is
relatively simple. This isn't a problem caused by hardware, it's the method
of executing the swap that's the problem.
Airman Basic
December 6th 03, 10:43 PM
Agreed. I usually copy "partition to image". When restoring, GHOST
doesn't seem to mind what brand or size partition I restore to. If the
restore is to a larger partition, GHOST asks if I want to use all the
available space. BTW, couldn't you boot to the XP CD and run recovery
console?
http://support.microsoft.com/?kbid=314058
I'm Dan wrote:
>
> You don't need to be lucky; it works just fine. Yes, major hardware
> changes -- such as a mainboard -- can be dicey, but a hard drive swap is
> relatively simple. This isn't a problem caused by hardware, it's the method
> of executing the swap that's the problem.
>
>
>
vBulletin® v3.6.4, Copyright ©2000-2012, Jelsoft Enterprises Ltd.