I used Apdatifier today, to install the updates, that it showed to me. Since the update a program called Bambu Studio did not start anymore. So, I wanted to restore a snapshot and ran into a frightening wall of, the system did not want to boot anymore.
So from your screenshots it looks like step 10 wasn’t successful (This is the step where you move the snapshots from the @.broken directory back to the newly created @ directory that you copied from the “good” snapshot. That is why BTRFS manager is showing the snapshots are still located in the @.broken directory.
Here is a link to that article:
You may have to boot off the usb drive to move it, I’m not sure what impact moving it on a live system would be.
the other issue is you just need to remove the database lock whenever you restore a snapshot (this is normal because the snapshots occur during the pacman process so the database is locked when the snapshot takes place so when you replace one of those snapshots the database is in a locked state).
You can either use the button in the CachyOS Helllo app by clicking the Apps/Tweaks button, and then clicking the button that says Remove db lock.
The other way is just to enter the command that that button is doing for you which is:
sudo rm /var/lib/pacman/db.lck
Once you do that the database will no longer be locked.
It is probably good that it was locked because I’m not sure where it would have created the snapshots since they are still under the @.broken directory. It probably would have created a new @/.snapshots directory but I don’t know for sure. Anyway the good news is you caught it before that happened. Just make sure that the snapshots are in the proper directory (@/.snapshots/) before you remove the database lock and start running pacman again.
Also a final note is the very end of that “How to restore a Snapper root snapshot on an unbootable system” I talk about the final cleanup of deleting the @.broken directory once your are back on a good snapshot. Just make sure your /.snapshots/ directory is moved out of the @.broken directory before cleaning up that snapshot. you can do the cleanup in BTRFS Assistant once it all looks good just go to the Subvolumes tab and delete @.broken there. Just as I said make sure you have successfully moved the /.snapshots/ folder over to the @ subvolume before you do so.
I do have problems understanding it completely, and I must say, without AI I would have probably switched back to Windows immediately .
I setup my currenty system with the BTRFs filesystem and systemd as bootloader. Today, I tried to do the process called “chroot” with the help of the guide on the wiki page, a youtube video and also AI, but I ran into one wall after another (after I sucessfully mounted the root partition).
So, I am planning to do a fresh install and now, I do some research about a better way to setup my snapshots and which bootloader to pick, so that I can better handle these situations.
You may want to give the Limine bootloader a try. The CachyOS team has done a bunch of work recently with it so that you can boot into different snapshots right from the bootloader which may give you more of the experience you are looking for.
I actually went this way, after I saw, that Limine was added. Though, I did not know what it is, but I googled it up and decided to give it a try. I already did a “test” with it. Booted into a snapshot and restored it. Worked without any issues.
.
.