Talk:Persistent block device naming
systemd-boot entry with label
- Could do, but it might also be worthwhile to consider slim down that section and crosslink more instead. Or, as a first step, you could convert the LABEL example at the end to a systemd-boot one and crosslink it to Systemd-boot#Standard root installations for the additional info there. --Indigo (talk) 20:35, 29 July 2015 (UTC)
Using persistent naming > Boot managers
This is suggested:
According to https://wiki.archlinux.org/index.php/Dm-crypt/Encrypting_an_entire_system#Configuring_the_boot_loader, this "naming" is expected by the cryptdevice kernel parameter of the cryptsetup mkinitcpio's hook. So I used a small variation on my computer:
And once in a few reboots, cryptsetup's hook can't find the disk! However, the following, supposed to be equivalent, works fine:
So I suggest replacing every
/dev/disk/ by either
UUID, either in those examples, or here https://wiki.archlinux.org/index.php/Dm-crypt/Encrypting_an_entire_system#Configuring_the_boot_loader.
As reference, the function used by cryptsetup's hook to parse the cryptdevice parameter: https://git.archlinux.org/mkinitcpio.git/tree/init_functions#n325.
- This section suggests
cryptdevice=/dev/disk/by-uuid/<device-UUID>:cryptroot, so I don't see the point of your proposal. -- Lahwaacz (talk) 18:12, 21 October 2017 (UTC)
- Let me reformulate, as always, I carefully visit the wiki and I first read:
deviceis the path to the device backing the encrypted device. Usage of Persistent block device naming is advisable.
- and then on the linked page the following example:
- So I write
cryptdevice=/dev/disk/by-partlabel/root_myhostinstead of the only thing that works every boot, which is:
- So I write