No, I'm afraid rEFInd's debugging features are pretty primitive.
What you might try is using an EFI shell to see how the Btrfs driver is affecting its view of the disks. It's entirely possible that the EFI (and therefore rEFInd) does see your Btrfs volumes and subvolumes, but that they've got a directory name that rEFInd is not scanning. If so, adding the appropriate path in the also_scan_dirs line in refind.conf should fix the problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Is there a way to enable some kind of logging in refind? I would like to know why it does not spot automatically btrfs subvolumes on my rig.
Thanks.
No, I'm afraid rEFInd's debugging features are pretty primitive.
What you might try is using an EFI shell to see how the Btrfs driver is affecting its view of the disks. It's entirely possible that the EFI (and therefore rEFInd) does see your Btrfs volumes and subvolumes, but that they've got a directory name that rEFInd is not scanning. If so, adding the appropriate path in the
also_scan_dirsline inrefind.confshould fix the problem.