© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
The error in your log is:
shim-signed (1.34.9+
x86_64-efi wird für Ihre Plattform installiert.
Could not prepare Boot variable: No space left on device
grub-install: Fehler: efibootmgr failed to register the boot entry: Eingabe-
[1mdpkg:[0m Fehler beim Bearbeiten des Paketes shim-signed (--configure):
This indicates that there is a problem writing the bootloader information to your firmware's nvram. It is a requirement that UEFI systems allow writing to these variables from the OS in order to update the boot options.
According to your bug report, you initially installed Ubuntu 17.10. Is it possible your firmware's nvram is locked because you are affected by bug #1734147?
Is it possible that you have somehow toggled a "lock" on the firmware variables, preventing them from being updated? I understand that some Lenovo firmware has such an option, did you knowingly turn it on?
Your existing firmware boot config shows no entry for ubuntu, and no BootOrder variable. How do you boot Ubuntu on this system, since it's not a boot option in your firmware config?