Your message dated Mon, 10 Jun 2019 01:37:08 +0100
with message-id <[email protected]>
and subject line Re: Bug#846927: does not check return value
has caused the Debian Bug report #846927,
regarding does not check return value
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
846927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846927
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub2-common
Version: 2.02~beta3-3
Severity: normal
File: /usr/sbin/grub-install
Hi!
grub-install does not check the return value of
efibootmgr:
| grub-install: info: Registering with EFI: distributor = `debian', path =
`\EFI\debian\grubx64.efi', ESP at hostdisk//dev/sda,gpt1.
| grub-install: info: executing efibootmgr --version </dev/null >/dev/null.
| grub-install: info: executing modprobe -q efivars.
| grub-install: info: executing efibootmgr -c -d /dev/sda -p 1 -w -L debian -l
\EFI\debian\grubx64.efi.
| Could not prepare Boot variable: No space left on device
| Installation finished. No error reported.
Despite efibootmgr failing and returning an eror code (5)
grub-install claims installation was successful. This
resulted into an unbootable system. See also
#845023 for an example.
grub-install should check the return code of efibootmgr,
report it to the user, and (idealy) suggest a strategy
to workaround this firmware bug.
Daniel
--- End Message ---
--- Begin Message ---
On Sun, Dec 04, 2016 at 01:12:26PM +0100, Daniel Bayer wrote:
>Package: grub2-common
>Version: 2.02~beta3-3
>Severity: normal
>File: /usr/sbin/grub-install
>
>Hi!
>
>grub-install does not check the return value of
>efibootmgr:
>
>| grub-install: info: Registering with EFI: distributor = `debian', path =
>`\EFI\debian\grubx64.efi', ESP at hostdisk//dev/sda,gpt1.
>| grub-install: info: executing efibootmgr --version </dev/null >/dev/null.
>| grub-install: info: executing modprobe -q efivars.
>| grub-install: info: executing efibootmgr -c -d /dev/sda -p 1 -w -L debian -l
>\EFI\debian\grubx64.efi.
>| Could not prepare Boot variable: No space left on device
>| Installation finished. No error reported.
>
>Despite efibootmgr failing and returning an eror code (5)
>grub-install claims installation was successful. This
>resulted into an unbootable system. See also
>#845023 for an example.
>
>grub-install should check the return code of efibootmgr,
>report it to the user, and (idealy) suggest a strategy
>to workaround this firmware bug.
ACK, this used to be an issue. This has now been fixed, in two ways:
* I added error-checking
* Later on, Colin has now switched Grub to using libefivar directly
(with error-checking!) instead of forking efibootmgr.
so I'm closing this bug.
--
Steve McIntyre, Cambridge, UK. [email protected]
You lock the door
And throw away the key
There's someone in my head but it's not me
--- End Message ---
