Timeshift crash during setup after snapshot restore

good thought. Just tried it. Grub reinstalled successfully without error, but no dice with fixing Timeshift - still same segmentation fault as before. Right, really off to bed now! Cherrs.

New pit-stop here!
Have a good rest :smiley: and maybe tomorrow you could check your /etc/timeshift/timeshift.json
I saw here the structure:

Eg check if btrfs_mode Is true and the device uuid...

Thanks Filo. I just checked. Both UUID fields in that file were empty ("") and the btrfs_mode was "false". I changed those to as per below and re-ran timeshift-launcher. Timeshift seems to be ignoring the timeshift.json file as it still opened with the wizard, asking me to choose between rsync and btrfs. Clicking btrfs gave the same segmentation fault terminal error message as per my initial post.

{
"backup_device_uuid" : "68c70d59-7ec4-47a5-bc2d-451cdf643b2d",
"parent_device_uuid" : "68c70d59-7ec4-47a5-bc2d-451cdf643b2d",
"do_first_run" : "true",
"btrfs_mode" : "true",
"include_btrfs_home" : "false",
"stop_cron_emails" : "true",
"schedule_monthly" : "false",
"schedule_weekly" : "false",
"schedule_daily" : "false",
"schedule_hourly" : "false",
"schedule_boot" : "false",
"count_monthly" : "2",
"count_weekly" : "3",
"count_daily" : "5",
"count_hourly" : "6",
"count_boot" : "5",
"snapshot_size" : "0",
"snapshot_count" : "0",
"exclude" : [
],
"exclude-apps" : [
]
}

....and, timeshift --list still shows mode as rsync. Weird.....

/dev/sda2 is mounted at: /run/timeshift/backup, options: rw,relatime,compress=zstd:3,ssd,space_cache,autodefrag,subvolid=5,subvol=/

Device : /dev/sda2
UUID   : 68c70d59-7ec4-47a5-bc2d-451cdf643b2d
Path   : /run/timeshift/backup
Mode   : RSYNC
Status : No snapshots on this device
First snapshot requires: 0 B

No snapshots found

....and I just noticed that Timeshift has been happily filling up my laptop ssd drive in the background with (I imagine) rsync snapshots - my sda2 drive is almost full where it should only be around 25% full !!.....

I can report that this issue is resolved - YAY!!! The problem seems to have been that Timeshift was getting confused with all the previous timeshift snapshots made prior to my system restore. I don't know why - beats me. To resolve I wrote a new live bootable USB using the latest version of Garuda and booted it up. Then I fired up Dolphin and looked for the /timeshift and /timeshift-btrfs and deleted those directories entirely thereby removing all timeshift snapshots. This seemed to effectively reset the timeshift snapshot system because when I booted into the machine (not the live USB) and started timeshift, everything was back to normal - I could select "btrfs" as default snapshot type without causing a crash and now I'm back to happily creating Timeshift snapshots. Weird ay?

1 Like

Okay so I spoke to soon. I just tried to take a manual snapshot with Timeshift and got the following error. Does anyone understand what might be going on here?? It's obvious in the picture that I am indeed running a system that is based on @ subvolumes......

1 Like

What a pity!
Maybe you could try reverting to the old /etc/timeshift/timeshift.json...
I'd also update grub again...

Unfortunately I've already done those things to no effect, thanks for the thought Filo. I feel that the real problem is tied up with how the system restored from the Timeshift snapshot when all this trouble started, causing the "not supported" dialogue in the above image. Here's my fstab - can you spot anything that might be a problem; and how does this structure compare to yours if you've gone through a timeshift restore process?

$ cat /etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=20BB-B92C                            /boot/efi      vfat    umask=0077 0 2
UUID=68c70d59-7ec4-47a5-bc2d-451cdf643b2d /              btrfs   subvol=/timeshift-btrfs/snapshots/2021-06-17_10-22-22/@,defaults,noatime,space_cache,autodefrag,compress=zstd,ssd 0 1
UUID=68c70d59-7ec4-47a5-bc2d-451cdf643b2d /home          btrfs   subvol=/@home,defaults,noatime,space_cache,autodefrag,compress=zstd,ssd 0 2
UUID=68c70d59-7ec4-47a5-bc2d-451cdf643b2d /root          btrfs   subvol=/@root,defaults,noatime,space_cache,autodefrag,compress=zstd,ssd 0 2
UUID=68c70d59-7ec4-47a5-bc2d-451cdf643b2d /srv           btrfs   subvol=/@srv,defaults,noatime,space_cache,autodefrag,compress=zstd,ssd 0 2
UUID=68c70d59-7ec4-47a5-bc2d-451cdf643b2d /var/cache     btrfs   subvol=/@cache,defaults,noatime,space_cache,autodefrag,compress=zstd,ssd 0 2
UUID=68c70d59-7ec4-47a5-bc2d-451cdf643b2d /var/log       btrfs   subvol=/@log,defaults,noatime,space_cache,autodefrag,compress=zstd,ssd 0 2
UUID=68c70d59-7ec4-47a5-bc2d-451cdf643b2d /var/tmp       btrfs   subvol=/@tmp,defaults,noatime,space_cache,autodefrag,compress=zstd,ssd 0 2
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

....Aha - got it! Somehow my /etc/fstab file got screwed up when I Timeshift system restored (I certainly didn't alter it manually). The "/" entry in the fstab above, incorrectly has a timeshift snapshot mounting as /. The correct entry for / should "subvol=/@". My fstab now looks like:

$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=20BB-B92C                            /boot/efi      vfat    umask=0077 0 2
UUID=68c70d59-7ec4-47a5-bc2d-451cdf643b2d /              btrfs   subvol=/@,defaults,noatime,space_cache,autodefrag,compress=zstd,ssd 0 1
UUID=68c70d59-7ec4-47a5-bc2d-451cdf643b2d /home          btrfs   subvol=/@home,defaults,noatime,space_cache,autodefrag,compress=zstd,ssd 0 2
UUID=68c70d59-7ec4-47a5-bc2d-451cdf643b2d /root          btrfs   subvol=/@root,defaults,noatime,space_cache,autodefrag,compress=zstd,ssd 0 2
UUID=68c70d59-7ec4-47a5-bc2d-451cdf643b2d /srv           btrfs   subvol=/@srv,defaults,noatime,space_cache,autodefrag,compress=zstd,ssd 0 2
UUID=68c70d59-7ec4-47a5-bc2d-451cdf643b2d /var/cache     btrfs   subvol=/@cache,defaults,noatime,space_cache,autodefrag,compress=zstd,ssd 0 2
UUID=68c70d59-7ec4-47a5-bc2d-451cdf643b2d /var/log       btrfs   subvol=/@log,defaults,noatime,space_cache,autodefrag,compress=zstd,ssd 0 2
UUID=68c70d59-7ec4-47a5-bc2d-451cdf643b2d /var/tmp       btrfs   subvol=/@tmp,defaults,noatime,space_cache,autodefrag,compress=zstd,ssd 0 2
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

...FYI this is my btrfs subvolume structure, including one snapshot (because that now works :smiley: )......

$ sudo btrfs subvolume list -a /
[sudo] password for rob:
ID 257 gen 66183 top level 5 path <FS_TREE>/@home
ID 258 gen 66166 top level 5 path <FS_TREE>/@root
ID 259 gen 64930 top level 5 path <FS_TREE>/@srv
ID 260 gen 66182 top level 5 path <FS_TREE>/@cache
ID 261 gen 66183 top level 5 path <FS_TREE>/@log
ID 262 gen 66162 top level 5 path <FS_TREE>/@tmp
ID 858 gen 66181 top level 5 path <FS_TREE>/@
ID 859 gen 66103 top level 5 path <FS_TREE>/timeshift-btrfs/snapshots/2021-08-24_13-48-20/@SGS GS

So now everything is back in balance in the world I can now mark this solved, which I will now do. Thanks for your support and encouragement to find solution everyone, I now understand a lot more about btrfs and how my Garuda Linux is set up for Timeshift :smiley: .

2 Likes

Great you got that bugger whacked!
:+1:
So what’s your next feat of daring do? inquiring minds want to know.
:wink:

1 Like

An Italian saying literally translates to "who endures wins".
There is no real translation, I think.
I liked "Slow and steady wins the race."
:wink:

2 Likes

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