[Bug 392836] Re: grub not adding correct uuid to grub.cfg
Bug #445367 seems like a duplicate of this. As described there, /etc/grub.d/30_os-prober ignores boot partition reported by os-prober. /usr/lib/linux-boot-probes/mounted/40grub and /usr/lib/linux-boot- probes/mounted/40grub2 are the files prepending the /boot to linux kernel/initrd lines. -- grub not adding correct uuid to grub.cfg https://bugs.launchpad.net/bugs/392836 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs
[Bug 392836] Re: grub not adding correct uuid to grub.cfg
As a temporary workaround (that only works with setups similar to mine,
since the test for separate /boot is simply wrong) I changed 30_os-
prober as follows:
--- 30_os-prober.orig 2009-11-01 13:26:40.787934691 +0200
+++ 30_os-prober2009-11-01 13:27:21.897932968 +0200
@@ -128,6 +128,11 @@
LINITRD=`echo ${LINUX} | cut -d ':' -f 5`
LPARAMS=`echo ${LINUX} | cut -d ':' -f 6- | tr '^' ' '`
+if [ ${LBOOT%%dev/md*} = / ] ; then
+ LKERNEL=${LKERNEL#/boot}
+ LINITRD=${LKERNEL#/boot}
+fi
+
if [ -z ${LLABEL} ] ; then
LLABEL=${LONGNAME}
fi
@@ -136,7 +141,7 @@
menuentry ${LLABEL} (on ${DEVICE}) {
EOF
save_default_entry | sed -e s/^/\t/
- prepare_grub_to_access_device ${DEVICE} | sed -e s/^/\t/
+ prepare_grub_to_access_device ${LBOOT} | sed -e s/^/\t/
cat EOF
linux ${LKERNEL} ${LPARAMS}
EOF
--
grub not adding correct uuid to grub.cfg
https://bugs.launchpad.net/bugs/392836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
[Bug 392836] Re: grub not adding correct uuid to grub.cfg
Or maybe that bug I mentioned above is separate one. But both seem to be symptoms of missing/broken support for separate /boot -partitions for kernels found by os-prober. Also my workaround above doesn't work as-is, so please ignore it. Since bug db isn't a discussion forum, guess I'll shut up until I have something that actually works, and for others besides me as well. -- grub not adding correct uuid to grub.cfg https://bugs.launchpad.net/bugs/392836 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs
[Bug 392836] Re: grub not adding correct uuid to grub.cfg
** Changed in: grub2 (Ubuntu) Status: New = Confirmed -- grub not adding correct uuid to grub.cfg https://bugs.launchpad.net/bugs/392836 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs
[Bug 392836] Re: grub not adding correct uuid to grub.cfg
I am running a system with 1 IDE drive (Intrepid), 1 SATA (Windows XP), 1 SATA (Jaunty) and 1 USB external drive which I am using to test Karmic. The Windows drive has the Windows MBR and all others have GRUB with the USB drive having GRUB2. The Jaunty drive also has a separate Boot partition. After Karmic installation all systems would boot from GRUB2 except for my current production system, Jaunty. My initial workaround was just to set the BIOS to boot from this drive first. After experimentation I have found that I must set the search specification in the GRUB2 menu to the UUID of the Boot partition and remove the /boot from each of the linux and initrd lines to get Jaunty to boot. -- grub not adding correct uuid to grub.cfg https://bugs.launchpad.net/bugs/392836 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs
[Bug 392836] Re: grub not adding correct uuid to grub.cfg
You have to change the UUID in 'root=UUID=89c07ebd-cc8e-4d65-be8d- e4db7fbfef06 ro quiet splash' to match your Jaunty's UUID. But every time, your kernel in Karmic gets updated and the grub.cfg is updated as well, this setting gets lost and is overwritten with Karmic's UUID. -- grub not adding correct uuid to grub.cfg https://bugs.launchpad.net/bugs/392836 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs
[Bug 392836] Re: grub not adding correct uuid to grub.cfg
Problems here with double boot configuration. Running Jaunty perfectly (/root at secondary hd0,8). Installed Karmic Beta (sept/29) at primary partition (hd0,0). Could not boot after install. Still unable to find out why, (perhaps it did not like my grub[1] at [hd0,8]?). Reset Grub to previous conditions and Jaunty booted OK. Installed Grub2 in Jaunty, just in case. Menu.lst was set to default (Karmic) parameters (hd0,0) and corresponding (wrong) UUID. Of course the system didn't boot. Restored original menu.lst parameters from (good grace, there was a) backup and managed to make Jaunty work again. No way I can further test Karmic with double boot. I'm currently trying to reinstall original Grub. -- grub not adding correct uuid to grub.cfg https://bugs.launchpad.net/bugs/392836 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs
[Bug 392836] Re: grub not adding correct uuid to grub.cfg
Same here, Karmic Alpha 6. I didn't have any problems/errors intalling Karmic, but in the grub.cfg the uuid for Jaunty was set to Karmic's uuid. When I updated Karmic today, the manually corrected entry was overwritten with the wrong uuid again. -- grub not adding correct uuid to grub.cfg https://bugs.launchpad.net/bugs/392836 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs
[Bug 392836] Re: grub not adding correct uuid to grub.cfg
** Package changed: grub (Ubuntu) = grub2 (Ubuntu) ** Changed in: grub2 (Ubuntu) Importance: Undecided = High -- grub not adding correct uuid to grub.cfg https://bugs.launchpad.net/bugs/392836 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs
Re: [Bug 392836] Re: grub not adding correct uuid to grub.cfg
Steve Langasek wrote:
** Package changed: grub (Ubuntu) = grub2 (Ubuntu)
** Changed in: grub2 (Ubuntu)
Importance: Undecided = High
Hi, would it help to see the menu.cfg from Kubuntu Karmic using grub2
and the menu.lst from Kubuntu Jaunty using grub?
I highlighted the problem in red and showed the correct UUID in green.
First, menu.cfg from Karmic
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=5
set root=(hd0,1)
search --no-floppy --fs-uuid --set 5c33e75f-d1e0-4dfd-b1a6-f1ac98c5791f
if loadfont /usr/share/grub/ascii.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry Ubuntu, Linux 2.6.30-8-generic {
set root=(hd0,1)
search --no-floppy --fs-uuid --set 5c33e75f-d1e0-4dfd-b1a6-f1ac98c5791f
linux/boot/vmlinuz-2.6.30-8-generic
root=UUID=5c33e75f-d1e0-4dfd-b1a6-f1ac98c5791f ro quiet splash
initrd/boot/initrd.img-2.6.30-8-generic
}
menuentry Ubuntu, Linux 2.6.30-8-generic (recovery mode) {
set root=(hd0,1)
search --no-floppy --fs-uuid --set 5c33e75f-d1e0-4dfd-b1a6-f1ac98c5791f
linux/boot/vmlinuz-2.6.30-8-generic
root=UUID=5c33e75f-d1e0-4dfd-b1a6-f1ac98c5791f ro single
initrd/boot/initrd.img-2.6.30-8-generic
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry Memory test (memtest86+) {
linux/boot/memtest86+.bin
}
menuentry Memory test (memtest86+, serial console 115200) {
linux/boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry Kubuntu 9.04, kernel 2.6.28-11-generic (on /dev/sda5) {
set root=(hd0,5)
search --no-floppy --fs-uuid --set 89c07ebd-cc8e-4d65-be8d-e4db7fbfef06
linux /boot/vmlinuz-2.6.28-11-generic
root=UUID=89c07ebd-cc8e-4d65-be8d-e4db7fbfef06 ro quiet splash
initrd /boot/initrd.img-2.6.28-11-generic
}
menuentry Kubuntu 9.04, kernel 2.6.28-11-generic (recovery mode) (on
/dev/sda5) {
set root=(hd0,5)
search --no-floppy --fs-uuid --set 89c07ebd-cc8e-4d65-be8d-e4db7fbfef06
linux /boot/vmlinuz-2.6.28-11-generic
root=UUID=89c07ebd-cc8e-4d65-be8d-e4db7fbfef06 ro single
initrd /boot/initrd.img-2.6.28-11-generic
}
menuentry Kubuntu 9.04, memtest86+ (on /dev/sda5) {
set root=(hd0,5)
search --no-floppy --fs-uuid --set 89c07ebd-cc8e-4d65-be8d-e4db7fbfef06
linux /boot/memtest86+.bin
}
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file is an example on how to add custom entries
### END /etc/grub.d/40_custom ###
Second, menu.lst from Kubuntu Jaunty
titleKubuntu 9.04, kernel 2.6.28-11-generic
uuid8d814ba7-a49c-4c0c-916a-df417306b1d4
kernel/vmlinuz-2.6.28-11-generic
root=UUID=89c07ebd-cc8e-4d65-be8d-e4db7fbfef06 ro quiet splash
initrd/initrd.img-2.6.28-11-generic
quiet
titleKubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
uuid8d814ba7-a49c-4c0c-916a-df417306b1d4
kernel/vmlinuz-2.6.28-11-generic
root=UUID=89c07ebd-cc8e-4d65-be8d-e4db7fbfef06 ro single
initrd/initrd.img-2.6.28-11-generic
titleKubuntu 9.04, memtest86+
uuid8d814ba7-a49c-4c0c-916a-df417306b1d4
kernel/memtest86+.bin
quiet
### END DEBIAN AUTOMAGIC KERNELS LIST
titleUbuntu 9.10, kernel 2.6.30-8-generic
root(hd0,0)
kernel/vmlinuz root=/dev/sda1
quiet
--
grub not adding correct uuid to grub.cfg
https://bugs.launchpad.net/bugs/392836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
