ChiefSpoonS

OH MY GOD. I think i figured it out... and its hilariously stupid and annoying. I had moved over to an RJ45 SFP+ port on my switch to get 2.5Gb transfers....Put back to a regular Gig port...and everything is fine. @JorgeB Any UNRAID issue as to why this would be the case? UNRAID did see the 2.5 connection - im guessing maybe fault SFP+ port

@JorgeB Any thoughts? installed new MOBO - Same issue, Tried each single stick of ram only. Same issue. On Unraid Support suggestion, I backed up my Unraid OS USB. Using the same USB i did a fresh install of UNRAID 7.0.1. Copied over the key, Super.dat, and the pools folder & Template folder for Docker. Same issue. Created a test share on the Cache Drive, Created a testarray share on the array. I can write to both Shares, I can copy between the shares. I can not Read/Copy any data from any of the Shares. (Original, Test, testarray) Any ideas? Along with new mobo, I also got a new PSU which didn't help. I'm not against trying a new/RMA 5800x3D, or new RAM - but it feels like a software issue. I have done this with all the suggest Ryzen Fixes and without (since it was previously working without them)

I've got a replacement PSU showing up in the AM. Thank you Amazon.

Update: I took my NVME drive out, plugged it into a other motherboard with Ryzen 7950x3D. Took the USB for unraid out and plugged it into my other computer. I plugged in all the Array drives and everything booted perfectly fine. I was able to transfer files w.o issue. I RMAd my Mobo expecting it to fix my issue. No luck. Created another new USB, only copied over my Array config, license, and docker setups. No luck there. I'm at a loss, unless it's some how ram or CPU or PSU issue.

Sata Cables did not help, Swapped all 5. Currenting running through Prime95 - but its been running for 10 minutes currently and everything is still working. Dropped down to 1 Stick of Ram (even though MEM test for 24 hours was 100% pass. Still have GPU plugged in, after all the CPU stress test is done I'll try without it.

gonna see if I have any Sata cables laying around - i'd need 5 lol

yeah thats how I have it setup, Write to cache, then in the morning hours a Schedule for Mover to kick off. I manually it to ensure that file transfer to the array wouldn't crash it. I do have my Plex Docker offline - just so no one tries to access it while im troubleshooting. But sitting idle for hours or using SAB/Radarr/sonarr hasn't trigger the issue. It was utilizing Plex or moving a file off the array.

Assuming that's was sufficient- I pulled a 4GB file and a 75GB file. Wrote to Cache then moved to Array w.o issues Server is still up and running.

If you can tell me how I can do that I can try. I can trigger a download from SAB, it would right to CACHE then to the array - that should suffice right?

I'm currently running a Long run Mem Test to validate my hardware is still good. I have been doing additional testing. I have since tried the following. Updated BIOS back to latest bios (no issues this update). MACVlan to IPVLAN, back to MACvlan again. Disable Global C-State Low Power idle Disabled PBO Curve +4 and +6 due to Ryzen and Linux Kernel issues. (https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173) No RAM XMP Profile. Used the Tips and Tweaks plugin to set Flow Control to OFF and NIC Offload to OFF Setting each Container to only use 10 GB Disabling all Containers - keeping the Array running and transfer data to another network device Tried setting rcu_nocbs on the syslinux config Tried adding ppcie_aspm=off The issue seems to be an I/O issues but i don't understand what's causing it from the Bios standpoint. Everything is running fine until you have to start utilizing the disk. I believe that, because As mentioned I can disable the Dockers - and just try doing a File transfer of a large file and it INSTANTLY freezes up. For the logs I attached above - the server Was powered on, as soon as I could connect to the WEBGUI I did a file transfer and it froze. I walked back to my Unraid Tower, Rebooted via the Command line since this is working for me still. when it came back up i pulled these logs. Any thoughts on BIOS that would impact I/O stuff?

Also so - it could have been because my NVidia card never had drivers installed via the plugin - it could be causing it. So i added the plugin - binhex-Plex sees it (i think) still crashing. latest diagnostics I just don't get it - its been rock solid since April 2023 houndtower-diagnostics-20250401-1453.zip

Also tried adding this to my /boot/config/go file /usr/local/sbin/zenstates --c6-disable Seemed to last longer but ended up crashing as well

Did all that except for 1 part here: https://wiki.archlinux.org/title/Ryzen#Random_reboots Install the amd-ucode package to enable microcode updates and enable it with the help of the Microcode page. These updates provide bug fixes that can be critical to the stability of your system. It is highly recommended to use it despite it being proprietary. Is that important too? Either i did something wrong - or my unraid install is jacked, it could install it

So i've done the following. Original Bios Latest BioS macvlan vs ipvlan C-state Disable Low Power Idle Disabled PBO Curve +4 & +6 No RAM XMP profile Digging through the web for others who had similar issues

Didn't help going back to the BIOS - i could try going back to MACVLAN vs IPVLAn?