[Bug 1017776] New: parted: invalid token: legacy_boot
http://bugzilla.opensuse.org/show_bug.cgi?id=1017776 Bug ID: 1017776 Summary: parted: invalid token: legacy_boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: richard.bos@xs4all.nl QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 708199 --> http://bugzilla.opensuse.org/attachment.cgi?id=708199&action=edit y2log for only the bootloader session Trying to install a bootloader using YaST/bootloader /dev/sda3 was used to create the boot prompt using openSUSE_13.1. This one has the option 'set active flag in partition table'. Currently /dev/sdb5 with openSUSE_42.2 is used, I used the same 'set active flag' check, to create the boot prompt. The result is: y2log:Error output: /usr/sbin/parted: invalid token: legacy_boot This seem to be caused by the 'set active flag in partition table' setting. When I removed the setting the setting, the bootloader creator finished.... Details in the attached log file, and screenshots. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017776 http://bugzilla.opensuse.org/show_bug.cgi?id=1017776#c1 --- Comment #1 from Richard Bos <richard.bos@xs4all.nl> --- Created attachment 708200 --> http://bugzilla.opensuse.org/attachment.cgi?id=708200&action=edit Screenshot showing the error message -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017776 http://bugzilla.opensuse.org/show_bug.cgi?id=1017776#c2 --- Comment #2 from Richard Bos <richard.bos@xs4all.nl> --- Created attachment 708203 --> http://bugzilla.opensuse.org/attachment.cgi?id=708203&action=edit YaST/bootloader settings in the boot code tab -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017776 http://bugzilla.opensuse.org/show_bug.cgi?id=1017776#c3 --- Comment #3 from Richard Bos <richard.bos@xs4all.nl> --- Is it possible to check in advance that the 'set active flag in partition table' will not be succesful? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017776 http://bugzilla.opensuse.org/show_bug.cgi?id=1017776#c4 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsrain@suse.com Assignee|jsrain@suse.com |jreidinger@suse.com --- Comment #4 from Jiri Srain <jsrain@suse.com> --- The question is why it was not successful. Obviously, it is set to /dev/sdb4 (which is the extended partition and which is IMO correct): 2017-01-02 20:03:49 <1> mycloud(7939) [Ruby] lib/cheetah.rb:158 Executing "/usr/sbin/parted -s /dev/sdb set 4 legacy_boot on". 2017-01-02 20:03:49 <3> mycloud(7939) [Ruby] lib/cheetah.rb:206 Error output: /usr/sbin/parted: invalid token: legacy_boot Josef, any idea what YaST could do wrong or is this problem of parted itself? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017776 http://bugzilla.opensuse.org/show_bug.cgi?id=1017776#c5 --- Comment #5 from Josef Reidinger <jreidinger@suse.com> --- (In reply to Jiri Srain from comment #4)
The question is why it was not successful. Obviously, it is set to /dev/sdb4 (which is the extended partition and which is IMO correct):
2017-01-02 20:03:49 <1> mycloud(7939) [Ruby] lib/cheetah.rb:158 Executing "/usr/sbin/parted -s /dev/sdb set 4 legacy_boot on". 2017-01-02 20:03:49 <3> mycloud(7939) [Ruby] lib/cheetah.rb:206 Error output: /usr/sbin/parted: invalid token: legacy_boot
Josef, any idea what YaST could do wrong or is this problem of parted itself?
well, combination is strange, as legacy_boot is used only for GPT disks and such disks do not have extended partition. Will check logs. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017776 http://bugzilla.opensuse.org/show_bug.cgi?id=1017776#c6 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #6 from Josef Reidinger <jreidinger@suse.com> --- ah, now I get where is problem /dev/sda uses gpt and /dev/sdb is msdos partition table. And for not yet known reason it confuse parted writer. I will try to find reason and also make code more robust in this area. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017776 http://bugzilla.opensuse.org/show_bug.cgi?id=1017776#c7 --- Comment #7 from Josef Reidinger <jreidinger@suse.com> --- Well, I do not see in logs why yast2-bootloader think /dev/sda is mbr device. But I will prepare more robust code that should prevent it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017776 http://bugzilla.opensuse.org/show_bug.cgi?id=1017776#c8 --- Comment #8 from Richard Bos <richard.bos@xs4all.nl> --- Joseph, for your information, some background info: sda and sdb are exactly the same disks. Bought at the same time (few years back). However until now only sda is/was used. At the time it was configured with openSUSE_13.1 -> different fdisk. sdb was configured during installation of openSUSE_42.2 (newer fdisk) and sda was not touched during this installation. That's probably why one disk is configured with gpt and the other msdos. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017776 http://bugzilla.opensuse.org/show_bug.cgi?id=1017776#c9 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Josef Reidinger <jreidinger@suse.com> --- yes, make sense. Send fix to TW and when stacked enough it will also reach Leap 42.2 and SP2 ( depends on maintenance team ). https://github.com/yast/yast-bootloader/pull/397 Thanks for report -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com