Re: [Linux-migration-list] Computer cloning

[Patrick M. <pat...@pa...>]

Thank you very much

Patrick

Op vr 31-01-2003, om 02:37 schreef Taylor, ForrestX:
> On Sat, 2003-01-25 at 15:09, Martin Stricker wrote:
> 
> "Taylor, ForrestX" wrote:
> 
> > The file is in OpenOffice.org format.  If you need a different
> > format, let me know.
> 
> Plain text would be wonderful. In emacs I see some XML header
> information and a lot of binary ghibberish...
> 
> Thank you very much!
> 
> Best regards,
> Martin Stricker
> 
> 
> Plain text it is.  Sorry about that.  I am just going to cut/paste, so I
> apologize if it is not very readable.
> 
> ---------------------------------------------
> 
> Ghosting Red Hat Linux with grub and ext3 partitions
> 
> 
> This white paper describes how to ghost Linux partitions, especially
> those with ext3 partitions.  Since Red Hat Linux 7.2, the default
> partition type has been ext3, which is a journalling file system.  Ghost
> does not recognize the partition as an ext3 partition, and thus removes
> the journal inode.  In order to get Linux to boot after having ghosted
> it, you must recreate the joural filesystem.  This has been verified
> with Ghost 2001 and Red Hat Linux 8.0.
> 
> 
> I.   This assumes that you already know how to use ghost and and that
> you have some Linux experience.  If you are ghosting a dual-boot machine
> (booting to Linux and Windows or another operating system), and the
> other operating system won’t boot, you may need to repair the MBR for
> the other operating system.  Once you can boot successfully, run the
> steps below to reinstall grub.  Before you begin, you should write down
> the names of the Linux partitions on the original disk.  `fdisk  –l` or
> `df` inside of Linux should show you the partitions.  Write down the
> /dev/???? names and their corresponding mount points.
> E.g.,
> /dev/hda2	/boot
> /dev/hda5	/
> /dev/hda6	/usr
> 
> 
> II.   After ghost has completed, you should try to reboot to see if, by
> chance, it worked.  Most likely you will get a GRUB screen with a
> blinking cursor.  First you need to get a Red Hat Linux CD (disc 1), and
> boot into rescue mode:
> 
>   a. Boot from the CD
>   b .Type  `linux rescue`  at the boot: prompt.
>   c.If it asks about verifying your disc, TAB to Skip and hit Enter. 
> Ans wer the questions about your language and keyboard, and Skip the
> question about mounting your partitions.
>   d. Find out which partitions are Linux native (0x83) if you haven’t
> done so already.  Write these down for the next step
>       i. fdisk –l    (or `fdisk  –l  /dev/hda`, `fdisk  –l  /dev/hdb`,
> `fdisk  -l  /dev/sda`, etc.).  Write down the Linux partitions (e.g.,
> /dev/hda2, /dev/hda5, etc.).
> 
> 
> III.  Now you need to remove the information about the journalling
> inode, and rejournal the partition.  This will not cause loss of data.
> 
>   a.tune2fs  –O  ^has_journal  /dev/hda2   (capital o)
>   b.Repeat for each Linux partition.
>   c.tune2fs –j /dev/hda2
>   d.Repeat for each Linux partition
> 
> 
> IV.  Mount the / and /boot (if you have one) partitions on /mnt/sysimage
> and /mnt/sysimage/boot respectively.  If you are not sure which is the /
> or /boot partition, try mounting each of the Linux partitions, and see
> if it contains boot/, bin/, sbin/, root/, etc. directories.  Once you
> mount /, check the boot/ directory to see if it contains kernel-* and
> vmlinuz-* files.  If it contains no files, /boot is on a separate
> partition, and you will need to mount it.
> 
>   a. mkdir /mnt/sysimage
>   b. mount  /dev/hda5  /mnt/sysimage  (where hda5 is your actual /
> partition)
>   c. mount  /dev/hda2  /mnt/sysimage  (where hda2 is your actual /boot
> partition.  Only mount it if /boot is on a separate partition.)
>   d. chroot /mnt/sysimage
>   e. grub-install  /dev/hda   (where /dev/hda is the disk that boots
> first.  This will write grub to the MBR of the disk.  If your Linux
> partitions are similar to /dev/hda5 or /dev/hdb2, you should use
> /dev/hda.  If your Linux partitions are /dev/sda5 or /dev/sdb2 (SCSI
> disks), you should use /dev/sda.)
>   f. Type `exit` to exit the chrooted environment.
> 
> 
> V.   Type `exit` to exit rescue mode, and make sure that you remove the
> CD so that it doesn’t boot from CD again.
> VI.Grub should now work, and you should be able to boot other OSes as
> well.
> 
> ------------------------------------
> 
> Let me know if that doesn't work better.
> 
> Forrest
-- 
Knowledge in a databank,is like food which is in a deepfreeze.
Nothing comes out better than what is initially put in.

PGP Key: http://users.pandora.be/rivendell/marquetp.gpg
Registered Linux User #44550 http://counter.li.org