From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: bug#40496: cannot install bootloader Date: Wed, 08 Apr 2020 11:53:52 +0200 Message-ID: <87369el2vj.fsf@devup.no> References: <87sghf2gek.fsf@web.de> <87ftdfkp1h.fsf@devup.no> <87k12r2dyu.fsf@web.de> <87a73mly4f.fsf@devup.no> <87sghe8oc6.fsf@web.de> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:43588) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jM7QG-00054f-C8 for bug-guix@gnu.org; Wed, 08 Apr 2020 05:55:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jM7QF-0007CN-0G for bug-guix@gnu.org; Wed, 08 Apr 2020 05:55:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:39833) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jM7QE-0007By-Dd for bug-guix@gnu.org; Wed, 08 Apr 2020 05:55:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jM7QE-0000lq-AP for bug-guix@gnu.org; Wed, 08 Apr 2020 05:55:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87sghe8oc6.fsf@web.de> 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: Arne Babenhauserheide Cc: 40496@debbugs.gnu.org --=-=-= Content-Type: text/plain 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"). >> 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,0x4800)/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. >> 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 LABEL UUID PTUUID PTTYPE PARTTYPE PARTLABEL PARTUUID PARTFLAGS RA RO RM HOTPLUG MODEL SERIAL SIZE STATE OWNER GROUP MODE ALIGNMENT MIN-IO OPT-IO 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. HTH, Marius --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl6NnzAACgkQoqBt8qM6 VPqQFgf/WE8iKih3SjzuxAYqQTzW4Hb4Z9ik0tPp/K07JOYGa2XDjlmgU1Nt08UP CM2+CzF34CUiwlzlbSTi9J12190p2Z5W9C7zgjmZA1WJFkva+AjkDtKYkAYZLpD+ gAz9FPXD9Od6RO+1cayrBYmPvVCYkdO/Vb2+Bn1T5vvqu+XB1UgWeoWlJSHwyDyB pOoZjak4Yq5P8IxRUHzIJdLLJlTHgR2lYcLa+I9f09dgr+AuYtXbwXbef88CjeP0 CY3sDWCZ91RtK46ObHAyx4XNRzOFUrultYw1SBG5hbYUSVKtANCunqBVo0AL9jpN Hjqrwq187r1+7b5W8G/ivag2rT1Hkg== =rmYR -----END PGP SIGNATURE----- --=-=-=--