You are not logged in.

#26 2020-09-12 19:18:11

chinesegranny
Member
From: Russia, Saint-Petersburg
Registered: 2020-09-11
Posts: 13

Re: EFISTUB problem

I appreciate your help, but your decision's a bit sophisticated and I don't want to manually reassemble those parts every time the core's updated.
Planning to read about GRUB sad .

Last edited by chinesegranny (2020-09-12 19:19:16)

Offline

#27 2020-09-12 20:24:57

d_fajardo
Member
Registered: 2017-07-28
Posts: 924

Re: EFISTUB problem

chinesegranny wrote:

Look at the output of blkid command (post №7):

I wasn't talking about partition UUID but GUID: https://en.wikipedia.org/wiki/GUID_Part … type_GUIDs
I believe this ID is set when you partition the drive (a kind of stamp) and is unique for each partition TYPE and so partitions of the same type can have the same GUID.
Also you might want to check this: https://www.rodsbooks.com/efi-bootloaders/efistub.html

Offline

#28 2020-09-12 21:12:19

chinesegranny
Member
From: Russia, Saint-Petersburg
Registered: 2020-09-11
Posts: 13

Re: EFISTUB problem

d_fajardo wrote:
chinesegranny wrote:

Look at the output of blkid command (post №7):

I wasn't talking about partition UUID but GUID: https://en.wikipedia.org/wiki/GUID_Part … type_GUIDs
I believe this ID is set when you partition the drive (a kind of stamp) and is unique for each partition TYPE and so partitions of the same type can have the same GUID.
Also you might want to check this: https://www.rodsbooks.com/efi-bootloaders/efistub.html

If you mean partition type, then I chose EFI system type at /dev/sda1 and Linux filesystem at /dev/sda2.

Offline

#29 2020-09-12 22:02:30

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 5,537
Website

Re: EFISTUB problem

chinesegranny wrote:

I don't want to manually reassemble those parts every time the core's updated

I wrote:

Use a pacman hook to recreate BOOTX64.EFI every time the kernel is updated

https://wiki.archlinux.org/index.php/Pacman#Hooks

And I've just noticed this on the "discussion" part of the EFISTUB [sic] ArchWiki page:

Vglfr wrote:

As of today, efibootmgr record with --unicode 'root=PARTUUID=00...' fails with message similar to "Cannot find disk /dev/disk/by-partuuid/00...". Replacing PARTUUID with UUID fixes the issue

So try that as well as the forward-slash for the initrd path.

FWIW the Debian wiki advises using a double backslash for the initrd path: https://wiki.debian.org/EFIStub

I suspect that different UEFI implementations have different requirements, what with UEFI being the buggy, bloated pile of shite that it is roll

Offline

#30 2020-09-13 07:51:44

nl6720
Wiki Admin
Registered: 2016-07-02
Posts: 244

Re: EFISTUB problem

d_fajardo wrote:

I wasn't talking about partition UUID but GUID: https://en.wikipedia.org/wiki/GUID_Part … type_GUIDs
I believe this ID is set when you partition the drive (a kind of stamp) and is unique for each partition TYPE and so partitions of the same type can have the same GUID.

UUID is basically the same thing as GUID, the Linux world calls it UUID.
The thing you're talking about is partition UUID (PARTUUID) vs partition type UUID (PARTTYPE). Multiple partitions can have the same partition type UUID, since it just designates the type of partition, but they must not have the same partition UUID. Partitioning software creates unique partition UUIDs, so the only chance of collision is when cloning a disk or manually setting a non-unique partition UUID.

Head_on_a_Stick wrote:

FWIW the Debian wiki advises using a double backslash for the initrd path: https://wiki.debian.org/EFIStub

That's just a shell escaping issue. https://wiki.archlinux.org/index.php/EFISTUB#efibootmgr uses single quotes, so one slash is fine.

Last edited by nl6720 (2020-09-13 07:56:39)

Offline

Board footer

Powered by FluxBB