Read only system

I have no idea what's going on but for some reason my computer keeps going into read-only a few minutes after I booed up my computer it'll work fine for a moment and then it'll just start screaming at me that it's read only and I can't do stuff I'm using Garuda dragonized gaming edition

  Kernel: 6.4.12-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=3c7e83b5-453b-495a-ae9f-4259e2aaf568 rw rootflags=subvol=@
    quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
  Desktop: KDE Plasma v: 5.27.7 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
    dm: SDDM Distro: Garuda Linux base: Arch Linux
  Type: Desktop Mobo: ASRock model: B450M Pro4 serial: <superuser required>
    UEFI-[Legacy]: American Megatrends v: P4.30 date: 07/14/2020
  Info: model: AMD Ryzen 5 2400G with Radeon Vega Graphics bits: 64
    type: MT MCP arch: Zen level: v3 note: check built: 2017-19 process: GF 14nm
    family: 0x17 (23) model-id: 0x11 (17) stepping: 0 microcode: 0x8101016
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB
    desc: 1x4 MiB
  Speed (MHz): avg: 2967 high: 3600 min/max: 1600/3600 boost: enabled
    scaling: driver: acpi-cpufreq governor: performance cores: 1: 3144 2: 2555
    3: 2553 4: 2769 5: 3192 6: 3600 7: 2954 8: 2970 bogomips: 57498
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
  Device-1: NVIDIA TU106 [GeForce RTX 2060 Rev. A] vendor: ASUSTeK
    driver: nvidia v: 535.104.05 alternate: nouveau,nvidia_drm non-free: 535.xx+
    status: current (as of 2023-08) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 8
    link-max: lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1f08 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.2.0
    compositor: kwin_x11 driver: X: loaded: modesetting,nvidia
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 81 s-size: 1204x343mm (47.40x13.50")
    s-diag: 1252mm (49.29")
  Monitor-1: HDMI-0 pos: primary,left res: 1920x1080 dpi: 81
    size: 600x340mm (23.62x13.39") diag: 690mm (27.15") modes: N/A
  Monitor-2: HDMI-1 pos: right res: 1920x1080 dpi: 82
    size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
  Monitor-3: None-1-1 size-res: N/A modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 535.104.05 renderer: NVIDIA GeForce RTX
    2060/PCIe/SSE2 direct-render: Yes
  Device-1: NVIDIA TU106 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
    link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f9 class-ID: 0403
  Device-2: AMD Family 17h/19h HD Audio vendor: ASRock driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 07:00.6
    chip-ID: 1022:15e3 class-ID: 0403
  Device-3: Corsair VOID ELITE Wireless Gaming Dongle
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 3-2:2 chip-ID: 1b1c:0a75 class-ID: 0300
  API: ALSA v: k6.4.12-zen1-1-zen status: kernel-api with: aoss
    type: oss-emulator tools: N/A
  Server-1: PipeWire v: 0.3.79 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
  Device-1: Intel Wireless 7265 driver: iwlwifi v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:095a class-ID: 0280
  IF: wlp4s0 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    port: e000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-8:3 chip-ID: 8087:0a2a
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: <filter> bt-v: 4.2 lmp-v: 8
    status: discoverable: no pairing: no
  Local Storage: total: 1.24 TiB used: 93.95 GiB (7.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Netac model: SSD 360GB
    size: 335.35 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 0A0 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: PNY model: CS900 1TB SSD
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 06B5 scheme: MBR
  ID-1: / raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
    used: 93.95 GiB (10.1%) fs: btrfs dev: /dev/sdb1 maj-min: 8:17
  ID-2: /home raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
    used: 93.95 GiB (10.1%) fs: btrfs dev: /dev/sdb1 maj-min: 8:17
  ID-3: /var/log raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
    used: 93.95 GiB (10.1%) fs: btrfs dev: /dev/sdb1 maj-min: 8:17
  ID-4: /var/tmp raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
    used: 93.95 GiB (10.1%) fs: btrfs dev: /dev/sdb1 maj-min: 8:17
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 15.54 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8 dev: /dev/zram0
  System Temperatures: cpu: 40.0 C mobo: N/A gpu: nvidia temp: 53 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
  Processes: 301 Uptime: 1m wakeups: 0 Memory: total: 16 GiB
  available: 15.54 GiB used: 3.36 GiB (21.6%) Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
  Packages: 1649 pm: pacman pkgs: 1639 libs: 482 tools: octopi,paru,yay
  pm: flatpak pkgs: 10 Shell: fish v: 3.6.1 default: Bash v: 5.1.16
  running-in: konsole inxi: 3.3.29
Garuda (2.6.16-1):
  System install date:     2023-08-27
  Last full system update: 2023-09-04
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       <superuser required>
  Failed units: 

Switch to a tty and do,

garuda-inxi | nc 9999

and also give us some logs.

journalctl -r -n 500 -b 0 | nc 9999

and post the link that is generated.

1 Like

I just received errors nothing else

were you perhaps not connected to internet? Use

sudo systemctl restart NetworkManager.service

To restart network manager and,


to connect to your wifi and then try the commands. If you still face errors please describe them.

1 Like

I most definitely was unless it was shut off somehow this is through my terminal after I rebooted my computer I've done it several times and it'll still go into read-only mode but I got a little bit of time

╭─valor@valor in ~
╰─λ garuda-inxi | nc 9999

╭─valor@valor in ~ took 5s
╰─λ journalctl -r -n 500 -b 0 | nc 9999

╭─valor@valor in ~ took 5s

Hmm... I actually wanted the logs after the system crashed so that we could diagnose what went wrong with it. The current logs only show conky was core dumped maybe because the "crash" hasn't happened when the logs were captured. How about this,

  1. start the system and wait for it to crash then reboot
  2. as soon as you reboot
journalctl -r -n 500 -b -1 | nc 9999

This should capture logs from the previous boot. The subtle difference of 0 and -1 tell the journalctl the boot offset to get logs from.

1 Like

So I don't know if it's crashing or what it just says it's read only but it works fine like my browser and stuff that's open I can use them just fine but if I try to download a file it says insufficient permissions and it's super weird

But yes I will attempt to do this then if that's still what's necessary

I just want the logs following the message that says you are in read-only mode. If you are able to access your teminal normally and able to get the logs after "the message" pops up.

journalctl -r -n 500 | xsel -i -b

This will copy your logs to your clip board then you can open your browser and using a pastebin service like

you can paste the logs there. I changed the commands since you said that you can't access termbin from terminal following the error message you get but are able to access and open browsers just fine.

Similarly, after the message saying you are in read mode pops up

sudo dmesg | xsel -i -b

and paste this to the pastebin service and generate the URL to share here.
would be nice too.


xsel: error opening logfile /home/valor/.cache/xsel.log for writing: Read-only file system

I simply get this error for both

I think I'm probably just going to reinstall it again I don't know what got f***** up but I did something

Hmm I sadly can’t help you a lot without any logs but you can try to look at these search results in case they help

Apart from why are you using legacy UEFI mode for booting? That could be a reason for your sudden crashes.

Also make sure that your device’s SATA controller is set to AHCI mode in your device’s setup utility aka UEFI menu. There have been a string of threads on forum lately that have been facing issues with their system because they hadn’t done this before.


I think you should its only a 7 day install and see if it persists :grinning:


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