Re: use what UUID to boot new kernel in menu.lst

lovecreatesbeauty@xxxxxxxxx wrote:
I upgrade kernel from 2.6.27 to 2.6.27.2 on Fedora 10 beta, but the
system won't boot with the new kernel. The system can still be booted
with the old one. The /boot/grub/menu.lst has the new and the old
entries as following. I use the same UUID as the one used for 2.6.27
for 2.6.27.2. This may be the problem, but I don't know how to get a
new UUID or do I need a new one.

# /boot/grub/menu.lst
title Fedora (2.6.27.2)
root (hd0,0)
kernel /vmlinuz-2.6.27.2 ro root=UUID=184eb91e-
e8f3-4812-8814-9e57f9b02a33 rhgb quiet
initrd /initrd-2.6.27.2.img

title Fedora (2.6.27-0.352.rc7.git1.fc10.i686)
root (hd0,0)
kernel /vmlinuz-2.6.27-0.352.rc7.git1.fc10.i686 ro
root=UUID=184eb91e-e8f3-4812-8814-9e57f9b02a33 rhgb quiet
initrd /initrd-2.6.27-0.352.rc7.git1.fc10.i686.img
# /boot/grub/menu.lst ends

The new kernel image has been generated. More information below. I
hope this is enough for you to diagnose my problem : ) Thanks!

$ ls /boot/vmlinuz*
/boot/vmlinuz /boot/vmlinuz-2.6.27.2
/boot/vmlinuz-2.6.27-0.352.rc7.git1.fc10.i686 /boot/
vmlinuz-2.6.27.2.old

$ ls -l /boot/initrd-2.6.27*
/boot/initrd-2.6.27-0.352.rc7.git1.fc10.i686.img
/boot/initrd-2.6.27.2.img

$ su -c 'fdisk -l'

...

/dev/sda1 * 1 25 200781 83 Linux
/dev/sda2 26 1044 8185117+ 8e Linux LVM

$ cat /etc/fstab

...

/dev/VolGroup00/LogVol00 / ext3
defaults 1 1
UUID=172a1e55-ebff-4739-b742-ddbd8bb87c97 /boot
ext3 defaults 1 2
tmpfs /dev/shm tmpfs
defaults 0 0
devpts /dev/pts devpts
gid=5,mode=620 0 0
sysfs /sys sysfs
defaults 0 0
proc /proc proc
defaults 0 0
/dev/VolGroup00/LogVol01 swap swap
defaults 0 0

$ su -c 'blkid'
Password:
/dev/sr0: LABEL="Fedora 10-Beta i386 DVD" TYPE="iso9660"
/dev/sda1: LABEL="/boot" UUID="172a1e55-ebff-4739-b742-ddbd8bb87c97"
TYPE="ext3" SEC_TYPE="ext2"
/dev/sda2: UUID="HsO8B2-lGD6-kQJj-PMlq-1eq3-PKjc-co07ax" TYPE="lvm2pv"
/dev/mapper/VolGroup00-LogVol00: UUID="184eb91e-
e8f3-4812-8814-9e57f9b02a33" TYPE="ext3"
/dev/mapper/VolGroup00-LogVol01: TYPE="swap" UUID="17622e4d-
fa41-49d6-8434-8507cf973166"
/dev/VolGroup00/LogVol00: UUID="184eb91e-e8f3-4812-8814-9e57f9b02a33"
TYPE="ext3"
/dev/VolGroup00/LogVol01: TYPE="swap" UUID="17622e4d-
fa41-49d6-8434-8507cf973166"
$
You said that you use the same UUID for both kernel. The most probable reason of not booting is the new kernel doesn't recognise your hard disk.
.

Relevant Pages

  • Re: Building a kernel from source on RH9
    ... make bzImage (here is kernel) ... # all kernel and initrd paths are relative to /boot/, ... # root ... title Red Hat Linux ...
    (RedHat)
  • Re: Another preupgrade disaster -
    ... missing the root line. ... kernel /vmlinuz-2.6.30.9-96.fc11.i586 ro ... initrd /initrd-2.6.30.9-96.fc11.i586.img ... title Omega 11.1 Fedora Remix ...
    (Fedora)
  • Re: 2.6.5 kernel will not boot
    ... >> root ... > disk that is used to load modules that are required at pre init 1 before ... > directly into the kernel, so no need for an initrd. ...
    (alt.os.linux)
  • Re: booting from ISO image on HD?
    ... I'm not going to write the pivot root script, ... > through customized initrd files for each one. ... I have to insmod the loop kernel module(e.g. ... The idea is that either you build what you need to boot into your ...
    (comp.os.linux.misc)
  • Re: Beige PowerMac G3/266 trouble
    ... installation system, it will later be mounted by the installer when the ... You'll find a kind of first stage of the installation system on the initrd ... It's responsible to load all kernel modules needed for the ... new root fs. ...
    (comp.os.linux.powerpc)