Re: Even More Grub & UUID
On Sat, Mar 20, 2010 at 10:13:07PM +0100, Florian Kulzer wrote:
> On Sat, Mar 20, 2010 at 12:19:26 -0700, Freeman wrote:
> > > On Sat, 20 Mar 2010 03:05:56 -0700 freeman wrote:
>
> > > > Finally installed grub legacy. (Long story. And no I don't want
> > > > Grub2/Grub-PC, whatever.
>
> [...]
>
> > However, the system still boots off menu.lst. It had to be edited to boot
> > the system correctly. grub-update writes a non-existent UUID to menu.lst,
> > which will mean manual editing after every kernel upgrade.
> >
> > But I am burying my question.
> >
> > My real question, where could grub-update be getting that wrong UUID from?
>
> I would be interested in seeing the output of:
>
> grep kopt /boot/grub/menu.lst
>
> (which has to be run as root because menu.lst is not readable for normal
> users)
>
|root@Europa:~# grep kopt /boot/grub/menu.lst
|## If you want special options for specific kernels use kopt_x_y_z
|## 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=8dbf4235-c212-4e27-a1ae-721d96ecf9d5 ro
|# xenkopt=console=tty0
|root@Europa:~#
OMG. It has just been reading the UUID specification I left from my old
drive. Since I've been running a non-packaged version of grub since the
change, and manually updating menu.lst, it hadn't mattered.
Eew! My bad.
I though update-grub was getting the UUID from the filesystem superblock the way
it seemed to for grub.cfg.
Thanks Florian!
--
Kind Regards,
Freeman
http://bugs.debian.org/release-critical/
Reply to: