Mailinglist Archive: opensuse-bugs (4172 mails)

< Previous Next >
[Bug 512695] New: grub does not support booting boot-by-label
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 12 Jun 2009 10:08:00 -0600
  • Message-id: <bug-512695-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>
http://bugzilla.novell.com/show_bug.cgi?id=512695


Summary: grub does not support booting boot-by-label
Classification: openSUSE
Product: openSUSE 11.1
Version: Final
Platform: All
OS/Version: openSUSE 11.1
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Bootloader
AssignedTo: jsrain@xxxxxxxxxx
ReportedBy: suse@xxxxxxxxx
QAContact: jsrain@xxxxxxxxxx
Found By: ---


User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10)
Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)

Much emphasis has been placed on not using fixed device addresses, but to use
symbolic labels. Grub seems to only support using 'fixed' addresses like
'hd(0,1)'.

Needless to say, this entirely defeats the purpose of moving toward addressing
disks by label -- as when disk ordering changes, the identity of hd(0) also
changes.



Reproducible: Always

Steps to Reproduce:
1. Create a new system and look at grub's boot menu options, or
2. look at a current system and note that OS's are booted by physical disk
hd(x) and partition, hd(x,part). Physically change the order of your disks so
what was.
3. In steps 1 and 2, you need to install with, or use a system that is mounting
the disks symbolically in fstab. I use mount by label, (so my fstab specifies
LABEL=Root / xfs noatime,logbufs=8 1 1
LABEL=Var /var xfs noatime,logbufs=8 1 2
Label=Swap swap swap defaults 0 0
Label=Boot /boot xfs noatime,logbufs=8 1 2
..etc.

Actual Results:
My kernel and grub menus were on /boot, which was originally sda2. However,
Sda2 wasn't big enough for the number and size of the new kernels I was putting
on it. So I repurposed another partition sda8. After copying the data from
sda2->sda8, then labeling the new partition 'Boot', and relabeling the old
partition 'Oboot',
grub continued to boot from the old partition (which, fortunately, I had not
scrubbed yet).

Only by manually changing grub's boot options and forcing it to rewrite the MBR
to boot from sda8, or, in 'grubby', hd(0,7), could I get it to boot from the
new partition.

Expected Results:
I expected grub to boot using the partition labeled 'Boot'

Flagging this as critical, since if someone doesn't realize that grub is still
booting from the old partition and reformats the old partition before manually
updating both grub's config files AND manually enters grub and learns grub
sufficiently to have it install a new boot record that points to the new
partition, they will have an unbootable system.

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
Follow Ups