Fastcompjason

I just found this post and had replied to a similar post (linked). I have been testing my RAM and have tested before without any errors reporting at all. I am also running an AMD Ryzen 9 3900X system on MSI X570 Prestige Creation mobo with 32GB (4 sticks of) G.Skill F43600-C16-8GVKC. I built this system back in late 2019 and it was running perfectly for a long time then I started having issues after some BIOS updates and updating unRaid. I am unsure now if I can backdate to an earlier BIOS revision and I am unsure of the version that I was most stable with. Also, one of the benefits i was looking forward to with the newer BIOS revisions was the better (more separated) IOMMU groups for VMs and other uses. I am curious if you are still running that same system and if you could help with any information about what "fixed" your issues. Thanks.

I am seeing some of these issues and blow is a snippet of my last error log and ends with the last entry as it died. I have been battling unraid stability for a far number of months and thought that maybe I was out of the woods with all of my problems but I fear not. Attached is my full log for my current BTRFS issue (error log with 11 hours uptime) and I was not able to get diagnostics as the system just completely locks up and is not reachable by the network and also will not respond to keyboard input if I plug a keyboard into it when it is in the locked up state. I have seen others on here always want to run to memory issues but I have seen that for many things and I have run memory tests a bunch and never come across any errors found. I have been chasing several issues and the other error log is after my previous crash where the system was totally unresponsive but that uptime was an awesome 32 days! (some of my runtimes have been as little as minutes and a few hours!!!) Last bit of error log: Jul 2 07:03:20 Cherry-Pit kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=10 block=642957312 slot=13, bad key order, prev (10376293541768855552 56 281472971966618) current (315621376 200 8388608) Jul 2 07:03:20 Cherry-Pit kernel: BTRFS info (device nvme0n1p1): leaf 642957312 gen 20047767 total ptrs 33 free space 7010 owner 10 Jul 2 07:03:20 Cherry-Pit kernel: item 0 key (206569472 200 8388608) itemoff 16027 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 1 key (214958080 200 8388608) itemoff 15771 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 2 key (223346688 200 8388608) itemoff 15515 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 3 key (231735296 200 8388608) itemoff 15259 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 4 key (240123904 200 8388608) itemoff 15003 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 5 key (248512512 200 8388608) itemoff 14747 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 6 key (256901120 200 8388608) itemoff 14491 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 7 key (265289728 200 8388608) itemoff 14235 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 8 key (273678336 200 8388608) itemoff 13979 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 9 key (282066944 200 8388608) itemoff 13723 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 10 key (290455552 200 8388608) itemoff 13467 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 11 key (298844160 200 8388608) itemoff 13211 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 12 key (10376293541768855552 56 281472971966618) itemoff 12955 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 13 key (315621376 200 8388608) itemoff 12699 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 14 key (324009984 200 8388608) itemoff 12443 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 15 key (332398592 200 8388608) itemoff 12187 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 16 key (340787200 200 8388608) itemoff 11931 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 17 key (349175808 200 8388608) itemoff 11675 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 18 key (357564416 200 8388608) itemoff 11419 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 19 key (365953024 200 8388608) itemoff 11163 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 20 key (374341632 200 8388608) itemoff 10907 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 21 key (382730240 200 8388608) itemoff 10651 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 22 key (391118848 200 8388608) itemoff 10395 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 23 key (399507456 200 8388608) itemoff 10139 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 24 key (407896064 200 8388608) itemoff 9883 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 25 key (416284672 200 8388608) itemoff 9627 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 26 key (424673280 200 8388608) itemoff 9371 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 27 key (433061888 200 8388608) itemoff 9115 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 28 key (441450496 200 8388608) itemoff 8859 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 29 key (449839104 200 8388608) itemoff 8603 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 30 key (458227712 200 8388608) itemoff 8347 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 31 key (466616320 200 8388608) itemoff 8091 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: item 32 key (475004928 200 8388608) itemoff 7835 itemsize 256 Jul 2 07:03:20 Cherry-Pit kernel: BTRFS error (device nvme0n1p1): block=642957312 write time tree block corruption detected Jul 2 07:03:20 Cherry-Pit kernel: BTRFS: error (device nvme0n1p1) in btrfs_commit_transaction:2494: errno=-5 IO failure (Error while writing out transaction) Jul 2 07:03:20 Cherry-Pit kernel: BTRFS info (device nvme0n1p1: state E): forced readonly Jul 2 07:03:20 Cherry-Pit kernel: BTRFS warning (device nvme0n1p1: state E): Skipping commit of aborted transaction. Jul 2 07:03:20 Cherry-Pit kernel: BTRFS: error (device nvme0n1p1: state EA) in cleanup_transaction:1992: errno=-5 IO failure Jul 2 07:03:22 Cherry-Pit kernel: loop: Write error at byte offset 2628378624, length 4096. Jul 2 07:03:22 Cherry-Pit kernel: I/O error, dev loop2, sector 5133552 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2 Jul 2 07:03:22 Cherry-Pit kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Jul 2 07:03:23 Cherry-Pit kernel: loop: Write error at byte offset 82739200, length 4096. Jul 2 07:03:23 Cherry-Pit kernel: I/O error, dev loop2, sector 161600 op 0x1:(WRITE) flags 0x1800 phys_seg 2 prio class 2 Jul 2 07:03:23 Cherry-Pit kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 Jul 2 07:03:23 Cherry-Pit kernel: loop: Write error at byte offset 351174656, length 4096. Jul 2 07:03:23 Cherry-Pit kernel: I/O error, dev loop2, sector 685888 op 0x1:(WRITE) flags 0x1800 phys_seg 2 prio class 2 Jul 2 07:03:23 Cherry-Pit kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 Jul 2 07:03:23 Cherry-Pit kernel: loop: Write error at byte offset 83017728, length 4096. Jul 2 07:03:23 Cherry-Pit kernel: I/O error, dev loop2, sector 162144 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 2 Jul 2 07:03:23 Cherry-Pit kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0 Jul 2 07:03:23 Cherry-Pit kernel: loop: Write error at byte offset 351453184, length 4096. Jul 2 07:03:23 Cherry-Pit kernel: I/O error, dev loop2, sector 686432 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 2 Jul 2 07:03:23 Cherry-Pit kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0 Jul 2 07:03:23 Cherry-Pit kernel: loop: Write error at byte offset 83050496, length 4096. Jul 2 07:03:23 Cherry-Pit kernel: I/O error, dev loop2, sector 162208 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 2 Jul 2 07:03:23 Cherry-Pit kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0 Jul 2 07:03:23 Cherry-Pit kernel: loop: Write error at byte offset 351485952, length 4096. Jul 2 07:03:23 Cherry-Pit kernel: I/O error, dev loop2, sector 686496 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 2 Jul 2 07:03:23 Cherry-Pit kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0 Jul 2 07:03:23 Cherry-Pit kernel: loop: Write error at byte offset 83263488, length 4096. Jul 2 07:03:23 Cherry-Pit kernel: I/O error, dev loop2, sector 162624 op 0x1:(WRITE) flags 0x1800 phys_seg 2 prio class 2 Jul 2 07:03:23 Cherry-Pit kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0 Jul 2 07:03:23 Cherry-Pit kernel: loop: Write error at byte offset 351698944, length 4096. Jul 2 07:03:23 Cherry-Pit kernel: I/O error, dev loop2, sector 686912 op 0x1:(WRITE) flags 0x1800 phys_seg 2 prio class 2 Jul 2 07:03:23 Cherry-Pit kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0 Jul 2 07:03:23 Cherry-Pit kernel: loop: Write error at byte offset 83558400, length 4096. Jul 2 07:03:23 Cherry-Pit kernel: I/O error, dev loop2, sector 163200 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Jul 2 07:03:23 Cherry-Pit kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0 Jul 2 07:03:23 Cherry-Pit kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2494: errno=-5 IO failure (Error while writing out transaction) Jul 2 07:03:23 Cherry-Pit kernel: BTRFS info (device loop2: state E): forced readonly Jul 2 07:03:23 Cherry-Pit kernel: BTRFS warning (device loop2: state E): Skipping commit of aborted transaction. Jul 2 07:03:23 Cherry-Pit kernel: BTRFS: error (device loop2: state EA) in cleanup_transaction:1992: errno=-5 IO failure Jul 2 07:03:27 Cherry-Pit kernel: lo_write_bvec: 49 callbacks suppressed Jul 2 07:03:27 Cherry-Pit kernel: loop: Write error at byte offset 2647875584, length 4096. Jul 2 07:03:27 Cherry-Pit kernel: blk_print_req_error: 49 callbacks suppressed Jul 2 07:03:27 Cherry-Pit kernel: I/O error, dev loop2, sector 5171632 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jul 2 07:03:27 Cherry-Pit kernel: btrfs_dev_stat_inc_and_print: 49 callbacks suppressed Jul 2 07:03:27 Cherry-Pit kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 60, rd 0, flush 0, corrupt 0, gen 0 Jul 2 08:36:35 Cherry-Pit webGUI: Successful login user root from 192.168.1.168 Jul 2 08:36:43 Cherry-Pit kernel: device br0 left promiscuous mode Jul 2 08:36:43 Cherry-Pit kernel: veth042f39b: renamed from eth0 Jul 2 08:37:29 Cherry-Pit monitor: Stop running nchan processes syslog from Cherry-Pit 2024-07-02 (Uptime 11 Hours).txt syslog from Cherry-Pit 2024-07-01 (Uptime 32 days).txt

I too have been recently puzzled by my GPU not working at all for transcoding. I have searched and came across this thread (with others pointing to it) and made the change to add the " --runtime=nvidia" to the EXTRA-PARAMETERS line (and have yet to test that this actually made it work yet), but did notice this warning (highlighted in Yellow below) in the console output after I made the change (I'm guessing that I just didn't notice this warning before). I have 32GB of RAM but notice before that if i let the container float with availablity to all RAM of the system that sometimes I could fill it up and it would crash the system. So I decided to limit it to 16GB and I never noticed this warning before. I recently have been having my system just die randomly and I am trying to track down what is causing it. Has anyone seen this issue before and I thought that this used to work (at least in previous Unraid versions)? " -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web/index.html' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/plex-logo.png' -v '/mnt/user/Media/TV/':'/tv':'rw' -v '/mnt/user/Media/Movies/':'/movies':'rw' -v '/dev/shm':'/transcode':'rw' -v '/mnt/disks/Plex/appdata/plex/':'/config':'rw' --runtime=nvidia --gpus all,capabilities=video --log-opt max-size=1m --log-opt max-file=1 --memory=16g 'lscr.io/linuxserver/plex' WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. 8388ca9751b2a1154aff24ff5355b240c21bdff2ae561ea4f469c3717f7c54ef The command finished successfully! "

I know that this seemed like am almost dead post (issue), but I have also been experiencing this issue and I have latest BIOS "MSI PRESTIGE X570 CREATION (MS-7C36), BIOS 1.M0 10/14/2023". I have had this system running for a few YEARS now and only recently (last few months) have been having SEVERE system stability issues. I recently enabled the syslog mirror to USB and found that my last system crash (last week) had these following lines as the last entries in the log before it powered itself down. Mar 24 08:32:12 Cherry-Pit kernel: mce: [Hardware Error]: Machine check events logged Mar 24 08:32:12 Cherry-Pit kernel: [Hardware Error]: Corrected error, no action required. Mar 24 08:32:12 Cherry-Pit kernel: [Hardware Error]: CPU:0 (17:71:0) MC25_STATUS[-|CE|MiscV|-|-|-|-|CECC|-|-|-]: 0x98004000003e0000 Mar 24 08:32:12 Cherry-Pit kernel: [Hardware Error]: IPID: 0x000100ff03830400 Mar 24 08:32:12 Cherry-Pit kernel: [Hardware Error]: Platform Security Processor Ext. Error Code: 62 Mar 24 08:32:12 Cherry-Pit kernel: [Hardware Error]: cache level: RESV, tx: INSN Does anyone have anything to help me get to a fix for this? Thanks in advance

I too am having a recent issue where nVidia HW transcoding used to work perfect, but recently I have been troubleshooting system issues and now that I think I have my system stable I have noticed that my Plex container will NOT use the nVidia GPU at all for transcoding and will only transcode video at all if I disable the option in Plex setting for using HW transcoding if available (then it will fall back to CPU transcoding). I like the previous poster have the same green info (different specific GPU of course) in the Nvidia info section of the nVidia driver settings option page in UNraid but when I have the plex setting enabled for "Use hardware acceleration when available" and "Use hardware-accelerated video encoding" Plex will NOT transcode at all and just sits there with a black player screen and no usage of either CPU or GPU (as shown in GPU statistics on the Dashboard of Unraid). What am I missing? To my knowledge I haven't had any changes to the docker edit settings (advanced) for anything and especially didn't change anything for GPU arguments. Can someone spot an issue? One strange thing is that in the nVidia driver settings page, I see that it shows " latest: v550.40.07 Production Branch: Not found for this unRAID version!" (I am on Unraid 6.12.6)

I am running Unraid 3.9.2 and I have a Ryzen 3900x with X570 chipset on the MSI Prestige Creation Mobo. I have never been able to get the CPU temps to show up in my Unraid since I built this server over a year ago. I realize that there have been improvements to the BIOS (which my mobo is on latest BIOS as of August 2021. How can I get my temps to show up? I want to make sure that my system is running cool enough. Is it something to do with BIOS options for CPU control like the other user mentioned above? Is there any documented settings that are known to work / not work that I can check? I thought that Unraid 6.9 was supposed to fix the issues with the Ryzen temps not showing?