Timeshift Snapshots disappeared

Hey there, so I've been having a few issues likely caused by me so I intended to restore an old snapshot. I booted into it through grub and accidentally deleted that snapshot. I then had to force restart my laptop. The other snapshots were still appearing in grub but when opening timeshift once booted, whether booted into a snapshot or the current system, there are 0 snapshots available. However, I can create a new snapshot which does appear. So how does grub see it but the timeshift program doesn't? Any way to fix this? Thanks.

inxi -Faz
System:    Kernel: 5.14.3-2-cacule-llvm x86_64 bits: 64 compiler: clang v: 12.0.0 
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-cacule-llvm 
root=UUID=d705e742-9d27-4001-909a-c8b33abd69ac rw [email protected] quiet splash 
rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 
resume=UUID=d2c6afb2-b903-4bf2-9889-2eb2819f64fa loglevel=3 
Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM 
Distro: Garuda Linux base: Arch Linux 
Machine:   Type: Laptop System: ASUSTeK product: X510UA v: 1.0 serial: <filter> 
Mobo: ASUSTeK model: X510UA v: 1.0 serial: <filter> UEFI: American Megatrends v: X510UA.312 
date: 04/29/2020 
Battery:   ID-1: BAT0 charge: 6.6 Wh (23.1%) condition: 28.6/42.1 Wh (67.9%) volts: 11.5 min: 11.5 
model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: Charging cycles: 401 
CPU:       Info: Dual Core model: Intel Core i7-7500U bits: 64 type: MT MCP arch: Amber/Kaby Lake 
note: check family: 6 model-id: 8E (142) stepping: 9 microcode: EA cache: L2: 4 MiB 
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 23220 
Speed: 3477 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 3477 2: 3475 3: 3493 4: 3478 
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
Type: meltdown mitigation: PTI 
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
Type: spectre_v2 
mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling 
Type: srbds mitigation: Microcode 
Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel HD Graphics 620 vendor: ASUSTeK driver: i915 v: kernel bus-ID: 00:02.0 
chip-ID: 8086:5916 class-ID: 0300 
Device-2: IMC Networks VGA UVC WebCam type: USB driver: uvcvideo bus-ID: 1-6:2 
chip-ID: 13d3:5a07 class-ID: 0e02 serial: <filter> 
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: intel 
unloaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1 
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9") 
Monitor-1: eDP1 res: 1920x1080 hz: 60 dpi: 143 size: 340x190mm (13.4x7.5") diag: 389mm (15.3") 
OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 21.2.1 direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
alternate: snd_soc_skl bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403 
Sound Server-1: ALSA v: k5.14.3-2-cacule-llvm running: yes 
Sound Server-2: JACK v: 1.9.19 running: no 
Sound Server-3: PulseAudio v: 15.0 running: no 
Sound Server-4: PipeWire v: 0.3.35 running: yes 
Network:   Device-1: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: f040 bus-ID: 02:00.0 
chip-ID: 8086:24fd class-ID: 0280 
IF: wlp2s0 state: up mac: <filter> 
Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-8:3 
chip-ID: 8087:0a2b class-ID: e001 
Report: bt-adapter ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: 
hardware: no software: yes address: <filter> 
Drives:    Local Storage: total: 704.24 GiB used: 75.91 GiB (10.8%) 
SMART Message: Unable to run smartctl. Root privileges required. 
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB 
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q 
scheme: GPT 
ID-2: /dev/sdb maj-min: 8:16 vendor: Micron model: 1100 MTFDDAV256TBN size: 238.47 GiB 
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: A020 
scheme: GPT 
Partition: ID-1: / raw-size: 448.43 GiB size: 448.43 GiB (100.00%) used: 75.91 GiB (16.9%) fs: btrfs 
dev: /dev/sda2 maj-min: 8:2 
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%) used: 563 KiB (0.2%) fs: vfat 
dev: /dev/sda1 maj-min: 8:1 
ID-3: /home raw-size: 448.43 GiB size: 448.43 GiB (100.00%) used: 75.91 GiB (16.9%) fs: btrfs 
dev: /dev/sda2 maj-min: 8:2 
ID-4: /var/log raw-size: 448.43 GiB size: 448.43 GiB (100.00%) used: 75.91 GiB (16.9%) 
fs: btrfs dev: /dev/sda2 maj-min: 8:2 
ID-5: /var/tmp raw-size: 448.43 GiB size: 448.43 GiB (100.00%) used: 75.91 GiB (16.9%) 
fs: btrfs dev: /dev/sda2 maj-min: 8:2 
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) 
ID-1: swap-1 type: partition size: 17.07 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3 
maj-min: 8:3 
ID-2: swap-2 type: zram size: 15.52 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0 
Sensors:   System Temperatures: cpu: 80.0 C mobo: N/A 
Fan Speeds (RPM): cpu: 4700 
Info:      Processes: 242 Uptime: 15m wakeups: 2 Memory: 15.52 GiB used: 3.12 GiB (20.1%) Init: systemd 
v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1393 lib: 340 
Shell: fish v: 3.3.1 default: Bash v: 5.1.8 running-in: konsole inxi: 3.3.06

Can we see the output of

sudo btrfs subvolume list /
ID 257 gen 9545 top level 5 path @home
ID 258 gen 9545 top level 5 path @root
ID 259 gen 9319 top level 5 path @srv
ID 260 gen 9545 top level 5 path @cache
ID 261 gen 9545 top level 5 path @log
ID 262 gen 9542 top level 5 path @tmp
ID 479 gen 9381 top level 5 path timeshift-btrfs/snapshots/2021-08-30_21-17-04/@
ID 528 gen 9535 top level 5 path timeshift-btrfs/snapshots/2021-08-31_00-44-20/@
ID 532 gen 9381 top level 5 path timeshift-btrfs/snapshots/2021-08-31_00-49-09/@
ID 535 gen 9545 top level 5 path @
ID 538 gen 9538 top level 5 path timeshift-btrfs/snapshots/2021-09-01_13-00-02/@
ID 556 gen 9311 top level 5 path timeshift-btrfs/snapshots/2021-09-06_14-42-05/@
ID 557 gen 9326 top level 5 path timeshift-btrfs/snapshots/2021-09-06_14-47-52/@
ID 558 gen 9380 top level 5 path timeshift-btrfs/snapshots/2021-09-14_23-00-02/@
ID 560 gen 9386 top level 5 path timeshift-btrfs/snapshots/2021-09-14_23-02-59/@
ID 563 gen 9396 top level 5 path timeshift-btrfs/snapshots/2021-09-14_23-06-37/@
ID 565 gen 9482 top level 5 path timeshift-btrfs/snapshots/2021-09-14_23-34-56/@
ID 566 gen 9544 top level 5 path timeshift-btrfs/snapshots/2021-09-15_21-39-09/@

Tried running sudo timeshift --check but no luck

sudo timeshift --check
Using system disk as snapshot device for creating snapshots in BTRFS mode

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

E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.819: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.820: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.821: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.822: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.822: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.823: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.823: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.824: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.825: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.825: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.826: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
Daily snapshots are enabled
Last daily snapshot not found
Tagged snapshot '2021-09-15_21-39-09': daily
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.945: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.946: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.946: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.947: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.948: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.949: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.949: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.950: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.951: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.952: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:28.952: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
------------------------------------------------------------------------------
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.057: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.058: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.058: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.059: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.060: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.060: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.061: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.062: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.062: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.063: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.064: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.173: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.176: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.179: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.183: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.185: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.187: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.190: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.194: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.196: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.199: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.203: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.326: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.329: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.332: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.335: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.338: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.341: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.344: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.348: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.353: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.356: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
E: JSON data must be UTF-8 encoded

(process:19542): Json-CRITICAL **: 22:26:29.360: json_node_get_object: assertion 'JSON_NODE_IS_VALID (node)' failed
Removing snapshots (incomplete):
------------------------------------------------------------------------------
Removing snapshot: 2021-08-30_21-17-04

The snapshots are there so maybe the timeshift metadata is corrupt?

2 Likes

No clue, it sees the snapshots there and in grub but not the timeshift program. I have no clue how to fix this tbh

Maybe you could try this one

Basically, if you can, you should create a new snapshot and copy the newly created info.json file into the directory of the other snapshot you want to restore.
If you can't create the snapshot, this file could be created manually.

2 Likes

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