[Bug 1007752] Re: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot
Steve Langasek
steve.langasek at canonical.com
Mon Jun 4 17:35:58 UTC 2012
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
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1007752
Title:
Most recent grub update uses root=/dev/sdX for boot image, may fail to
boot
Status in “grub2” package in Ubuntu:
Incomplete
Bug description:
Hello :)
The recent update (today) of grub,
grub-pc:amd64 (1.99-21ubuntu3, 1.99-21ubuntu3.1)
grub-pc-bin:amd64 (1.99-21ubuntu3, 1.99-21ubuntu3.1)
grub-common:amd64 (1.99-21ubuntu3, 1.99-21ubuntu3.1)
killed my grub, apart from also looking strange (used to be gray background, and a nice logo splash when booting, now black background and just low-res text when booting).
The BOOT_IMAGE command defined root as - in my case - /dev/sdq2, while
at boot it would be /dev/sdb2. Also, this might not stay the same
regardless, and as I understand it, this should point to either a
partition UUID or perhaps /dev/disk/by-id/something-or-other?
In any event, as it stands, all boot options ends with busybox and an
initramfs prompt. Editing the grub command and fixing the root= to the
right path before booting will send me normally into Kubuntu where I
can (hopefully) fix the problem manually.
Cheerio :)
Daniel
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
Uname: Linux 3.0.0-17-generic x86_64
NonfreeKernelModules: nvidia zfs zcommon znvpair zavl zunicode
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Sat Jun 2 10:44:50 2012
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120421.1)
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+subscriptions
More information about the foundations-bugs
mailing list