You are not logged in.

Pages: 1

#1 2019-10-31 15:10:04

ArchLinuxSU
Member
Registered: 2019-10-09
Posts: 13

Failed to start Store a System Token in an EFI Variable.

After the moment when grub-install selected the following message for me: 

grub-install: error: cannot find EFI directory

I noticed a message that appeared on the screen for a second at boot: 

Failed to start Store a System Token in  an EFI Variable.

To get logs about the service, I used: 

systemctl status systemd-boot-system-token.service

  Actually, the output:

● systemd-boot-system-token.service - Store a System Token in an EFI Variable
   Loaded: loaded (/usr/lib/systemd/system/systemd-boot-system-token.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2019-10-31 16:34:47 UTC; 4min 2s ago
     Docs: man:systemd-boot-system-token.service(8)
  Process: 518 ExecStart=/usr/bin/bootctl random-seed (code=exited, status=1/FAILURE)
 Main PID: 518 (code=exited, status=1/FAILURE)

Oct 31 16:34:47 archiso systemd[1]: Starting Store a System Token in an EFI Variable...
Oct 31 16:34:47 archiso bootctl[518]: Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.
Oct 31 16:34:47 archiso bootctl[518]: Alternatively, use --esp-path= to specify path to mount point.
Oct 31 16:34:47 archiso systemd[1]: systemd-boot-system-token.service: Main process exited, code=exited, status=1/FAILURE
Oct 31 16:34:47 archiso systemd[1]: systemd-boot-system-token.service: Failed with result 'exit-code'.
Oct 31 16:34:47 archiso systemd[1]: Failed to start Store a System Token in an EFI Variable.

And now it’s not entirely clear to me how to work with this.

I beg you, if you understand how to solve the problem or at least get closer to this, you do not need to leave links to infinitely large manuals from ArchWiki, avoiding responsibility.  Just help.  I really want to return to work with this distribution, but after a variety of measures have been taken, I understand that I can’t do it on my own.

Last edited by ArchLinuxSU (2019-10-31 17:36:14)

Offline

#2 2019-10-31 15:21:28

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,650

Re: Failed to start Store a System Token in an EFI Variable.

The error message you posted and what you are actually having an issue with have nothing do with each other (grub and the efi system token are unrelated, and largely irrelevant concepts at the point in time you are at). If you want to know more about that service and that message read  https://systemd.io/RANDOM_SEEDS (but again, this isn't whatever your actual problem is, and not relevant to the failing grub install)

Use [ code ] [ /code ] tags not some weird highlight to post output. Please change the title to what you are actually having an issue with (again, that error message is irrelevant and expected at that point in time if you are still in the beginning of installation)

Post the commands you've used to set up the system, post the output of 

lsblk -f
efibootmgr -v

from inside the chroot, the exact and unalterated complete grub-install command you attempt to use and it's output.

ArchLinuxSU wrote:

I beg you, if you understand how to solve the problem or at least get closer to this, you do not need to leave links to infinitely large manuals from ArchWiki, avoiding responsibility.

The wiki has been written to not need to repeat the most basic information endlessly. There are cases where the best possible answer to an issue you are having is posting the relevant wiki excerpt.

Last edited by V1del (2019-10-31 15:33:19)

Offline

#3 2019-11-01 11:40:17

ArchLinuxSU
Member
Registered: 2019-10-09
Posts: 13

Re: Failed to start Store a System Token in an EFI Variable.

V1del wrote:

Use [ code ] [ /code ] tags not some weird highlight to post output.

Thanks for telling me how to format the syntax correctly.

I apologize in advance for the terrible hierarchy of sections.  This is a necessary measure.


lsblk -f && echo "\n\n\n" && efibootmgr -v

Output:

NAME   FSTYPE   LABEL        UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0  squashfs                                                         0   100% /run/archiso/sfs/airootfs
sda                                                                              
├─sda1                                                                           
├─sda2 ntfs                  50F667BBF667A048                                    
├─sda3 ext4     Home         0e06e5a7-2e87-4898-ad1b-de8bf4df5aeb                
├─sda4 ntfs     Restore 76F41CE1F41CA581                                    
├─sda5 vfat                  B21D-9B19                                           
├─sda6 ntfs                  DE0673CE0673A665                                    
├─sda7 ext2     Boot         31452050-c297-47c1-9f10-d713fd2d55ae                
└─sda8 ext4     Root         dfab427e-7f3c-42d7-8902-23897a259246                
sdb                                                                              
└─sdb1 vfat     ARCH_201910  767E-C5F1                              28.4G     2% /run/archiso/bootmnt




BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0000,0001,0002
Boot0000  Windows Boot Manager	HD(5,GPT,df37daa8-06db-4188-9d1b-fa9b5aa853df,0x1edb8800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................
Boot0001  Hard Drive	BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)..GO..NO..........C.T.4.8.0.B.X.5.0.0.S.S.D.1...................\.,.@.r.d.=.X..........A.................................>..Gd-.;.A..MQ..L.9.1.3.2.1.E.6.8.9.0.E.D. . . . . . . . ........BO
Boot0002  USB KEY	BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0b00)..GO..NO..........S.a.n.D.i.s.k...................\.,.@.r.d.=.X..........A.............................>..Gd-.;.A..MQ..L.4.C.5.3.0.0.0.1.0.5.0.6.2.2.1.1.0.4.4.1........BO
Boot0003* UEFI: SanDisk, Partition 1	PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x0)/USB(11,0)/HD(1,GPT,64fb306d-6353-4a0a-b0e4-ef4022157bba,0x800,0x3a1f7df)..BO

Regarding Grub:

With any method from ArchWiki that is applicable to UEFI, when I try to execute a command, I get 

grub-install: error: cannot find EFI directory.

As a simple example, this happens with 

 grub-install /dev/sda

Last edited by ArchLinuxSU (2019-11-01 11:43:21)

Offline

#4 2019-11-01 11:58:54

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,650

Re: Failed to start Store a System Token in an EFI Variable.

That simple example of yours is a BIOS boot installation method (which "Archwiki in relation to uefi article" did you get that from exactly?). If you actually want an EFI install you must mount your ESP (in your case /dev/sda5 or B21D-9B19 ) somewhere (as you explicitly have a boot parititon (you don't need to have one FWIW, but that's not inherently problematic)) you will want to use some other directory) to install the EFI binary into, e.g. /efi . So at that point in time, mount your root to /mnt your boot to /mnt/boot and your ESP (/dev/sda5) to /mnt/efi chroot in and run the relevant EFI GRUB installation command, i.e. 

grub-install --target=x86_64-efi --efi-directory=/efi--bootloader-id=GRUB

https://wiki.archlinux.org/index.php/GRUB#UEFI_systems  read that link, it explains the why and what's and why your command doesn't work.

Last edited by V1del (2019-11-01 12:05:08)

Offline

#5 2019-11-02 13:16:36

ArchLinuxSU
Member
Registered: 2019-10-09
Posts: 13

Re: Failed to start Store a System Token in an EFI Variable.

You were a little mistaken when you rewrote the team, but it generally helped.  Among other things, three simple steps had to be preliminarily performed:

mkinitcpio -P
pacman -S efibootmgr
grub-mkconfig -o /boot/grub/grub.cfg

And finally, what you talked about:

grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB

The biggest culprit that I was forced to kill several days of my life fighting GRUB was the efibootmgr package, the installation of which turned out to have to be done beforehand.  But because this is not explicitly stated, I was looking for a problem elsewhere, and even the right steps were in vain.  I was very disorientated that this package is present in the image, but not in the base group.  The second mistake was to use(mount) the section without the EFI System label, but this is not so important, and if I read the article again, I would probably notice this.

Thanks for the help.

Offline

#6 2019-11-02 14:43:43

loqs
Member
Registered: 2014-03-06
Posts: 17,318

Re: Failed to start Store a System Token in an EFI Variable.

efibootmgr is an optional dependency for grub when you install a package with optional dependencies pacman will list each of those
along with an optional description of the feature the dependency enables and if the dependency is currently installed e.g.:

Optional dependencies for grub
    freetype2: For grub-mkfont usage [installed]
    fuse2: For grub-mount usage [installed]
    dosfstools: For grub-mkrescue FAT FS and EFI support [installed]
    efibootmgr: For grub-install EFI support [installed]
    libisoburn: Provides xorriso for generating grub rescue iso using
    grub-mkrescue
    os-prober: To detect other OSes when generating grub.cfg in BIOS systems
    mtools: For grub-mkrescue FAT FS support

Offline

Pages: 1

Board footer

Powered by FluxBB