From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arne Babenhauserheide Subject: bug#40496: cannot install bootloader Date: Wed, 08 Apr 2020 22:33:42 +0200 Message-ID: <87lfn590pl.fsf@web.de> References: <87sghf2gek.fsf@web.de> <87ftdfkp1h.fsf@devup.no> <87k12r2dyu.fsf@web.de> <87a73mly4f.fsf@devup.no> <87sghe8oc6.fsf@web.de> <87369el2vj.fsf@devup.no> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:40921) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jMHOd-00068d-Sw for bug-guix@gnu.org; Wed, 08 Apr 2020 16:34:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jMHOc-0006z3-RM for bug-guix@gnu.org; Wed, 08 Apr 2020 16:34:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:41388) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jMHOc-0006yu-Kj for bug-guix@gnu.org; Wed, 08 Apr 2020 16:34:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jMHOc-0000Lq-Ej for bug-guix@gnu.org; Wed, 08 Apr 2020 16:34:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87369el2vj.fsf@devup.no> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org Sender: "bug-Guix" To: Marius Bakke Cc: 40496@debbugs.gnu.org Marius Bakke writes: > Arne Babenhauserheide writes: > >> Marius Bakke writes: >> >>> I hope you are able to recover your system. If the problem is "just" >>> that the boot entry is missing, >> >> Do you mean in grub? > > I mean in the firmware boot menu. The way UEFI works is that > bootloaders update the firmware directly with a name, EFI System > Partition, and executable (most likely "/EFI/Guix/grubx64.efi"). Ah, I did not know that. Thank you! >>> you should be able to create a new one >>> with "efibootmgr --create" manually. Here is a typical entry with the >>> EFI System Partition as the first partition of a disk: >>> >>> # efibootmgr -v >>> BootCurrent: 0000 >>> Timeout: 1 seconds >>> BootOrder: 0000,0002 >>> Boot0000* Guix HD(1,GPT,32944052-6012-4cda-b270-fe653d430c84,0x800,0x4= 800)/File(\EFI\Guix\grubx64.efi) >> >> When I run efibootmgr -v, I get an error: >> $ efibootmgr -v >> EFI variables are not supported on this system. > > This also requires booting in "EFI mode" so that /sys/firmware/efi is > present. The live USB image supports EFI, but you may need to disable > "legacy boot" to make it boot in EFI mode. I=E2=80=99ll try that. >>> 1 is the partition number, and the UUID is the same as 'lsblk -o >>> PARTUUID /dev/sda1' assuming your disk is /dev/sda. I don't remember >>> what 0x800 and 0x4800 means, but don't think they are required. >> >> I get somewhat too little information from that: >> >> $ lsblk -O /dev/nvme1n1p1 >> NAME KNAME PATH MAJ:MIN FSAVAIL FSSIZE FSTYPE FSUSED FSUSE% MOUNTPOINT L= ABEL UUID PTUUID PTTYPE PARTTYPE PARTLABEL PARTUUID PARTFLAGS RA RO RM HOT= PLUG MODEL SERIAL SIZE STATE OWNER GROUP MODE ALIGNMENT MIN-IO OPT-I= O PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE TYPE DISC-ALN DISC-GRAN DISC-MAX DISC-= ZERO WSAME WWN RAND PKNAME HCTL TRAN SUBSYSTEMS REV VENDOR ZONED >> nvme1n1p1 >> nvme1n1p1 >> /dev/nvme1n1p1 >> 259:2 15,4G 884,9G 824,5G 93% /home = 128 0 0 = 0 900G root disk brw-rw---- 0 512 = 0 512 512 0 none 1023 part 0 512B 2T = 0 0B 0 nvme block:nvme:pci > > You probably need to use "sudo" to read the PARTUUID. Ah, yes, that works! Thank you! > HTH, > Marius --=20 Unpolitisch sein hei=C3=9Ft politisch sein ohne es zu merken