-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Maciej Zenczykowski Sent: Wednesday, April 27, 2005 4:33 PM To: CentOS mailing list Subject: Re: [CentOS] Does CentOS has problems with Norton Ghost 2003 images?
Does it have to be Norton Ghost 2003? I know there are other solutions (GPL'ed) which achieve much the same thing... g4u and g4l coming to mind (and let's keep off the question
of
whether g4l was ripped of g4u, I think it was and I also think the arguments for g4l being a rip of g4u are totally misguided and screwed up). Never used either, although I'd probably try g4l first (it's
come
along way since the rough beginnings...)
We've successfully used g4l on CentOS 3.4 boxes, but as has been mentioned, that's pre-SELinux.
-- Marc
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.
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@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Maciej Zenczykowski Sent: Wednesday, April 27, 2005 5:37 PM To: CentOS mailing list Subject: RE: [CentOS] 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@centos.org http://lists.centos.org/mailman/listinfo/centos
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@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Maciej Zenczykowski Sent: Wednesday, April 27, 2005 5:37 PM To: CentOS mailing list Subject: RE: [CentOS] 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@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, 2005-04-28 at 09:20 +0100, Peter Farrow wrote:
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
I know that selinux has added some extensions to the ext3 ... and you can't share the CentOS-2.1 and CentOS-4 ext3 partitions very well, so that might have an impact on ghost as well.
This is not a CentOS-4 only thing ... it is a SELINUX, LVM2, RHEL4 thing :)
-
Andrew Cotter -
Johnny Hughes -
Maciej Zenczykowski -
Marc Powell -
Peter Farrow