** Attachment removed: "AptOrdering.txt"
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1776271/+attachment/5151390/+files/AptOrdering.txt
** Attachment removed: "BootEFIContents.txt"
https://askubuntu.com/questions/1072618/could-not-prepare-boot-variable-
no-space-left-on-device-grub-install-error-ef
Solved the issue for me by clearing out the dump files in
/sys/firmware/efi/efivars (ubuntu 18)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I have not been able to reboot my desktop in nearly two months. What is
the fix? Do I have to reflash the BIOS? How do I ensure the desktop is
bootable after I reflash? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also tried that before I flashed my firmware and got the same error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776271
Title:
Could not prepare Boot variable: No space left on device (package
thanks,
this
sudo apt install --reinstall shim-signed
didn't work for me.. still getting the same error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776271
Title:
Could not prepare Boot
It was a new version. If you are able to reflash the same version, it may work,
it doesn't seem to be related to a specific firmware version from what I can
tell, I think something in the process of flashing the firmware enables the
boot device to be updated properly.
--
You received this bug
I just need to do this:
sudo apt install --reinstall shim-signed
Thanks abssorb.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776271
Title:
Could not prepare Boot variable: No space left on
I had flashed the latest firmware a few months back, did you re-flash
the same version or a new one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776271
Title:
Could not prepare Boot variable: No
Sure, this is happening on an IBM Tower System x3400 M3
Product name System x3400 M3
Machine type and model: 737954A
Firmware VPD
Firmware Type Version String Release Date
IMM YUOOH5A-1.55 01/15/2018
UEFI Y4E161A-1.17 06/07/2018
DSA DSYT83D-3.33 01/07/2011
--
You received this
Hi !
The device is a Lenovo Thinkpad X121 netbook/notebook built roughly mid
of 2011. It has got a not sooo powerful AMD E-350 CPU with related AMD
chipset. It is serving as my gateway to the world when travelling
around.
Lenovo is said to have a sort of strange BIOS / UEFI implenentations
Same error after upgrade
root@node13:/boot/efi/EFI/ubuntu# efibootmgr -v
BootCurrent: 000D
Timeout: 10 seconds
No BootOrder is set; firmware will attempt recovery
Boot* CD/DVD RomVenMedia(0c588db8-6af4-11dd-a992-00197d890238,0c)
Boot0001* Floppy Disk
I'm also running into this issue on 18.04 (fresh install about 3 months
ago)
Motherboard: Asus Sabertooth Z97 Mark S
CPU: Intel I7-4790K
RAM: 32GB
Primary Boot Drive: Crucial M550 256GB SSD
Secondary Drives (ZFS mirror, non-boot): Crucial M550 256GB SSD and Samsung
830 SSD.
sudo apt -f
Update - a BIOS upgrade fixed this for me. HP Pavilion All-in-One - 23-q199na.
Perhaps this cleared the NVRAM.
sudo apt -f install resulted in:
W: APT had planned for dpkg to do more than it reported back (0 vs 4).
Affected packages: shim-signed:amd64
and was fixed with a reinstall
sudo
I had the same today, dist-upgrade to linux-headers-4.15.0-34 resulted
in the same error as above.
sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
Sorry for double-paste. Meant to copy this.
sudo efibootmgr -v
BootCurrent: 0003
Timeout: 2 seconds
No BootOrder is set; firmware will attempt recovery
Boot* Windows Boot Manager
May be similar to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1776271
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776271
Title:
Could not prepare Boot variable: No space left on
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shim-signed (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776271
Title:
** Changed in: shim-signed (Ubuntu)
Status: Incomplete => New
** Changed in: shim-signed (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As requested:
0 reinhard@kolibri-lnx $ sudo efibootmgr -v
[sudo] Passwort für reinhard:
BootCurrent: 0007
Timeout: 0 seconds
BootOrder: 000A,,0001,0002,0005,0006,0007,0008,0009
Boot Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0001 Boot Menu
** Tags added: id-5b200d53e16a747ff2a43bb0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776271
Title:
Could not prepare Boot variable: No space left on device (package
shim-signed
Hi,
Could you please run the following commands and report their full
output?
sudo efibootmgr -v
sudo efibootmgr -v -c -L ubuntu -l \\EFI\\ubuntu\\shimx64.efi
(the backslashes there matter, we are building a path in EFI mode)
Thanks!
--
You received this bug notification because you are a
21 matches
Mail list logo
