efibootmgr can not create new entry due to ENOSPC error

Bug #1167567 reported by RussianNeuroMancer
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

After 2013-04-09 GRUB2 update in Raring, Ubuntu disappear from boot entry list in UEFI so system was unable to boot. I tried to recreate boot entry using Ubuntu 13.04 Beta 2 LiveCD (command: efibootmgr --create --gpt --disk /dev/sda --part 1 --write-signature --label "ubuntu" --loader "\\EFI\\ubuntu\\grubx64.efi") but get this error message in dmesg:
[ 1036.500775] efivars: set_variable() failed: status=8000000000000009
Error message in strace output (attached): "-1 ENOSPC (No space left on device)".
I tried to reset UEFI settings but this doesn't help.

With Ubuntu 12.10 LiveCD I able to successfully add boot entry to UEFI and system boot fine.

Hardware: ZOTAC ZBOX Blu-ray AD03 PLUS
UEFI version: 4.6.4 10/12/2012

Revision history for this message
RussianNeuroMancer (russianneuromancer) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1167567

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
RussianNeuroMancer (russianneuromancer) wrote : Re: efobootmgr can not create new entry due to ENOSPC error

> If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

All useful logs probably left on LiveCD session. If I need to rerun Raring LiveCD and do apport-collect after efivars error message, please let me know.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0]. You will need to install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc6-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
RussianNeuroMancer (russianneuromancer) wrote :

Issue still reproducible with Linux 3.9rc6.

I also checked pstore content and if I do everything right (simply "mount -t pstore /sys/fs/pstore /sys/fs/pstore and looked into /sys/fs/pstore") pstore looks like empty.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
summary: - efobootmgr can not create new entry due to ENOSPC error
+ efibootmgr can not create new entry due to ENOSPC error
Revision history for this message
mard0 (martijn-doornbusch-l) wrote :

I am also unable to create a boot entry with efibootmgr in raring. I'm not sure about the "no space left" error, but I also have [ 1036.500775] efivars: set_variable() failed: status=8000000000000009 in dmesg.
This is on a asus F1A75-M pro motherboard with the latest bios

Revision history for this message
RussianNeuroMancer (russianneuromancer) wrote :

> I'm not sure about the "no space left" error
You can check if you run efibootmgr under strace.

Revision history for this message
falstaff (falstaff) wrote :

I can confirm this bug too under raring. I'm using a HP EliteBook 8530w, I'm absolutly sure the command used to work in quantal... I've the set_variable failed in dmesg and No space left on device:

open("/sys/firmware/efi/vars/BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/sys/firmware/efi/vars/new_var", O_WRONLY) = 3
write(3, "B\0o\0o\0t\0O\0r\0d\0e\0r\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 2084) = -1 ENOSPC (No space left on device)
close(3) = 0
exit_group(1) = ?

Revision history for this message
falstaff (falstaff) wrote :

Just tested latest upstream, it still doesn't work, however, the strace looks a bit different:

open("/sys/firmware/efi/vars/BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var", O_WRONLY) = 3
write(3, "B\0o\0o\0t\0O\0r\0d\0e\0r\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 2084) = -1 EIO (Input/output error)
close(3) = 0
exit_group(1) = ?
sag@alpha ~$ uname -a
Linux alpha 3.9.1-030901-generic #201305080210 SMP Wed May 8 06:11:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.