Your message dated Mon, 3 Apr 2017 13:01:38 +0100
with message-id <20170403120138.ga5...@einval.com>
and subject line Re: [wea...@debian.org: Bug#858832: calls efibootmgr with
invalid options]
has caused the Debian Bug report #858832,
regarding calls efibootmgr with invalid options
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 ow...@bugs.debian.org
immediately.)
--
858832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-efi-arm64
Version: 2.02~beta3-5
Severity: serious
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team
On upgrading from jessie to stretch on our arm64 box acker.debian.org I
noticed this issue with grub-efi-arm64:
acker:~# apt-get install --reinstall grub-efi-arm64
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
Need to get 73.0 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://mirror.netcologne.de/debian stretch/main arm64 grub-efi-arm64
arm64 2.02~beta3-5 [73.0 kB]
Fetched 73.0 kB in 0s (603 kB/s)
Preconfiguring packages ...
(Reading database ... 62883 files and directories currently installed.)
Preparing to unpack .../grub-efi-arm64_2.02~beta3-5_arm64.deb ...
Unpacking grub-efi-arm64 (2.02~beta3-5) over (2.02~beta3-5) ...
Setting up grub-efi-arm64 (2.02~beta3-5) ...
Installing for arm64-efi platform.
efibootmgr: option requires an argument -- 'd'
efibootmgr version 14
usage: efibootmgr [options]
-a | --active sets bootnum active
-A | --inactive sets bootnum inactive
-b | --bootnum XXXX modify BootXXXX (hex)
-B | --delete-bootnum delete bootnum
-c | --create create new variable bootnum and add to bootorder
-C | --create-only create new variable bootnum and do not add to
bootorder
-D | --remove-dups remove duplicate values from BootOrder
-d | --disk disk (defaults to /dev/sda) containing loader
-r | --driver Operate on Driver variables, not Boot Variables.
-e | --edd [1|3|-1] force EDD 1.0 or 3.0 creation variables, or guess
-E | --device num EDD 1.0 device number (defaults to 0x80)
-g | --gpt force disk with invalid PMBR to be treated as GPT
-i | --iface name create a netboot entry for the named interface
-l | --loader name (defaults to \EFI\redhat\grub.efi)
-L | --label label Boot manager display label (defaults to "Linux")
-m | --mirror-below-4G t|f mirror memory below 4GB
-M | --mirror-above-4G X percentage memory to mirror above 4GB
-n | --bootnext XXXX set BootNext to XXXX (hex)
-N | --delete-bootnext delete BootNext
-o | --bootorder XXXX,YYYY,ZZZZ,... explicitly set BootOrder (hex)
-O | --delete-bootorder delete BootOrder
-p | --part part (defaults to 1) containing loader
-q | --quiet be quiet
-t | --timeout seconds set boot manager timeout waiting for user input.
-T | --delete-timeout delete Timeout.
-u | --unicode | --UCS-2 pass extra args as UCS-2 (default is ASCII)
-v | --verbose print additional information
-V | --version return version and exit
-w | --write-signature write unique sig to MBR if needed
-y | --sysprep Operate on SysPrep variables, not Boot
Variables.
-@ | --append-binary-args file append extra args from file (use "-"
for stdin)
-h | --help show help/usage
grub-install: error: efibootmgr failed to register the boot entry: Operation
not permitted.
Failed: grub-install --target=arm64-efi
WARNING: Bootloader is not properly installed, system may not be bootable
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.9.0-2-arm64
Found initrd image: /boot/initrd.img-4.9.0-2-arm64
Found linux image: /boot/vmlinuz-4.9.0-0.bpo.2-arm64
Found initrd image: /boot/initrd.img-4.9.0-0.bpo.2-arm64
Found linux image: /boot/vmlinuz-4.8.0-0.bpo.2-arm64
Found initrd image: /boot/initrd.img-4.8.0-0.bpo.2-arm64
Adding boot menu entry for EFI firmware configuration
done
acker:~#
Cheers,
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `- https://www.debian.org/
--- End Message ---
--- Begin Message ---
On Tue, Mar 28, 2017 at 08:59:30PM +0300, Andrei Borzenkov wrote:
>28.03.2017 09:34, Peter Palfrader пишет:
>> } /dev/md2 953M 176K 953M 1% /boot/efi
>
>Sorry, that's not going to work. Even assuming that grub can map from
>Linux MD to underlying physical device + partition (as that is what
>efibootmgr needs, we cannot simply pass /dev/md2 to it), this will
>obviously fail unless metadata is 0.90 or 1.0 (and current mdadm default
>is 1.2). And even if you are careful enough - EFI application is free to
>write to ESP, so unless you have EFI driver for Linux MD it is no go to
>try to mirror it, as you are never sure whether mirrors are identical
>after boot. And if you have EFI driver for Linux MD you need to modify
>efibootmgr to understand it.
ACK, good catch.
>We need to return better error message here to explain what happens
>though, that's the actual bug.
>
>The (IMHO) correct way to handle ESP redundancy is to call "grub-install
>/path/to/first/ESP /path/to/second/ESP". I have half-finished patch
>allowing this, but it will need distributions cooperation to actually be
>useful.
More than happy to help with that - it's something I've been wanting
for a while.
--
Steve McIntyre, Cambridge, UK. st...@einval.com
"I used to be the first kid on the block wanting a cranial implant,
now I want to be the first with a cranial firewall. " -- Charlie Stross
--- End Message ---
