I installed an update last night, but it won’t boot. This is normal since I started using bcache, in a couple of days there’ll be another update and it’ll be fine. I just boot from a previous snapshot in the meantime
The previous snapshot starts the boot process, I get the tumbleweed logo for a bit, but then I get a “UUID does not exist” error and won’t boot. Initially I thought maybe a drive had failed or had become disconnected but they all seem to be detected. (Also surely it wouldn’t get this far if that were the case?) I tried to probe the disks in recovery mode and I didn’t see any issues, but I couldn’t see most of the information because I couldn’t work out how to scroll up in tty.
I checked in YaST via install media and got “Probing file system with UUID XXXXXX failed”. If I ignore and go through the process as if I were installing tumbleweed again all of the drives and LVMs are visible when I go through with “start with existing proposal”, but bcache itself is not showing up under the bcache header, but I don’t know if it’s supposed to at this stage.
I found this thread: YAST Bootloader error: Probing filesystem failed which suggests that it’s a snapper issue (which would track) but ngl I can’t make head nor tail of the proposed workaround which is to invoke “LIBSTORAGE_BTRFS_SNAPSHOT_RELATIONS=no” uh somehow. Someone else in the comments of that bug report asked where exactly to put that and didn’t get a response. I tried pressing E in the grub screen and typing it next to the bit about CPU mitigations etc but it didn’t do anything that I could tell.
Is anyone able to offer any advice? Every day is a school day