Snapper Boot Enabled or not?

Currently Snapper boot enabled isn’t ticked.
I have read that when enabled this will take a snapshot of your last successful boot.
That to me seems to be something that is best enabled?
Am I right in that please?

Preformatted text

 System:
Kernel: 6.9.3-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=4f8e2cdc-79a4-4506-a9c3-1aaf2113722e rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A info: frameworks v: 6.2.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: Z790 AORUS XTREME X v: -CF
serial: <superuser required>
Mobo: Gigabyte model: Z790 AORUS XTREME X v: x.x
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: F3 date: 09/12/2023
CPU:
Info: model: Intel Core i9-14900K bits: 64 type: MST AMCP arch: Raptor Lake
gen: core 14 level: v3 note: check built: 2022+ process: Intel 7 (10nm)
family: 6 model-id: 0xB7 (183) stepping: 1 microcode: 0x123
Topology: cpus: 1x cores: 24 mt: 8 tpc: 2 st: 16 threads: 32 smt: enabled
cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32 KiB, 16x64 KiB
L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
Speed (MHz): avg: 3001 high: 5425 min/max: 800/5700:6000:4400 scaling:
driver: intel_pstate governor: powersave cores: 1: 4600 2: 800 3: 5425
4: 800 5: 4620 6: 800 7: 4229 8: 3394 9: 4743 10: 800 11: 4743 12: 800
13: 3488 14: 800 15: 2991 16: 4135 17: 4401 18: 1647 19: 4406 20: 4401
21: 4427 22: 4396 23: 4411 24: 4407 25: 800 26: 3002 27: 1382 28: 800
29: 800 30: 4389 31: 4412 32: 800 bogomips: 203980
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Raptor Lake-S GT1 [UHD Graphics 770] vendor: Gigabyte
driver: i915 v: kernel alternate: xe arch: Gen-13 process: Intel 7 (10nm)
built: 2022+ ports: active: none empty: DP-4,DP-5,HDMI-A-3 bus-ID: 00:02.0
chip-ID: 8086:a780 class-ID: 0300
Device-2: NVIDIA AD102 [GeForce RTX 4090] vendor: ASUSTeK driver: nvidia
v: 550.78 alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-04) arch: Lovelace code: AD1xx
process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16
ports: active: none off: DP-1,DP-3,HDMI-A-2 empty: DP-2,HDMI-A-1
bus-ID: 01:00.0 chip-ID: 10de:2684 class-ID: 0300
Device-3: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.4.3.1:17
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0
compositor: kwin_x11 driver: X: loaded: modesetting,nvidia unloaded: nouveau
alternate: fbdev,intel,nv,vesa dri: iris gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 5360x2080 s-dpi: 94 s-size: 1447x561mm (56.97x22.09")
s-diag: 1552mm (61.1")
Monitor-1: DP-1 mapped: DP-0 note: disabled pos: middle-l
model: ASUS VG249Q1A serial: <filter> built: 2023 res: 1920x1080 hz: 144
dpi: 94 gamma: 1.2 size: 521x293mm (20.51x11.54") diag: 598mm (23.5")
ratio: 16:9 modes: max: 1920x1080 min: 640x480
Monitor-2: DP-3 mapped: DP-4 note: disabled pos: primary,top-right
model: Gigabyte M34WQ serial: <filter> built: 2022 res: 3440x1440 dpi: 109
gamma: 1.2 size: 800x340mm (31.5x13.39") diag: 867mm (34.1") modes:
max: 3440x1440 min: 640x480
Monitor-3: HDMI-A-2 mapped: HDMI-1 note: disabled pos: bottom-l
model: HDMI serial: <filter> built: 2019 res: 1920x720 hz: 60 dpi: 133
gamma: 1.2 size: 368x207mm (14.49x8.15") diag: 313mm (12.3") modes:
max: 1920x720 min: 640x480
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.78
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
memory: 23.43 GiB
API: Vulkan v: 1.3.279 layers: 14 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 4090 driver: nvidia v: 550.78 device-ID: 10de:2684
surfaces: xcb,xlib device: 1 type: integrated-gpu
name: Intel Graphics (RPL-S) driver: mesa intel v: 24.1.0-arch1.1
device-ID: 8086:a780 surfaces: xcb,xlib device: 2 type: cpu name: llvmpipe
(LLVM 17.0.6 256 bits) driver: mesa llvmpipe v: 24.1.0-arch1.1 (LLVM
17.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: Intel Raptor Lake High Definition Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
bus-ID: 00:1f.3 chip-ID: 8086:7a50 class-ID: 0403
Device-2: NVIDIA AD102 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:22ba class-ID: 0403
Device-3: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.4.3.1:17
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
Device-4: Thesycon System & Consulting GmbH SMSL USB AUDIO
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 480 Mb/s
lanes: 1 mode: 2.0 bus-ID: 1-1.4.4.4:19 chip-ID: 152a:85dd class-ID: 0300
Device-5: Giga-Byte ESSential HEX USB DAC
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 480 Mb/s
lanes: 1 mode: 2.0 bus-ID: 1-10:7 chip-ID: 0414:a013 class-ID: 0300
API: ALSA v: k6.9.3-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.0.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Aquantia AQtion AQC107 NBase-T/IEEE 802.3an Ethernet [Atlantic
10G] vendor: Gigabyte driver: atlantic v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 2 link-max: lanes: 4 port: N/A bus-ID: 06:00.0
chip-ID: 1d6a:07b1 class-ID: 0200 temp: 44.1 C
IF: enp6s0 state: down mac: <filter>
Device-2: Intel Ethernet I226-V vendor: Gigabyte driver: igc v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 07:00.0
chip-ID: 8086:125c class-ID: 0200
IF: enp7s0 state: up speed: 2500 Mbps duplex: full mac: <filter>
Device-3: Qualcomm WCN785x Wi-Fi 7 320MHz 2x2 [FastConnect 7800]
vendor: Foxconn driver: ath12k_pci v: N/A modules: ath12k pcie: gen: 3
speed: 8 GT/s lanes: 1 link-max: lanes: 2 bus-ID: 08:00.0
chip-ID: 17cb:1107 class-ID: 0280
IF: wlp8s0 state: down mac: <filter>
Device-4: Microsoft Xbox Wireless Adapter for Windows driver: N/A
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.2:4
chip-ID: 045e:02fe class-ID: 0000 serial: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Foxconn / Hon Hai driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:14 chip-ID: 0489:e10d
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 17.28 TiB used: 88.23 GiB (0.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO 4TB
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 0B2QJXG7 temp: 43.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Western Digital
model: WD BLACK SN850X 4000GB size: 3.64 TiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 624331WD temp: 54.9 C scheme: GPT
ID-3: /dev/nvme2n1 maj-min: 259:5 vendor: Western Digital
model: WD BLACK SN850X 4000GB size: 3.64 TiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 624331WD temp: 52.9 C scheme: GPT
ID-4: /dev/nvme3n1 maj-min: 259:4 vendor: Western Digital
model: WD BLACK SN850X 4000GB size: 3.64 TiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 624331WD temp: 59.9 C scheme: GPT
ID-5: /dev/sda maj-min: 8:0 vendor: Seagate model: Expansion Desk
size: 2.73 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: 9401 scheme: GPT
Partition:
ID-1: / raw-size: 3.64 TiB size: 3.64 TiB (100.00%) used: 44.22 GiB (1.2%)
fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 3.64 TiB size: 3.64 TiB (100.00%)
used: 44.22 GiB (1.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 3.64 TiB size: 3.64 TiB (100.00%)
used: 44.22 GiB (1.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 3.64 TiB size: 3.64 TiB (100.00%)
used: 44.22 GiB (1.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 62.56 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 32 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 28.0 C mobo: N/A gpu: nvidia temp: 27 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Info:
Memory: total: 64 GiB note: est. available: 62.56 GiB
used: 21.03 GiB (33.6%)
Processes: 728 Power: uptime: 2h 47m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 24.98 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2234 libs: 619 tools: gnome-software, octopi,
pamac, paru Compilers: clang: 17.0.6 gcc: 14.1.1 Shell: garuda-inxi
default: fish v: 3.7.1 running-in: yakuake inxi: 3.3.34
Garuda (2.6.26-1):
System install date:     2024-05-27
Last full system update: 2024-06-04 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:`Preformatted text`

That isn’t exactly right, that service takes a snapshot early in the boot process. Whether that is useful for you or not depends on your specific use case.

3 Likes

It will take a snapshot after each boot.

It is totally up to you. Most people don’t enable it. Snapper has several times it takes snapshots:

  • Before and after each update
  • Hourly
  • After each boot
  • Manually

What combination you prefer is your choice.

Personally, I only use timeline snapshots but I know a lot of people do just the opposite where they only use update snapshots.

3 Likes

I worded that badly. Should have said during boot I think?

Yes, I was advised that hourly was too much, even though I have several Tb for storage.
I was just thinking that it might be a good ‘just in case’ plan to have.

IMO, that isn’t good advice unless you have an atypical use case where you have an extremely high data turnover rate. Recent snapshots will usually take close to no space and Snapper can prune them to whatever amount you want to retain.

5 Likes