zustellr

I stand corrected. Wow. Never thought RAM could get bad so quickly. Flashed memtest to another stick, booted, and get a ton of errors in the first pass. Removed the two old modules (2022 May). Now running with the newly purchased ones and got no error yet. Thanks for insisting on doing the memtest!

Hi Trurl. Please see my original post. I tried. Really tried. Still no idea why the thing I downloaded from memtest86 did not work. Tried with different USB drives.

Hi Jorge. The diagnostics zip is quite large. I ran into quite a few problems with people posting logsfiles in public forums, without realising that they had some stuff that should not be posted, and me having to "clean up" the mess. Hope you understand my issues with going this route. No disrespect to the people who built this function, but without checking the file, I would have a very bad feeling to post it publicly. I would be okay to send it to a specific person (preferably at Lime). And thanks in advance for offering to check the config.

Hi, I've been using Unraid for quite a while. Never had a severe issue. All fine. Recently, I wanted to create another VM, but failed. Weird BTRFS errors every time I created the machine. Even the boot ISO got corrupted. I also noticed that I started to get errors on docker containers. Which I did not really see before. Not sure if it was the update to 6.12. Not sure if it was another config change I did with the machine. It got weirder over the next hours, with RCU_preempt CPU stalls, native_queue_spinlock_slowpath errors... strange stuff. If I switch off docker and vms, the machine is rock solid. If I switch docker back on, btrfs on the ssd starts to have issues. tested again today by just running one jellyfin docker. After an hour, the log said Oct 30 10:07:52 unraid kernel: BTRFS warning (device dm-9): csum failed root 5 ino 72988 off 14955741184 csum 0xcbb64ed6 expected csum 0x2cd71eff mirror 1 Oct 30 10:07:52 unraid kernel: BTRFS error (device dm-9): bdev /dev/mapper/sdm1 errs: wr 0, rd 0, flush 0, corrupt 95, gen 0 I already bought a new ssd and changed the adapter the ssd is connected to. And I have a hard time believing that anything else would just wear and tear suddenly. So I would like to check if it's a software problem (maybe self-inflicted) before digging into hardware diagnosis. As my docker containers and the VMs are anyway corrupted beyond repair, I would like to test if a "clean" 6.11 would behave the same way. Can I just create a 6.11 usb, copy /config/super.dat and /config/shares and boot from that? I would guess that should get me to a usable state with not much tweaks. Correct? From there, I would just create a new VM and see, if it also behaves badly. If so, I would continue to check for hardware errors. Any comment would be appreciated. Especially ones that would point me to things breaking or potential data loss if I go ahead with my plan. Thanks! andreas. P.S.: Not sure if this is important, but all my drives are encrypted (xfs for spinning disks, btrfs for ssds). P.P.S.: I read a ton a posts. The typical first response to such issues seems to do a memtest. Tried that. The memtest included in unraid is not willing to boot in my board. The memtest I downloaded from the original site did not boot either. Gave up after trying several times.