On Mon, Jun 04, 2012 at 07:39:17AM -0000, Daniel Smedegaard Buus wrote: > Sorry for being unclear. With BOOT_IMAGE, I was referring to the output of > cat /proc/cmdline, e.g. > BOOT_IMAGE=/@/boot/vmlinuz-3.0.0-17-generic root=/dev/sdq2 ro > rootflags=subvol=@ quiet splash vt.handoff=7.
> Above is what grub creates on my system with this is /etc/default/grub: > # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux > #GRUB_DISABLE_LINUX_UUID=true > So either GRUB_DISABLE_LINUX_UUID is now defaulting to true, or > something else is going on. Something else is going on. Nobody else has reported this behavior, and nothing changed in the precise-updates version that would cause the behavior to change. I really don't know where that 'hd16' has come from, but that may be the root of your problem. > This may be a wildly inaccurate bug report in that this behavior may > either be the default(?) or it may be much older than the most recent > update. It just happend to coincide with me doing hard drive fiddling > and updates to GRUB rolling in. Yes, I think it's not tied to the recent update - if you were fiddling with hard drives at the same time, that was probably the trigger. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007752 Title: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
