Package: grub2-common
Version: 2.06-5
Followup-For: Bug #925591
It looks like the Ubuntu folks have added this as a template named
grub-efi/install_devices in their templates.in located in the source for
package:
---
https://packages.ubuntu.com/source/kinetic/grub2-unsigned
related to their bug o
A script that syncs EFI volume data to mountpoints with numbered suffixes '.N'
and adds boot entries via efibootmgr#!/bin/sh
if [ "$1" = "--write" ]
then
COMMAND_PREFIX=''
RSYNC_N=''
elif [ "$1" = "--dry-run" ]
then
COMMAND_PREFIX='echo will run:'
RSYNC_N='n'
else
echo "Usage: $(basename "$0
Installing ESP on software raid may not be a good idea, even if raid metadata
is at the end of partitions.
Perhaps, a better approach would be to add procedural ESP duplication via hooks
in grub and whatever else needs to write to /boot/efi (potentially
debian-installer?).
Basic concept of a m
Just stumbled upon this after converting a system from Legacy Boot to
UEFI (boot into live, sort out partitions, remove grub-pc, install
grub-efi, reboot, reconfigure bios).
After running `apt install grub-efi` and rebooting, although the former
fails with the error mentioned above, debian corr
Jakub,
if it's still relevant, I faced with exactly same problem during Debian
installation on Terramaster F5-421, grub-install fails with same messages.
I wonder if there's any workaround possible.
On Sun, 27 Oct 2019 23:29:28 + Jakub Filo wrote:
> Hello,
>
> I would like to ask, what fi
Hello,
I would like to ask, what firmware is this happening on? Any chance it's
OVMF?
Best Regards,
Jakub Filo
Package: grub2-common
Version: 2.02+dfsg1-13
# grub-install
Installing for x86_64-efi platform.
efibootmgr: option requires an argument -- 'd'
efibootmgr version 15
usage: efibootmgr [options]
-a | --active sets bootnum active
-A | --inactive sets bootnum inactive
7 matches
Mail list logo
