[Bug 413345] Re: incorrectly assumes /dev/mapper/ -> LVM
[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: grub2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/413345 Title: incorrectly assumes /dev/mapper/ -> LVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/413345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413345] Re: incorrectly assumes /dev/mapper/ -> LVM
This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know. ** Changed in: grub2 (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/413345 Title: incorrectly assumes /dev/mapper/ -> LVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/413345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413345] Re: incorrectly assumes /dev/mapper/ - LVM
The same happens if the former jackalope-install used sda1 for grub and kernels
and lvm /dev/mapper/ubuntu-jackalope for root.
it just assumes that all old systems boot from the new /dev/mapper/ubuntu-lucid
even if it corrctly guesses the labels.
here are some lines from grub.cfg:
...
### BEGIN /etc/grub.d/30_os-prober ###
menuentry Ubuntu, with Linux 2.6.32-16-generic (on
/dev/mapper/ubuntu-jackalope) {
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set 720da49e-1432-4601-9e1f-ac3335f1fa5e
linux /vmlinuz-2.6.32-16-generic root=/dev/mapper/ubuntu-lynx ro quiet
splash
initrd /initrd.img-2.6.32-16-generic
}
...
menuentry Ubuntu, with Linux 2.6.28-18-generic (on
/dev/mapper/ubuntu-jackalope) {
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set 720da49e-1432-4601-9e1f-ac3335f1fa5e
linux /vmlinuz-2.6.28-18-generic root=/dev/mapper/ubuntu-lynx ro quiet
splash
initrd /initrd.img-2.6.28-18-generic
}
...
--
incorrectly assumes /dev/mapper/ - LVM
https://bugs.launchpad.net/bugs/413345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413345] Re: incorrectly assumes /dev/mapper/ - LVM
** Tags added: lucid -- incorrectly assumes /dev/mapper/ - LVM https://bugs.launchpad.net/bugs/413345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413345] Re: incorrectly assumes /dev/mapper/ - LVM
I think I have experienced another facet of this bug. I had Jaunty
installed in /dev/sda with a separate /boot partition. When I installed
Karmic on another partition (also on /dev/sda) and *not* using the /boot
partition for Karmic, the resulting grub.cfg created entries for Jaunty
that ignored the separate /boot partition. In other words, In other
words, it produced:
menuentry Ubuntu 9.04, kernel 2.6.28-15-generic (on /dev/sda6) {
insmod ext2
set root=(hd0,6)
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
}
when it should have been:
menuentry Ubuntu 9.04, kernel 2.6.28-15-generic (on /dev/sda6) {
insmod ext2
set root=(hd0,6)
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
}
Annotated results from 'blkid'
r...@cypress:/media/disk/boot/grub# blkid
/dev/sda1: UUID=5C0CDB8F0CDB6296 LABEL=SERVICEV003 TYPE=ntfs
/dev/sda2: UUID=C4F8DDE6F8DDD730 LABEL=SW_Preload TYPE=ntfs
/dev/sda3: UUID=DE62E0C562E0A38D LABEL=Lenovo TYPE=ntfs
/dev/sda5: UUID=9bdeb391-8fd9-48b1-9316-c4a00b7fa7a2 TYPE=ext3
Jaunty /boot
/dev/sda6: UUID=7f69072f-cea2-4ec3-bde9-81dd16744034 TYPE=ext3
Jaunty /
/dev/sda7: TYPE=swap UUID=a8b4289b-34b4-4c92-a7b9-c0bd7f253cff
/dev/sda8: UUID=e186fa4e-a98c-49b9-b491-2205628c1f75 TYPE=ext3
SEC_TYPE=ext2 (shared /home)
/dev/sda9: UUID=836c9f55-820b-4760-b2cb-81af5b6fedfe TYPE=ext4
Karmic /
r...@cypress:/media/disk/boot/grub#
This was on the Karmic beta Desktop CD as of 2009-10-06. Following work
around (which will require manual editing of grub.cfg every time I run
'update-grub on Karmic) I installed grub-pc on Jaunty and found that it
did appear to produce grub.cfg compliant with a separate /boot partition
when run from that installation. I'm not certain that the Jaunty
grub.cfg is correct for Jaunty (which does not use the /boot partition.)
It produced the entry:
menuentry Ubuntu, Linux 2.6.31-12-generic (on /dev/sda9) {
set root=(hd0,9)
linux /boot/vmlinuz-2.6.31-12-generic
root=UUID=836c9f55-820b-4760-b2cb-81af5b6fedfe ro quiet splash
initrd /boot/initrd.img-2.6.31-12-generic
}
If that uses the search line for Jaunty it will not find the kernel or
initial RAM disk as those are not in the /boot partition.
--
incorrectly assumes /dev/mapper/ - LVM
https://bugs.launchpad.net/bugs/413345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413345] Re: incorrectly assumes /dev/mapper/ - LVM
Hi Colin, Thank you for triaging this bug. If anything else is needed from me, please let me know. I hope this can be fixed before the karmic alt/server ISO release. -- incorrectly assumes /dev/mapper/ - LVM https://bugs.launchpad.net/bugs/413345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413345] Re: incorrectly assumes /dev/mapper/ - LVM
Here's the broken code (possibly other similar bits elsewhere):
int
grub_util_get_dev_abstraction (const char *os_dev UNUSED)
{
#ifdef __linux__
/* Check for LVM. */
if (!strncmp (os_dev, /dev/mapper/, 12))
return GRUB_DEV_ABSTRACTION_LVM;
/* Check for RAID. */
if (!strncmp (os_dev, /dev/md, 7))
return GRUB_DEV_ABSTRACTION_RAID;
#endif
/* No abstraction found. */
return GRUB_DEV_ABSTRACTION_NONE;
}
--
incorrectly assumes /dev/mapper/ - LVM
https://bugs.launchpad.net/bugs/413345
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
