reggienaz

I think I figured it out, I disabled dynamix cache directories and discs stopped constant reads and writes and have stayed spun down with docker and vms disabled. Hope this helps anyone trying to troubleshoot this. These were my settings when cache directories was enabled with 128gb of ram.

Today I took the time to try both of these methods. Downloaded 6.11.5 zip, swapped bz files, made bootable. Didn't/couldn't format drives when setting the new config up on 6.11.5 because of single disc zfs in array and zfs pools (all array and pool devices) so perhaps the new config never really started since the array never really started? Updated back to rc3 and still no spin down. Tried downgrade again without new config and then upgraded back to rc3 still no spin down. Currently array started on rc3, no smb, nfs, or external access. Docker and vm service disabled. Still getting constant reads and writes on all discs that hold data, much more reads and writes on the drive containing more data(50% capacity segate exos18tb vs 3%same drive). Interestingly enough backup server running zfs on all array and pool devices spins down perfectly after a new build and fresh install of Unraid directly to rc3. infinity-diagnostics-20230427-1344.zip

Happy to share any logs, diagnostics, or follow any troubleshooting tips that might help. Im spinning up a backup server so i can offload/backup all the data on this one. But in the mean time fingers crossed for RC4 or figuring out the root cause 😀

Still the same on RC3. I thought it was zfs doing its checksums and checks in the background

I've been experiencing this since rc2 with zfs. If I manually spin down disk 1 and 2 spin back up immediately even with docker service and vm disabled. Constant read and writes even with smb disabled.

From my limited research support for our sensors and chips with Ryzen 7000 should be added in a future Linux version, and as Uraid gets updated hopefully we get working sensors again. This might apply more specifically to ASUS motherboards for reasons I cant fully articulate, but something to do with the way ASUS handles superIO chip communication.

Uptime has gotten a lot better. Im still running 0705 bios and im tempted to upgrade to 0805. Logs are filling at a rapid rate sometimes more than other times causing the need to reboot before they fill up ram. The fastest ive seen the logs fill is probably around 72 hours but on the high end ive probably gone 14 days before the need to reboot. infinity-diagnostics-20230103-1514.zip infinity-syslog-20230103-2021.zip

Your symptoms are pretty much identical to the crashes I was experiencing. Try and make sure expo/XMP on memory is disabled. For my motherboard there is a tab called Ai Tweaker, and there I had to turn off performance enhancement as well as turning off expo/XMP on bios homepage. The description for that option said something along the lines of automatically overclocking RAM and CPU for more performance. Given the way ryzen 7000 automatically tries to run the fastest stable timings for ram, this seemed like the culprit to me. Linux from what I understand doesn't pair very well with overclocked ram.

Updated from bios 0611 to 0705 last night. Others here might find this interesting, but there is no longer a bios option for "Power Supply Idle Control" where on the previous bios revision there was. Also tried searching "idle" and ASUS bios reports no settings, so It would seem at least on this motherboard and bios combo there's no longer a Power Supply Idle Control setting. I left c states in default this time, and currently my plan is if there is still instability to be found I'm going to change one setting at a time for the future of the Unraid community. Going on 15 hours right now of uptime on new bios and default settings. Fingers are also crossed that bios improved stability and I'll never have experience an unexpected reboot again 😅

I could see this being related to the issue. My reboots have stopped, and I didn't make other changes. Today I re-enabled c states fingers crossed it remains stable. But I am running dual GPU one for ML and heavier tasks and an old GTX960 for lighter tasks.

Currently going on about 20hours of runtime with docker enabled. Disabled c states in bios as well as disabling all forms of overclocking other than PBO curve optimizer. Previously had memory set to default non XMP/EXPO but realized there are multiple auto overclock settings auto enabled that mention CPU and memory. Ryzen 7000 integrates a lot of power saving features from the mobile Ryzen 6000 so I'm going to try and narrow down which of these changes made this happen.

It could be hardware I guess with a 1-week-old system. Brand-new processor + new bios, chipset, and 4 sticks of DDR5 Om going to tinker and change a few things. I'll disable c states just in case, but there is one issue I've noticed for unraid on my motherboard. I have no USB 2.0 ports on my motherboard. Figuring higher heat of usb3 devices, I bought a USB 3.0 flash drive and plugged it into a 2.0 port on my old motherboard. Logic was it should last longer IF they designed it for likely higher USB 3.0 heat output plugged into a usb 2.0 port making it run slower/cooler in the long run. My motherboard is an asus x670e creator proart(for 4x nvme, and 3x pcie slots and 4x sata ports. I doubt this flash drive is failing given it's less than 9 months old. Early adopters beware. Might spin up a test server and hope the issues with ryzen 7000 get ironed out of unraid if thats the case or I can figure out what to do for stability. I managed to get it to run for close to 24 hours with docker disabled. Trying to figure out more right now.

From what I understand about vms the performance given the VM is properly configured would be slightly less than a bare metal gaming VM but nothing too crazy in terms of performance loss. These days a lot of games come with anti-cheat software and depending on what games you play this can be a non issue, or a huge issue because most anti-cheat software hates VMs and will assume cheats are being used.

Kind of thinking the same thing with ryzen 7000. System entirely froze up in safe mode earlier. Newest syslogs attached. syslog

Still rebooting randomly. Here is an updated syslog and diagnostics for anyone willing to help. infinity-diagnostics-20221006-1054.zip syslog4