Re: Replicating multi-boot disks

["Horace G. Friend III" <okee mail com>]

On Fri, Apr 27, 2001 at 04:08:34PM -0700, Mark Knecht wrote:
> Thomas,
>    Thanks for the reply. Apparently we used Version 6.03, so we have a
> chance with your information.
> 
> Mark
> 
> -----Original Message-----
> From: Chung, Thomas [mailto:tchung pasadena oao com]
> Sent: Friday, April 27, 2001 3:32 PM
> To: 'redhat-install-list redhat com'
> Subject: RE: Replicating multi-boot disks
> 
> 
> I believe Norton Ghost 6.0 or 6.5 does not support Red Hat 7.0 yet according
> to Symantec Support Web Site.
> But I tried Norton Ghost 7.0 trial version and it seems to be working OK
> with Red Hat 7.0
> 
> Thomas.
> 
> -----Original Message-----
> From: Mark Knecht [mailto:mknecht controlnet com]
> Sent: Friday, April 27, 2001 3:15 PM
> To: Redhat-Install-List (E-mail)
> Subject: Replicating multi-boot disks
> 
> 
> Hi all,
>    I've got some new machines where we attempted to replicate a known good
> drive using Norton Ghost. The systems use System Commander 2000, and then
> boot DOS, Win ME and Linux. The ghosting process seemed to go smoothly.
> However, when we attempted Linux (RH 7.0) it refused. Kernel panic. Unable
> to mount file system. DOS and Win ME worked fine.
> 
>    Does anyone have any experience with doing this sort of thing? (I don't.
> Maybe someone at Redhat?) Are there any special requirements about matching
> disks when ghosting for Linux that are not requirements for DOS or Windows?
> The drives are both nominally the same size, but not from the same
> manufacturer and therefore not identical.
> 
>    Thanks in advance to anyone who can save me some time over the weekend!
> ;-)
> 
> Mark
> 
> 

Dunno if this'll help.

Twice in less than a month, I've transferred my root and swap partitions
from my primary HDD (/dev/hda14) to my secondary HDD (/dev/hdb5) then
back to primary HDD (this time as /dev/hda15). I used Partition Magic
4.0. It takes long to transfer data but works like magic.

Twice I got the "kernel panic" msg because I did not set the correct
parameters in /etc/fstab and etc/lilo.conf and ran /sbin/lilo before
rebooting.

Now everything's working fine.

-- 
Horace G. Friend III
okee mail com
GnuPG DSA/ElGamal Key Fingerprint
9295 80C4 C723 621B 9C2D  B53E D432 7936 4CA9 8AD6