FW: Re: RedHat AS 2.1 (kernel panic)

[Jerry Feldman]

On Wednesday 23 November 2005 7:46 pm, Rich Braun wrote:
> Bottom line:  if you get dumped at the GRUB command-line prompt instead
> of seeing a kernel, your menu.lst file is probably blown away.  To boot
> the system, you will either have to remember what commands to type, e.g.
>
>   kernel (hd0,0)/vmlinuz
>   initrd (hd0,0)/initrd
>   boot
>
> or dig out your installation CD and tell it to boot your root fs.  Once
> you've done that, restore /boot/grub/menu.lst to its original state.
>  (You did take my advice about backups, right?  You do have an rsync'ed
> copy of /boot, right?
In general, I have not had a problem with the GRUB installation on SuSE. One 
thing you can do is to go through the installation (without formatting the 
disks). Since you have installed everything, this will go reasonably 
quickly. Make sure that you select the boot loader and check the 
parameters. The installer should install GRUB properly. 
One of the real advantages of GRUB is that it is a 2-stage boot. The boot 
block contains stage1 that points to stage2 that resides in /boot/grub. 
Then stage2 reads the menu.lst (or grub.conf depending on what version of 
GRUB), then it boots the selected kernel or OS. 

Also, note that the GRUB device ids are 0 relative. The first drive is drive 
0 and the first partition is partition 0. So, in the above spec, vmlinuz 
resides in the first partition on the first drive. 
-- 
Jerry Feldman <gaf at blu.org>
Boston Linux and Unix user group
http://www.blu.org PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9