efivar-0.21 fails to create boot entry when device min number > 127, breaks efibootmgr
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| efivar (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
This bug has also been reported and fixed on github, but is present in the version of libefivar0 present in Ubuntu 15.10:
https:/
This bug breaks efibootmgr when trying to setup an EFI boot entry for a device with a minor number > 127:
E.g.
$ sudo efibootmgr --create --disk /dev/sdk --part 1 --label "GRUB2 Shim" --loader "\\EFI\
efibootmgr: Could not set variable: No such file or directory
efibootmgr: Could not prepare boot variable: No such file or directory
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdk 8:160 1 3.8G 0 disk
└─sdk1 8:161 1 1G 0 part /boot/efi
This also seems to break Ubuntu 15.10 upgrades and install on system where the EFI boot device has a minor number >127.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libefivar0 0.21-1
ProcVersionSign
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
Date: Fri Oct 23 17:41:28 2015
Dependencies:
gcc-5-base 5.2.1-22ubuntu2
libc6 2.21-0ubuntu4
libgcc1 1:5.2.1-22ubuntu2
InstallationDate: Installed on 2014-04-27 (544 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: efivar
UpgradeStatus: Upgraded to wily on 2015-10-23 (0 days ago)

This has been fixed in the current version in 16.04 per that upstream commit. 16.04 is carrying 0.23 release.