From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Peter Palfrader <weasel@debian.org>, 858832-forwarded@bugs.debian.org
Subject: Re: [weasel@debian.org: Bug#858832: calls efibootmgr with invalid options]
Date: Mon, 27 Mar 2017 16:08:30 +0300 [thread overview]
Message-ID: <CAA91j0U9w2+QdyqOVBh4z2ZxqTY+V_a3KNe81R1ao16FJ51_8A@mail.gmail.com> (raw)
In-Reply-To: <20170327124133.GG9002@riva.ucam.org>
Link to the bug report would be helpful. I assume it contains actual
invocation with arguments, I do not see them in this mail.
On Mon, Mar 27, 2017 at 3:41 PM, Colin Watson <cjwatson@debian.org> wrote:
> I guess that the attached bug happens because grub_install_register_efi
> is called on non-biosdisk-ish systems but uses
> grub_util_biosdisk_get_osdev to get an OS device name for
> efidir_grub_dev->disk, which isn't going to work so well. I'm a bit
> rusty here - would anyone care to venture a guess at suitable
> replacement code that would work on devices other than biosdisk?
>
> Thanks,
>
> --
> Colin Watson [cjwatson@debian.org]
>
>
> ---------- Forwarded message ----------
> From: Peter Palfrader <weasel@debian.org>
> To: Debian Bug Tracking System <submit@bugs.debian.org>
> Cc:
> Bcc:
> Date: Mon, 27 Mar 2017 12:24:16 +0000
> Subject: Bug#858832: calls efibootmgr with invalid options
> Package: grub-efi-arm64
> Version: 2.02~beta3-5
> Severity: serious
> User: debian-admin@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/
>
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
next prev parent reply other threads:[~2017-03-27 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 12:41 [weasel@debian.org: Bug#858832: calls efibootmgr with invalid options] Colin Watson
2017-03-27 13:08 ` Andrei Borzenkov [this message]
2017-03-27 13:09 ` Peter Palfrader
2017-03-27 16:25 ` Andrei Borzenkov
2017-03-28 6:34 ` Peter Palfrader
2017-03-28 17:59 ` Andrei Borzenkov
2017-04-03 12:01 ` Steve McIntyre
2017-04-03 20:22 ` Patch to support ESP redundancy [was: Re: [weasel@debian.org: Bug#858832: calls efibootmgr with invalid options]] Francesco Poli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA91j0U9w2+QdyqOVBh4z2ZxqTY+V_a3KNe81R1ao16FJ51_8A@mail.gmail.com \
--to=arvidjaar@gmail.com \
--cc=858832-forwarded@bugs.debian.org \
--cc=grub-devel@gnu.org \
--cc=weasel@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).