Read only home folder when booting a snapshot

zany130 · 22 March 2024 17:21

when booting into a snapshot I get some kde errors complaining that it cant write to its config files and the desktop never loads. It seems this user had the same issue How to solve this error in Garuda kde plasma ( attempt to write a readonlydatabase

but didn’t provide any specifics

so basically what happens is after booting the snapshot I am presented with a bunch of kde error messages that say attempt-to-write-a-readonlydatabase and the rest of the desktop never loads

eventually the restore snapshot prompt does appear and once I restore the snapshot and reboot everything is fine.

garuda-inxi
System:
  Kernel: 6.8.1-3-cachyos arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-linux
    root=UUID=8a69f047-feee-46cf-81a1-d299eb173883 rw rootflags=subvol=@
    rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
    sysrq_always_enabled=1 mitigations=off amd_pstate=active
    amdgpu.ppfeaturemask=0xffffffff tsc=reliable clocksource=tsc nowatchdog
    nmi_watchdog=0 initrd=@\boot\initramfs-linux-cachyos.img
  Desktop: KDE Plasma v: 6.0.2 tk: Qt v: N/A info: frameworks v: 6.0.0
    wm: kwin_wayland with: krunner vt: 1 dm: SDDM Distro: Garuda
    base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: X470 Taichi serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends v: P5.10
    date: 10/20/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 3
    serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 2 microcode: 0xA20120A
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
    L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 3868 high: 4576 min/max: 550/4687 scaling:
    driver: amd-pstate-epp governor: performance cores: 1: 3658 2: 3656 3: 4573
    4: 3653 5: 3657 6: 3661 7: 3658 8: 3695 9: 4576 10: 3657 11: 4316 12: 3667
    bogomips: 88815
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
    vendor: Gigabyte driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
    process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
    lanes: 16 ports: active: DP-1,HDMI-A-2 empty: DP-2,HDMI-A-1,Writeback-1
    bus-ID: 10:00.0 chip-ID: 1002:73df class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.4
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu d-rect: 3584x1728 display-ID: 0
  Monitor-1: DP-1 pos: bottom-r res: 2048x864 size: N/A modes: N/A
  Monitor-2: HDMI-A-2 pos: primary,top-left res: 1536x864 size: N/A
    modes: N/A
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.3-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6700 XT (radeonsi
    navi22 LLVM 17.0.6 DRM 3.57 6.8.1-3-cachyos) device-ID: 1002:73df
    memory: 11.72 GiB unified: no display-ID: :0.0
  API: Vulkan v: 1.3.279 layers: 23 device: 0 type: discrete-gpu name: AMD
    Radeon RX 6700 XT (RADV NAVI22) driver: mesa radv v: 24.0.3-arch1.1
    device-ID: 1002:73df surfaces: xcb,xlib,wayland device: 1 type: cpu
    name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
    v: 24.0.3-arch1.1 (LLVM 17.0.6) device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 10:00.1 chip-ID: 1002:ab28
    class-ID: 0403
  Device-2: Sony INZONE H9 / H7
    driver: cdc_acm,hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 5-2:3 chip-ID: 054c:0e53
    class-ID: 0a00
  API: ALSA v: k6.8.1-3-cachyos status: kernel-api with: aoss
    type: oss-emulator tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.4 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 Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 08:00.0
    chip-ID: 8086:24fb class-ID: 0280
  IF: wlp8s0 state: down mac: <filter>
  Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 0a:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp10s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
  Info: services: NetworkManager, smbd, sshd, systemd-timesyncd
Bluetooth:
  Device-1: Edimax Bluetooth Adapter driver: btusb v: 0.8 type: USB rev: 1.1
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1.4.2:8 chip-ID: 7392:c611
    class-ID: e001 serial: <filter>
  Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.1
    lmp-v: 10 status: discoverable: yes pairing: yes class-ID: 6c0104
Drives:
  Local Storage: total: 3.64 TiB used: 3.98 TiB (109.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
    model: WD BLACK SN770 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 731120WD temp: 34.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Samsung model: SSD 980 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 3B4QFXO7 temp: 35.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DX002-2DV164
    size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC41 scheme: GPT
Partition:
  ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 796.51 GiB (85.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 44.3 MiB (14.8%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 796.51 GiB (85.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 796.51 GiB (85.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 796.51 GiB (85.5%) 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: 31.26 GiB used: 1.62 GiB (5.2%)
    priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 63.5 C mobo: 34.0 C gpu: amdgpu temp: 40.0 C
    mem: 38.0 C
  Fan Speeds (rpm): cpu: 2356 fan-1: 0 fan-3: 1306 fan-4: 1311 fan-5: 1509
    gpu: amdgpu fan: 0
  Power: 12v: N/A 5v: N/A 3.3v: 3.23 vbat: 3.28 gpu: amdgpu watts: 9.00
Info:
  Memory: total: 32 GiB available: 31.26 GiB used: 12.84 GiB (41.1%)
  Processes: 541 Power: uptime: 21m states: freeze,mem,disk suspend: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume
    image: 12.49 GiB services: org_kde_powerdevil, power-profiles-daemon,
    upowerd Init: systemd v: 255 default: graphical tool: systemctl
  Packages: 2819 pm: pacman pkgs: 2774 libs: 632 tools: octopi,paru,yay
    pm: appimage pkgs: 0 pm: flatpak pkgs: 45 Compilers: clang: 17.0.6
    gcc: 13.2.1 Shell: garuda-inxi default: fish v: 3.7.0
    running-in: alacritty inxi: 3.3.33
Garuda (2.6.23-1):
  System install date:     2024-01-11
  Last full system update: 2024-03-20
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:

NaN · 23 March 2024 03:44

Try adding,

GRUB_BTRFS_SNAPSHOT_KERNEL_PARAMETERS="rd.live.overlay.overlayfs=1"

To /etc/default/grub

And run,

sudo update-grub

Try booting into snapshots and see if this helps?

zany130 · 23 March 2024 19:49

Nope still gives errors when I boot a snapshot

Sorry for the bad quality had to take it with my phone since I can’t write to disk can’t Even get a journal

K0shVorlon · 24 March 2024 00:28

It looks like either, the /home/zany130 is chowned by a different account than the one you log in with (i.e: may be owned by root and you log in as a non-root account, which is the right way to operate, but I digress…) OR your system may be mounting as read-only (which is unlikely as your garuda-inxi shows your boot image parameter has rw enabled, however, it may be mounting that way due to a percieved error. I’ve had that issue in FreeBSD and Linux.)

I’d check the /var/logs for clues ( /var/log/Xorg.0, Xorg.old) and dmesg .

zany130 · 24 March 2024 00:34

The strange thing is that it ONLY happens when booting a snapshot. When booting normally, I don’t have any issues with my home partition.

will try to see if I can find something in dmesg and pipe it into a paste bin service (actually didn’t think about that before)

zany130 · 24 March 2024 02:33

Here is my Journal

and her is my dmesg
both from taken after booting a snapshot

I see a ton of errors there (most of them seem to be because of the read only home partition) but I also see systemd-remount-fs.service failed which could be linked?

BluishHumility · 24 March 2024 17:57

Try creating a new snapshot and see if you are able to boot to it normally.

NaN · 24 March 2024 18:03

If nothing else works try a,

garuda-update remote reset-snapper

as a last resort. It will remove all backup subvolumes and snapshots created by Snapper, and force reset snapper configs.

Then try creating a new snapshot manually and boot into it and see if it works?

Oh btw, to register new snapshots as grub entries to boot into you need to perform,

sudo update-grub

These changes won’t be reflected in grub otherwise.

K0shVorlon · 24 March 2024 20:28

@zany130 I don’t claim to be a kernel expert by any means, but it looks like Linux can’t mount your system. It tries, using the following command:

Mar 23 22:12:19 Garuda-Linux kernel: Command line: BOOT_IMAGE=/@/.snapshots/1899/snapshot/boot/vmlinuz-linux-cachyos root=UUID=8a69f047-feee-46cf-81a1-d299eb173883 loglevel=3 sysrq_always_enabled=1 amd_pstate=active amdgpu.ppfeaturemask=0xffffffff tsc=reliable clocksource=tsc nowatchdog nmi_watchdog=0 ibt=off rd.live.overlay.overlayfs=1 rootflags=defaults,noatime,compress=zstd,subvol=@/.snapshots/1899/snapshot

However, Linux doesn’t think this is a valid parameter:
Mar 23 22:12:19 Garuda-Linux kernel: Kernel command line: BOOT_IMAGE=/@/.snapshots/1899/snapshot/boot/vmlinuz-linux-cachyos root=UUID=8a69f047-feee-46cf-81a1-d299eb173883 loglevel=3 sysrq_always_enabled=1 amd_pstate=active amdgpu.ppfeaturemask=0xffffffff tsc=reliable clocksource=tsc nowatchdog nmi_watchdog=0 ibt=off rd.live.overlay.overlayfs=1 rootflags=defaults,noatime,compress=zstd,subvol=@/.snapshots/1899/snapshot
Mar 23 22:12:19 Garuda-Linux kernel: sysrq: sysrq always enabled.
Mar 23 22:12:19 Garuda-Linux kernel: Unknown kernel command line parameters “BOOT_IMAGE=/@/.snapshots/1899/snapshot/boot/vmlinuz-linux-cachyos”, will be passed to user space.

Seems to me something about the snapshot set the mount command incorrectly. Since it’s a snapshot, I’d agree with @BluishHumility and create a new snapshot, but I’d take a look at how it’s being created first to make sure the correct mount point is being given.

NaN · 24 March 2024 22:04

Don’t worry that’s a message you can ignore. I have it too and so does everyone else using GRUB.

Mar 19 22:21:34 siddharth kernel: Kernel command line: BOOT_IMAGE=/@hypr/boot/vmlinuz-linux-clear root=UUID=e0a08d20-208f-444a-a6f0-281ffd8a1e1b rw rootflag>
Mar 19 22:21:34 siddharth kernel: DMAR: Disable GFX device mapping
Mar 19 22:21:34 siddharth kernel: Unknown kernel command line parameters "BOOT_IMAGE=/@hypr/boot/vmlinuz-linux-clear", will be passed to user space.
Mar 19 22:21:34 siddharth kernel: random: crng init done

BOOT_IMAGE is an obsolete command line parameter that GRUB and LILO pass to kernel. From what I read online it was meant for the init system.

https://www.linuxquestions.org/questions/slackware-14/unknown-kernel-command-line-parameters-boot_image%3D-boot-vmlinuz-5-15-36-a-4175711814%2F

K0shVorlon · 24 March 2024 22:16

Shukria @NaN Like I said, I don’t claim to be an expert or anything. I have had a system or two mount as read-only due to incorrect parameters, obviously not this one .

zany130 · 28 March 2024 00:22

Try creating a new snapshot and see if you are able to boot to it normally.

I still get a read-only home partition error when booting that new snapshot

If nothing else works try a,
garuda-update remote reset-snapper

EDIT: NVM was an issue with grub not updating to the new snapshots Should have realized it when it was showing old snapshots (I installed a package after the reset to create a new snapshot and I thought that would update grub for me)

After doing this I get this error when trying to boot snapshots

tried the default kernel (zen) and the lts kernel and got the same error

I still get problems with the home partition being read only however

system · 11 April 2024 00:22

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