biuro74

OK, now it works with that UID given by blkid. Previously, I was using "UID" given by Gparted and ls -lha /dev/disk/by-uuid. And altough I was aware of few "UID"s (UUID, GUID etc), I was pretty convinced that these tools would give me a correct UID in case of FAT-based partition, but apparently there are too many UIDs - and given by various tools - which leads to nothing but confusion. I am really sorry you have to deal with that mess, because OS makers try to force own solutions instead of present...

So - shortly - ESPs are not recognizable for loader token at this moment ? As far as I know, I can't relabel ESP, and they all have the same (filesystem ?) label "System" by default. Maybe is it any chance to make some workaround in rEFInd code to recognize ESPs - or all FATs in general - at loading all partitions stage and identify them by FAT serial number (because it's all they can be identified by, I'm afraid - or am I wrong ?).

So - shortly - ESPs are not recognizable for loader token at this moment ? As far as I know, I can't relabel ESP, and they all have the same (filesystem ?) label "System" by default. Maybe is it any chance to make some workaround in rEFInd code to recognize ESPs at loading all partitions stage and identify them by FAT serial number (because it's all they can be identified by, I'm afraid - or am I wrong ?).

I'm quite sure the 225A-B0BF's GRUB is loading F31, because I've got an UEFI BIOS entry done with: efibootmgr -c -d /dev/md126 -p 8 -l \\EFI\\fedora\\grubx64.efi -L FEDORA311 which loads that GRUB and its menu shows few F31 kernels to boot. So - UEFI BIOS can read that ESP and start F31 GRUB, but rEFInd can't, from some reason. I'm old school man and all (un)related questions I answer & explain, maybe they look like unrelated, but they all matter at least to me, when I remind this thred after some...

I'm quite sure the 225A-B0BF's GRUB is loading F31, because I've got an UEFI BIOS entry (done with efibootmgr) which loads that GRUB and its menu shows few F31 kernels to boot. So - UEFI BIOS can read that ESP and start F31 GRUB, but rEFInd can't, from some reason. I'm old school man and all (un)related questions I answer & explain, maybe they look like unrelated, but they all matter at least to me, when I remind this thred after some time :)

I'm quite sure the 225A-B0BF's GRUB is loading F31, because I've got an UEFI BIOS entry which loads that GRUB and its menu shows few F31 kernels to boot. So - UEFI BIOS can read that ESP and start F31 GRUB, but rEFInd can't, from some reason. I'm old school man and all (un)related questions I answer & explain, maybe they look like unrelated, but they all matter at least to me, when I remind this thred after some time :)

Sorry for interrupting this interesting firmware_bootnum sub-thread, but I'm still waiting for any clue why a volume token doesn't work properly (at least for me - regarding to multiple EFI partitions) ?

Sorry for interrupting this interestingfirmware_bootnum sub-thread, but I'm still waiting for any clue why a volume token doesn't work properly (at least for me - regarding to multiple EFI partitions) ?