[Bug 845652] New: single line chainloader syntax fails ("GRUB _" displays on boot attempts)
https://bugzilla.novell.com/show_bug.cgi?id=845652 https://bugzilla.novell.com/show_bug.cgi?id=845652#c0 Summary: single line chainloader syntax fails ("GRUB _" displays on boot attempts) Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: mrmazda@earthlink.net QAContact: jsrain@suse.com Found By: --- Blocker: --- Created an attachment (id=563225) --> (http://bugzilla.novell.com/attachment.cgi?id=563225) y2logs from 32 bit core2duo host hs80e Initial summary: single line chainloader syntax fails ("GRUB _" displays on boot attempts) On attempt to chainload boot: "chainloader (hd2,23)+1 GRUB _" is all that displays after Grub menu clears. That first line is the sole menu.lst stanza cmdline. This dates back at least to 11.4. I've only seen it on systems with md RAID1 partitions spread across HD0 and HD1 and the target / on HD2 (and / partitions above #15). Failure happens whether Grub Legacy setup is during installation, or using YaST-configured /etc/grub.conf and grub script, or using setup from a grub> prompt. Even after changing /boot/grub/device.map to contain only valid by-id entries boot fails, though setup command reports success on every attempt. I normally boot 13.1 (and 11.4, 12.1, 12.2 & 12.3) on the system by loading vmlinuz and initrd directly (Grub Legacy IIRC from 12.3B1 installed on a HD0 partition) instead of by chainloading. If the menu.lst stanza is instead of as above is as follows: rootnoverify (hd2,23) chainloader +1 then success, or root (hd2,23) chainloader +1 then also success. In every single HD installation I've done (hundreds), the single line syntax normally works. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=845652 https://bugzilla.novell.com/show_bug.cgi?id=845652#c1 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mrmazda@earthlink.net AssignedTo|jsrain@suse.com |duwe@suse.com --- Comment #1 from Jiri Srain <jsrain@suse.com> 2013-10-14 06:40:19 UTC --- To make sure, this still is GRUB1, right? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=845652 https://bugzilla.novell.com/show_bug.cgi?id=845652#c2 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mrmazda@earthlink.net | --- Comment #2 from Jiri Srain <jsrain@suse.com> 2013-10-14 07:11:27 UTC --- Legacy GRUB, as confirmed via email. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=845652 https://bugzilla.novell.com/show_bug.cgi?id=845652#c Torsten Duwe <duwe@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=845652 https://bugzilla.novell.com/show_bug.cgi?id=845652#c3 Torsten Duwe <duwe@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |mrmazda@earthlink.net --- Comment #3 from Torsten Duwe <duwe@suse.com> 2013-12-04 17:32:52 UTC --- Are you sure you're examining a suse grub1 that got compiled with the chainloader-devicefix patch? It should do exactly this trick. And you probably know that partitions > 15 mean asking for trouble on Linux, although grub is able to handle this. What do the config files look like? Do you have BSD slices on the disk? Is the whole disk mirrored? With BIOS support (fake RAID)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=845652 https://bugzilla.novell.com/show_bug.cgi?id=845652#c4 --- Comment #4 from Felix Miata <mrmazda@earthlink.net> 2013-12-04 21:52:41 UTC --- Created an attachment (id=570281) --> (http://bugzilla.novell.com/attachment.cgi?id=570281) partitioning of comment 0 system Note that this is primarily a backup to my local server, configured with MD RAID1 on selected partitions on the two internal HDs. I use it secondarily with an external HD to participate in openSUSE Factory processes. With or without the eSATA attached, booting is from sda1, which currently has Grub Legacy from an openSUSE 12.2 pre-release, with binary files in (hd0,0)/grub (e.g. stage1) dated 15 July 2012. Note also that the LVM column applies to OS/2 LVM info only, which here is used as an annotation device accessible from DOS boot facilitating keeping track of what's what in a building with dozens of HDs and many hundreds of partitions. (In reply to comment #3)
And you probably know that partitions > 15 mean asking for trouble on Linux, although grub is able to handle this.
As you may be able to infer from the attachment, I've been using disks with more than 15 partitions with Linux and multibooting since long before libata was born.
Do you have BSD slices on the disk?
Nowhere in the whole building.
Is the whole disk mirrored?
Partitions only.
With BIOS support (fake RAID)?
Not available on this hardware. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=845652 https://bugzilla.novell.com/show_bug.cgi?id=845652#c5 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|mrmazda@earthlink.net | --- Comment #5 from Felix Miata <mrmazda@earthlink.net> 2013-12-04 21:52:48 UTC --- Created an attachment (id=570282) --> (http://bugzilla.novell.com/attachment.cgi?id=570282) menu.lst from (hd0,0)/grub on host hs80e from comment 0 I've modified what was to this current state to facilitate follow-up to this bug by creating extra copies of one line and two line stanzas directly following the default stanza, both for chainloading 13.1 on BIOS HD2. Default+1, the "one line" stanza, produces the errant behavior here reported. Default+2, the "two line" stanza, produces expected behavior. (In reply to comment #3)
Are you sure you're examining a suse grub1 that got compiled with the chainloader-devicefix patch? It should do exactly this trick.
How can I tell that? Is this patch newer than 17 months old? Maybe it's broken?
What do the config files look like?
#device map from (hd0,0)/grub/ (hd0) /dev/disk/by-id/ata-ST3500418AS_9VMSH74A (hd1) /dev/disk/by-id/ata-ST3320613AS_6SZ088F7 (hd2) /dev/disk/by-id/ata-HDS722580VLSA80_VN6B3ECBF65LMC Any other config files of interest? The only time Grub scripts ever get run here is when YaST uses them during openSUSE installation, and always to install to a partition, never MBR. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=845652 https://bugzilla.novell.com/show_bug.cgi?id=845652#c6 Torsten Duwe <duwe@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO AssignedTo|duwe@suse.com |mchang@suse.com --- Comment #6 from Torsten Duwe <duwe@suse.com> 2013-12-18 10:51:09 UTC --- Is this report still valid for openSuse 13.1? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=845652 https://bugzilla.novell.com/show_bug.cgi?id=845652#c7 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider| |mrmazda@earthlink.net --- Comment #7 from Felix Miata <mrmazda@earthlink.net> 2013-12-18 22:22:45 UTC --- Did the binary content in the Grub Legacy rpm change between 13.1RC1 and 13.1? Last Grub changelog entry was in April, about BuildRequire/automake. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=845652 https://bugzilla.novell.com/show_bug.cgi?id=845652#c8 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|mrmazda@earthlink.net | --- Comment #8 from Felix Miata <mrmazda@earthlink.net> 2014-03-03 00:59:34 UTC --- (In reply to comment #7)
Did the binary content in the Grub Legacy rpm change between 13.1RC1 and 13.1? Last Grub changelog entry was in April, about BuildRequire/automake.
To answer my own question, no, it did not change. So, yes, this applies to 13.1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com