I'm marking the thread as solved, though I still have some concerns, so feel free to add your thoughts or advice. In any case, if using btrfs as my main filesystem, I want to become proficient at using its built-in functions instead of relying on another tool. It shakes my confidence of using this as a reliable backup system for / but, as mentioned, I'm still very new to btrfs, so maybe I'm overstating the I misspoke, fsarchiver can work with btrfs, but my filesystem is written on a partitionless whole disk, which fsarchiver cannot work with. As you'd mentioned, the path of the subvolume of the subvolume showed up as an empty folder, so I could just add the relevant ID to fstab to mount it where I want.īecause of grub's failure to boot after I changed the default subvolume, which forced me to take the steps outlined, it makes me wonder what other 'gotchas' might potentially be hidden in other programs that have internal references to the root filesystem of ID 0. According to the wiki, the kernel line and fstab both need to be modified to boot into a snapshot, but I did neither and my method worked successfully. The solution was to boot back into systemrescuecd, mount and chroot the filesystem, regenerate the grub config and then reinstall grub. Rebooting simply replicated the same fatal error as before. Should the update go badly, instead, the snapshot can be made the default subvolume and, after a reboot, everything is as it was before.Īctually, it's not quite that simple.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |