[Bug 1156688] New: Caller: /usr/share/YaST2/lib/bootloader/grub_install.rb:141:in `target'
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688 Bug ID: 1156688 Summary: Caller: /usr/share/YaST2/lib/bootloader/grub_install.rb:141:in `target' Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: axel.braun@gmx.de QA Contact: jsrain@suse.com Found By: --- Blocker: --- Details: unsupported combination of architecture aarch64 and disabled EFI Above error message was received when saving a change to GRUB from YaST -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c1
--- Comment #1 from Axel Braun
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c2
Josef Reidinger
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c3
Axel Braun
Can you specify what exactly you do? What change you want to apply and also how your system was installed?
Installed Leap 15.0 from the official LXQT image (last year...) Did a zypper dup to Leap 15.1 called up YaST -> boot loader added init 3 to the command line Save -> 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=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c4
Josef Reidinger
Hello Josef,
(In reply to Josef Reidinger from comment #2)
Can you specify what exactly you do? What change you want to apply and also how your system was installed?
Installed Leap 15.0 from the official LXQT image (last year...)
Can you be a more specific what is exactly LXQT image? some prebuild drop in image for arm or DVD installation?
Did a zypper dup to Leap 15.1 called up YaST -> boot loader added init 3 to the command line Save -> error message
Looks like content of /etc/sysconfig/bootloader is wrong. Can you please attach it? I have suspicion that it can be wrong in original image ( if it is not dvd installation ) as there was some bugs in kiwi. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c5
Axel Braun
(In reply to Axel Braun from comment #3)
Hello Josef,
(In reply to Josef Reidinger from comment #2)
Can you specify what exactly you do? What change you want to apply and also how your system was installed?
Installed Leap 15.0 from the official LXQT image (last year...)
Can you be a more specific what is exactly LXQT image? some prebuild drop in image for arm or DVD installation?
It was this one (maybe an even older version): http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/appliances...
Did a zypper dup to Leap 15.1 called up YaST -> boot loader added init 3 to the command line Save -> error message
Looks like content of /etc/sysconfig/bootloader is wrong. Can you please attach it? I have suspicion that it can be wrong in original image ( if it is not dvd installation ) as there was some bugs in kiwi.
will do -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c6
--- Comment #6 from Axel Braun
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c7
Jiri Srain
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c8
Axel Braun
Your sysconfig shows
LOADER_TYPE="grub2"
while it should be set to "grub2-efi". If you change this manually, YaST should work for you.
Yes, that fixes the error.
I assume that you got to this situation because of bug in the image. Could you, please, check whether deploying newer version (15.1 or TumbleWeed) results in the same or this is fixed? I don't have any ARM machine at hand.
The system was zypper dup'ed from a perfectly working 15.0 to 15.1. Anyway, I wanted to try the DVD Installation method anyway -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c9
Jiri Srain
(In reply to Jiri Srain from comment #7)
I assume that you got to this situation because of bug in the image. Could you, please, check whether deploying newer version (15.1 or TumbleWeed) results in the same or this is fixed? I don't have any ARM machine at hand.
The system was zypper dup'ed from a perfectly working 15.0 to 15.1. Anyway, I wanted to try the DVD Installation method anyway
Do you see any chance to find out how "grub2" appeared in sysconfig? Otherwise, I don't see much we could do about this bug :-( -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c10
Axel Braun
Do you see any chance to find out how "grub2" appeared in sysconfig?
Any log in which it might be?
Otherwise, I don't see much we could do about this bug :-(
A fix for the error message could be a potential solution as well :-) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c11
Josef Reidinger
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c12
Jiri Srain
A fix for the error message could be a potential solution as well :-)
Axel: Given the explanation, the error message is pretty accurate. Sure we can improve it, but do you have a suggestion? The JeOS images are usually maitnained by Fabian; before reassigning it, it would be useful to know whether most recent images are affected too (I've already seen images which had similar bugs fixed in later versions) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c13
Axel Braun
OK, let me clarify situation here:
1. it is not trivial to guess which boot code and where system has it placed ( e.g. in x86 it can be MBR or PBR on any disk ), so yast use value from /etc/sysconfig/bootloader to know what bootloader and where it is installed.
2. For arm we support only EFI booting.
3. In your case it looks like bug in image. It probably use image from kiwi that is from x86_64 which use legacy boot and just modify what is needed. It install grub2 to EFI partition, so it is working, but when yast tries to modify it, it things it uses non-EFI variant which is not supported.
I dont think so. The system-setup was already quite old and stable, based on Leap 15.0. The issue occured after I did an online-update to Leap 15.1. So it is _not_ an image-issue
A fix for the error message could be a potential solution as well :-)
Axel: Given the explanation, the error message is pretty accurate. Sure we can improve it, but do you have a suggestion?
Good question - I understand that EFI was disabled somehow? So instead of Caller: /usr/share/YaST2/lib/bootloader/grub_install.rb:141:in `target' the root cause of the problem: unsupported combination of architecture aarch64 and disabled EFI - please enable EFI
The JeOS images are usually maitnained by Fabian; before reassigning it, it would be useful to know whether most recent images are affected too (I've already seen images which had similar bugs fixed in later versions)
I did a full setup with a recent image and did not encounter the issue. As
written above, it seemed to be related to the upgrade process
--- Comment #14 from Axel Braun
OK, let me clarify situation here:
1. it is not trivial to guess which boot code and where system has it placed ( e.g. in x86 it can be MBR or PBR on any disk ), so yast use value from /etc/sysconfig/bootloader to know what bootloader and where it is installed.
2. For arm we support only EFI booting.
3. In your case it looks like bug in image. It probably use image from kiwi that is from x86_64 which use legacy boot and just modify what is needed. It install grub2 to EFI partition, so it is working, but when yast tries to modify it, it things it uses non-EFI variant which is not supported.
I dont think so. The system-setup was already quite old and stable, based on Leap 15.0. The issue occured after I did an online-update to Leap 15.1. So it is _not_ an image-issue
A fix for the error message could be a potential solution as well :-)
Axel: Given the explanation, the error message is pretty accurate. Sure we can improve it, but do you have a suggestion?
Good question - I understand that EFI was disabled somehow? So instead of Caller: /usr/share/YaST2/lib/bootloader/grub_install.rb:141:in `target' the root cause of the problem: unsupported combination of architecture aarch64 and disabled EFI - please enable EFI
The JeOS images are usually maitnained by Fabian; before reassigning it, it would be useful to know whether most recent images are affected too (I've already seen images which had similar bugs fixed in later versions)
I did a full setup with a recent image and did not encounter the issue. As written above, it seemed to be related to the upgrade process -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c13
Axel Braun
OK, let me clarify situation here:
1. it is not trivial to guess which boot code and where system has it placed ( e.g. in x86 it can be MBR or PBR on any disk ), so yast use value from /etc/sysconfig/bootloader to know what bootloader and where it is installed.
2. For arm we support only EFI booting.
3. In your case it looks like bug in image. It probably use image from kiwi that is from x86_64 which use legacy boot and just modify what is needed. It install grub2 to EFI partition, so it is working, but when yast tries to modify it, it things it uses non-EFI variant which is not supported.
I dont think so. The system-setup was already quite old and stable, based on Leap 15.0. The issue occured after I did an online-update to Leap 15.1. So it is _not_ an image-issue
A fix for the error message could be a potential solution as well :-)
Axel: Given the explanation, the error message is pretty accurate. Sure we can improve it, but do you have a suggestion?
Good question - I understand that EFI was disabled somehow? So instead of Caller: /usr/share/YaST2/lib/bootloader/grub_install.rb:141:in `target' the root cause of the problem: unsupported combination of architecture aarch64 and disabled EFI - please enable EFI
The JeOS images are usually maitnained by Fabian; before reassigning it, it would be useful to know whether most recent images are affected too (I've already seen images which had similar bugs fixed in later versions)
I did a full setup with a recent image and did not encounter the issue. As
written above, it seemed to be related to the upgrade process
--- Comment #14 from Axel Braun
OK, let me clarify situation here:
1. it is not trivial to guess which boot code and where system has it placed ( e.g. in x86 it can be MBR or PBR on any disk ), so yast use value from /etc/sysconfig/bootloader to know what bootloader and where it is installed.
2. For arm we support only EFI booting.
3. In your case it looks like bug in image. It probably use image from kiwi that is from x86_64 which use legacy boot and just modify what is needed. It install grub2 to EFI partition, so it is working, but when yast tries to modify it, it things it uses non-EFI variant which is not supported.
I dont think so. The system-setup was already quite old and stable, based on Leap 15.0. The issue occured after I did an online-update to Leap 15.1. So it is _not_ an image-issue
A fix for the error message could be a potential solution as well :-)
Axel: Given the explanation, the error message is pretty accurate. Sure we can improve it, but do you have a suggestion?
Good question - I understand that EFI was disabled somehow? So instead of Caller: /usr/share/YaST2/lib/bootloader/grub_install.rb:141:in `target' the root cause of the problem: unsupported combination of architecture aarch64 and disabled EFI - please enable EFI
The JeOS images are usually maitnained by Fabian; before reassigning it, it would be useful to know whether most recent images are affected too (I've already seen images which had similar bugs fixed in later versions)
I did a full setup with a recent image and did not encounter the issue. As written above, it seemed to be related to the upgrade process -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688
http://bugzilla.opensuse.org/show_bug.cgi?id=1156688#c15
--- Comment #15 from Jiri Srain
(In reply to comment #11 and #12)
I dont think so. The system-setup was already quite old and stable, based on Leap 15.0. The issue occured after I did an online-update to Leap 15.1. So it is _not_ an image-issue
Did you run the YaST bootloader module also before upgrade from 15.0 to 15.1? I can imagine that the problem did not show up if you did not. I'm aware of at least one issue, where a bootloader was not configured correctly in the initial image, but the bug was revealed after upgrade first. While it is hardly any related to this particular bug (back then it was only about the label), especially if you did not run YaST bootloader module at all before upgrade it sounds likely that the bug was there from the beginning (or could have been introduced any time before you performed upgrade).
A fix for the error message could be a potential solution as well :-)
Axel: Given the explanation, the error message is pretty accurate. Sure we can improve it, but do you have a suggestion?
Good question - I understand that EFI was disabled somehow? So instead of Caller: /usr/share/YaST2/lib/bootloader/grub_install.rb:141:in `target' the root cause of the problem: unsupported combination of architecture aarch64 and disabled EFI - please enable EFI
Not necessarily: The point is: YaST stores the information in sysconfig. If the information there is wrong from the beginning, it does not prevent system from booting and in many cases even update of the bootloader itself will not result in failure.
The JeOS images are usually maitnained by Fabian; before reassigning it, it would be useful to know whether most recent images are affected too (I've already seen images which had similar bugs fixed in later versions)
I did a full setup with a recent image and did not encounter the issue. As written above, it seemed to be related to the upgrade process
-- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com