Loading a previous snapshot breaks snapshots making loading snapshots impossible

System is broken and can not be updated.

Snapshots are not working.

Older snapshots are being deleted without prompt due to a setting change.

This happens every few months.

Requires full reinstall.

Much appreciated.

System:
Kernel: 6.14.6-hardened1-1-hardened arch: x86_64 bits: 64 compiler: gcc
v: 15.1.1 clocksource: tsc avail: hpet,acpi_pm parameters: pti=on
page_alloc.shuffle=1 BOOT_IMAGE=/@/boot/vmlinuz-linux-hardened
root=UUID=90bad688-87c2-4fa2-a41d-19c0de4179f2 rw rootflags=subvol=@
quiet rd.luks.uuid=55e381a9-1da2-4774-9917-9126737d9ffd loglevel=3
ibt=off
Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A info: frameworks v: 6.14.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG STRIX B850-I GAMING WIFI v: Rev 1.xx
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 0825 date: 11/29/2024
CPU:
Info: model: AMD Ryzen 7 8700G w/ Radeon 780M Graphics bits: 64 type: MT MCP
arch: Zen 4 gen: 4 level: v4 note: check built: 2022+ process: TSMC n5 (5nm)
family: 0x19 (25) model-id: 0x75 (117) stepping: 2 microcode: 0xA705206
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 8 MiB
desc: 8x1024 KiB L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 2403 min/max: 400/5177 boost: enabled scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 2403 2: 2403 3: 2403
4: 2403 5: 2403 6: 2403 7: 2403 8: 2403 9: 2403 10: 2403 11: 2403 12: 2403
13: 2403 14: 2403 15: 2403 16: 2403 bogomips: 134145
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 32 [Radeon RX 7700 XT /
7800 XT] vendor: XFX driver: amdgpu v: kernel arch: RDNA-3 code: Navi-3x
process: TSMC n5 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16
ports: active: DP-3 empty: DP-1, DP-2, HDMI-A-1, Writeback-1
bus-ID: 03:00.0 chip-ID: 1002:747e class-ID: 0300
Device-2: Advanced Micro Devices [AMD/ATI] Phoenix1 vendor: ASUSTeK
driver: amdgpu v: kernel arch: RDNA-3 code: Phoenix process: TSMC n4 (4nm)
built: 2023+ pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: none
empty: DP-4, DP-5, DP-6, DP-7, DP-8, HDMI-A-2, Writeback-2 bus-ID: 0d:00.0
chip-ID: 1002:15bf class-ID: 0300 temp: 41.0 C
Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
Monitor-1: DP-3 model: Samsung S34CG50 serial: <filter> built: 2024 res:
mode: 3440x1440 hz: 100 scale: 114% (1.15) to: 2991x1252 dpi: 109 gamma: 1.2
size: 798x334mm (31.42x13.15") diag: 869mm (34.2") modes: max: 3440x1440
min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: radeonsi device: 2 drv: swrast gbm: drv: radeonsi
surfaceless: drv: radeonsi wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.5-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7800 XT (radeonsi
navi32 LLVM 19.1.7 DRM 3.61 6.14.6-hardened1-1-hardened)
device-ID: 1002:747e memory: 15.62 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.4.313 layers: 9 device: 0 type: discrete-gpu name: AMD
Radeon RX 7800 XT (RADV NAVI32) driver: mesa radv v: 25.0.5-arch1.1
device-ID: 1002:747e surfaces: N/A device: 1 type: integrated-gpu name: AMD
Radeon Graphics (RADV PHOENIX) driver: mesa radv v: 25.0.5-arch1.1
device-ID: 1002:15bf surfaces: N/A device: 2 type: cpu name: llvmpipe
(LLVM 19.1.7 256 bits) driver: mesa llvmpipe v: 25.0.5-arch1.1 (LLVM
19.1.7) device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 HDMI/DP Audio
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 03:00.1 chip-ID: 1002:ab30 class-ID: 0403
Device-2: Advanced Micro Devices [AMD/ATI] Rembrandt Radeon High
Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0d:00.1 chip-ID: 1002:1640
class-ID: 0403
Device-3: ASUSTek 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-6:2
chip-ID: 0b05:1be1 class-ID: 0300
API: ALSA v: k6.14.6-hardened1-1-hardened status: kernel-api tools: N/A
Server-1: PipeWire v: 1.4.2 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: Intel Ethernet I226-V vendor: ASUSTeK driver: igc v: kernel pcie:
gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 0a:00.0 chip-ID: 8086:125c
class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager,systemd-timesyncd
Drives:
Local Storage: total: 1.82 TiB used: 59.65 GiB (3.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QJXD7 temp: 46.9 C
scheme: GPT
Partition:
ID-1: / raw-size: 71.28 GiB size: 71.28 GiB (100.00%)
used: 59.62 GiB (83.6%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-55e381a9-1da2-4774-9917-9126737d9ffd
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 31.3 MiB (32.7%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 71.28 GiB size: 71.28 GiB (100.00%)
used: 59.62 GiB (83.6%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-55e381a9-1da2-4774-9917-9126737d9ffd
ID-4: /var/log raw-size: 71.28 GiB size: 71.28 GiB (100.00%)
used: 59.62 GiB (83.6%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-55e381a9-1da2-4774-9917-9126737d9ffd
ID-5: /var/tmp raw-size: 71.28 GiB size: 71.28 GiB (100.00%)
used: 59.62 GiB (83.6%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-55e381a9-1da2-4774-9917-9126737d9ffd
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 60.48 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 16
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 51.4 C mobo: 41.2 C
Fan Speeds (rpm): N/A
GPU: device: amdgpu temp: 54.0 C mem: 53.0 C fan: 286 watts: 28.00
device: amdgpu temp: 40.0 C watts: 20.15
Info:
Memory: total: 64 GiB note: est. available: 60.48 GiB used: 5.28 GiB (8.7%)
Processes: 394 Power: uptime: 24m states: freeze,mem suspend: deep
avail: s2idle wakeups: 0 services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1460 libs: 458 tools: octopi,paru Compilers:
gcc: 15.1.1 Shell: garuda-inxi default: fish v: 4.0.2 running-in: konsole
inxi: 3.3.38
Garuda (2.7.2-1):
System install date:     2025-02-05
Last full system update: 2025-05-19
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:

In what way is it “broken”?

What is preventing you from updating? Copy and paste the output of garuda-update into the thread so we can see what is happening.

They are not working in what way? Describe what is happening, and how it differs from the expected behavior.

I’m not sure what setting you changed, but older snapshots getting deleted is completely normal so you may need to describe what is happening another way.

What does?

8 Likes

And what does that have to do with broken snapshots?

If this is what you want:

then use this:

garuda-update -- --overwrite '*'
4 Likes

Something breaks that requires a reinstall of Garudal; which is fine its bleeding edge and things are getting fixed; just trying to help in that process.

There are a few things a user with root access can do where reinstalling is legitimately warranted. But almost always a system can be fixed instead, and certainly a perfectly working installation doesn’t just become broken on its own.

If you would like to be more forthcoming with some relevant information, maybe we can help you fix your computer. If you would rather continue to pretend things just break on their own for no reason and you need to periodically reinstall the entire OS because that’s just the way it is, then probably you could spare everyone the forum post next time and just keep it to yourself.

11 Likes

Was mostly the amount of things breaking simultaneously that was daunting to the level of seeming as if it was an exploit as well as the behavior of various applications running over a period of months.

Reinstalling seems to be working again not sure about Snapper.

So the only really crucial issue is encrypted Linux and windows drives breaking in Dolphin only on some systems yet ongoing on this system.

These drives breaking stop Steam from working because the games are on those drives.

The bitlocker drives usually break first so there is likely some exploit that allows other encrypted drives to be broken as well as it only happens on some systems that are usually being used more then other systems that is not breaking on.

Have been working with Steam as well to fix issues on their client based on Chrome as well.

ESO was working in Garuda then stopped; would like to stop using bitlocker drives entirely that is one the of the things stopping that; as well as some pro audio and content creation applications.

You need to stop imagining a hacker is responsible for every hiccup that occurs on your system. You need to realize that while encryption provides an extra layer of security it also adds a lot of extra layers of complexity to your system.

Are your games of such a nature that they really require protection from the spying eyes of hackers and governmental security agencies. Perhaps you need to reassess if your games are of such great importance that they really require data encryption.

When you encounter a system breakage, drive encryption often makes things far more complex to repair. That is fine if you know how to fix these things yourself. In your case most repair operations seem to fall to a small handful of our skilled forum assistants such as @BluishHumility and @nepti. You are really beginning to expect far to much from our forum’s limited support resources with your never ending requests for assistance with your system “exploits”.

Hence:

Be carefull you don’t make too many trips to the well, lest the well runs dry.

9 Likes

Without wanting to offend you, I would like to mention few more things.

You are using a large mix. It’s asking for problems. Dual boot, BitLocker, LUKS, BTRFS, NTFS, etc.etc. You can certainly do all that and handle it successfully. I have done similar things in the past. The problem is that there’s a relatively high risk of something breaking. As is the subsequent repair effort, of course.

I enjoyed the challenge of working with complex structures, and I learned a lot about Linux and computing. However, this requires you to be willing to figure things out for yourself. Search, read, read, read and read again. This path is rocky and often frustrating when you realize you’ve made a mistake out of lack of knowledge, requiring a lot of work to get the system running as desired again. Otherwise, you just can do the 127th reinstallation.

In my almost 30 years of using Linux, I certainly haven’t opened 20 threads on any forums to ask for help. I wanted the complexity, and I wanted to deal with it and work out solutions to problems myself by reading about them. Without the necessary background knowledge and most off all the necessary energy to help yourself, it doesn’t make much sense to make things more complicated than they already are.

A forum in which people sacrifice their free time and work without pay to help others can only help people learn to help themselves. You have to do most of the work yourself. In addition to searching and reading, this involves listening to others, accepting advice, and questioning your own approach. Making a clean cut and taking a step back toward simplicity if you aren´t able to sort thinngs out yourself is not a defeat, but proof of greatness.

6 Likes

Have had two systems completely broken in the last 2 days; no longer able to get access to either system (except for the dual boot partition the OS is completely gone with no ability to restore from a previous snap which are gone seems like as well; here is what transpired.

After posting to the forum the last time; without notice of Snapper icon as happened below; operating system became inaccessible as well as previous Snaps.
(Windows Dual boot partitions were not effected. Encryption unlock works fine & boot menu.)

The second system was just compromised using Snapper to delete the currently running operating system; disappeared turning into a black screen with just a cursor after downloading consecutive ISOs from Distrowatch. Librewolf was crashing as volume was being maxed out but would return to downloading after the files were moved; this happened probably two times; there was a Snapper warning that requested (erroneously) to delete previous Snaps which happened to be all snaps and the current running operating system. This warning was displayed when trying to boot into the OS or switch to a previous Snap.

"

[Failed] Failed to start Load/Save OS Random Seed
[Failed] Failed to start Load/Save OS Random Seed
[Failed] Failed to start Load/Save OS Random Seed
[Failed] Failed to start Load/Save OS Random Seed
[Failed] Failed to start Record System Boot/Shutdown in UTMP.

"

Sorry for offtopic but I am simply speechless.

3 Likes

It’s those reptoloids again, riding unicorns across the internet and using trained smurfs to distribute eploits to hack you. :upside_down_face:


Edit:

This is the reason why:

Obviously the partition is too small for your use case and therefore you regularly run out of free disk space…
/Edit end.


I deliberately didn’t move or close this topic in the hope that the posts by @BluishHumility, @tbg and @Apocalypticus would have an effect and make you think. And I myself had already pointed out in one of your previous topics that obviously too little Linux knowledge is the actual cause of almost all your issues. But obviously this has no positive effect.

I strongly advise you to familiarize yourself fundamentally with the functioning of Linux and especially with Arch/Archbased distributions, as well as with the functioning of special features such as BTRFS and snapshots. You should also learn how to deal with encryption, how to set up a correct dual boot and, above all, how to use the proprietary NTFS on Linux correctly.

Until then, I seriously recommend that you reduce the complexity of your systems and instead of a rolling release distro, use a less demanding static distribution such as Linux Mint, Ubuntu, Debian or Fedora.

Closed.

6 Likes