rEFInd Snags on BTRFS Snapshots: Why Booting Past the Kernel Line Needs Root Access
Booting into BTRFS snapshots via rEFInd is failing for multiple users, with the dedicated `refind-btrfs` module proving ineffective in practice.
The debate centers on two fronts: the technical procedure for snapshot restoration and the method for diagnosing failures. Some suggest restoring a root subvolume demands that the system not be actively using it. Meanwhile, others like Moonpiedumplings point fingers at kernel mismatch, warning that old kernels reading new modules after a snapshot restore causes the failure. On the procedural front, gpstarman noted the complexity added by non-standard /boot and /efi partitions.
The immediate consensus demands users bypass speculation and focus on log analysis. Both taaz and harsh3466 insist the fix lies in examining system logs upon reaching emergency mode; however, Moonpiedumplings issues a stark warning: if the root account is locked by default, simply accessing emergency mode won't reveal the root cause.
Key Points
The rEFInd module failure is a critical barrier to accessing BTRFS snapshots.
gpstarman confirmed the installed `refind-btrfs` module failed to achieve the primary goal of snapshot booting.
Kernel incompatibility is a suspected root cause.
Moonpiedumplings alleges that kernel module reading conflicts arise when older kernels attempt to view modules post-snapshot restore.
System logs are the undeniable next diagnostic step.
taaz and harsh3466 both mandate examining system logs by gaining root credentials.
Snapshot restoration timing matters immensely.
Some argue the restore process cannot occur while the root subvolume is actively utilized, while the issue could simply be an out-of-date /etc/fstab entry, as possiblylinux127 suggested.
Troubleshooting from emergency mode is blind if the root account is locked.
Moonpiedumplings pointed out that if the root account is locked (default on CachyOS), emergency mode troubleshooting provides no actionable data.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.