Couple of hiccups with btrfs timeshift restoring

Hello, this is just a post to help maybe resolve or get info on a couple of issues I’ve run into when doing a timeshift btrfs snapshot restore test.

For context, I basically made a manual snapshot (snapshot A), and then added a test folder and file to my desktop and made another snapshot (snapshot B), so I could see if it functions properly. I was able to boot into snapshot A via the grub-btrfs menu, and then from there I restored snapshot A properly via Timeshift and rebooted, and it worked fine, aside from now when it boots up, instead of saying “Welcome to EndeavourOS” it says “Welcome to EndeavourOS dracut-107 (initramfs)” which is odd but not really an issue i suppose.

I also tried to delete snapshot A after thinking the system was fine, but that ended up bricking my system, or at least my desktop environment which I wasn’t expecting. I figured it wouldn’t actually be loaded into snapshot A after a restore, but would instead make a copy. I guess I was wrong. Either way no biggie, I was able to do the same process for loading into snapshot B and I didn’t lose anything.

But now I can’t fully delete the backup Timeshift made before it restored snapshot A without getting an error and I’m also missing 2 of my subvolumes, var/lib/portables and var/lib/machines, I’m not sure if they were important but they’re gone now post restore. Mostly I’m just concerned that I now have to be mindful not to delete a certain snapshot in Timeshift or my whole system might break, or that the restore has messed something up and my system will break out of nowhere eventually.

Basically I’m just asking for any extra info or guidance on what I should do from here in case there’s something I’m not doing that i should be or some things here that are easily fixable, anyone who’s ever used timeshift restores please chime in and correct me if I’m doing it wrong.

also couple things, in btrfs-assistant it actually has my old subvolumes in a backup for some reason but not in any other backup, and when i go to manually look at the backup its not actually there, i mean did try to delete it so thats probably why, and also my drive has changed to show @ and stuff instead of what it was previous which i cant recall i believe it was just / or something instead of @ for the root

image

ok now im quite confused, my drive has gone back to this, sorry if im rattling on a bit this is all new to me

Can you share the output of findmnt --real and sudo btrfs sub list /

Please post the text, not screenshots.

output of first command:

TARGET SOURCE FSTYPE OPTIONS
/      /dev/nvme0n1p2[/timeshift-btrfs/snapshots/2025-05-14_23-22-41/@]
│             btrfs  rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=276,subvol=/timeshif
├─/run/media/me/more linux data
│      /dev/sdd3
│             btrfs  rw,nosuid,nodev,relatime,space_cache=v2,subvolid=5,subvol=/
├─/run/media/me/windows backups
│      /dev/sdd2
│             ntfs3  rw,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8
├─/home
│      /dev/nvme0n1p2[/@home]
│             btrfs  rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=280,subvol=/@home
├─/var/cache
│      /dev/nvme0n1p2[/@cache]
│             btrfs  rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=258,subvol=/@cache
├─/var/log
│      /dev/nvme0n1p2[/@log]
│             btrfs  rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=259,subvol=/@log
└─/boot/efi
       /dev/nvme0n1p1
              vfat   rw,relatime,fmask=0137,dmask=0027,codepage=437,iocharset=ascii,shortname=mixed,utf8,error

2nd command:

ID 256 gen 9314 top level 5 path timeshift-btrfs/snapshots/2025-05-14_23-25-15/@
ID 258 gen 9722 top level 5 path @cache
ID 259 gen 10025 top level 5 path @log
ID 260 gen 2051 top level 256 path timeshift-btrfs/snapshots/2025-05-14_23-25-15/@/var/lib/portables
ID 261 gen 2051 top level 256 path timeshift-btrfs/snapshots/2025-05-14_23-25-15/@/var/lib/machines
ID 264 gen 8250 top level 5 path timeshift-btrfs/snapshots/2025-05-09_16-45-00/@
ID 265 gen 2040 top level 5 path timeshift-btrfs/snapshots/2025-05-09_16-45-00/@home
ID 266 gen 8250 top level 5 path timeshift-btrfs/snapshots/2025-05-10_04-35-14/@
ID 267 gen 2040 top level 5 path timeshift-btrfs/snapshots/2025-05-10_04-35-14/@home
ID 268 gen 9012 top level 5 path timeshift-btrfs/snapshots/2025-05-12_05-46-50/@
ID 269 gen 9066 top level 5 path timeshift-btrfs/snapshots/2025-05-12_05-46-50/@home
ID 270 gen 9012 top level 5 path timeshift-btrfs/snapshots/2025-05-14_17-40-43/@
ID 271 gen 9066 top level 5 path timeshift-btrfs/snapshots/2025-05-14_17-40-43/@home
ID 272 gen 9012 top level 5 path timeshift-btrfs/snapshots/2025-05-14_19-00-00/@
ID 273 gen 9066 top level 5 path timeshift-btrfs/snapshots/2025-05-14_19-00-00/@home
ID 276 gen 10025 top level 5 path timeshift-btrfs/snapshots/2025-05-14_23-22-41/@
ID 277 gen 9186 top level 5 path timeshift-btrfs/snapshots/2025-05-14_23-22-41/@home
ID 280 gen 10025 top level 5 path @home
ID 281 gen 9257 top level 5 path @

Unless you were booted off a snapshot when you ran this command, this is a problem.

When you boot off a timeshift snapshot, you need to be careful not to do anything except restore the snapshot and reboot.

You should be especially careful not to do a system update or install/remove any packages. If you do that, you can end up in the situation you are in right now where your system is no longer booting off the root subvolume, but a snapshot.

It is worth noting that Snapper snapshots don’t have this issue because they are read-only.

all i did was boot into the snapshot via grub menu, then restored the same snapshot i was booted into, and restarted, no updates or anything, my system isnt set up to do that automatically, everything i did i wrote down in the original post

the whole booting into a snapshot to restore it seems quite volatile, and i saw some stuff about not being able to boot into read only snapshots but snapper has grub-btrfs support so that confuses me. anyways if i can fix it from here i will try

We provide an overlay so you can boot into read-only snapshots.

ok, after i fix this i think ill switch to snapper, i found this post that seems to be in a similar vein to what i have, editing the grub.cfg file seems to be the next step

followed the article and it bricked my system. didnt work, although im restoring now and i just caught something, should this be @ or am i just restoring a snapshot to a snapshot

ok i think ive actually fixed it now, this is what my findmnt command says now

TARGET  SOURCE            FSTYPE OPTIONS
/       /dev/nvme0n1p2[/@]
│                         btrfs  rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=284,subv
├─/run/media/me/more linux data
│       /dev/sdd3         btrfs  rw,nosuid,nodev,relatime,space_cache=v2,subvolid=5,subvol=/
├─/run/media/me/windows backups
│       /dev/sdd2         ntfs3  rw,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8
├─/home /dev/nvme0n1p2[/@home]
│                         btrfs  rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=283,subv
├─/var/cache
│       /dev/nvme0n1p2[/@cache]
│                         btrfs  rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=258,subv
├─/var/log
│       /dev/nvme0n1p2[/@log]
│                         btrfs  rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=259,subv
└─/boot/efi
        /dev/nvme0n1p1    vfat   rw,relatime,fmask=0137,dmask=0027,codepage=437,iocharset=ascii,shortname=mixe

it doesn’t say snapshot anymore, all i did was boot into my latest snapshot backup but i didnt restore the same one i restored a seperate untouched earlier one from the previous day, and i made sure to close all applications this time as well just to rule out any error, and i think its actually worked

That looks better

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.