[Bug 411705] Re: have run udate-grub2 and my other linux wont boot

[HankB]

I have confirmed that grub-pc did not recognize usage of the /boot partition for the "other" Linux install. I was able to boot my Jaunty install after changing the UUID in the search option and modifying the kernel and initial RAM disk file names to be relative to /boot:
102,104c102,104
< 	search --no-floppy --fs-uuid --set 9bdeb391-8fd9-48b1-9316-c4a00b7fa7a2
< 	linux /vmlinuz-2.6.28-15-generic root=UUID=7f69072f-cea2-4ec3-bde9-81dd16744034 ro quiet splash
< 	initrd /initrd.img-2.6.28-15-generic
---
> 	search --no-floppy --fs-uuid --set 7f69072f-cea2-4ec3-bde9-81dd16744034
> 	linux /boot/vmlinuz-2.6.28-15-generic root=UUID=7f69072f-cea2-4ec3-bde9-81dd16744034 ro quiet splash
> 	initrd /boot/initrd.img-2.6.28-15-generic

Following this, I installed grub-pc on Jaunty and after manually running
update-grub, I note that it found Karmic but did not include a separate
search line for that. I'm not sure it will boot Karmic using this
because I do not know if it requires the search line for those entries.
(Jaunty grub.cfg is attached.) If it uses the search specified for
Jaunty (points to separate /boot partition) it will not find the Karmic
kernel and initrd.

** Attachment added: "grub.cfg produced on Jaunty"
   http://launchpadlibrarian.net/33229091/grub.cfg

-- 
have run udate-grub2 and my other linux wont boot
https://bugs.launchpad.net/bugs/411705
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs