GRUB x Timeshift Issue

No newly created timeshift snapshots are showing in GRUB ---> Garuda Linux Snapshots. Automatic snapshots and snapshots that are manually created with "doas timeshift --create && doas update-grub" both have the same outcome. In fact, manually running it outputs this:

╭─ Garuda Linux at jordan in ⌁
╰─λ snapshot #"snapshot" is an alias for "doas timeshift --create && doas update-grub"
Password:
Using system disk as snapshot device for creating snapshots in BTRFS mode

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

Creating new backup...(BTRFS)
Saving to device: /dev/dm-0, mounted at path: /run/timeshift/backup
Created directory: /run/timeshift/backup/timeshift-btrfs/snapshots/2021-03-04_15-14-30
Created subvolume snapshot: /run/timeshift/backup/timeshift-btrfs/snapshots/2021-03-04_15-14-30/@
Created subvolume snapshot: /run/timeshift/backup/timeshift-btrfs/snapshots/2021-03-04_15-14-30/@home
Created control file: /run/timeshift/backup/timeshift-btrfs/snapshots/2021-03-04_15-14-30/info.json
BTRFS Snapshot saved successfully (0s)
Tagged snapshot '2021-03-04_15-14-30': ondemand
------------------------------------------------------------------------------
Password:
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda/theme.txt
Found linux image: /boot/vmlinuz-linux-tkg-bmq
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-tkg-bmq.img
Found fallback initrd image(s) in /boot: initramfs-linux-tkg-bmq-fallback.img
Found Garuda Linux on /dev/mapper/luks-c6f2f205-28a7-466d-8260-80a97c16d975
Detecting snapshots ...
Info: Separate boot partition not detected
Found snapshot: 2021-03-04 15:14:30 | timeshift-btrfs/snapshots/2021-03-04_15-14-30/@
Found snapshot: 2021-03-04 14:12:54 | timeshift-btrfs/snapshots/2021-03-04_14-12-54/@
Found snapshot: 2021-03-04 13:22:44 | timeshift-btrfs/snapshots/2021-03-04_13-22-44/@
Found snapshot: 2021-03-04 12:47:16 | timeshift-btrfs/snapshots/2021-03-04_12-47-16/@
Found snapshot: 2021-03-04 12:33:32 | timeshift-btrfs/snapshots/2021-03-04_12-33-32/@
Found snapshot: 2021-03-03 18:51:59 | timeshift-btrfs/snapshots/2021-03-03_18-51-59/@
Found snapshot: 2021-03-03 14:08:55 | timeshift-btrfs/snapshots/2021-03-03_14-08-55/@
Found snapshot: 2021-03-02 20:01:52 | timeshift-btrfs/snapshots/2021-03-02_20-01-52/@
Found snapshot: 2021-03-01 22:12:01 | timeshift-btrfs/snapshots/2021-03-01_22-12-01/@
Found 9 snapshot(s)
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

It seems to be updating but the GRUB menu that I choose snapshots to boot into just can't access the new ones? My GRUB menu is actually way out of sync, not recognizing the last 12 snapshots that timeshift shows in the GUI(All 12 are since march 4th, 2021 at 02:51 UTC).

output of 'journalctl --since "2 days ago" -p "emerg".."crit"' located here

output of 'inxi -Fxxxza' located here

output of 'pacman -Qe' located here (297 packages)

You say your grub menu is out of sync.
That could be due to it booting configuration files from a timeshift snapshot instead of your actual system(if you've restored any snapshots in the past)

Refer to my post here:
https://forum.garudalinux.org/t/deletion-of-timeshift-snapshots-caused-havoc/4351/32

3 Likes

Forgive my noobness, I just read the linked post and that sounds like exactly my issue. I can't figure out how to edit the grub entry though. I looked in /boot/grub/grub.cfg(nothing in the file at all), /boot/grub/grub-btrfs.cfg(no instances of "/@/timeshift/btrfs/snapshots/" only "/timeshift-btrfs/snapshots/"), and /boot/grub/grubenv(only see a bunch of # in that file).

@r3st0ck3r In the grub boot menu, hit "e" for edit on the "Garuda Linux" boot entry
It should pull up an edit menu within grub itself.
When you've completed the edits, hit F10 to boot

Also, it's not really noobness, this problem is a pretty bad one. It took me a good 2 hours to figure out

Let me know what happens! My issue may not exactly resemble your current issue

1 Like

I went in and took a picture. Knowing how important the grub is, I don't want to edit out the wrong one. There looks to be two options:

linux          /timeshift-btrfs/snapshots/2021-03-03_18-51-59/@/boot/vmlinuz-linux-tkg-bmq root=UUID=fc9f75cb-9a53-4b16-b51a-0f9799b895ed rw root flags=subvol=timeshift-btrfs/snapshots/2021-03-03_18-51-59/@

Should I edit out the first "/timeshift-btrfs/snapshots/2021-03-03_18-51-59" up to the forward slash before the @ or should I edit the one after the "subvol" flag leaving subvol=/@ or should I edit out both?

You want to edit out both! I said in my post to delete "all instances"

Let me know how it goes!
I think I am going to make an announcement thread explaining this issue pretty soon, so people can just search for the problem and find the solution

2 Likes

It booted up perfectly. Nothing looked out of the ordinary or like it took longer than normal. Something that I do think may be beneficial to post for everyone to checkout:

This is my output of "update-grub":

╭─ Garuda Linux at jordan in ⌁
╰─λ doas update-grub
Password:
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda/theme.txt
Found linux image: /boot/vmlinuz-linux-tkg-bmq
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-tkg-bmq.img
Found fallback initrd image(s) in /boot: initramfs-linux-tkg-bmq-fallback.img
Found Garuda Linux on /dev/mapper/luks-c6f2f205-28a7-466d-8260-80a97c16d975
Detecting snapshots ...
Info: Separate boot partition not detected
Found snapshot: 2021-03-04 19:31:45 | timeshift-btrfs/snapshots/2021-03-04_19-31-45/@
Found snapshot: 2021-03-04 19:30:27 | timeshift-btrfs/snapshots/2021-03-04_19-30-27/@
Found snapshot: 2021-03-04 19:19:04 | timeshift-btrfs/snapshots/2021-03-04_19-19-04/@
Found snapshot: 2021-03-04 18:59:16 | timeshift-btrfs/snapshots/2021-03-04_18-59-16/@
Found snapshot: 2021-03-04 18:24:35 | timeshift-btrfs/snapshots/2021-03-04_18-24-35/@
Found snapshot: 2021-03-04 15:14:30 | timeshift-btrfs/snapshots/2021-03-04_15-14-30/@
Found snapshot: 2021-03-04 14:12:54 | timeshift-btrfs/snapshots/2021-03-04_14-12-54/@
Found snapshot: 2021-03-04 13:22:44 | timeshift-btrfs/snapshots/2021-03-04_13-22-44/@
Found snapshot: 2021-03-04 12:47:16 | timeshift-btrfs/snapshots/2021-03-04_12-47-16/@
Found snapshot: 2021-03-04 12:33:32 | timeshift-btrfs/snapshots/2021-03-04_12-33-32/@
Found snapshot: 2021-03-03 18:51:59 | timeshift-btrfs/snapshots/2021-03-03_18-51-59/@
Found 11 snapshot(s)
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

Everything seems to be good there but then this is my "yay -Syu --devel":

The output for this is much longer so I decided to attach it here.

A few concerns I have with that. It took FOREVER removing those last snapshots during the yay update(probably because it was so far behind). The second is all the Json-CRITICAL messages that I got. Those errors may or may not be because of what I decided to edit out. In this line:

linux          /timeshift-btrfs/snapshots/2021-03-03_18-51-59/@/boot/vmlinuz-linux-tkg-bmq root=UUID=fc9f75cb-9a53-4b16-b51a-0f9799b895ed rw root flags=subvol=timeshift-btrfs/snapshots/2021-03-03_18-51-59/@

I left the end as "rw root flags=subvol=/@" should that be "rw root [email protected]" instead? I tried doing it that way first and the boot up before my login screen looked off(it was grey with three dots). So I decided go back and leave it with the "/@".

I did a second "yay -Syu --devel" and got this output:

╭─ Garuda Linux at jordan in ⌁
╰─λ upd # upd is an alias for "yay -Syu --devel"
Password:
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community                                                           5.4 MiB  11.8 MiB/s 00:00 [-------------------------------------------------------] 100%
 multilib is up to date
 chaotic-aur is up to date
:: Starting full system upgrade...
:: Replace doas with community/opendoas? [Y/n] n
warning: gesture-manager-x-git: local (0.1-1) is newer than chaotic-aur (r9.ce6f7d0-1)
 there is nothing to do
:: Searching databases for updates...
:: Searching AUR for updates...
 -> gesture-manager-x-git: local (0.1-1) is newer than chaotic-aur (r9.ce6f7d0-1)
:: Checking development packages...
 there is nothing to do

Everything seems back to normal!

1 Like

Glad to see this fixed your issue!
I don't know exactly what those json issues were about, but they seem to have gone away.

Now that it's solved, could you mark the solution?
Also, I'll probably release the announcement about this issue tomorrow

2 Likes

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