Ghost image from IDE to SATA

inthell

Senior member
Aug 30, 2005
291
0
0
Ghost image from IDE to SATA

so i cloned my current IDE hdd to my new SATA hdd using ghost 2003.

The files copied over fine but i can't boot on the new drive it gives a some odd hardware config error on boot up (forget what it says exactly)

didn't find much info searching google and the Ghost user guide says nothing about sata drives.

So is what im doing just not possible? I guess the sata drivers arent loading on boot. :(

any thoughts on this ...
 

DidlySquat

Banned
Jun 30, 2005
903
0
0
If this is a windows boot partition that you copied then you also need to change something in the registry. The backup software that comes with most hardisks does it automatically, but I'm not sure if Ghost does it. You can even do it yourself, you'll need to boot the original partition and then modify the registry in the new partition. If it's a linux root partition, all you need to change are device names in /etc/fstab and also the bootloader config (typically /boot/grub/menu.lst).
 

NogginBoink

Diamond Member
Feb 17, 2002
5,322
0
0
It's a little more complex than DidlySquat suggests.

Not giving us the error message really doesn't help us help you.

I suspect the error you're getting is the result of the ARC path in boot.ini no longer matching the actual location of the system partition.

That's easy to solve; you can get past that by creating an NT boot disk and editing boot.ini until you find the correct ARC path.

Once you get past that, however, you're going to get a STOP 0x7B blue screen (INACCESSIBLE_BOOT_DEVICE). This is because the OS that you cloned likely doesn't have the SATA controller driver installed as a boot start driver.

So, re-install the original drive and boot to it.

Add a slew of boot.ini entries that point to every conceivable location you think the new drive might end up on.

Install the drivers for the SATA card.

Clone the drive.

You should have a high chance of success.
 

skyking

Lifer
Nov 21, 2001
22,704
5,824
146
much like Noggin said.:)
My procedure when swtiching drive types at a clone:
Install card and new drive.
Boot into old OS. It will prompt you for drivers if needed, and install the device(s).
Give it one more reboot.
Shut down and clone.
Do the boot.ini editing if needed.
 

inthell

Senior member
Aug 30, 2005
291
0
0
here is my boot.ini.backup i did a search on the drive and no boot.ini came up just this backup one
[boot loader]
timeout=30
default=signature(1)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
signature(1)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

im going to try the new drive again and write down the error message.

i also emailed norton support but no response yet
 

NogginBoink

Diamond Member
Feb 17, 2002
5,322
0
0
Boot.ini is at the root of the C: drive. It's a hidden file so won't show up in a search unless your shell options are set to show hidden files.

If the boot.ini truly isn't there, ntldr will try booting to the default arc path of multi(0)disk(0)rdisk(0)partition(1)\windows; you can create a boot.ini to try other paths.
 

corkyg

Elite Member | Peripherals
Super Moderator
Mar 4, 2000
27,370
239
106
Cloning and imaging are two different things. Cloning a drive creates a bit-by-bit duplicate with everything in the exact same place - so bootable is bootable. Imaging does not do that. It is intended for file and data backup more than anything else.

For cloning, Ghost is a poor country cousin to TrueImage by Acronis.

Are you sure you cloned your drive with Ghost or merely imaged it?
 

inthell

Senior member
Aug 30, 2005
291
0
0
Originally posted by: NogginBoink
Boot.ini is at the root of the C: drive. It's a hidden file so won't show up in a search unless your shell options are set to show hidden files.

If the boot.ini truly isn't there, ntldr will try booting to the default arc path of multi(0)disk(0)rdisk(0)partition(1)\windows; you can create a boot.ini to try other paths.

edit: I found the boot.ini and it looks ok i guess

--------
Cloning and imaging are two different things. Cloning a drive creates a bit-by-bit duplicate with everything in the exact same place - so bootable is bootable. Imaging does not do that. It is intended for file and data backup more than anything else.

For cloning, Ghost is a poor country cousin to TrueImage by Acronis.

Are you sure you cloned your drive with Ghost or merely imaged it?

yes i used Clone to make the copy


thx for the feedback