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

I just made the change to ipvlan. Thanks for the tip. Memory is also running at stock non xmp speeds.

Made some recent hardware upgrades. Long story short, ASUS x670e proart, and AMD 7950x. However, my system hasn't seen 6+hours of continuous uptime in almost 2 days now. The power supply is 1200w and brand new, cstates are normal, but Power Supply Idle Control is set to typical current idle. Any help is greatly appreciated. I believe the attached syslog has at least 2 reboots captured. One happened just before turning syslog on while Docker and vm service were disabled. syslog3 infinity-diagnostics-20221006-0454.zip

SOLVED!! Make sure to disable adressable-bar in actual bios. Above-4G decoding is still enabled but changing that setting in bios fixed everything.

Havent been able to figure thois out so far. What i do know is no matter what if i create a vm and use the graphics card i get the same error and the vm never starts. I just get a message in vnc saying guest has not initialized the display yet.

It's failing to boot and hanging before. Every cpu core assigned is at 0% as long as the gpu is being passed through.

The specific vm is the one called "Dev1". Im pretty sure things look correct on my end. <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/domains/DEV1/vdisk1.img' index='3'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows/Window11_Insiders.iso' index='2'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.190-1.iso' index='1'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:b9:43:05'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-5-DEV1/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5901' autoport='yes' websocket='5701' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> Does that help? I've tried re-configuring things so far outside the XML view to avoid accidentally breaking something.

Also, tried with a display attached to the graphics card out and still no luck. The message only shows on the VNC window and not on the display attached to the graphics card being passed through in this instance.

I 've had stable and working VMs for a while now. Recently, I passed through a GPU to my headless vm for machine learning acceleration in Windows on Python Things were working fine with VNC used as primary graphics output (headless vm) and the 3090ti used as a secondary graphics card with the NVIDIA sound card attached as well. After a server reboot(and first time booting it with a display plugged into the graphics card HDMI out) I continuously get the error "Guest has not initialized the display(yet)". For now, the only way to get the vm to boot and show anything other than that error message over VNC is to remove the 2nd graphics card and just run vnc. I've tried disabling docker and vm manager. Multiple reboots (with docker and vm's disabled) and so far i can tell it happens no matter what vm i try to attach the graphics card to. I have the NVIDIA drivers installed in unraid as well as on the Windows VM when it is running. There is currently nothing plugged into the HDMI or any other display output on the motherboard or graphics card. infinity-diagnostics-20220511-1332.zip

Fix Common Problems discovered errors. Anything to worry about here? infinity-diagnostics-20220130-0608.zip

Still getting errors, as well as cache drive overheating and complete freezing of the gui. Not sure if the diagnostics help here but any advice is greatly appreciated. infinity-diagnostics-20220105-1540.zip