Image deployment

> however with this new image Ghost will not create a copy if I use the disk to disk option
Please post the messages you got from Ghost gui when you clone the disk.
Did you see the file and directory count when clone it? If you see the file count on the source disk, then the ghost can read the source image ok. Otherwise, the image you create has problem.

Besides, make sure you can see the target disk in Ghost. Sometimes, you have newer disk controller which Ghost doesn't support, which need third party driver for Ghost to see the target disk.

I can see the target and source drives and partitions, when Ghost run s it shows ext2 file system being created but it does not show any files being copied, the process ends as soon as the file system completes.

How about the file count for the source image?

How about full the source disk to target machine to do disk to disk image, which bypass creating image file to see if it work or not. If yes, then something wrong with the image you create.

> How about full the source disk to target...
How about put the source disk to target ...

I'm doing Disk to disk the disk I want to copy is good there is no issue with it, I think however it may be that Ghost cant read the file system Im using. I created an image with the same process using SLES 9 deployed to 700 registers as a Ghost image, now I need an OS upgrade and thats where the issue is whatever the cause I dont know, I may need a new Ghost version.

When you install SLES11, make sure you select ext2 or ext3, not ext4, which Ghost might not support at this moment.

The install used ext2, another diferance from my SLES9 image is that the SLES 11 was created using KIWI and the drive loaded via PXE boot, SLES 9 was an ISO that I installed then made the Ghost image.
Perhaps something with the Kiwi image may be the cause, I realy need this to work but not looking good.
I will try G4L hope that will work.

G4L can just image the entire disk, especially good if all your machines have the same make/model hard disk - but will work even if they don't (as long as if what disk structure your restoring isn't bigger than the destination hard drive device)

G4L, has worked better then Ghost so far, however I'm getting a driver error on the cloned drive and it will n ot fully boot. I have used the SLES C D to fix the error and I will have to try it again and see if that will be my solution. thanks for the directing me to G4L had never used it. As far as my hardware they are all the same hardware including the drive size.

I have attempted to use G4L and I'm having an issue with grub below is my menu.lst entry, and the issue I have with the image is that the part 2 portion of the script fails. Any Ideas?

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE Linux Enterprise Server 11 - 2.6.27.19-5
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.27.19-5-pae root=/dev/disk/by-id/ata-IC35L060AVV207-0_VNVB30G8TSTXRH-part1 resume=/dev/disk/by-id/ata-IC35L060AVV207-0_VNVB30G8TSTXRH-part2 splash=silent crashkernel=128M-:64M@16M showopts vga=0x317
    initrd /boot/initrd-2.6.27.19-5-pae

Since your now on a new disk, that line has remembered the identifier for the old disk.  I recommend chroot'ing into the filesystem from a Live CD and re-running grub-install to re-install grub and re-populate your menu.list

A simpler way might be to use the SuperGRUB live CD that can fix many GRUB related issues.

I was able to fix one of the new image however my issue is that any new drive created will need to be corrected before deployment. Is this a grub issue that can not be corrected before coning the drive?