Help with manual boot stanza #17
Comments
|
Hi, I'm going to have to see your generated boot stanza. Also, paste the writable snapshot's (should be located in /root/.refind-btrfs) fstab file here, as well. Do you still have the auto-generated refind_linux.conf file located in /boot? If so, try deleting it. That one might cause issues, as well. |
|
I'm not sure what you mean by generated boot stanza if it's not what I put above. Here's the fstab of the latest snapshot: I do not have a refind_linux.conf. I saw another comment about getting rid of the commented out partuuid after volume but don't see it now. I deleted that and still the same results. |
|
There should be a generated boot stanza (defined in a generated config file) located in the "btrfs-snapshot-stanzas" directory which is itself located in the rEFInd's root directory. What you've pasted is your own boot stanza which you've defined directly in the refind.conf file, i.e. the source boot stanza. The fstab file that you've pasted here appears to be correct. I've deleted that comment because it turned out not to be true because the comments are completely ignored while parsing (which is good). |
|
Oh sorry! Now I understand. Here it is: |
|
Also, the relevant section from my refind-btrfs.conf: |
|
Try checking whether the loader and initrd files actually exist in the /root/.refind-btrfs/rwsnap_2021-09-18_13-00-01_ID387/boot directory. These files are: vmlinuz-linux, initramfs-linux.img and amd-ucode.img. Their existence (within the writable snapshot, after it's been created) is validated by refind-btrfs but check them manually as well, just to be sure. Also, it's pretty weird seeing this part being present in the "options" field - "video=DP-1:2560x1440@144 video=DP-2:2560x1440@144", considering that it doesn't exist in the source boot stanza. Other than that, I don't really have an idea as to what exactly went wrong. |
|
They do exist there as well. I threw that in the options because there's some funkiness going on with a RX 5700XT and 2 monitors and it resolved the issue for me with GRUB. Was testing whether or not I still need it. |
|
Well, I don't really have an idea in that case - my setup is very, very similar to yours (Intel instead of AMD and a somewhat different subvolume setup) and I'm able to boot into snapshots just fine. |
|
Managed to get it to boot. But I have no idea why this worked lol. Changed my stanza to this: I checked the boot options of the entry that worked and saw that it had |
|
And how does a generated stanza look like after these changes? |
|
Well, when I run I'm wondering if there's something more fundamentally wrong with my install. |
|
That is expected since you've removed the root subvolume's prefix from the paths themselves ("@"). I really don't see what might be wrong with your setup, it looks just fine to me. I've downloaded rEFInd's source (version 0.13.2) just to see whether I can find exactly what can cause the error you've been receiving. It's kinda cryptic, though: These conditions result in false being set to the "IsValid" variable, in your case. Why? Honestly, I have no idea because that snippet is indecipherable to me. |
|
Hello! I am having the exact same problem - but, I can not even boot into the manual stanza created initially for the First, my setup is this: I use a PCIe NVMe for my main OS, Windows, and it also has the ESP I use all the time for everything. I installed Garuda on a SATA SSD (seen as Anyway, since I use rEFInd for booting, I wrote this: Since I am experimenting with Linux modules, I also added entries for the mainline kernel alongside zen. But although this should be all correct, I still get "Invalid Loader!" errors, on all four configurations. Using the btrfs driver for Windows, I can confirm that the loader and images are there: Did I overlook something in the stanza? I am feeling a little confused :) Thank you in advance! |
|
Hi there, you might want to split the linux-mainline and linux-zen into two boot stanzas because I don't think that the "Boot - Zen" sub-menu entry could ever work correctly due to the mismatch between its "loader" option and the main "initrd" option which it inherits. All I can do is offer you the same advice that I've offered to @wazlecracker, that is to try asking this question in rEFInd's official discussion page. Why? Well, simply because its author and maintainer, Rod Smith, is active there and he is more far more likely to help you than I am. |
|
Not 100% sure this will work just yet. I will confirm if it does. I think I ran into a similar issue. Here is a portion of my Then when I run: My Subvolumes:
|
|
My setup is almost exactly the same as the one described in the example. The sole difference of note is the fact that I've isolated the /root/.refind-btrfs directory as a subvolume of its own, named You could try setting this option to "true" and observing what happens with regards to the inability to boot into a snapshot. This way, no new writable snapshots will be created from the read-only ones created by, presumably, Snapper. EDIT: You're using Fedora, if I'm not mistaken? It is fairly obvious but I'm not sure if its derivatives exist so it's a fair question (from my perspective, at least). If so, there also exists a discrepancy between rEFInd's version as offered by official Arch and Fedora repositories. It appears that version available for Fedora is 0.13.3.1 (fairly outdated by now, released over a year ago) whereas version 0.14.0.2 is available for Arch. |
Hello!
I'm on Arch and have installed your tool and can successfully run
refind-btrfs, however I can't seem to get the manual boot stanza correct to boot into my system. I can boot into it with the default entry rEFInd generates with its (I think) scanning, but trying to boot the manual entry fails with "invalid loader file!" and I'm not sure what I'm doing wrong.Stanza:
My fstab:
Can you help me figure out what I'm doing wrong here?
The text was updated successfully, but these errors were encountered: