Public bug reported: Binary package hint: grub2
After upgrading from Lucid Lynx to Maverick beta, my system didn't boot anymore. I spent the last few days learning grub2, and I can boot my system now, as long as I type the following incantation in the grub shell... So instead of showing me the boot menu, I only get the grub console (not the rescue one, the normal one, with no error shown whatsoever). I have tried to fix my system for a few days now, and I believe I'm facing a bug in Grub2, as I really should see the Grub Menu now. I know my setup is a bit strange, but it worked fine on 9:10 and 10:04. I actually don't know if my upgrade from 9:10 to 10:04 pushed grub2 onto my system, and my guess is that it didn't, as I would probably have noticed. I have 4 drives on software RAID 10 for most of the space, except for the root and boot partitions, both on RAID 1. My root and boot are on separate partitions, as this was needed when I set up my system. I only have Ubuntu on my system, no dual-boot. So it seems that Grub2 is not finding my grub.cfg file, which is correctly sitting in /boot/grub/grub.cfg and which looks OK, I regenerated it a few times already. I will attach it to the bug as well. I also get warnings on boot: kernel-provided name 'dm-0' and NAME= 'mapper/vg_boot-boot' disagree, please use SYMLINK+= or change the kernel to provide the proper name. I assume I'll be able to fix those by using the UUID of the disks in the boot command. Here the commands I have to type in order to boot: linux /vmlinuz-2.6.35-20-generic root=/dev/mapper/vg_sys-lv_root initrd /initrd.img-2.6.35-20-generic boot Notice I don't need to run "set root=X", the root is already correctly set! >From the booted system, I can do everything normally though. I have try all combinations of sudo grub-install /dev/sda sudo grub-install /dev/sdc sudo grub-install --root-directory=/boot /dev/sda sudo grub-install --root-directory=/boot /dev/sdc sudo update-grub to no avail... Hopefully not too many people will be affected by this, and I could hold on grub1, but I prefer pushing for Grub2 to be totally functional. Thank you! Aloys -- Output of grub-probe: sudo grub-probe -t device /boot/grub /dev/mapper/vg_boot-boot -- Output of mdadm: Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md1 : active raid10 sda2[0] sdb1[1] sdc2[2] sdd1[3] 195318016 blocks 64K chunks 2 near-copies [4/4] [UUUU] md0 : active raid1 sda1[0] sdc1[1] 192640 blocks [2/2] [UU] md2 : active raid10 sdc5[2] sda3[0] sdb2[1] sdd2[3] 1757815936 blocks 64K chunks 2 near-copies [4/4] [UUUU] unused devices: <none> -- Output of fdisk: sudo fdisk -l Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0004dda1 Device Boot Start End Blocks Id System /dev/sdb1 1 12158 97659103+ fd Linux RAID autodetect /dev/sdb2 12159 121577 878908117+ fd Linux RAID autodetect Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ad053 Device Boot Start End Blocks Id System /dev/sda1 * 1 24 192748+ fd Linux RAID autodetect /dev/sda2 25 12182 97659135 fd Linux RAID autodetect /dev/sda3 12183 121601 878908117+ fd Linux RAID autodetect Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000e188f Device Boot Start End Blocks Id System /dev/sdc1 * 1 24 192748+ fd Linux RAID autodetect /dev/sdc2 25 12182 97659135 fd Linux RAID autodetect /dev/sdc3 12183 121601 878908117+ 5 Extended /dev/sdc5 12183 121601 878908086 fd Linux RAID autodetect Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000815eb Device Boot Start End Blocks Id System /dev/sdd1 1 12158 97659103+ fd Linux RAID autodetect /dev/sdd2 12159 121577 878908117+ fd Linux RAID autodetect Disk /dev/md2: 1800.0 GB, 1800003518464 bytes 2 heads, 4 sectors/track, 439453984 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 65536 bytes / 131072 bytes Disk identifier: 0x00000000 Disk /dev/md2 doesn't contain a valid partition table Disk /dev/md0: 197 MB, 197263360 bytes 2 heads, 4 sectors/track, 48160 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 200.0 GB, 200005648384 bytes 2 heads, 4 sectors/track, 48829504 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 65536 bytes / 131072 bytes Disk identifier: 0x00000000 Disk /dev/md1 doesn't contain a valid partition table Disk /dev/dm-0: 192 MB, 192937984 bytes 255 heads, 63 sectors/track, 23 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1: 1800.0 GB, 1800002338816 bytes 255 heads, 63 sectors/track, 218837 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 65536 bytes / 131072 bytes Disk identifier: 0x00000000 Disk /dev/dm-1 doesn't contain a valid partition table Disk /dev/dm-2: 100.0 GB, 100008984576 bytes 255 heads, 63 sectors/track, 12158 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 65536 bytes / 131072 bytes Disk identifier: 0x00000000 Disk /dev/dm-2 doesn't contain a valid partition table Disk /dev/dm-3: 88.0 GB, 87996497920 bytes 255 heads, 63 sectors/track, 10698 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 65536 bytes / 131072 bytes Disk identifier: 0x00000000 Disk /dev/dm-3 doesn't contain a valid partition table Disk /dev/dm-4: 12.0 GB, 11999903744 bytes 255 heads, 63 sectors/track, 1458 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 65536 bytes / 131072 bytes Disk identifier: 0x00000000 Disk /dev/dm-4 doesn't contain a valid partition table Disk /dev/sdi: 1997 MB, 1997537280 bytes 255 heads, 63 sectors/track, 242 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x009c235f Device Boot Start End Blocks Id System /dev/sdi1 * 1 243 1950688 6 FAT16 Partition 1 has different physical/logical beginnings (non-Linux?): phys=(0, 1, 1) logical=(0, 1, 2) Partition 1 has different physical/logical endings: phys=(1023, 254, 63) logical=(242, 217, 39) -- /var/log/boot.log /var/log/boot.log:udevd-work[766]: kernel-provided name 'dm-3' and NAME= 'mapper/vg_sys-lv_root' disagree, please use SYMLINK+= or change the kernel to provide the proper name /var/log/boot.log:udevd-work[768]: kernel-provided name 'dm-1' and NAME= 'mapper/vg_data-data' disagree, please use SYMLINK+= or change the kernel to provide the proper name /var/log/boot.log:udevd-work[764]: kernel-provided name 'dm-2' and NAME= 'mapper/vg_sys-home' disagree, please use SYMLINK+= or change the kernel to provide the proper name /var/log/boot.log:udevd-work[664]: kernel-provided name 'dm-3' and NAME= 'mapper/vg_sys-lv_root' disagree, please use SYMLINK+= or change the kernel to provide the proper name /var/log/boot.log:udevd-work[642]: kernel-provided name 'dm-1' and NAME= 'mapper/vg_data-data' disagree, please use SYMLINK+= or change the kernel to provide the proper name /var/log/boot.log:udevd-work[644]: kernel-provided name 'dm-2' and NAME= 'mapper/vg_sys-home' disagree, please use SYMLINK+= or change the kernel to provide the proper name /var/log/boot.log:udevd-work[769]: kernel-provided name 'dm-4' and NAME= 'mapper/vg_sys-lv_swap' disagree, please use SYMLINK+= or change the kernel to provide the proper name /var/log/boot.log:udevd-work[663]: kernel-provided name 'dm-0' and NAME= 'mapper/vg_boot-boot' disagree, please use SYMLINK+= or change the kernel to provide the proper name /var/log/boot.log:udevd-work[642]: kernel-provided name 'dm-0' and NAME= 'mapper/vg_boot-boot' disagree, please use SYMLINK+= or change the kernel to provide the proper name ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: grub-pc 1.98+20100804-4ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4 Uname: Linux 2.6.35-20-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Sep 8 21:18:13 2010 ProcEnviron: PATH=(custom, user) LANG=en_AU.utf8 SHELL=/bin/bash SourcePackage: grub2 ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- Grub Menu not displaying on LVM+RAID with separate boot partition on raid https://bugs.launchpad.net/bugs/633120 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