[ale] reboot problem

Armsby John-G16665 John.Armsby at motorola.com
Sat Aug 23 19:34:37 EDT 2003



We finally got Ghost to work on RedHat 8.0 ext3.  I am fairly pleased.  My summary is as follows:

Problem:  How do you get a "dumb" restore in the event of BIG PC problem(s)?

Solution: 

1.  Make an image and restore the image.  
	a.  Mondo/Mindi never really worked on my personal mandrake 8.0.  I got file errors on the first restore file of each CD I burned in the image set.  SOB....

	b.  Partition Magic Drive Image 4.0 worked great AFTER selecting options for disabling smart sector copying.  In short you want to select options to get everything, no smart anything.  Successfuly worked on Mandrake 9.1 with Reiser fs. Everything on my home installation worked, network, everything...

	c.  Latest Norton GHOST on Redhat 8.0 with ext3 (Partition Magic 4.0 did NOT like ext3). The box was a default Redhat workstation install with 3 partitions....

 We selected the ALL DISK image creation.  We tried selecting other types of images (Disk vs partition) on the selection list.  The restored PC could not boot.  Using a boot disk all worked well (almost). The most inclusive disk image selection (All Disk) worked great (almost).

Here is the "almost".  I am in a corporate environment, with the Redhat box having a host name and obtaining network informaiton via DHCP.  After the restore, the PC could not see the network!  Trying to use the GUI to Activate/Deactivate the "network" never did work. We assigned it a static IP and the restored box's ability to see the network..... AFTER some DNS purging/cleanup.  I am not a network expert.  Apparently there was some cached info on the box when it was a DHCP client.... or some such....

FYI for what it is worth.  I have struggled with tape restores, etc.  When your disk is shredded, It appears you have to pretty much start over with a new install and then get your data from CD/Tape, etc.

My experience.....

John



-----Original Message-----
From: Jonathan Glass [mailto:jonathan.glass at ibb.gatech.edu]
To: ale at ale.org
Sent: Wednesday, August 20, 2003 9:46 PM
To: ale at ale.org
Subject: RE: [ale] reboot problem


Should be.  WHen the RH rescue mode comes up, the instructions tell you
how to manipulate the system in a chroot environment.  It should be that
easy, though.

I don't have a linux box here to test this on, but this is how I've done
in the past.

Thanks
Jonathan


> When I mount the OS filesystem rw, is line 2 on your advice below the
> correct syntax?
>
> John
>
>
> -----Original Message-----
> From: Jonathan Glass [mailto:jonathan.glass at ibb.gatech.edu]
> Sent: Wednesday, August 20, 2003 8:22 PM
> To: ale at ale.org
> Subject: Re: [ale] reboot problem
>
>
> Boot into rescue mode.
> Mount OS filesystem rw
> chroot /mnt/sysimage
> grub-install
> exit chroot
> reboot
>
>> Armsby John-G16665 wrote:
>>> I have a GHOST image restored on an identical PC to the original.
>>> Operating system is Redhat 8.0.  Upon boot it STOPS at a GRUB prompt.
>>> When I insert the rescue floppy, it boots normally.  How do I fix the
>>> boot loader to boot normally?
>>>
>>> The man page on grub is not helpful to me.  Neither is the info grub
>>> manual.
>>>
>>> I know this is simple.  It evades me however...
>>
>> What does /boot/grub/grub.conf look like on machine A and machine B?
>> Does it refer to the correct device for both? Here is my file:
>>
>> # grub.conf generated by anaconda
>> #
>> # Note that you do not have to rerun grub after making changes to this
>> file
>> # NOTICE:  You do not have a /boot partition.  This means that
>> #          all kernel and initrd paths are relative to /, eg.
>> #          root (hd0,0)
>> #          kernel /boot/vmlinuz-version ro root=/dev/hda1
>> #          initrd /boot/initrd-version.img
>> #boot=/dev/hda
>> default=0
>> timeout=10
>> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
>> title Red Hat Linux (2.4.21)
>>          root (hd0,0)
>>          kernel /boot/vmlinuz-2.4.21 ro root=/dev/hda1
>>
>> Check that file and be sure that all references and paths are correct.
>>
>>
>> _______________________________________________
>> Ale mailing list
>> Ale at ale.org
>> http://www.ale.org/mailman/listinfo/ale
>>
>
>
> --
> Jonathan Glass
> Systems Support Specialist II
> IBB/GTEC
> W: 404-385-0127
> C: 404-444-4086
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
>


-- 
Jonathan Glass
Systems Support Specialist II
IBB/GTEC
W: 404-385-0127
C: 404-444-4086
_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale
_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale





More information about the Ale mailing list