http://bugzilla.suse.com/show_bug.cgi?id=1051006
http://bugzilla.suse.com/show_bug.cgi?id=1051006#c2
--- Comment #2 from Raymund Will
there's NO bootorder set, unlike previously
efibootmgr BootCurrent: 0002 Timeout: 1 seconds No BootOrder is set; firmware will attempt recovery
This is *very* strange! But that's more often a firmware issue that a problem with 'efibootmgr' itself. Did you keep the log files from your upgrade?
attempting to WRITE a boot order, as always,
efibootmgr --create \ --gpt \ --write-signature \ --part-uuid 7124dec5-4c19-53e4-4654-1e42652c3d01 \ --loader '\EFI\opensuse\grubx64.efi' \ --label "SVR01"
This command is, well. quite creative -- and, AFAICT, has *never* worked! First a) no need to use '--gpt', unless your PMBR is broken. Is yours? then b) no need to use '--write-signature', as that's for pseudo-ESP on legacy/MS-DOS partition tables, where the boot sector is used to store a somewhat unique ID. *Useless* on GPT. but most importantly c) this '--part-uuid' option is only supported for '--delete' (ATM). You'll have to use '--disk' with '--part', as always.
FAILs at
efibootmgr: unrecognized option '--part-uuid'
Granted, this error message could use a "for --create" appendix. [...]
efibootmgr --help | grep part-uuid
Well, efibootmgr -h | grep -i UUID --delete delete entry by bootnum (-b), by UUID (-P) -P | --part-uuid UUID select all variables for given partition UUID will provide (a little) more context. (Especially that "select all variables" sub-phrase!) [...]
fyi, worked OK on leap 42.2's efibootmgr ...
No -- definitely not! Not your command -- that's IMHO impossible. -- You are receiving this mail because: You are on the CC list for the bug.