Hello everyone; I have installed Endeavour OS on this machine:
xxxxxxxxxxx@xxxxxxxxxxx-80eu ~]$ fastfetch
./o. XXXXXXXXXXXXXXXXXXXXXX
./sssso- ------------------------
`:osssssss+- OS: EndeavourOS x86_64
`:+sssssssssso/. Host: 80EU (Lenovo B50-70)
`-/ossssssssssssso/. Kernel: Linux 6.12.10-arch1-1
`-/+sssssssssssssssso+:` Uptime: 13 mins
`-:/+sssssssssssssssssso+/. Packages: 1105 (pacman)
`.://osssssssssssssssssssso++- Shell: bash 5.2.37
.://+ssssssssssssssssssssssso++: Display (SDC3652): 1366x768 @ 60 Hz in 16" [Built-in]
.:///ossssssssssssssssssssssssso++: DE: KDE Plasma 6.2.5
`:////ssssssssssssssssssssssssssso+++. WM: KWin (Wayland)
`-////+ssssssssssssssssssssssssssso++++- WM Theme: Breeze
`..-+oosssssssssssssssssssssssso+++++/` Theme: Breeze (Dark) [Qt], Breeze-Dark [GTK2], Breeze [GTK3]
./++++++++++++++++++++++++++++++/:. Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
`:::::::::::::::::::::::::------`` Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
Cursor: breeze (24px)
Terminal: konsole 24.12.1
CPU: Intel(R) Core(TM) i3-4030U (4) @ 1.80 GHz
GPU: Intel Haswell-ULT Integrated Graphics Controller @ 1.00 GHz ]
Memory: 1.52 GiB / 11.60 GiB (13%)
Swap: Disabled
Disk (/): 7.75 GiB / 475.93 GiB (2%) - btrfs
Local IP (wlan0): xxxxxxxxxxxxxxxxxxxxxx
Battery (PABAS0241231): 100% [AC Connected]
Locale: it_IT.UTF-8
My purpose is to have the system create snapshots from which to boot ,in case of a crash, via refind. I will tell you what I did. I installed refind despite having only one OS and modified refind.conf by inserting the following block:
menuentry "Endeavour OS" {
icon /EFI/refind/icons/os_endeavouros.png
volume "VOLFS"
loader @/boot/vmlinuz-linux
initrd @/boot/initramfs-linux.img
options "root=PARTUUID=93622fa8-49e9-4ccf-8a24-0a85eba0fc5b rw rootflags=subvol=@ quiet splash udev.log_priority=3"
submenuentry "Boot using fallback initramfs" {
initrd @/boot/initramfs-linux-fallback.img
}
submenuentry "Boot to terminal" {
add_options "systemd.unit=multi-user.target"
}
}
the entry “root” is justified because:
sudo blkid
[sudo] password di xxxxxxxxx:
/dev/sda2: LABEL="VOLFS" UUID="ce5492b6-2a24-49b8-8f6a-8befe130db4c" UUID_SUB="a8c91a7a-cd0e-420b-a6b8-3dfeb7cb18f5" BLOCK_SIZE="4096" TYPE="btrfs" PARTLABEL="endeavouros" PARTUUID="93622fa8-49e9-4ccf-8a24-0a85eba0fc5b"
Having done that ,I got an extra entry in the refind boot menu, which ,if selected, always starts Endeavour with the previous “options”; at this point I install refind-btrfs . Here the problems begin: to configure it I modified /etc/refind-btrfs.conf. In particular: in the block
# esp_uuid = <string>
## Explicitly defined ESP's Part-UUID which can be used in case the ESP itself
## cannot be automatically located on the system (for whatever reason).
## This option is, by default, defined as an empty UUID which means that it is
## ignored.
esp_uuid = "35c14e60-4dfb-404d-97ee-5e7ffa5fe574"
I entered esp_uuid which is the Part-UUID of ESP, which is basically /dev/sda1; as for the “[[snapshot-search]]” part then, after many attempts , I entered
[[snapshot-search]]
## directory = "/.snapshots"
directory = "/mnt/timeshift/timeshift-btrfs/snapshots"
is_nested = false
max_depth = 4
“directory” is justified in that the snapshots are ( by default ) in /timeshift-btrfs/snapshots , which however refind-btrfs does not see. So I mounted “/” to “/mnt/timeshift” as seen from fstab which I attach:
UUID=BD11-2FB6 /boot/efi vfat fmask=0137,dmask=0027 0 2
UUID=ce5492b6-2a24-49b8-8f6a-8befe130db4c / btrfs subvol=/@,noatime,compress=zstd 0 0
UUID=ce5492b6-2a24-49b8-8f6a-8befe130db4c /home btrfs subvol=/@home,noatime,compress=zstd 0 0
UUID=ce5492b6-2a24-49b8-8f6a-8befe130db4c /var/cache btrfs subvol=/@cache,noatime,compress=zstd 0 0
UUID=ce5492b6-2a24-49b8-8f6a-8befe130db4c /var/log btrfs subvol=/@log,noatime,compress=zstd 0 0
UUID=ce5492b6-2a24-49b8-8f6a-8befe130db4c /mnt/timeshift btrfs subvol=/,rw 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
At this point refind-btrfs sees the folder /mnt/timeshift/timeshift-btrfs/snapshots , and runs without error to the end, creating the snapshots. As expected, at boot refind it presents a new entry for some snapshots ,from which to boot, prior to the last update.
By booting from the last of these snapshots, however, the system is not stable: once it starts, it fails to run timeshift properly, and when you try to update the system, pacman -Syu fails ( because precisely timeshift, which is called, crashes).
I report the tree structure of the partition “/”
live@live:/media/live/VOLFS$ ls -la
totale 16
drwxr-xr-x 1 root root 62 19 gen 14.55 .
drwxr-x---+ 3 root root 60 21 gen 14.35 ..
drwxr-xr-x 1 root root 122 19 gen 08.50 @
drwxr-xr-x 1 root root 118 19 gen 08.58 @cache
drwxr-xr-x 1 root root 18 19 gen 08.59 @home
drwxr-xr-x 1 root root 358 20 gen 18.11 @log
drwxr-xr-x 1 root root 210 20 gen 17.35 timeshift-btrfs
live@live:/media/live/VOLFS$ cd timeshift-btrfs
live@live:/media/live/VOLFS/timeshift-btrfs$ ls -la
totale 16
drwxr-xr-x 1 root root 210 20 gen 17.35 .
drwxr-xr-x 1 root root 62 19 gen 14.55 ..
drwxr-xr-x 1 root root 114 20 gen 17.35 snapshots
drwxr-xr-x 1 root root 0 20 gen 17.35 snapshots-boot
drwxr-xr-x 1 root root 0 20 gen 17.35 snapshots-daily
drwxr-xr-x 1 root root 0 20 gen 17.35 snapshots-hourly
drwxr-xr-x 1 root root 0 20 gen 17.35 snapshots-monthly
drwxr-xr-x 1 root root 152 20 gen 17.35 snapshots-ondemand
drwxr-xr-x 1 root root 0 20 gen 17.35 snapshots-weekly
cd snapshots
live@live:/media/live/VOLFS/timeshift-btrfs/snapshots$ ls -la
totale 0
drwxr-xr-x 1 root root 114 20 gen 17.35 .
drwxr-xr-x 1 root root 210 20 gen 17.35 ..
drwxr-xr-x 1 root root 20 19 gen 18.40 2025-01-19_19-40-42
drwxr-xr-x 1 root root 20 19 gen 18.44 2025-01-19_19-44-13
drwxr-xr-x 1 root root 20 20 gen 17.35 2025-01-20_18-35-28
Here is the result of running refind-btrfs
sudo refind-btrfs
Initializing the block devices using lsblk.
Initializing the physical partition table for device '/dev/sda' using lsblk.
Analyzing the 'refind-btrfs.conf' file.
Initializing the live partition table for device '/dev/sda' using findmnt.
Initializing the physical partition table for device '/dev/sr0' using lsblk.
Initializing the live partition table for device '/dev/sr0' using findmnt.
Found the ESP mounted at '/boot/efi' on '/dev/sda1'.
Found the root partition on '/dev/sda2'.
Searching for snapshots of the '@' subvolume in the '/mnt/timeshift/timeshift-btrfs/snapshots' directory.
Found subvolume '@' mounted as the root partition.
Found 3 snapshots of the '@' subvolume.
Searching for the 'refind.conf' file on '/dev/sda1'.
Found 1 boot stanza matched with the root partition.
Initializing the static partition table for subvolume 'timeshift-btrfs/snapshots/2025-01-24_16-31-02/@' from its fstab file.
Initializing the static partition table for subvolume 'timeshift-btrfs/snapshots/2025-01-24_16-30-32/@' from its fstab file.
Initializing the static partition table for subvolume 'timeshift-btrfs/snapshots/2025-01-23_16-17-39/@' from its fstab file.
Found 3 snapshots for addition.
Found 3 snapshots for removal.
Modifying the '/mnt/timeshift/timeshift-btrfs/snapshots/2025-01-24_16-31-02/@/etc/fstab' file.
Modifying the '/mnt/timeshift/timeshift-btrfs/snapshots/2025-01-24_16-30-32/@/etc/fstab' file.
Modifying the '/mnt/timeshift/timeshift-btrfs/snapshots/2025-01-23_16-17-39/@/etc/fstab' file.
WARNING: The '/mnt/timeshift/timeshift-btrfs/snapshots/2025-01-20_18-35-28/@' directory is not a subvolume.
WARNING: The '/mnt/timeshift/timeshift-btrfs/snapshots/2025-01-19_19-40-42/@' directory is not a subvolume.
WARNING: The '/mnt/timeshift/timeshift-btrfs/snapshots/2025-01-19_19-44-13/@' directory is not a subvolume.
Writing to the 'btrfs-snapshot-stanzas/volfs_vmlinuz-linux.conf' file.
and here is the timeshift msg when run from the terminal (when the system starts from a snapshot):
[xxxxxxxx@xxxxxxxx-80eu ~]$ sudo timeshift --list
[sudo] password di francesco:
Mounted '/dev/sda2' at '/run/timeshift/1661/backup'
Errore di segmentazione
Does anyone have an idea how to modify the procedure ?