http://bugzilla.novell.com/show_bug.cgi?id=951962 http://bugzilla.novell.com/show_bug.cgi?id=951962#c4 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |glin@suse.com --- Comment #4 from Michael Chang <mchang@suse.com> --- This sounds very unusual to me. The "Error: you need to load the kernel first" is from linuxefi which failed in loading the kernel image then subsequent command "initrdefi" reported it. Usually, the reasoning of the failure (to load the kernel image) should have been logged as well, but from that attached screenshot in comment#1 I did not see any error message but only the command itself, which is weird. These boot configuration from running openSUSE system (booted by refind) could be useful 1. EFI boot manager efibootmgr -v 2. Contents of ESP find /boot/efi 3. content of /boot/grub2/grub.cfg 4. content of /boot/efi/EFI/opensuse/grub.cfg 5. And please specify which boot entry in one of efibootmgr -v output is being used for booting opensuse
The only thing I have to check is that there is a "boot" folder with a "bootx64.efi" in > the EFI partition of each disk to be able to interchange them when the system is off. > (I need to worry to do this mainly on Debian. Manjaro and Antergos even create a > Microsoft folder with bootmgfw.efi.)
This sounds fishy to me, the EFI/boot/bootx64.efi is default loader path on ESP and openSUSE wouldn't overwrite it if it exist before installation. I think one failure scenario could be that, you exchanged the disk and default loader was always used for booting the previously installed system, which may have been erased by newer openSUSE install that wouldn't make it's loader as default .. CC gary -- You are receiving this mail because: You are on the CC list for the bug.