BTRFS Assistant is not letting me create a new snapshot

Did you delete every subvolume containing this string?
If yes, run sudo snapper delete-config && sudo snapper create-config --template garuda and send the output

Oh come on you gotta be kidding me...

sudo btrfs subvolume delete [email protected]_232533961/.snapshots/36/snapshot
sudo btrfs subvolume delete [email protected]_232533961/.snapshots/{43..58}/snapshot
sudo btrfs subvolume delete [email protected]_232533961/.snapshots
sudo btrfs subvolume delete [email protected]_232533961

Copy paste this into your terminal.

I shot you a dm, please take a look.

Run it in bash.

I don't know what to tell you, but that's fish. Run it in bash.
Follow my instructions carefully: Type "bash". Press enter. Copy paste the command.
Also sharing the command I sent you is like really stupid and you shouldn't have done that >.>

Ok that.... was an absolute mess to deal with. Anyway, got it all fixed and even installed Nvidia drivers after they broke the system (thanks optimus-manager we all hate love you)

3 Likes

Hello, I have a similar problem. Somehow, my Btrfs files are not recognized as btrfs?
I think it has to do with Optimus maybe? This issue happened after I tried to switch to open source drivers.
I cannot make snapshots, it doesn't recognize my snapshots in Btrfs Assistant and, therefore, I cannot delete them.

System:
  Kernel: 5.15.22-1-lts x86_64 bits: 64 compiler: gcc v: 11.1.0
    parameters: BOOT_IMAGE=/@/.snapshots/68/snapshot/boot/vmlinuz-linux-lts
    root=UUID=a71ccffc-c86d-4a9e-b97c-fb26882f24a1 quiet splash rd.udev.log_priority=3
    vt.global_cursor_default=0 loglevel=3
    rootflags=defaults,noatime,noautodefrag,compress=zstd,discard=async,ssd,[email protected]/.snapshots/68/snapshot
  Desktop: KDE Plasma 5.24.0 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: B365M H v: x.x serial: <superuser required>
    UEFI: American Megatrends v: F3 date: 09/05/2019
CPU:
  Info: model: Intel Core i5-9400F bits: 64 type: MCP arch: Coffee Lake family: 6
    model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xEC
  Topology: cpus: 1x cores: 6 smt: <unsupported> cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB
    L2: 1.5 MiB desc: 6x256 KiB L3: 9 MiB desc: 1x9 MiB
  Speed (MHz): avg: 2398 high: 3989 min/max: 800/4100 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 911 3: 2260 4: 2952 5: 3477 6: 3989 bogomips: 34798
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  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: disabled, RSB filling
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU117 [GeForce GTX 1650] vendor: Gigabyte driver: nvidia v: 510.47.03
    alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:1f82 class-ID: 0300
  Device-2: GEMBIRD USB2.0 PC CAMERA type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-1:2
    chip-ID: 1908:2310 class-ID: 0102
  Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver: loaded: nvidia
    unloaded: modesetting alternate: fbdev,nouveau,nv,vesa display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1680x1050 s-dpi: 90 s-size: 474x303mm (18.7x11.9") s-diag: 563mm (22.1")
  Monitor-1: DP-0 res: 1680x1050 hz: 60 dpi: 90 size: 474x296mm (18.7x11.7") diag: 559mm (22")
  OpenGL: renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2 v: 4.6.0 NVIDIA 510.47.03
    direct render: Yes
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403
  Device-2: NVIDIA vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 01:00.1
    chip-ID: 10de:10fa class-ID: 0403
  Device-3: GEMBIRD USB2.0 PC CAMERA type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-1:2
    chip-ID: 1908:2310 class-ID: 0102
  Sound Server-1: ALSA v: k5.15.22-1-lts running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.45 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169
    v: kernel port: d000 bus-ID: 07:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp7s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Integrated System Solution Bluetooth Device type: USB driver: btusb v: 0.8
    bus-ID: 1-9:5 chip-ID: 1131:1004 class-ID: fe01
  Report: bt-adapter ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
    hardware: no software: no address: <filter>
Drives:
  Local Storage: total: 1.64 TiB used: 499.13 GiB (29.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37240G size: 223.57 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: B1D2 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD5000AZRX-00A
8LB0
    size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: N/A
    serial: <filter> rev: 1A01 scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WD10EZEX-60WN4A1 size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: 1A03 scheme: GPT
  ID-4: /dev/sdd maj-min: 8:48 type: USB model: Specific STORAGE DEVICE size: 58.59 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 0009 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 25.6 MiB (26.6%) fs: vfat
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /home raw-size: 68.36 GiB size: 68.36 GiB (100.00%) used: 19.22 GiB (28.1%) fs: btrfs
    dev: /dev/sda5 maj-min: 8:5
  ID-3: /var/log raw-size: 68.36 GiB size: 68.36 GiB (100.00%) used: 19.22 GiB (28.1%) fs: btrfs
    dev: /dev/sda5 maj-min: 8:5
  ID-4: /var/tmp raw-size: 68.36 GiB size: 68.36 GiB (100.00%) used: 19.22 GiB (28.1%) fs: btrfs
    dev: /dev/sda5 maj-min: 8:5
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.57 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 27.8 C mobo: 16.8 C gpu: nvidia temp: 43 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
  Processes: 284 Uptime: 1h 23m wakeups: 0 Memory: 15.57 GiB used: 5.16 GiB (33.1%) Init: systemd
  v: 250 tool: systemctl Compilers: gcc: 11.1.0 Packages: pacman: 1361 lib: 341
  Client: shell wrapper v: 5.1.16-release inxi: 3.3.12
Garuda (2.5.4-2):
  System install date:     2022-02-11
  Last full system update: 2022-02-12
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       Probably (Run as root to verify)
  Snapshots:               Snapper
  Failed units:            snapper-boot.service snapper-cleanup.service snapper-timeline.service 
4.863s ldconfig.service
 616ms mnt-62D2D04CD2D025D7.mount
 590ms mnt-2E2812B92812804F.mount
 577ms mnt-9440CC3240CC1CBC.mount
 562ms mnt-80DE4F00DE4EEDCA.mount
 469ms mnt-6EE25599E255667D.mount
 469ms [email protected]
 319ms updatedb.service
 213ms udisks2.service
 199ms lvm2-monitor.service
 175ms upower.service
 155ms accounts-daemon.service
 145ms systemd-rfkill.service
 139ms systemd-journal-flush.service
 135ms ModemManager.service
 135ms mnt-usb\x2dSpecific_STORAGE_DEVICE_19090601010022\x2d0:0\x2dpart1.mount
 131ms power-profiles-daemon.service
 129ms polkit.service
 110ms avahi-daemon.service
 109ms bluetooth.service
 108ms NetworkManager.service
 100ms systemd-logind.service
  80ms dev-zram0.swap
  72ms systemd-guest-config.service
  70ms systemd-udev-trigger.service
  67ms [email protected]\x2duuid-B0FE\x2dC42E.service
  62ms systemd-tmpfiles-setup.service
  61ms systemd-vconsole-setup.service
  45ms mnt-4BC8\x2d76D1.mount
  44ms systemd-tmpfiles-clean.service
  44ms systemd-udevd.service
  42ms systemd-journald.service
  36ms boot-efi.mount
  36ms systemd-oomd.service
  36ms root.mount
  36ms var-cache.mount
  35ms systemd-timesyncd.service
  35ms [email protected]
  35ms [email protected]
  34ms var-log.mount
  33ms systemd-modules-load.service
  31ms srv.mount
  31ms var-tmp.mount
  29ms home-guest.mount
  29ms systemd-journal-catalog-update.service
  27ms tmp.mount
  26ms plymouth-deactivate.service
  26ms plymouth-quit-wait.service
  25ms plymouth-quit.service
  24ms home.mount
  20ms systemd-guest-user.service
  18ms plymouth-start.service
  18ms [email protected]
  16ms systemd-sysusers.service
  15ms colord.service
  13ms plymouth-read-write.service
  10ms rtkit-daemon.service
   8ms dev-hugepages.mount
   8ms [email protected]
   8ms snapper-boot.service
   8ms dev-mqueue.mount
   7ms systemd-tmpfiles-setup-dev.service
   7ms sys-kernel-debug.mount
   7ms snapperd.service
   7ms systemd-random-seed.service
   7ms sys-kernel-tracing.mount
   6ms systemd-user-sessions.service
   6ms kmod-static-nodes.service
   6ms [email protected]
   5ms systemd-update-utmp.service
   5ms [email protected]
   5ms garuda-pacman-lock.service
   5ms systemd-remount-fs.service
   5ms linux-modules-cleanup.service
   4ms systemd-sysctl.service
   3ms systemd-update-done.service
   1ms sys-kernel-config.mount
 376us sys-fs-fuse-connections.mount

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @11.400s
└─multi-user.target @11.399s
  └─ModemManager.service @11.263s +135ms
    └─polkit.service @11.133s +129ms
      └─basic.target @11.127s
        └─sockets.target @11.127s
          └─dbus.socket @11.126s
            └─sysinit.target @11.125s
              └─systemd-update-done.service @11.122s +3ms
                └─ldconfig.service @6.257s +4.863s
                  └─local-fs.target @6.255s
                    └─tmp.mount @6.227s +27ms
                      └─swap.target @5.372s
                        └─dev-zram0.swap @5.291s +80ms
                          └─[email protected] @5.255s +35ms
                            └─dev-zram0.device @5.245s

I tried some of the steps from above but they don't seem to work

[🔴] × sudo snapper list
[sudo] password for catalin:
IO Error (query default id failed, subvolume is not a btrfs subvolume).
λ sudo systemctl --failed
[sudo] password for catalin:
UNIT                     LOAD   ACTIVE SUB    DESCRIPTION
● snapper-boot.service     loaded failed failed Take snapper snapshot of root on boot
● snapper-cleanup.service  loaded failed failed Daily Cleanup of Snapper Snapshots
● snapper-timeline.service loaded failed failed Timeline of Snapper Snapshots

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
3 loaded units listed.
λ sudo journalctl -p 3 -xb
feb 12 11:37:14 catalin-b365mh kernel: x86/cpu: SGX disabled by BIOS.
feb 12 11:37:14 catalin-b365mh kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._>
feb 12 11:37:14 catalin-b365mh kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous e>
feb 12 11:37:14 catalin-b365mh kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT4._>
feb 12 11:37:14 catalin-b365mh kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous e>
feb 12 11:37:14 catalin-b365mh kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._>
feb 12 11:37:14 catalin-b365mh kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous e>
feb 12 11:37:14 catalin-b365mh kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._>
feb 12 11:37:14 catalin-b365mh kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous e>
feb 12 11:37:14 catalin-b365mh kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT4._>
feb 12 11:37:14 catalin-b365mh kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous e>
feb 12 11:37:14 catalin-b365mh kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._>
feb 12 11:37:14 catalin-b365mh kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous e>
feb 12 11:37:14 catalin-b365mh kernel:
feb 12 11:37:14 catalin-b365mh systemd[312]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator fa>
feb 12 11:37:47 catalin-b365mh bluetoothd[582]: Failed to set mode: Failed (0x03)
feb 12 11:45:37 catalin-b365mh sudo[3447]:  catalin : a password is required ; TTY=pts/1 ; PWD=/home/catalin >
feb 12 11:45:48 catalin-b365mh systemd[3497]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator f>
feb 12 11:46:54 catalin-b365mh systemd[3759]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator f>
feb 12 11:46:55 catalin-b365mh systemd[3778]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator f>
feb 12 11:46:55 catalin-b365mh systemd[3797]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator f>
feb 12 11:46:56 catalin-b365mh systemd[3822]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator f>
feb 12 11:47:53 catalin-b365mh sudo[4041]:  catalin : a password is required ; TTY=pts/2 ; PWD=/home/catalin >
feb 12 11:48:48 catalin-b365mh systemd[4199]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator f>
feb 12 11:49:45 catalin-b365mh sudo[7827]:  catalin : a password is required ; TTY=pts/1 ; PWD=/home/catalin >
feb 12 11:55:17 catalin-b365mh sudo[8097]:  catalin : a password is required ; TTY=pts/2 ; PWD=/home/catalin >
feb 12 11:56:27 catalin-b365mh systemd[8925]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator f>
lines 1-27

Sure is. My questions were prior to the screenshots. The output seemed to indicate perhaps a different filesystem.

So glad you got it sorted. What a great demonstration of hands-on help. :smiley:

It was obvious before that too tho :stuck_out_tongue:

1 Like

A take back my compliment.
:tongue:

1 Like

What does sudo btrfs subvolume list / show?

1 Like

Thanks for replying!
You have a very responsive community here :raised_hands:

I have already reinstalled KDE #LOL. I tried tinkering on my own and messed up even more xD.
I am new to Arch Linux and new to Linux in general, but I love it. Garuda KDE is so snappy and customisable! I tried many distros but they are just not performant as this one! :heart: I like this philosophy Unused RAM is wasted RAM.

I was trying to see if open source driver could keep my Nvidia under 44-45 C degrees as it makes noise. On windows it used to stay pretty much all the time at 38-39 degrees. I don't play video games anymore.. but I don't have an integrated GPU.
I amalso on youtube trying to learn more Linux commands.
So my BTRFS Assistant issue has been resolved.

At the moment I am trying to understand the kernel thing - was reading this forum post.
I have, installed by default, linux-zen 5.16.8 zen1-1 but I also installed linux-lts 5.15.22-246
Since I am not gaming, which one should I use? And how can I change between kernels at start?
Garuda boot options doesn't want to keep my LTS as main. What do you think?

Choose whichever gives you the performance you seek from the GRUB menu when you re/boot. You mentioned heat? The LTS may pleasantly affect that, and also try the normal linux kernel.

And sometimes some of us who think we're living on the edge keep several handy in case we fall off.
:wink:

1 Like

Have you tried thermald from Garuda-Assistant? If not, it might be worth a try, even if you are on a desktop.

I would suggest Linux-zen, even if you are not gaming. It is snappier even if you are not gaming. But I guess, others might have different opinion.

2 Likes

Thanks for the help!

1 Like

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

Anyone stumbling across this in the future, I made a script to solve this issue automatically:

6 Likes