If you use ghost to copy a Linux install, Ghost does not support EXT3
file systems, so ghost omits the journalling inode when it copies it.
When the system boots from the new Hard Disk, it will fail because fstab
specifies EXT3 filesystems.
To correct this set the ext3 entries in fstab to ext2, then ghost the
disk, boot the new disk and run
tune2fs -J /dev/hda1...etc etc for each partition to re-create the
journalling inode.
Then edit fstab and re-boot.
I have done this procedure many many times with no problems.
regards
Pete
Andrew Cotter wrote:
>We have used g4u for imaging all sorts of systems (XP,W2K,98,RH). Seems to
>work very well in most situations. In a couple of situations we have gone
>back to Ghost if g4u didn't work.
>
>Andrew
>
>-----Original Message-----
>From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx]On
>Behalf Of Maciej Zenczykowski
>Sent: Wednesday, April 27, 2005 5:37 PM
>To: CentOS mailing list
>Subject: RE: Does CentOS has problems with Norton Ghost 2003
>images?
>
>
>
>
>>We've successfully used g4l on CentOS 3.4 boxes, but as has been
>>mentioned, that's pre-SELinux.
>>
>>
>
>Due to the way g4u/g4l operate they don't give a damn about operating
>system / file system versions. They simply xerox the hard disk. If
>backing up a single partition doesn't work (unlikely but possible) than
>you can always backup the entire disk - thats 99.9999% guaranteed to work
>- if it doesn't work it's hardware issues and nothing to do with the file
>system or operating system versions (there's no filesystem or operating
>system dependent code within g4u/g4l).
>
>Cheers,
>MaZe.
>
>
>_______________________________________________
>CentOS mailing list
>CentOS@xxxxxxxxxx
>http://lists.centos.org/mailman/listinfo/centos
>
>
>_______________________________________________
>CentOS mailing list
>CentOS@xxxxxxxxxx
>http://lists.centos.org/mailman/listinfo/centos
>
>
