https://bugzilla.suse.com/show_bug.cgi?id=1179170 https://bugzilla.suse.com/show_bug.cgi?id=1179170#c7 Raymund Will <rw@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(rw@suse.com) | --- Comment #7 from Raymund Will <rw@suse.com> --- [in reverse order... ;)] 1. efibootmgr-17 (available from [1]) already has `efi_set_verbose(opts.verbose - 2, stderr);` in it's "verbosity handling", so if you try that, please use (at least) '-vvv'. 2. no, I have no recollection of or other idea about what could be going on, but would be interested to learn, whether efibootmgr-17 would make any difference! 3. is it be possible, that this is a "reused" installation, which has been upgraded at least once? Or are there other explanations for the LVM-related warnings in the log? 4. do we need to look into those "leaked file descriptors"? 5. why do we think that updating `grub2-i386-pc` would have any effect on this UEFI machine? 6. how would a failed modification of an UEFI variable, in an otherwise "unchanged" boot setup, lead to a 'grub>' prompt? Are there any error messages from grub before the prompt? And 6) is the most pressing issue reported here, IMHO. AFAICT, something must have gone wrong in the `update-bootloader --refresh` (AKA `grub2-mkconfig`) area, as opposed to `update-bootloader --reinit` (AKA `grub2-install`). IOW, 7. is the contents of `/boot/grub2/grub.cfg` plausible? Same for `/boot/efi/efi/openSUSE/grub.cfg`? Unfortunately more questions that answers... [1] https://download.opensuse.org/repositories/home:/rwill:/branches:/Base:/Syst... -- You are receiving this mail because: You are on the CC list for the bug.