Help, system still unstable after reinstall

Context:
https://discourse.nixos.org/t/help-nixos-kde-plasma-6-kept-crashing-and-freezing-even-in-tty/58425/32

After the reinstall, the system outputs the following message that caught my eye after I ran dmesg -w:

> [  461.314090] traps: .kwin_wayland-w[1352] trap int3 ip:7efc487a3a46 sp:7ffe0991f400 error:0 in libQt6Gui.so.6.8.1[3a3a46,7efc48531000+69d000]
> [  977.282526] crashreporter[7016]: segfault at 7ffd5878f500 ip 00007fc7782e0e06 sp 00007ffd5878f500 error 4 in librsvg-2.so.2.50.0[2e0e06,7fc7780b0000+380000] likely on CPU 5 (core 5, socket 0)
> [  977.282540] Code: 49 8b 06 49 29 c5 48 01 c3 4d 89 26 eb cc 66 0f 1f 44 00 00 55 41 57 41 56 41 55 41 54 53 48 81 ec 58 01 00 da bb 9b 07 2e 18 <59> f2 1e 86 59 73 4d e2 dd d1 8d 5c 24 38 48 c7 44 24 38 00 00 00

Basically, kde settings will crash sometimes after I open it and firefox will crash some time after I open it but inconsistent.
Furthermore, sometimes the system will be still running fine after boot but suddenly mouse and keyboard will stop working, re plug in does not help.

I will do a hardware test on Windows 11 soon with follow up.

I have done CPU tests on Windows 11 with no issues at all.

Please find my configuration.nix file below.

I would like to have some suggestions, please.

> { config, pkgs, lib, nix, ...}:
> 
> {
>   imports =
>     [ # Include the results of the hardware scan.
>       ./hardware-configuration.nix
>     ];
> 
>   # Bootloader.
>   boot.loader.systemd-boot.enable = true;
>   boot.loader.efi.canTouchEfiVariables = true;
> 
>   # Use newest linux kernel
>   boot.kernelPackages = pkgs.linuxPackages_latest;
> 
>   networking.hostName = "nixos"; # Define your hostname.
>   # networking.wireless.enable = true;  # Enables wireless support via wpa_supplicant.
> 
>   # Configure network proxy if necessary
>   # networking.proxy.default = "http://user:password@proxy:port/";
>   # networking.proxy.noProxy = "127.0.0.1,localhost,internal.domain";
> 
>   # Enable networking
>   networking.networkmanager.enable = true;
> 
>   # Set your time zone.
>   time.timeZone = "Asia/Shanghai";
> 
>   # Select internationalisation properties.
>   i18n.defaultLocale = "en_US.UTF-8";
> 
>   i18n.extraLocaleSettings = {
>     LC_ADDRESS = "zh_CN.UTF-8";
>     LC_IDENTIFICATION = "zh_CN.UTF-8";
>     LC_MEASUREMENT = "zh_CN.UTF-8";
>     LC_MONETARY = "zh_CN.UTF-8";
>     LC_NAME = "zh_CN.UTF-8";
>     LC_NUMERIC = "zh_CN.UTF-8";
>     LC_PAPER = "zh_CN.UTF-8";
>     LC_TELEPHONE = "zh_CN.UTF-8";
>     LC_TIME = "zh_CN.UTF-8";
>   };
> 
>   # Enable btrfs automatic scrubbing
>   services.btrfs.autoScrub.enable =true;
> 
>   # Setting up NixOS to correctly use AMD Graphics card
>   boot.initrd.kernelModules = [ "amdgpu" ];
>   services.xserver.videoDrivers = [ "amdgpu" ];
>   systemd.tmpfiles.rules = [
>     "L+    /opt/rocm/hip   -    -    -     -    ${pkgs.rocmPackages.clr}"
>   ];
> 
>   # Enable the X11 windowing system.
>   # You can disable this if you're only using the Wayland session.
>   services.xserver.enable = true;
> 
>   # Enable hardware graphics configuration
>   hardware.graphics.enable = true;
>   hardware.graphics.enable32Bit = true;
> 
>   # Enable the KDE Plasma Desktop Environment.
>   services.displayManager.sddm.enable = true;
>   services.displayManager.sddm.wayland.enable = true;
>   services.desktopManager.plasma6.enable = true;
>   services.displayManager.defaultSession = "plasma";
> 
>   # Configure keymap in X11
>   services.xserver.xkb = {
>     layout = "us";
>     variant = "";
>   };
> 
>   # Enable CUPS to print documents.
>   services.printing.enable = true;
> 
>   # Enable sound with pipewire.
>   hardware.pulseaudio.enable = false;
>   security.rtkit.enable = true;
>   services.pipewire = {
>     enable = true;
>     alsa.enable = true;
>     alsa.support32Bit = true;
>     pulse.enable = true;
>     # If you want to use JACK applications, uncomment this
>     #jack.enable = true;
> 
>     # use the example session manager (no others are packaged yet so this is enabled by default,
>     # no need to redefine it in your config for now)
>     #media-session.enable = true;
>   };
> 
>   # Enable touchpad support (enabled default in most desktopManager).
>   # services.xserver.libinput.enable = true;
> 
>   # Define a user account. Don't forget to set a password with β€˜passwd’.
>   users.users.sherlockxia = {
>     isNormalUser = true;
>     description = "SherlockXia";
>     extraGroups = [ "networkmanager" "wheel" ];
>   };
> 
>   # Enable automatic login for the user.
>   services.displayManager.autoLogin.enable = true;
>   services.displayManager.autoLogin.user = "sherlockxia";
> 
>   # Allow unfree packages
>   nixpkgs.config.allowUnfree = true;
> 
>   # Enable rocmSupport
>   nixpkgs.config.rocmSupport = true;
> 
>   # Change Nix channels
>   system.autoUpgrade.channel = "https://mirrors.tuna.tsinghua.edu.cn/nix-channels/nixos-24.11";
> 
>   # Change binaryCaches mirror
>   nix.settings.trusted-substituters = lib.mkForce ["https://mirror.sjtu.edu.cn/nix-channels/store"];
> 
>   # List packages installed in system profile. To search, run:
>   # $ nix search wget
> 
>   # Install extra fonts
>   fonts.packages = with pkgs; [
>     noto-fonts
>     noto-fonts-cjk-sans
>     noto-fonts-cjk-serif
>   ];
> 
>   environment.systemPackages = with pkgs; [
>     # Necessary AMD programs
>     rocmPackages.rocm-smi
>     rocmPackages.rocm-core
>     rocmPackages.rocm-runtime
>     rocmPackages.rocm-device-libs
>     rocmPackages.rocm-thunk
>     rocmPackages.rocminfo
>     rocmPackages.clr.icd
>     radeontop
>     radeontools
>     radeon-profile
>     # Necessary system optimization packages
>     nil
>     clinfo
>     gamemode
>     gamescope
>     steam
>     steam-unwrapped
>     steam-run
>     mesa
>     firefox
>     # btrfs tools
>     btrfs-snap
>     btrfs-heatmap
>     btrfs-assistant
>     btrfs-auto-snapshot
>     # Additional Terminal packages
>     ffmpeg_6
>     imagemagick
>     fastfetch
>     neovim
>     tmux
>     wget
>     cmus
>     btop
>     btop-rocm
>     fd
>     lf
>     fzf
>     zoxide
>     bat
>     delta
>     glow
>     tealdeer
>     tldr
>     gdb
>     # Additional KDE packages
>     kdePackages.kate
>     kdePackages.yakuake
>     kdePackages.kdevelop
>     kdePackages.kdenlive
>     kdePackages.partitionmanager
>     #Fcitx support
>     kdePackages.fcitx5-with-addons
>     kdePackages.fcitx5-configtool
>     kdePackages.fcitx5-chinese-addons
>     kdePackages.fcitx5-unikey
>     fcitx5
>     fcitx5-pinyin-zhwiki
>     libpinyin
>     # Additional packages
>     mpv
>     vlc
>     libreoffice
>     blender
>     gimp
>     krita
>     qbittorrent
>     ardour
>     gnucash
>     calibre
>     calibre-web
>     godot_4
>     musescore
>     rsync
>     bsync
>   ];
> 
>   #Garbage collection and optimisation
>   nix.optimise.automatic = true;
>   nix.gc.persistent = true;
>   nix.gc.dates = "weekly";
>   nix.gc.automatic = true;
> 
>   #Auto system upgrade
>   system.autoUpgrade.enable = false;
> 
>   # Some programs need SUID wrappers, can be configured further or are started in user sessions.
>   # programs.mtr.enable = true;
>   # programs.gnupg.agent = {
>   #   enable = true;
>   #   enableSSHSupport = true;
>   # };
> 
>   # List services that you want to enable:
> 
>   # Enable the OpenSSH daemon.
>   # services.openssh.enable = true;
> 
>   # Open ports in the firewall.
>   # networking.firewall.allowedTCPPorts = [ ... ];
>   # networking.firewall.allowedUDPPorts = [ ... ];
>   # Or disable the firewall altogether.
>   # networking.firewall.enable = false;
> 
> }

@TLATER
@NobbZ

I would like your opinion on my configuration file, please.
You can also find the dmesg error in the first post.
I do not know exactly what caused it, but if anyone can give me some debugging advice, I will be greatful. Thanks.

it would be alot easier to help you if you’d quit creating new threads for every problem, and include all relevant context as well as logs.

Im still thinking you have a damaged CPU windows is covering up for, the fact core 5 consistently dumps makes me think that.

1 Like

Do you have an intel 13. or 14. Gen?
If so download the intel diagnostic tool and see if you CPU passed or failed the test.
If it fails try to return it, because than it is most likely been affected by the microcode problem and
the cpu has been degraded over the time.
https://www.intel.com/content/www/us/en/download/15951/intel-processor-diagnostic-tool.html

I have an AMD Ryzen 9700X

@Mephist0phel3s

Okay, I will stop creating new threads and all future updates will be posted here.

I don’t know if I should be happy or confused.

The current session is strangely reliable with 0 crashes.
I even did a FurMark2 1080p benchmark with no errors produced from dmesg and journalctl.

Please find the results here: https://www.gpumagick.com/scores/show.php?id=698264

It has been a nightmare trying to debug the errors on my system because they are really inconsistent and possibly different on each boot.

Weeks ago people suggested Amdgpu error, then they suspect memory issue, then CPU issue.

In the last boot, the entire firesystem turned into read only mode and I was unable to save any modification of configuration.nix so I had to reboot from generation 2.

The only current journal logs that I can reproduce is from nixos plasmashell [1582] It always seems to suggest:

1月 16 16:52:42 nixos plasmashell[1582]: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce.
1月 16 16:52:42 nixos plasmashell[1582]: kf.windowsystem.wayland: Failed to recreate shadow for PlasmaQuick::AppletPopup_QML_158(0x1012e180, name=β€œpopupWindow”)
1月 16 16:52:42 nixos plasmashell[1582]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0

Edit 1: I also just tried btrfs scrubbing and it produced the following error messages.

[ 2566.556710] BTRFS warning (device nvme0n1p2): tree block 29111664640 mirror 1 has bad csum, has 0xe54d4
919 want 0xa053d371
[ 2566.556712] BTRFS error (device nvme0n1p2): unable to fixup (regular) error at logical 29111615488 on d
ev /dev/disk/by-uuid/e064f821-d0af-44d2-91e9-816795f39739 physical 17308844032

Edit 2: I have found the corrupted data, they are as follows, I am thinking about what to do with them

find: β€˜/nix/store/31bbzb0vywlsfps1m3mav15pphak8b2z-nixos-24.11/nixos/pkgs/tools/security/echidna’: Input/output error
find: β€˜/nix/store/31bbzb0vywlsfps1m3mav15pphak8b2z-nixos-24.11/nixos/pkgs/tools/security/firefox_decrypt’:Input/output error
find: β€˜/nix/store/31bbzb0vywlsfps1m3mav15pphak8b2z-nixos-24.11/nixos/pkgs/tools/security/lethe’: Input/output error
find: β€˜/nix/store/31bbzb0vywlsfps1m3mav15pphak8b2z-nixos-24.11/nixos/pkgs/tools/security/ghidra’: Input/output error

EDIT 3: I have went to the faulty directory and only echidna exists but cannot be opened or deleted.

Could you please provide more details of your system:
Which Specs
Which temps
How is your system partitioned (you mentioned you have windows installed, is it on the same drive?)
Which Versions are you on (Nix Version, Kernel Version, KDE Version, Compositor Version Gpu driver Version…)

@Postboote

          β–—β–„β–„β–„       β–—β–„β–„β–„β–„    β–„β–„β–„β––             sherlockxia@nixos
          β–œβ–ˆβ–ˆβ–ˆβ–™       β–œβ–ˆβ–ˆβ–ˆβ–™  β–Ÿβ–ˆβ–ˆβ–ˆβ–›             -----------------
           β–œβ–ˆβ–ˆβ–ˆβ–™       β–œβ–ˆβ–ˆβ–ˆβ–™β–Ÿβ–ˆβ–ˆβ–ˆβ–›              OS: NixOS 24.11.713159.9c6b49aeac36 (Vicuna) x86_64
            β–œβ–ˆβ–ˆβ–ˆβ–™       β–œβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–›               Host: SAPPHIRE PULSE B650M WIFI
     β–Ÿβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–™ β–œβ–ˆβ–ˆβ–ˆβ–ˆβ–›     β–Ÿβ–™         Kernel: Linux 6.12.9
    β–Ÿβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–™ β–œβ–ˆβ–ˆβ–ˆβ–™    β–Ÿβ–ˆβ–ˆβ–™        Uptime: 2 hours, 43 mins
           β–„β–„β–„β–„β––           β–œβ–ˆβ–ˆβ–ˆβ–™  β–Ÿβ–ˆβ–ˆβ–ˆβ–›        Packages: 1923 (nix-system)
          β–Ÿβ–ˆβ–ˆβ–ˆβ–›             β–œβ–ˆβ–ˆβ–› β–Ÿβ–ˆβ–ˆβ–ˆβ–›         Shell: bash 5.2.37
         β–Ÿβ–ˆβ–ˆβ–ˆβ–›               β–œβ–› β–Ÿβ–ˆβ–ˆβ–ˆβ–›          Display (27M2N5810): 3840x2160 @ 160 Hz (as 2194x1234) in 27[External]
β–Ÿβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–›                  β–Ÿβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–™    DE: KDE Plasma
β–œβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–›                  β–Ÿβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–›    WM: KWin (Wayland)
      β–Ÿβ–ˆβ–ˆβ–ˆβ–› β–Ÿβ–™               β–Ÿβ–ˆβ–ˆβ–ˆβ–›             WM Theme: Breeze
     β–Ÿβ–ˆβ–ˆβ–ˆβ–› β–Ÿβ–ˆβ–ˆβ–™             β–Ÿβ–ˆβ–ˆβ–ˆβ–›              Theme: Breeze (Dark) [Qt]
    β–Ÿβ–ˆβ–ˆβ–ˆβ–›  β–œβ–ˆβ–ˆβ–ˆβ–™           ▝▀▀▀▀               Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
    β–œβ–ˆβ–ˆβ–›    β–œβ–ˆβ–ˆβ–ˆβ–™ β–œβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–›         Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
     β–œβ–›     β–Ÿβ–ˆβ–ˆβ–ˆβ–ˆβ–™ β–œβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–›          Cursor: breeze (24px)
           β–Ÿβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–™       β–œβ–ˆβ–ˆβ–ˆβ–™                Terminal: .konsole-wrappe
          β–Ÿβ–ˆβ–ˆβ–ˆβ–›β–œβ–ˆβ–ˆβ–ˆβ–™       β–œβ–ˆβ–ˆβ–ˆβ–™               CPU: AMD Ryzen 7 9700X (16) @ 5.58 GHz
         β–Ÿβ–ˆβ–ˆβ–ˆβ–›  β–œβ–ˆβ–ˆβ–ˆβ–™       β–œβ–ˆβ–ˆβ–ˆβ–™              GPU 1: AMD Radeon RX 7900 XT [Discrete]
         ▝▀▀▀    β–€β–€β–€β–€β–˜       β–€β–€β–€β–˜              GPU 2: AMD Radeon Graphics [Integrated]
                                               Memory: 4.15 GiB / 46.17 GiB (9%)
                                               Swap: 0 B / 8.80 GiB (0%)
                                               Disk (/): 22.36 GiB / 1.81 TiB (1%) - btrfs
                                               Local IP (wlp8s0): 192.168.2.17/24
                                               Locale: en_US.UTF-8

nvme1n1 is windows drive
nvme0n1 is nixOS drive

NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
nvme1n1     259:0    0  1.8T  0 disk 
β”œβ”€nvme1n1p1 259:2    0  100M  0 part 
β”œβ”€nvme1n1p2 259:3    0   16M  0 part 
β”œβ”€nvme1n1p3 259:4    0  1.8T  0 part 
└─nvme1n1p4 259:5    0  704M  0 part 
nvme0n1     259:1    0  1.8T  0 disk 
β”œβ”€nvme0n1p1 259:6    0  512M  0 part /boot
β”œβ”€nvme0n1p2 259:7    0  1.8T  0 part /home
└─nvme0n1p3 259:8    0  8.8G  0 part [SWAP]

Pardon if this is a dumb question, but have you ruled out the drive being bad? If you have separate drives for both os’s but the Linux drive is borked, it wouldn’t reflect on your windows drive. This would also explain why CPU or memory intense tasks don’t produce consistent results as well as the input/output errors specifically

We’ve ruled out the thumb drive, the iso, the board, proc, memory, and DE already. There ain’t much left to debug here


Just scanned the drive through Victoria. There is 0 bad blocks.

I am going to try running nixOS again today, if it ever crashes once, I will wipe the drive and install Linux Mint to see if it ran fine.

1 Like

I have tried everything to solve the error.

[sherlockxia@nixos:~]$ sudo nix-collect-garbage -d
removing old generations of profile /nix/var/nix/profiles/per-user/root/channels
removing old generations of profile /nix/var/nix/profiles/system
removing old generations of profile /nix/var/nix/profiles/per-user/root/channels
finding garbage collector roots…
deleting garbage…
deleting β€˜/nix/store/31bbzb0vywlsfps1m3mav15pphak8b2z-nixos-24.11’
1 store paths deleted, 0.00 MiB freed
error: opening directory β€˜β€œ/nix/store/31bbzb0vywlsfps1m3mav15pphak8b2z-nixos-24.11/nixos/pkgs/tools/securi
ty/echidna”’: Input/output error

[sherlockxia@nixos:~]$ sudo nix-store --repair-path /nix/store/31bbzb0vywlsfps1m3mav15pphak8b2z-nixos-24.1
1/nixos/pkgs/tools/security
error: path β€˜/nix/store/31bbzb0vywlsfps1m3mav15pphak8b2z-nixos-24.11’ is not valid

None works, anyone had any good ideas?

When you try another distro make sure that you have the same Versions.
If you than have the same issues in this distro there is maybe a Version problem

https://www.reddit.com/r/linuxquestions/comments/1edaoa2/input_output_error/

The internet and my own experience both agree that this is def a hardware issue, of some sort.
If this isnt a dead drive or a partially dead CPU, there MUST be something you are doing different from the rest of us if its not in fact the SSD or CPU as we’ve tested.
(this needs to be mentioned, but it COULD be an intermittent drive read error although its not likely)

Lets go deep.

Give a dump of your entire config, i know your doing some security stuff so if you’ve got anything you need to redact no worries, go ahead just try not to strip config options if possible. You can exclude the users section though.

Also get a dump of your dmesg on a fresh boot, entire thing.
Get a dump of the last 30,000 lines of journal
Put both into a https://pastebin.com/
Lastly, get a dump of your hardware state. Use hw-probe
Create a probe
TLDR:

nix-shell -p hw-probe
sudo -E hw-probe -all -upload

this will return a link to linux-hardware.org with your hardware state

Share this link with us

Hello everyone, this will be the last update on this thread because …

I have reinstalled NixOS for the third time and this time it ran without any issues!

No random errors, no core dump, no crashing, no freezing. Nothing.

I believe that there is a couple of reasons that might contribute to the success.

  1. I properly configured hardware-configuration.nix during installation this time.
    After generating config, I checked hardware-configuration.nix and most of the mount options such as compression, swap device path, noatime for /nix, umask=0077 for boot are all not there. Thus, I manually typed them in there.
    I accidentally discovered this by accident because I forgot to give /nix noatime.

  2. I removed the following options in my configuration.nix from the get go.

I have read a blog post about nix.optimise,automatic = true being possibly dangerous. Please find the blog below.

https://realjenius.com/2023/07/21/corrupt-store/

Since btrfs auto scrubbing and nix garbage collection were running in the background, it is possible for them to corrupt the file systems when they just happend to get cought in a system freeze or crash. Who knows what will happen to the system with their unfinished jobs next time during boot.
In the previous installation of NixOS, I believe that garbage collection or something might have messed up my /Nix and the damage was not fixable. I literally tried everything to fix the I/O error but nothing worked. Yep, that is how bad it is.

Therefore, I now believe that any btrfs scrubbing and nix garbage collection should be done manually and system snapshots should be created prior to any clean up activities. Hopefully the snapshots are able to fix up any file corruption after a serious crash.

  1. nixos-install and nixos-rebuild switch should be ran smoothly without frequent interruption. If the rebuild process did not finish, do not do garbage collection.
1 Like

Btrfs would still detect corruption on boot, and recover from the journal. People realized that random failures cause filesystem issues some 40 years ago and did something about it. Nix’ garbage collection can result in your database and actual files not agreeing, which can result in the confusing errors from that blog post; however, restoring the store is usually just as easy as mentioned in the blog post. I’ve also heard of hairy database corruption, but this is clearly not the case here.

Your case is different. If you set a quota with btrfs, that’s the error you’ll get if you try to delete stuff when it’s full. I think this is more likely to have been a filesystem misconfiguration than random bugs.

Btrfs scrub should be totally harmless unless btrfs itself is fundamentally broken; you probably should run it. Garbage collection isn’t such a big deal, you can just do it manually, but watch out that you never hit your quota if you use btrfs quotas. If you do hit them, you have to unset the quota, do the garbage collect, and then re-set it.

Thanks for your reply. I have never set any quotas for btrfs because I didn’t get to do it before the crash.

Like I have said, my case is really weird because all the previous errors were inconsistent. Amdgpu error, memory core dump error, file corruption error. It is really hard to diagnose what the issues are and it is really painful having to reinstall the system.

Anyways, the system is running fine now.

1 Like

Ive been chewing on it for a while and the only thing that all those parts + the os have in common, the motherboard.

Your mobo chipset might be dying or the board might be dirty.

Might be worth cracking the case open and taking an hour or so to closely inspect your mobo for signs of damage or dirt on traces that could be blocking signal.

Its also probably not a bad idea to get the sensors for the mobo working (if possible) and pull temps from the chipset and any other spots that have temps and see if they are higher than normal.

Its really the only thing ive been able to think of that even sort of halfway makes sense, you got signs of drive failure, CPU core damage, RAM bullshit but none from your mobo because it normally doesnt talk to you. Your mobo might be borked and returning shit data, probably worth updating UEFI/BIOS if it needs it. Might be a bug?

Probably worth just sitting it out if it works now. If there are any issues with the hardware they’ll show up on their own time. I’d just make sure to keep backups (not just btrfs snapshots) of anything important and move on for now.

The installation process seems to have been tricky, and it’s @SherlockXia 's first time with btrfs, so in all likelyhood the most recent install just was finally actually correct and functional :slight_smile:

Very possible, it took me about 6 solid attempts to finally get an NVMe RAID0 array on BTRFS done right since the wiki is… incomplete to be diplomatic.
There are alot of opportunities to mash the wrong key in that process. This was actually the main reason i suggested reading the BTRFS wiki and man page thoroughly and repeatedly. BTRFS is tricky compared to ext4