[Bug 1184617] Re: Wrong uuid in grub/menu.lst

[jerryb]

More information on this:

I'm using Grub legacy.  The update-grub script generates a command
uuid 1123...

however, Grub legacy says "invalid command".  It appears that grub
legacy does *not* support this command.  the script should generate the
euqivalent

root (hdn,m)

command instead.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to os-prober in Ubuntu.
https://bugs.launchpad.net/bugs/1184617

Title:
  Wrong uuid in grub/menu.lst

Status in “os-prober” package in Ubuntu:
  New

Bug description:
  I'm seeing the wrong uuid put in grub's menu.lst file (grub legacy).

  Some history:

  I've been with Ubuntu for many years, through many updates.  Initially
  I set up a 100 meg boot partition which has been enough for two
  kernels (three, initially) at a time.  Now, however, it only holds one
  kernel, which means that kernel updates fail.  To mitigate the
  problem, I

  1. copied the contents of the boot partition (SDA1 in my case) to a new directory, "myboot" on my root device (sda6, in my case).
  2. unmounted the boot partition (and commented it out in fstab)
  3. renamed "myboot" to just "boot"
  4. ran synaptic to install the kernel update

  When synaptic finished, the new kernel was sitting in the new
  directory and menu.lst had been updated, BUT I have something like
  this (not the actual uuids):

  title "new kernel"
  uuid  1
  kernel /vmlinuz... uuid=2
  initrd /init...

  The problem is that the new kernel is on uuid=2 and in /boot, NOT on
  uuid1 and not in the root directory of any device on my system.  I
  fixed the problem by saving the new menu.lst under another name,
  remounting sda1 on /boot, editing the menu.lst found there and adding
  the new menu item with the correct uuids.  Only then could I boot the
  new kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1184617/+subscriptions