[Jaunty] Grub problem after update

Thu Apr 9 20:58:56 UTC 2009



--- On Thu, 4/9/09, Jim Smith <jim at oz.net> wrote:

> From: Jim Smith <jim at oz.net>
> Subject: Re: [Jaunty] Grub problem after update
> To: "Ubuntu user technical support, not for general discussions" <ubuntu-users at lists.ubuntu.com>
> Date: Thursday, April 9, 2009, 3:08 PM
> wirechief wrote:
> > I would try using ls -l /dev/disk/by-uuid and see what
> the UUID is currently.
> > and change the menu.lst to match.
> >
> > On Thu, Apr 9, 2009 at 7:10 PM, Jim Smith
> <jim at oz.net> wrote:
> >   
> >> Yesterday I ran about 80+ updates which included
> grub. Since then this
> >> laptop won't boot the first kernel but will
> drop into Busybox and give
> >> the error message "ALERT!
> /dev/disk-by-UUID/=UUID= (UUID given) does not
> >> exist." Running sudo gedit
> /boot/grub/menu.lst shows that all the UUIDs
> >> given are identical for all kernels and identical
> to the UUID given in
> >> the error message. Second kernel will boot
> normally.
> >> My menu.lst is attached in case I missed anything,
> running "sudo
> >> update-grub" picks up all the kernels but the
> end result is the same,
> >> firtst kernel will not boot.
> >>
> >> Any ideas?
> >>
> >> Thanks in advance
> >>
> >> Jim
> >> --
> >>
> >> Its only a hobby, only a hobby, only a hobby, only
> a ho............
> >>
> >>
> >> # menu.lst - See: grub(8), info grub,
> update-grub(8)
> >> #            grub-install(8), grub-floppy(8),
> >> #            grub-md5-crypt, /usr/share/doc/grub
> >> #            and /usr/share/doc/grub-doc/.
> >>
> >> ## default num
> >> # Set the default entry to the entry number NUM.
> Numbering starts from 0, and
> >> # the entry number 0 is the default if the command
> is not used.
> >> #
> >> # You can specify 'saved' instead of a
> number. In this case, the default entry
> >> # is the entry saved with the command
> 'savedefault'.
> >> # WARNING: If you are using dmraid do not change
> this entry to 'saved' or your
> >> # array will desync and will not let you boot your
> system.
> >> default         0
> >>
> >> ## timeout sec
> >> # Set a timeout, in SEC seconds, before
> automatically booting the default entry
> >> # (normally the first entry defined).
> >> timeout         150
> >>
> >> ## hiddenmenu
> >> # Hides the menu by default (press ESC to see the
> menu)
> >> #hiddenmenu
> >>
> >> # Pretty colours
> >> color cyan/blue blink-white/blue
> >>
> >> ## password ['--md5'] passwd
> >> # If used in the first section of a menu file,
> disable all interactive editing
> >> # control (menu entry editor and command-line) 
> and entries protected by the
> >> # command 'lock'
> >> # e.g. password topsecret
> >> ## password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
> >> # password topsecret
> >>
> >> #
> >> # examples
> >> #
> >> # title         Windows 95/98/NT/2000
> >> # root          (hd0,0)
> >> # makeactive
> >> # chainloader   +1
> >> #
> >> # title         Linux
> >> # root          (hd0,1)
> >> # kernel        /vmlinuz root=/dev/hda2 ro
> >> #
> >>
> >> #
> >> # Put static boot stanzas before and/or after
> AUTOMAGIC KERNEL LIST
> >>
> >> ### BEGIN AUTOMAGIC KERNELS LIST
> >> ## lines between the AUTOMAGIC KERNELS LIST
> markers will be modified
> >> ## by the debian update-grub script except for the
> default options below
> >>
> >> ## DO NOT UNCOMMENT THEM, Just edit them to your
> needs
> >>
> >> ## ## Start Default Options ##
> >> ## default kernel options
> >> ## default kernel options for automagic boot
> options
> >> ## If you want special options for specific
> kernels use kopt_x_y_z
> >> ## where x.y.z is kernel version. Minor versions
> can be omitted.
> >> ## e.g. kopt=root=/dev/hda1 ro
> >> ##      kopt_2_6_8=root=/dev/hdc1 ro
> >> ##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
> >> #
> kopt=root=UUID=c8253db2-ac0b-4664-9e3c-837ce469a95d ro
> >>
> >> ## default grub root device
> >> ## e.g. groot=(hd0,0)
> >> # groot=(hd0,3)
> >>
> >> ## should update-grub create alternative automagic
> boot options
> >> ## e.g. alternative=true
> >> ##      alternative=false
> >> # alternative=true
> >>
> >> ## should update-grub lock alternative automagic
> boot options
> >> ## e.g. lockalternative=true
> >> ##      lockalternative=false
> >> # lockalternative=false
> >>
> >> ## additional options to use with the default boot
> option, but not with the
> >> ## alternatives
> >> ## e.g. defoptions=vga=791 resume=/dev/hda5
> >> # defoptions=quiet splash
> >>
> >> ## should update-grub lock old automagic boot
> options
> >> ## e.g. lockold=false
> >> ##      lockold=true
> >> # lockold=false
> >>
> >> ## Xen hypervisor options to use with the default
> Xen boot option
> >> # xenhopt=
> >>
> >> ## Xen Linux kernel options to use with the
> default Xen boot option
> >> # xenkopt=console=tty0
> >>
> >> ## altoption boot targets option
> >> ## multiple altoptions lines are allowed
> >> ## e.g. altoptions=(extra menu suffix) extra boot
> options
> >> ##      altoptions=(recovery) single
> >> # altoptions=(recovery mode) single
> >>
> >> ## controls how many kernels should be put into
> the menu.lst
> >> ## only counts the first occurence of a kernel,
> not the
> >> ## alternative kernel options
> >> ## e.g. howmany=all
> >> ##      howmany=7
> >> # howmany=3
> >>
> >> ## specify if running in Xen domU or have grub
> detect automatically
> >> ## update-grub will ignore non-xen kernels when
> running in domU and vice versa
> >> ## e.g. indomU=detect
> >> ##      indomU=true
> >> ##      indomU=false
> >> # indomU=detect
> >>
> >> ## should update-grub create memtest86 boot option
> >> ## e.g. memtest86=true
> >> ##      memtest86=false
> >> # memtest86=true
> >>
> >> ## should update-grub adjust the value of the
> default booted system
> >> ## can be true or false
> >> # updatedefaultentry=false
> >>
> >> ## should update-grub add savedefault to the
> default options
> >> ## can be true or false
> >> # savedefault=false
> >>
> >> ## ## End Default Options ##
> >>
> >> title           Ubuntu jaunty (development
> branch), kernel 2.6.28-11-generic
> >> root            (hd0,3)
> >> kernel          /boot/vmlinuz-2.6.28-11-generic
> root=UUID=c8253db2-ac0b-4664-9e3c-837ce469a95d ro quiet
> splash
> >> initrd          /boot/initrd.img-2.6.28-11-generic
> >>
> >> title           Ubuntu jaunty (development
> branch), kernel 2.6.28-11-generic (recovery mode)
> >> root            (hd0,3)
> >> kernel          /boot/vmlinuz-2.6.28-11-generic
> root=UUID=c8253db2-ac0b-4664-9e3c-837ce469a95d ro  single
> >> initrd          /boot/initrd.img-2.6.28-11-generic
> >>
> >> title           Ubuntu jaunty (development
> branch), kernel 2.6.28-6-386
> >> root            (hd0,3)
> >> kernel          /boot/vmlinuz-2.6.28-6-386
> root=UUID=c8253db2-ac0b-4664-9e3c-837ce469a95d ro quiet
> splash
> >> initrd          /boot/initrd.img-2.6.28-6-386
> >>
> >> title           Ubuntu jaunty (development
> branch), kernel 2.6.28-6-386 (recovery mode)
> >> root            (hd0,3)
> >> kernel          /boot/vmlinuz-2.6.28-6-386
> root=UUID=c8253db2-ac0b-4664-9e3c-837ce469a95d ro  single
> >> initrd          /boot/initrd.img-2.6.28-6-386
> >>
> >> title           Ubuntu jaunty (development
> branch), kernel 2.6.27-14-generic
> >> root            (hd0,3)
> >> kernel          /boot/vmlinuz-2.6.27-14-generic
> root=UUID=c8253db2-ac0b-4664-9e3c-837ce469a95d ro quiet
> splash
> >> initrd          /boot/initrd.img-2.6.27-14-generic
> >>
> >> title           Ubuntu jaunty (development
> branch), kernel 2.6.27-14-generic (recovery mode)
> >> root            (hd0,3)
> >> kernel          /boot/vmlinuz-2.6.27-14-generic
> root=UUID=c8253db2-ac0b-4664-9e3c-837ce469a95d ro  single
> >> initrd          /boot/initrd.img-2.6.27-14-generic
> >>
> >> title           Ubuntu jaunty (development
> branch), memtest86+
> >> root            (hd0,3)
> >> kernel          /boot/memtest86+.bin
> >>
> >> ### END DEBIAN AUTOMAGIC KERNELS LIST
> >>
> >> # This is a divider, added to separate the menu
> items below from the Debian
> >> # ones.
> >> title           Other Operating Systems:
> >>
> >>
> >>
> >> # This entry automatically added by the Debian
> installer for a non-linux OS
> >> # on /dev/sda2
> >> title           Microsoft Windows XP Professional
> >> root            (hd0,1)
> >> savedefault
> >> makeactive
> >> chainloader     +1
> >>
> >>
> >> --
> >> ubuntu-users mailing list
> >> ubuntu-users at lists.ubuntu.com
> >> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
> >>
> >>
> >>     
> >
> >
> >
> >   
> Using that command gives this result:
> jim at JimsBook:~$ ls -l /dev/disk/by-uuid
> total 0
> lrwxrwxrwx 1 root root 10 2009-04-09 04:31
> 188ba7f1-4de4-4961-9f4b-10dc11811e1b -> ../../sda3
> lrwxrwxrwx 1 root root 10 2009-04-09 04:31 209049EE9049CACC
> -> ../../sda2
> lrwxrwxrwx 1 root root 10 2009-04-09 04:31 45DD-FC5B ->
> ../../sda1
> lrwxrwxrwx 1 root root 10 2009-04-09 04:31
> c8253db2-ac0b-4664-9e3c-837ce469a95d -> ../../sda4
> jim at JimsBook:~$
>  which is the same as menu.lst. I did a check with gparted
> and it is
> actually /sda4 as called out by the ls command. All of the
> UUIDs in
> menu.lst are identical, so if the second kernel boots the
> first one
> should as well. I'm thinking maybe kernel related? If
> so next update
> might fix.
> Thanks, I'll keep plugging on this.
> 
It wouldn't hurt to try reinstalling the problem kernel.

sudo aptitude reinstall <linux-image-2.6.28-11-generic>

Leonard Chatagnier
lenc5570 at sbcglobal.net