I need help configuring garuda kde Dr4gonized gaming edition to play well with a software raid 0 (btrfs or mdadm)

Issues & Assistance
,
1

When I first installed Garuda KDE dr4gonized gaming edition, I followed a guide to do manual partitioning and using a btrfs raid 0 for / mount point, this worked well, was beautifully fast, and was stable for a long time until I got hit with a stupid issue due to a qt bug (see this post Garuda kde dr4gonised graphical glitches leading to crashed programs in some cases). After this was resolved I had more time enjoying this wonderful setup. more recently, my system suddenly became unbootable claiming a btrfs problem straight out of grub, I couldn’t boot from any snapshots or even mount the volume in a live environment.

20240807_232040
20240807_2320401920Ă—749 155 KB

Researching this error lead me up a few garden paths that ultimately proved fruitless. I discovered that it could be a result of bad firmware on some of my drives, so I went through the hell of putting windows on this pc for the first time to use samsung disk magician to update the firmware and check the drives for problems advised in multiple youtube videos and various websites/forum posts regarding the samsung 980 pro 2tb nvme drives (amongst other models with a similar problem). I then did a clean install of garuda in the same manner I had done before. This time the btrfs raid 0 self-destructed after 1 or 2 updates and a reboot. At this point I snapped, went with a single drive for /efi/boot and /, the aim being to create a btrfs raid 0 with the remaining 4 ssds to house my games library. This self-destructed after an update again. Using a virtual machine and passing through the NVME drives to run samsung disk magician software, I found the drives had no problems, and the firmware was correct on all 4 of the drives I had used for the btrfs raid 0. And that brings us to today, please, please tell me what I need to do differently to have that lovely large raid array to run with either a 4 disk or 5 disk raid 0 array that won’t self destruct randomly after an update.

Please note, after each failure of the raid 0 array, the array became unmountable.

here is my current garuda-inxi:

System:
  Kernel: 6.10.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=bd10dd0b-5dbe-41bd-9e59-7eef259d26c8 rw rootflags=subvol=@
    quiet loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.1.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
  Mobo: ASUSTeK model: ROG CROSSHAIR VIII EXTREME v: Rev X.0x
    serial: <filter> part-nu: SKU uuid: a3a29ff7-4204-061a-4258-04421a064257
    UEFI: American Megatrends v: 1505 date: 03/18/2024
CPU:
  Info: model: AMD Ryzen 9 5950X socket: AM4 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: 0 microcode: 0xA20102B
  Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache:
    L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 8 MiB desc: 16x512 KiB
    L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 3400 min/max: 2200/5083 boost: enabled
    base/boost: 3400/5050 scaling: driver: acpi-cpufreq governor: performance
    volts: 1.1 V ext-clock: 100 MHz cores: 1: 3400 2: 3400 3: 3400 4: 3400
    5: 3400 6: 3400 7: 3400 8: 3400 9: 3400 10: 3400 11: 3400 12: 3400
    13: 3400 14: 3400 15: 3400 16: 3400 17: 3400 18: 3400 19: 3400 20: 3400
    21: 3400 22: 3400 23: 3400 24: 3400 25: 3400 26: 3400 27: 3400 28: 3400
    29: 3400 30: 3400 31: 3400 32: 3400 bogomips: 217615
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA GA102 [GeForce RTX 3090] driver: nvidia v: 555.58.02
    alternate: nouveau,nvidia_drm non-free: 550.xx+ status: current (as of
    2024-06; EOL~2026-12-xx) arch: Ampere code: GAxxx process: TSMC n7 (7nm)
    built: 2020-2023 pcie: gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 4
    speed: 16 GT/s lanes: 16 ports: active: none off: DP-3
    empty: DP-1,DP-2,HDMI-A-1 bus-ID: 44:00.0 chip-ID: 10de:2204
    class-ID: 0300
  Display: unspecified server: X.Org v: 24.1.2 with: Xwayland v: 24.1.2
    compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
    display-ID: :1 screens: 1
  Screen-1: 0 s-res: 5120x1440 s-dpi: 96 s-size: 1355x381mm (53.35x15.00")
    s-diag: 1408mm (55.42")
  Monitor-1: DP-3 note: disabled model: Samsung C49RG9x serial: <filter>
    built: 2018 res: 5120x1440 hz: 120 dpi: 109 gamma: 1.2
    size: 1193x336mm (46.97x13.23") diag: 1239mm (48.8") modes: max: 3840x1080
    min: 640x480
  API: EGL v: 1.5 platforms: device: 1 drv: swrast surfaceless: drv: swrast
    x11: drv: swrast inactive: gbm,wayland,device-0
  API: OpenGL v: 4.5 vendor: mesa v: 24.1.6-arch1.1 note: incomplete (EGL
    sourced) renderer: llvmpipe (LLVM 18.1.8 256 bits)
  API: Vulkan Message: No Vulkan data available.
Audio:
  Device-1: NVIDIA GA102 High Definition Audio driver: snd_hda_intel v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 44:00.1 chip-ID: 10de:1aef class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 48:00.4 chip-ID: 1022:1487
    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: 7-5:3
    chip-ID: 0b05:1a27 class-ID: 0300
  API: ALSA v: k6.10.6-zen1-1-zen 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.2.3 status: n/a (root, process) 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 Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 3f:00.0
    chip-ID: 8086:2725 class-ID: 0280
  IF: wlp63s0 state: up mac: <filter>
  Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 40:00.0
    chip-ID: 8086:15f3 class-ID: 0200
  IF: enp64s0 state: down mac: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 7-2:2 chip-ID: 8087:0032
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
    lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
  Local Storage: total: 60.03 TiB used: 99.83 GiB (0.2%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 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: 5B2QGXA7 temp: 49.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 71 hrs cycles: 274
    read-units: 11,915,587 [6.10 TB] written-units: 5,998,577 [3.07 TB]
  ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Samsung model: SSD 980 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: 5B2QGXA7 temp: 45.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 46 hrs cycles: 207
    read-units: 11,321,942 [5.79 TB] written-units: 4,660,218 [2.38 TB]
  ID-3: /dev/nvme2n1 maj-min: 259:6 vendor: Samsung model: SSD 980 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: 5B2QGXA7 temp: 47.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 70 hrs cycles: 262
    read-units: 11,612,966 [5.94 TB] written-units: 6,375,348 [3.26 TB]
  ID-4: /dev/nvme3n1 maj-min: 259:5 vendor: Samsung model: SSD 980 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: 5B2QGXA7 temp: 43.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 73 hrs cycles: 262
    read-units: 11,880,964 [6.08 TB] written-units: 6,408,090 [3.28 TB]
  ID-5: /dev/nvme4n1 maj-min: 259:4 vendor: Samsung model: SSD 980 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: 5B2QGXA7 temp: 42.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 73 hrs cycles: 261
    read-units: 11,852,429 [6.06 TB] written-units: 6,452,130 [3.30 TB]
  ID-6: /dev/sda maj-min: 8:0 vendor: Toshiba model: HDWR21E family: X300
    size: 12.73 TiB block-size: physical: 4096 B logical: 512 B sata: 3.3
    speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter> fw-rev: 0601
    temp: 45 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 325d 19h cycles: 1162
  ID-7: /dev/sdb maj-min: 8:16 vendor: Toshiba model: HDWG21E
    family: N300/MN NAS HDD size: 12.73 TiB block-size: physical: 4096 B
    logical: 512 B sata: 3.3 speed: 6.0 Gb/s tech: HDD rpm: 7200
    serial: <filter> fw-rev: 0601 temp: 42 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 51d 22h cycles: 261
  ID-8: /dev/sdc maj-min: 8:32 vendor: Toshiba model: HDWG21E
    family: N300/MN NAS HDD size: 12.73 TiB block-size: physical: 4096 B
    logical: 512 B sata: 3.3 speed: 6.0 Gb/s tech: HDD rpm: 7200
    serial: <filter> fw-rev: 0601 temp: 41 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 51d 22h cycles: 261
  ID-9: /dev/sdd maj-min: 8:48 vendor: Toshiba model: HDWR21E family: X300
    size: 12.73 TiB block-size: physical: 4096 B logical: 512 B sata: 3.3
    speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter> fw-rev: 0601
    temp: 44 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 51d 20h cycles: 261
Partition:
  ID-1: / raw-size: 1.82 TiB size: 1.82 TiB (100.00%) used: 99.83 GiB (5.4%)
    fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 584 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
    maj-min: 259:1
  ID-3: /home raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
    used: 99.83 GiB (5.4%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
    maj-min: 259:2
  ID-4: /var/log raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
    used: 99.83 GiB (5.4%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
    maj-min: 259:2
  ID-5: /var/tmp raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
    used: 99.83 GiB (5.4%) fs: btrfs block-size: 4096 B 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: 125.68 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 32 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 51.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 128 GiB available: 125.68 GiB used: 7.6 GiB (6.0%)
  Processes: 545 Power: uptime: 1h 36m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 50.23 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 2049 libs: 585 tools: octopi,paru Compilers:
    clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi (sudo) default: Bash v: 5.2.32
    running-in: konsole inxi: 3.3.35
Garuda (2.6.26-1):
  System install date:     2024-08-18
  Last full system update: 2024-08-27 ↻
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       No/Undetected
  Failed units:            nmb.service

Thankyou for taking the time to read this and any subsequent assistance^^

2

If you can describe the way you are setting it up (so we have some information about what is not working), that would be a useful starting point.

3

sorry, long day. I boot the live environment, I use the terminal to create fat 32 partition for /efi/boot, when using swap, I create a swap partition equal to that of my ram, I make a btrfs partition using the remaining space on nvme0n1, next I use

sudo mkfs.btrfs -f /dev/nvme1n1 
sudo mkfs.btrfs -f /dev/nvme2n1
sudo mkfs.btrfs -f /dev/nvme3n1
sudo mkfs.btrfs -f /dev/nvme4n1
sudo mkfs.btrfs -l games -d raid0 -m raid0 -f /dev/nvme0n1p2 /dev/nvme1n1 /dev/nvme2n1 /dev/nvme3n1 /dev/nvme4n1

then I launch the installer, go through the normal process but choosing manual partitioning, and selecting the appropriate mount points for the efi partition and the / partition, then set the installer going. the install is successful, a reboot is required ofcourse, the storage media is removed, garuda boots, I go through the process of setting it up through setup assistant.

reboot after the update.

I install my games and software via steam, lutris, heroic, etc. I haven’t got as far as setting up the emulation side of things, as I was still reformating my game backups in the latest and greatest format for their relevant emulators (.chd for ps2 games for example).

My initial raid0 setup was fine for quite a while. Then wasn’t. The wife wanted me to play “Once Human” with her. I started seeing weird behaviour after exiting that game, trying to remember the order of things here. I was forced into doing a hard reboot after the 2nd session. ran a scrub and a balance through btrfs assistant, and a system update via garuda-assistant. left it for quite a while after the update before I restarted the system. when I restarted the system I got that lovely error screen straight out of grub iirc.

I tried to mount the volume from a live environment only to be thwarted, afraid I forget the error message exactly but something along the lines of “the partiton could not be mounted”.

I trawled the internet for the error message (and one other I received subsequently after many boot attempts), attempted something I read in a forum post on how to repair the log tree. This ran for over 7 days in terminal in a live environment. at this point I did a little more research, and realised that it was taking far too long, and it was beyond salvation via that method. I then started to wonder if there was something wrong with the hardware, because the installation I had before the first installation I mentioned in my op had a drive fail entirely and stop showing up in bios. I figured there must be something wrong with them if the same symptons are showing up in the same brand and model and capacity of drive again. did my research, attempted to use a boot usb image from samsung to update the firmware, this bugged out and failed spectacularly, attempted to follow a guide that dictated a method to use that image from a live environment to update the firmware, this didn’t work for some reason. Forced to installed windows 10 to put the new firmware on the drives with samsung’s windows utility, and do a full diagnostic scan on them all to be certain. Redid what I did for installation before, got to an entirely different error screen coming out of grub that unfortunately I didn’t take a photo of at the time. I vaguely remember it complaining about not being able to read the root partition after coming out of grub. very busy month at work, I’m sad to say I was exhausted when I got to that point. and decided to separate the raid 0 from OS drive as described above.
Finer details on my current install. I created a btrfs raid 0 array using nvme1n1-4n1, added the uuid and defaults to /etc/fstab like so

UUID=7f39813d-4d7f-4ec1-aa5c-29c91d323909   /home/tco/Games2   btrfs   defaults                        0 0

when this array failed to mount suddenly, I commented out the line from /etc/fstab, became occupied by unrelated matters and finally got round to posting all this.

please let me know if I need to add more information, unfortunately some of it I probably just don’t have =/

4

The plot thickens…
After recreating the btrfs raid0 separate from the single drive that the garuda btrfs partition occupies, I added the newly created volume to fstab, restarted my pc and set up a steam library on there. I downloaded my library over the last couple of days and ran a game from it. The game had a weird problem and wouldn’t launch after I exited it for the second time. I tried a few proton versions, but the game would not launch.
I then tried to launch any game, nothing would launch. I then tried restarting the system via the menu button. The result was that the system hung on the loading zram disk. Then brought me to that error screen, so I commented out the appropriate line from fstab, rebooted, and had to force power off since the motherboard hung on “loading vga bios”. I then booted up, mounted the volume in dolphin, which worked compared to last time. I uncommented the appropriate line in fstab and rebooted. Things seem back to normal now. Games launch and run from my btrfs raid0 again. So, not solved, but…
Dirty solution found I guess.

5

As far as I can tell, the way you are setting up the RAID looks fine. It sounds like it has been pretty unstable though, unless the RAID is a red herring and your system has some other kind of issue. Off the top of my head, I would say these three things would be at least worth testing if you haven’t yet:

  • Try switching to the LTS kernel and see if you run into any of these same issues. There were a lot of Btrfs kernel changes the last couple releases, and at least a few RAID-related ones. It is possible a regression was introduced somewhere.
  • Instead of using Btrfs RAID, try setting up an ordinary mdadm RAID array and put Btrfs on top of it. RAID - ArchWiki
  • If you run into issues with both of those setups, try running your system without any RAID at all to see if there is some other underlying issue, not related to RAID which is responsible for the strange behavior coming out of games and so on.
1 Like
6

not to ignore what you are saying here, but since I hit the symptoms again today,
I tried using sudo mount -a right after it happened, it through up an error message like this:

mount: /home/tco/Games2: wrong fs type, bad option, bad superblock on /dev/nvme2n1, missing codepage or helperprogram, or other error.
dmesg(1) may have more information after failed mount system call.

This lead me lead me to to do sudo dmsg -H which produced tons of lines, so I decided to do sudo dmsg -H > dmsgoutput.txt I’ve been looking through it, and while I don’t claim to fully understand everything I read through, I used the find function in kate to look through the file for the term nvme, and this looks quite relevant to me:

[  +0.036058] nvme nvme2: D3 entry latency set to 10 seconds
[  +0.463385] nvme nvme2: 32/0/0 default/read/poll queues
[Sep 5 20:24] nvme nvme2: I/O tag 738 (e2e2) QID 3 timeout, disable controller
[  +0.212789] I/O error, dev nvme2n1, sector 1633757216 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 0
[  +0.000009] BTRFS error (device nvme1n1): bdev /dev/nvme2n1 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0
[  +0.000015] I/O error, dev nvme2n1, sector 1633757504 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 0
[  +0.000003] BTRFS error (device nvme1n1): bdev /dev/nvme2n1 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0
[  +0.000005] I/O error, dev nvme2n1, sector 1633757568 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 0
[  +0.000002] BTRFS error (device nvme1n1): bdev /dev/nvme2n1 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0
[  +0.000001] BTRFS: error (device nvme1n1) in btrfs_commit_transaction:2505: errno=-5 IO failure (Error while writing out transaction)
[  +0.000004] I/O error, dev nvme2n1, sector 1633857536 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 0
[  +0.000001] BTRFS error (device nvme1n1 state E): bdev /dev/nvme2n1 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0
[  +0.000001] BTRFS info (device nvme1n1 state E): forced readonly
[  +0.000002] BTRFS warning (device nvme1n1 state E): Skipping commit of aborted transaction.
[  +0.000002] BTRFS error (device nvme1n1 state EA): Transaction aborted (error -5)
[  +0.000001] I/O error, dev nvme2n1, sector 1633887872 op 0x1:(WRITE) flags 0x1800 phys_seg 6 prio class 0
[  +0.000001] BTRFS: error (device nvme1n1 state EA) in cleanup_transaction:1999: errno=-5 IO failure
[  +0.000002] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0
[  +0.000006] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0
[  +0.000005] I/O error, dev nvme2n1, sector 1633888544 op 0x1:(WRITE) flags 0x1800 phys_seg 10 prio class 0
[  +0.000003] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0
[  +0.000006] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0
[  +0.000005] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0
[  +0.000005] I/O error, dev nvme2n1, sector 1633906240 op 0x1:(WRITE) flags 0x1800 phys_seg 8 prio class 0
[  +0.000003] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 11, rd 0, flush 0, corrupt 0, gen 0
[  +0.000008] I/O error, dev nvme2n1, sector 1633909216 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 0
[  +0.000005] I/O error, dev nvme2n1, sector 1633945440 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 0
[  -0.000001] I/O error, dev nvme2n1, sector 1633823872 op 0x1:(WRITE) flags 0x101000 phys_seg 8 prio class 0
[  +0.000259] nvme nvme2: failed to mark controller live state
[  +0.000003] nvme nvme2: Disabling device after reset failure: -19
[ +31.341744] IoService: attempt to access beyond end of device
              nvme2n1: rw=524288, sector=888030464, nr_sectors = 128 limit=0
[  +0.000078] PoolThread 28: attempt to access beyond end of device
              nvme2n1: rw=524288, sector=887597312, nr_sectors = 128 limit=0
[  +0.009044] PoolThread 28: attempt to access beyond end of device
              nvme2n1: rw=0, sector=887597312, nr_sectors = 8 limit=0
[  +0.000006] btrfs_dev_stat_inc_and_print: 22 callbacks suppressed
[  +0.000002] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 1, flush 0, corrupt 0, gen 0
[  +0.003148] IoService: attempt to access beyond end of device
              nvme2n1: rw=0, sector=888030464, nr_sectors = 8 limit=0
[  +0.000004] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 2, flush 0, corrupt 0, gen 0
[  +0.000042] IoService: attempt to access beyond end of device
              nvme2n1: rw=0, sector=888030464, nr_sectors = 8 limit=0
[  +0.000002] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 3, flush 0, corrupt 0, gen 0
[  +0.000011] IoService: attempt to access beyond end of device
              nvme2n1: rw=0, sector=888030464, nr_sectors = 8 limit=0
[  +0.000002] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 4, flush 0, corrupt 0, gen 0
[  +0.000028] IoService: attempt to access beyond end of device
              nvme2n1: rw=0, sector=888030464, nr_sectors = 8 limit=0
[  +0.000002] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 5, flush 0, corrupt 0, gen 0
[  +0.000010] IoService: attempt to access beyond end of device
              nvme2n1: rw=0, sector=888030464, nr_sectors = 8 limit=0
[  +0.000001] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 6, flush 0, corrupt 0, gen 0
[  +0.000028] IoService: attempt to access beyond end of device
              nvme2n1: rw=0, sector=888030464, nr_sectors = 8 limit=0
[  +0.000001] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 7, flush 0, corrupt 0, gen 0
[  +0.000015] IoService: attempt to access beyond end of device
              nvme2n1: rw=0, sector=888030464, nr_sectors = 8 limit=0
[  +0.000002] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 8, flush 0, corrupt 0, gen 0
[  +0.000036] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 9, flush 0, corrupt 0, gen 0
[  +0.000016] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 10, flush 0, corrupt 0, gen 0
[Sep 5 20:26] input: Microsoft X-Box 360 pad 0 as /devices/virtual/input/input16
[  +1.154168] bio_check_eod: 62 callbacks suppressed
[  +0.000004] CJobMgr::m_Work: attempt to access beyond end of device
              nvme2n1: rw=4096, sector=386891136, nr_sectors = 32 limit=0
[  +0.000005] btrfs_dev_stat_inc_and_print: 55 callbacks suppressed
[  +0.000001] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 66, flush 0, corrupt 0, gen 0
[  +0.000030] CJobMgr::m_Work: attempt to access beyond end of device
              nvme2n1: rw=4096, sector=386891168, nr_sectors = 32 limit=0
[  +0.000002] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 67, flush 0, corrupt 0, gen 0
[  +0.000016] CJobMgr::m_Work: attempt to access beyond end of device
              nvme2n1: rw=4096, sector=386891136, nr_sectors = 32 limit=0
[  +0.000002] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 68, flush 0, corrupt 0, gen 0
[  +0.000011] CJobMgr::m_Work: attempt to access beyond end of device
              nvme2n1: rw=4096, sector=386891168, nr_sectors = 32 limit=0
[  +0.000002] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 69, flush 0, corrupt 0, gen 0
[  +0.000244] CJobMgr::m_Work: attempt to access beyond end of device
              nvme2n1: rw=4096, sector=386891136, nr_sectors = 32 limit=0
[  +0.000003] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 70, flush 0, corrupt 0, gen 0
[  +0.000012] CJobMgr::m_Work: attempt to access beyond end of device
              nvme2n1: rw=4096, sector=386891168, nr_sectors = 32 limit=0
[  +0.000002] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 71, flush 0, corrupt 0, gen 0
[  +0.000016] CJobMgr::m_Work: attempt to access beyond end of device
              nvme2n1: rw=4096, sector=386891136, nr_sectors = 32 limit=0
[  +0.000002] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 72, flush 0, corrupt 0, gen 0
[  +0.000008] CJobMgr::m_Work: attempt to access beyond end of device
              nvme2n1: rw=4096, sector=386891168, nr_sectors = 32 limit=0
[  +0.000002] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 73, flush 0, corrupt 0, gen 0
[  +0.000037] CJobMgr::m_Work: attempt to access beyond end of device
              nvme2n1: rw=4096, sector=386891136, nr_sectors = 32 limit=0
[  +0.000003] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 74, flush 0, corrupt 0, gen 0
[  +0.000009] CJobMgr::m_Work: attempt to access beyond end of device
              nvme2n1: rw=4096, sector=386891168, nr_sectors = 32 limit=0
[  +0.000002] BTRFS error (device nvme1n1 state EA): bdev /dev/nvme2n1 errs: wr 34, rd 75, flush 0, corrupt 0, gen 0
[Sep 5 20:29] BTRFS info: devid 1 device path /dev/disk/by-uuid/bd10dd0b-5dbe-41bd-9e59-7eef259d26c8 changed to /dev/nvme0n1p2 scanned by mount (231589)

I will attempt to get the raid0 to a mountable state, back up the files and try switching to the lts kernel. I don’t want to have to re-download my steam library again^^; 4tb takes ages^^;