2.02~beta3-5 exposes the same problem, but during grub-install I now get
the following error message:
nataraja:/sys/fs/pstore# grub-install
Installing for x86_64-efi platform.
File descriptor 4 (/dev/sda3) leaked on vgs invocation. Parent PID 16830:
grub-install
File descriptor 4 (/dev/sda3) leaked on vgs invocation. Parent PID 16830:
grub-install
Could not prepare Boot variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Input/output
error.
This seems related/identical to #756253 / #852513
I also had plenty of dmesg-* files in /sys/fs/pstore. Removing them
didn't help
strace tells me:
[pid 16934]
access("/sys/firmware/efi/efivars/Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c",
F_OK) = -1 ENOENT (No such file or directory)
[pid 16934]
open("/sys/firmware/efi/efivars/Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c",
O_WRONLY|O_CREAT, 0644) = 3
[pid 16934] ioctl(3, FS_IOC_GETFLAGS, 0x7ffe0df7b194) = 0
[pid 16934] write(3,
"\7\0\0\0\1\0\0\0b\0d\0e\0b\0i\0a\0n\0\0\0\4\1*\0\3\0\0\0"..., 122) = -1 ENOSPC
(No space left on device)
[pid 16934] ioctl(3, FS_IOC_GETFLAGS, 0x7ffe0df7b194) = 0
[pid 16934]
unlink("/sys/firmware/efi/efivars/Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c")
= 0
[pid 16934] close(3) = 0
[pid 16934] write(2, "Could not prepare Boot variable", 31Could not prepare
Boot variable) = 31
[pid 16934] write(2, ": No space left on device\n", 26: No space left on
device) = 26
Manually deleting a random entry with efibootmgr (the one for the NVMe
which I don't have) also didn't help.
--
- Harald Welte <[email protected]> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
