Btrfs system crash, howto recover?

Support
1

Hi all.

I just updated a kde btrfs system (stable) with the latest updates and activated a new kernel (6.6->6.10) on my Samsung 900x3c.
I noticed it also started to update some aur stuff, which were orphans and things I never use. I deleted the few orphans and at the next boot suddenly the system is not booting anymore. Oops, did I remove something that I shouldn’t have?
It shows:
[FAILED] Failed to start Load/Save OS Random Seed, Create System Users, Record System Boot/Shutdown in UTMP, Rebuild Journal Catalog, Rebuid Dynamic Linker Cache, Update is completed, pkgfile database update, Samba NMB and SMB Deamon and Failed to listen on GnuPG …

So, I tried in Grub to boot a timeshift snapshot, but that also doesn’t work: I get similar but also different error messages.
Not all snapshots were visible, so I booted into the live USB and restored a snapshot in timeshift.
No luck either…

In the end I backupped important stuff in @home, and tried to run the calamares installer on top of the system without erasing anything. Calamares said it cannot mount.

So, how can I repair this?
Either boot in a snapshot or reinstall while keeping the @home folder?

Thanks for helping!

edit:

System:
  Kernel: 6.9.12-3-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
    misobasedir=manjaro misolabel=MANJARO_KDE_2407 quiet systemd.show_status=1
    splash driver=nonfree nouveau.modeset=0 i915.modeset=1 radeon.modeset=1
  Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A wm: kwin_x11 dm: SDDM
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: SAMSUNG product: 900X3C/900X3D/900X4C/900X4D v: 0.1
    serial: <filter> Chassis: type: 9 v: 0.1 serial: <filter>
  Mobo: SAMSUNG model: SAMSUNG_NP1234567890 v: FAB1 serial: <filter>
    uuid: 19759a60-1dd2-11b2-8000-aa8ca0b6e579 UEFI-[Legacy]: Phoenix v: P07AAC
    date: 11/18/2013
Battery:
  ID-1: BAT1 charge: 27.4 Wh (100.0%) condition: 27.4/40.3 Wh (68.0%)
    volts: 8.2 min: 7.4 model: SAMSUNG Electronics type: Li-ion serial: N/A
    status: full cycles: 1742
Memory:
  System RAM: total: 4 GiB available: 3.53 GiB used: 2.19 GiB (61.9%)
    igpu: 64 MiB
  Array-1: capacity: 32 GiB slots: 4 modules: 2 EC: None
    max-module-size: 8 GiB note: est.
  Device-1: ChannelA-DIMM0 type: DDR3 detail: synchronous size: 2 GiB
    speed: 1600 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: Samsung part-no: M471B5674BM0-CK0 serial: N/A
  Device-2: ChannelA-DIMM1 type: no module installed
  Device-3: ChannelB-DIMM0 type: DDR3 detail: synchronous size: 2 GiB
    speed: 1600 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: Samsung part-no: M471B5674BM0-CK0 serial: N/A
  Device-4: ChannelB-DIMM1 type: no module installed
PCI Slots:
  Slot: 0 type: PCIe status: available length: long volts: 3.3 bus-ID: 00:00.0
  Slot: 1 type: PCIe gen: 1 status: in use length: short volts: 3.3
    bus-ID: 00:00.0
  Slot: 2 type: PCIe gen: 2 status: available length: short volts: 3.3
    bus-ID: 00:00.0
  Slot: 3 type: PCIe gen: 3 status: available length: short volts: 3.3
    bus-ID: 00:00.0
  Slot: 4 type: PCIe gen: 4 status: in use length: short volts: 3.3
    bus-ID: 00:00.0
  Slot: 5 type: PCIe gen: 5 status: in use length: short volts: 3.3
    bus-ID: 00:00.0
CPU:
  Info: model: Intel Core i5-3317U socket: rPGA988B (U3E1) note: check bits: 64
    type: MT MCP arch: Ivy Bridge gen: core 3 level: v2 built: 2012-15
    process: Intel 22nm family: 6 model-id: 0x3A (58) stepping: 9
    microcode: 0x17
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
    L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 814 high: 859 min/max: 800/2600 base/boost: 1700/1700
    scaling: driver: intel_cpufreq governor: schedutil volts: 0.8 V
    ext-clock: 100 MHz cores: 1: 859 2: 800 3: 800 4: 800 bogomips: 13575
  Flags: acpi aes aperfmperf apic arat arch_perfmon avx bts clflush cmov
    constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb
    ept erms est f16c flexpriority fpu fsgsbase fxsr ht ida lahf_lm lm mca mce
    mmx monitor msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm
    pebs pge pln pni popcnt pse pse36 pti pts rdrand rdtscp rep_good sep smep
    ss sse sse2 sse4_1 sse4_2 ssse3 syscall tm tm2 tpr_shadow tsc
    tsc_deadline_timer vme vmx vnmi vpid x2apic xsave xsaveopt xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode;
    SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; STIBP: disabled; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Vulnerable: No microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel 3rd Gen Core processor Graphics vendor: Samsung Co
    driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports:
    active: eDP-1 empty: DP-1,HDMI-A-1,VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0166
    class-ID: 0300
  Device-2: Silicon Motion Webcam SC-13HDL11624N [Namuga ] driver: uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.6:3
    chip-ID: 2232:1024 class-ID: 0e02 serial: <filter>
  Display: unspecified server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2
    compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: crocus gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37")
    s-diag: 485mm (19.11")
  Monitor-1: eDP-1 model: Seiko Epson 0x3546 built: 2011 res: 1600x900 hz: 60
    dpi: 139 gamma: 1.2 chroma: red: x: 0.592 y: 0.341 green: x: 0.329 y: 0.541
    blue: x: 0.153 y: 0.133 white: x: 0.314 y: 0.329
    size: 293x165mm (11.54x6.5") diag: 336mm (13.2") ratio: 16:9
    modes: 1600x900
  API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
    device: 1 drv: swrast gbm: drv: crocus surfaceless: drv: crocus x11:
    drv: crocus inactive: wayland
  API: OpenGL v: 4.5 compat-v: 4.2 vendor: intel mesa v: 24.1.6-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 4000 (IVB GT2)
    device-ID: 8086:0166 memory: 1.46 GiB unified: yes
  API: Vulkan v: 1.3.279 layers: N/A device: 0 type: integrated-gpu
    name: Intel HD Graphics 4000 (IVB GT2) driver: mesa intel v: 24.1.6-arch1.1
    device-ID: 8086:0166 surfaces: xcb,xlib
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Samsung Co
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20
    class-ID: 0403
  API: ALSA v: k6.9.12-3-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.2.2 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Qualcomm Atheros AR928X Wireless Network Adapter vendor: Lite-On
    driver: ath9k v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 01:00.0
    chip-ID: 168c:002a class-ID: 0280
  IF: wlp1s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Samsung Co driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: 2000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 495.06 GiB used: 445.19 GiB (89.9%)
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO mSATA 500GB
    family: based SSDs size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 1B6Q temp: 40 C scheme: MBR
  SMART: yes state: enabled health: PASSED on: 1y 266d 19h cycles: 4757
    written: 17.81 TiB
  ID-2: /dev/sdb maj-min: 8:16 vendor: Generic model: Flash Disk
    size: 29.3 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 2.0
    spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: <filter> fw-rev: 8.07
    scheme: GPT
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  Message: No optical or floppy data found.
Partition:
  ID-1: /run/media/manjaro/spiffy raw-size: 457.97 GiB
    size: 457.97 GiB (100.00%) used: 445.19 GiB (97.2%) fs: btrfs
    block-size: 4096 B dev: /dev/sda1 maj-min: 8:1 label: spiffy
    uuid: 9efe6e2e-7355-4b52-8b47-b545e67ae8c5
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/dm-0 maj-min: 254:0 mapped: ventoy size: 3.64 GiB fs: iso9660
  ID-2: /dev/sda2 maj-min: 8:2 size: 7.79 GiB fs: swap label: N/A
    uuid: 90a910e5-a181-45e1-a749-47ce5ddc0aab
  ID-3: /dev/sdb1 maj-min: 8:17 size: 29.26 GiB fs: exfat label: Ventoy
    uuid: 4E21-0000
  ID-4: /dev/sdb2 maj-min: 8:18 size: 32 MiB fs: vfat label: VTOYEFI
    uuid: 3F32-27F5
USB:
  Hub-1: 1-0:1 info: full speed or root hub ports: 3 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:0024
    class-ID: 0900
  Device-1: 1-1.6:3 info: Silicon Motion Webcam SC-13HDL11624N [Namuga ]
    type: video driver: uvcvideo interfaces: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 2232:1024 class-ID: 0e02 serial: <filter>
  Hub-3: 2-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 2-1:2 info: Alcor Micro Flash Drive type: mass storage
    driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 200mA chip-ID: 058f:6387 class-ID: 0806
    serial: <filter>
  Hub-4: 3-0:1 info: super-speed hub ports: 2 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 62.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1260 libs: 333 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: http://ftp.uni-kl.de/pub/linux/manjaro/stable/$repo/$arch
    2: https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
    3: https://nnenix.mm.fcix.net/manjaro/stable/$repo/$arch
    4: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
    5: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
    6: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch
    7: https://mirrors.dotsrc.org/manjaro/stable/$repo/$arch
    8: http://ossmirror.mycloud.services/os/linux/manjaro/stable/$repo/$arch
    9: https://mirror.nyist.edu.cn/manjaro/stable/$repo/$arch
    10: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
    11: https://mirrors.manjaro.org/repo/stable/$repo/$arch
    12: https://mirrors.piconets.webwerks.in/manjaro-mirror/stable/$repo/$arch
    13: http://ftp.free.org/mirrors/repo.manjaro.org/repos/stable/$repo/$arch
    14: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch
    15: https://mirrors.xtom.jp/manjaro/stable/$repo/$arch
    16: https://manjaro.mirrors.lavatech.top/stable/$repo/$arch
    17: https://mirror.yandex.ru/mirrors/manjaro/stable/$repo/$arch
    18: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
    19: https://mirror.init7.net/manjaro/stable/$repo/$arch
    20: https://mirror.seahost.de/manjaro/stable/$repo/$arch
    21: https://mirror.csclub.uwaterloo.ca/manjaro/stable/$repo/$arch
    22: https://mirrors.up.pt/pub/manjaro/stable/$repo/$arch
    23: http://manjaro.grena.ge/stable/$repo/$arch
    24: https://mnvoip.mm.fcix.net/manjaro/stable/$repo/$arch
    25: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
    26: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
    27: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
    28: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
    29: https://mirrors2.manjaro.org/stable/$repo/$arch
    30: http://mirror.datacenter.by/pub/mirrors/manjaro/stable/$repo/$arch
    31: https://mirror.zetup.net/manjaro/stable/$repo/$arch
    32: https://manjaro.ynh.ovh/stable/$repo/$arch
    33: https://bd.mirror.vanehost.com/Manjaro/stable/$repo/$arch
    34: https://mirror.it4i.cz/manjaro/stable/$repo/$arch
    35: https://mirror.albony.xyz/manjaro/stable/$repo/$arch
    36: http://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
    37: https://quantum-mirror.hu/mirrors/pub/manjaro/stable/$repo/$arch
    38: https://uvermont.mm.fcix.net/manjaro/stable/$repo/$arch
    39: https://mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch
    40: https://mirrors.xtom.de/manjaro/stable/$repo/$arch
    41: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    42: https://mirror.archlinux.tw/Manjaro/stable/$repo/$arch
    43: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
    44: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
    45: https://mirror.2degrees.nz/manjaro/stable/$repo/$arch
    46: https://edgeuno-bog2.mm.fcix.net/manjaro/stable/$repo/$arch
    47: https://mirror.kamtv.ru/manjaro/stable/$repo/$arch
    48: https://mirror.23m.com/manjaro/stable/$repo/$arch
    49: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
    50: https://mirrors.nic.cz/manjaro/stable/$repo/$arch
    51: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
    52: http://manjaro.mirrors.uk2.net/stable/$repo/$arch
    53: https://mirror.alwyzon.net/manjaro/stable/$repo/$arch
    54: http://mirror.xeonbd.com/manjaro/stable/$repo/$arch
    55: https://mirror.ufam.edu.br/manjaro/stable/$repo/$arch
    56: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
    57: https://manjarolinux-mirror.cloud.mu/stable/$repo/$arch
    58: https://mirror1.sox.rs/manjaro/stable/$repo/$arch
    59: http://kartolo.sby.datautama.net.id/manjaro/stable/$repo/$arch
    60: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
    61: http://ftp.riken.jp/Linux/manjaro/stable/$repo/$arch
    62: https://mirrors.pku.edu.cn/manjaro/stable/$repo/$arch
    63: https://mirrors.jlu.edu.cn/manjaro/stable/$repo/$arch
    64: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
    65: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
    66: http://ftp.snt.utwente.nl/pub/linux/manjaro/stable/$repo/$arch
    67: https://fastmirror.pp.ua/manjaro/stable/$repo/$arch
    68: https://ftpmirror1.infania.net/mirror/manjaro/stable/$repo/$arch
    69: https://manjaro.repo.cure.edu.uy/stable/$repo/$arch
    70: http://manjaro.mirrors.theom.nz/manjaro/stable/$repo/$arch
    71: https://ftp.caliu.cat/pub/distribucions/manjaro/stable/$repo/$arch
    72: http://mirror.is.co.za/mirrors/manjaro.org/stable/$repo/$arch
    73: https://fosszone.csd.auth.gr/manjaro/stable/$repo/$arch
    74: https://repo.iut.ac.ir/repo/manjaro/stable/$repo/$arch
    75: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
    76: https://mirror.bouwhuis.network/manjaro/stable/$repo/$arch
    77: https://mirror.dkm.cz/manjaro/stable/$repo/$arch
    78: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    79: https://mirror.ibakerserver.pt/manjaro/stable/$repo/$arch
    80: https://mirror.funami.tech/manjaro/stable/$repo/$arch
    81: https://mirror.truenetwork.ru/manjaro/stable/$repo/$arch
    82: https://linorg.usp.br/manjaro/stable/$repo/$arch
    83: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
    84: https://mirrors.netix.net/manjaro/stable/$repo/$arch
    85: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
    86: http://manjaro.mirror.ac.za/stable/$repo/$arch
    87: http://ftp.dei.uc.pt/pub/linux/manjaro/stable/$repo/$arch
    88: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    89: https://manjaro.mirror.liquidtelecom.com/stable/$repo/$arch
    90: https://mirror.freedif.org/Manjaro/stable/$repo/$arch
    91: https://mirror.telepoint.bg/manjaro/stable/$repo/$arch
    92: https://ipng.mm.fcix.net/manjaro/stable/$repo/$arch
    93: https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch
    94: https://ftp.linux.org.tr/manjaro/stable/$repo/$arch
    95: https://ftp.cc.uoc.gr/mirrors/linux/manjaro/stable/$repo/$arch
    96: https://ftp.psnc.pl/linux/manjaro/stable/$repo/$arch
    97: https://mirror.koddos.net/manjaro/stable/$repo/$arch
    98: https://ba.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    99: http://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
    100: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    101: https://mirrors.ustc.edu.cn/manjaro/stable/$repo/$arch
    102: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
    103: https://manjaro.mirror.garr.it/manjaro/stable/$repo/$arch
    104: https://mirror.easyname.at/manjaro/stable/$repo/$arch
    105: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
    106: https://mirrors.xtom.ee/manjaro/stable/$repo/$arch
    107: https://manjaro.mirror.wearetriple.com/stable/$repo/$arch
    108: https://manjaro.kurdy.org/stable/$repo/$arch
    109: https://mirror.futureweb.be/manjaro/stable/$repo/$arch
    110: https://mirrors.aliyun.com/manjaro/stable/$repo/$arch
    111: https://mirror.kku.ac.th/manjaro/stable/$repo/$arch
    112: https://mirrors.atlas.net.co/manjaro/stable/$repo/$arch
    113: https://repos.silknet.com/manjaro/stable/$repo/$arch
    114: https://mirror.dc.uz/manjaro/stable/$repo/$arch
    115: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
    116: https://ct.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    117: https://mirrors.tuna.tsinghua.edu.cn/manjaro/stable/$repo/$arch
    118: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
    119: https://mirror.nju.edu.cn/manjaro/stable/$repo/$arch
    120: http://ftp.belnet.be/mirrors/manjaro/repos/stable/$repo/$arch
    121: https://mirror.aarnet.edu.au/pub/manjaro/stable/$repo/$arch
    122: http://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
    123: https://mirrors.cicku.me/manjaro/stable/$repo/$arch
    124: http://mirror.fcix.net/manjaro/stable/$repo/$arch
    125: http://mirror.terrahost.no/linux/manjaro/stable/$repo/$arch
    126: http://free.nchc.org.tw/manjaro/stable/$repo/$arch
    127: https://ridgewireless.mm.fcix.net/manjaro/stable/$repo/$arch
    128: https://mirror.ufro.cl/manjaro/stable/$repo/$arch
    129: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
    130: https://mirror.bardia.tech/manjaro/stable/$repo/$arch
    131: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 212
  1: cpu: 62.7% command: firefox pid: 2530 mem: 386.4 MiB (10.6%)
  2: cpu: 50.0% command: ps pid: 3197 mem: 3.38 MiB (0.0%)
  3: cpu: 14.2% command: konsole pid: 3129 mem: 118.8 MiB (3.2%)
  4: cpu: 12.2% command: firefox pid: 2784 mem: 241.6 MiB (6.6%)
  5: cpu: 6.7% command: zsh pid: 3143 mem: 7.81 MiB (0.2%)
  Memory top: 5 of 212
  1: mem: 386.4 MiB (10.6%) command: firefox pid: 2530 cpu: 62.7%
  2: mem: 300.1 MiB (8.3%) command: plasmashell pid: 1460 cpu: 0.4%
  3: mem: 241.6 MiB (6.6%) command: firefox pid: 2784 cpu: 12.2%
  4: mem: 164.5 MiB (4.5%) command: kwin_x11 pid: 1427 cpu: 1.0%
  5: mem: 130.0 MiB (3.5%) command: firefox pid: 2677 cpu: 1.0%
Info:
  Processes: 212 Power: uptime: 46m states: freeze,standby,mem,disk
    suspend: deep avail: s2idle,shallow wakeups: 0 hibernate: platform
    avail: shutdown, reboot, suspend, test_resume image: 1.37 GiB
    services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd
    v: 256 default: graphical tool: systemctl
  Compilers: N/A Shell: Sudo (sudo) v: 1.9.15p5 default: Bash v: 5.2.32
    running-in: konsole inxi: 3.3.35
2

Welcome to Manjaro! :smiling_face_with_three_hearts:

  1. Please read the information behind this link. It will help you to post necessary information.
  1. Please press the three dots … below your post and then press the :pencil2:
  • If you give us information about your system, we can see what we’re talking about and make better suggestions.
  • You can do this by using inxi in a terminal or in console.
sudo inxi --verbosity=8 --filter --width
  • Personally identifiable information such as serial numbers and MAC addresses are filtered out by this command
  • Presenting the information in this way allows everyone to be familiar with the format and quickly find the items they need without missing anything.
  1. Copy the output from inxi (including the command) and paste it into your post.
  • To make it more readable, add 3 backticks ``` on an extra line before and after the pasted text.
  1. Or we can try to play hide and seek :wink:
    Have you already :mag: for your problem in the forum ? (Wisdom lies in asking → listening → reading :wink: )

These error-messages are necessary to help you. Please do provide them as exact as possible.
:footprints:

1 Like
3

Thanks @andreas85 for your feedback :slight_smile:
I am actually not new to Manjaro (>15 years of use), I am new to the forum as I never before needed to ask something of the community.
I of course already went through the forum to find solutions, but could not find a suitable one that I could make work.
Maybe I missed some? That could be of course.

Is there besides what I already described in my OP and the inxi output anything needed?
(inxi output is from the live usb)

edit: I see your update. Will restart and write down the other error messages

edit2: I chose from grub to boot the oldest of 3 timeshift snapshots (all from 24/8, but on the disk there are more available from may and april which do not show up in grub)

the messages while booting that snapshot:

WARNING
The root device is not configured to be mounted read-write! it may be fsck'd later.
[FAILED]
Failed to start:
Create List of Static Devices Modes
Load/Save OS Random Seed

Failed to mount Mount unit for:
bare, revision 5
converternow, core, various revisions
core 18, core  20, core 22, core 24, various revisions
ferdium, formatlab, gnome-3, gtk-common-themes, pyqt5-runtime-core20, snapd, telegram-desktop
->(these all look like snap / flatpak processes)

Failed to listen on GnuPG network certificate management deamon for /etc/pacman.d/gnupg
(and 5 similar GnuPG /etc/pacman.d/gnupg errors)

Failed to start:
Wait for Network to be configured
Samba NMB and DMB Deamon
Snap Deamon
Failure handling of the snapd swap
4
  • Is this your “main”-filesystem ?
  • Is this filesystem “full” ?

You find good Information about Btrfs in the wiki

Please provide :

sudo btrfs filesystem usage /

(I am out of here for a few hours, but maybe someone will try to help you in this time) :footprints:

1 Like
5

The system is indeed quite full, but there is still 12,3GB free space, so that shouldn’t be a problem.

6

edit: I chrooted into the system.

[manjaro /]# sudo btrfs filesystem usage /
Overall:
    Device size:                 457.96GiB
    Device allocated:            457.96GiB
    Device unallocated:            1.01MiB
    Device missing:                  0.00B
    Device slack:                  1.00KiB
    Used:                        444.69GiB
    Free (estimated):             12.26GiB      (min: 12.26GiB)
    Free (statfs, df):            12.26GiB
    Data ratio:                       1.00
    Metadata ratio:                   2.00
    Global reserve:              512.00MiB      (used: 0.00B)
    Multiple profiles:                  no

Data,single: Size:451.95GiB, Used:439.69GiB (97.29%)
   /dev/sda1     451.95GiB

Metadata,DUP: Size:3.00GiB, Used:2.50GiB (83.34%)
   /dev/sda1       6.00GiB

System,DUP: Size:8.00MiB, Used:64.00KiB (0.78%)
   /dev/sda1      16.00MiB

Unallocated:
   /dev/sda1       1.01MiB
7

No free space…

Estimated 12.3 GB in the 1GB chunks. It is pretty much full and has no air to breath. When was the last btrfs balance of the chunks? I would do this first…

sudo btrfs balance start -musage=90 -dusage=90 --bg /mnt  ;  sudo watch -n1 'btrfs balance status /mnt'

Not in chroot of course :wink:

That doesn’t matter here. It is only 3% free space, spreaded over several chunks. That is too low on a CopyOnWrite filesystem. It has to be 10% at least.

1 Like
8

Thanks.
What should I replace /mnt for or what should I mount on it?
/mnt and /dev/sda1 and /run/media/manjaro are not working

9

I recommend to create Timeshift snapshots with a external USB Drive.

You have more security when your Root and this snapshots are separated.

10

Usually the mount point of your device, not the block device file.

Cannot compute “not working”. :robot:

11

@megavolt
Sorry :wink:
/run/media/manjaro:
not a btrfs filessystem

but my bad, I already corrected it to /run/media/manjaro/spiffy
Output from that is:
no balance found on ‘/run/media/manjaro/spiffy’

12

@Kobold
Thanks, I understand.
I thought having timeshift set to automatic snapshots of @ whenever an update is done would work to make it easy to go to a previous snapshot if something went wrong with an update. Could I better use Snapper for that?

13

@birdibird So the problem is not btrfs, but actually your maintenance task before reboot? Seems so. If it is not mounted read-only, then most likely no problem with btrfs.

Sooo… what have you done?

Looks more like a configuration of the bootloader. Grub is configured to mount it read-only? Or it kernel 6.10, which produces your problem…

14

Since I assume, you are running the default of Timeshift’s 3 snapshots you may want to increase that. (Just so you don’t lose possible snapshots you might need for restoring).

In: /etc/timeshift-autosnap.conf

# maxSnapshots defines how much old snapshots script should left.
# Only positive whole numbers can be used.
# Default value is 3.
maxSnapshots=3

So you will lose the oldest (auto-)snapshots the when the new ones are taken, unless you increase this value.

Obviously, this doesn’t help you free up space. But it may be a change you want in case you need one of those snapshots.

Kobold will recommend Timeshift with rsync pseudo snapshots to anyone, regardless of your setup, needs, or filesystem type(s). It is simple to enable, since it’s GUI bullet option of two, And suits the use case of many people, but you are losing a lot of what you can do with brtfs this way. (It gets rsynced to a separate POSIX compliant filesystem if you want.) If you were running an ext4 root FS, I could even get on board with this.

For one example of many, a rollback is instant with (Timeshift) btrfs, but with Timeshift rsync, you have to rsync (analyze then copy) all the data back to the drive. (This can work as a quick backup.) But it’s better not to be lazy, and backup the btrfs snapshots, which can just be folders, your own way. Plus, there are options to send btrfs snapshots to different drives and/or hosts, regardless if you are using Timeshift, Snapper, or running btrfs sub snapshot yourself.

Snapper is a a lot more configuration. (Sure, you can do more.) But you can really switch at any time. I even have both running in a guest VM. If you are still trying to understand btrfs and/or Timeshift, I would stick with Timeshift for now. Unless you feel you have a good grasp on it.

Timeshift does have simplicity going for it, with a very clean GUI. And you can still do a much of the advanced stuff on the command line, since they are just plain ol’ btrfs snapshots.

15

I really have no idea. I of course did a btrfs check (also csum) and everything is fine.
I guess I will delete some larger files from @home (after backup) and see what happens.
Otherwise I will just delete @ and reinstall Manjaro…

edit: choosing kernel 6.10 or 6.6 in grub doesn’t make a difference…

16

@Molski
The strange thing is that I do see the older snapshots in the timeshift and timeshift-btrfs folders. If I boot into the liveusb I can see them in the Timeshift gui, but clicking restore there doesn’t give me a bootable solution.

Good idea indeed to up the maxSnapshots. I will do that.

And yes, I prefer to not use the rsync but the btrfs snapshots of timesync exactly for the reason of the power of btrfs.
But now that I need it, it doesn’t work :frowning:
(well, let’s first see what happens if I delete some stuff from my @home, so I have > 10% diskspace, but I have a feeling it won’t make a difference)

17

When space is tight, nothing helps but more space :wink:

Have you already read the chapter on “out of space” in the wiki?

:footprints:

You seem to have 2 problems:

  • You are running out of disk space with btrfs (-- read the wiki to solve the problem)
  • Your system-update / kernel-change may have failed because of this (and you didn’t read the messages carefully enough to notice where this happened)
  • The update may be incomplete
  • A kernel may be missing or incomplete
  • The initramdisk may be missing or incomplete

Warning: So far the btrfs file system does not seem to be damaged. I would be careful to keep it that way.

Suggested procedure:

  1. Fix the out of space problem (This is described in detail in the wiki. This will take some time. But it is worth it.)

  2. Check if the kernel is there (can also be done while (1) is still running)

  • If necessary, reinstall the kernel (or better install a second kernel) (from chroot)
  • If necessary, repeat the update (from chroot)
  1. Regenerate the initrd to be on the safe side

All of this can be done from the live session. The btrfs file system must be mounted somewhere for all of these steps!

After step 3, reboot

:+1:

1 Like
18

lol
Well, I learned the 12.3GB free does not say everthing.
I am backupping and removing stuff from @home as we speak.

19

With btrfs you gain a lot of security (raid, checksums, CoW) and possibilities (snapshots, compression), but this requires that you treat btrfs the way this file system needs to be treated.

If you just treat it the way you would treat ext or fat, you can run into big problems.
:footprints:

1 Like
20

Ha, yes, that’s clear now indeed.
Thanks for pointing me there.
I am reading your [HowTo] get "out of space" with BTRFS now and Btrfs - Manjaro