MarkRMonaco

good point. thx

Runs fine on either platform. With all due respect, I get where you're going with the troubleshooting (and appreciate it), but I do know what I'm doing. I've been a desktop and server engineer for many years. That is why I was looking to do a deep-dive on the logs in the first place.

Thanks for confirming my suspicion about the drive being "ok". I definitely acknowledged the errors, but the drive did eventually go into disabled status twice over the course of yesterday. So, this is my second time trying to rebuild (it locked up again overnight and I decided to leave the server powered-off). I'll definitely get the syslog server configured (something that I've been meaning to do) as well. I'm also going to check the cabling (when I get home) and see if there is anything that stands out (like a deep crease or a crimp from a zip tie).

That's not necessarily a true statement. That particular generation of Ryzen runs fine on RAM speeds between 3000 and 3200 MHz (+/-). In fact, I've had Unraid running on that combination for over a year and its been fine.

Thanks, I am aware of that, but I don't think its the issue this time around. C-states are idle power states and my system is definitely locking up during activity (not while being idle).

I've been running into an issue where my Unraid (v6.9.0-beta25) server has gone completely unresponsive (the server itself, all hosted Docker containers, and no network communication whatsoever) several times this past week and had to be power-cycled to come back online (each time). - This has happened enough to the point where I'm rebuilding one of my array disks (which previously reported UDMA CRC errors, but passed several SMART tests). Can someone take a look at my diag logs and see if there are any other underlying issues that I may be missing (outside of the one reported drive)? I have a feeling that it may have to do with when the system is experiencing an unusually high load, but I'm not 100% certain. - As far as hardware changes are concerned, none have been made for (roughly) about a month and a half now. Thanks in advance. wadewilson-diagnostics-20200913-2324.zip

ACPI CPU Freq

I'm trying to use the scheduling features of this plugin to set my CPU to "performance" or "on-demand" depending on time. However, I'm finding that instead of "on-demand" it is setting my CPU to "power save" which is definitely not boosting when needed (have been monitoring via terminal). - Is there any way to fix this? My CPU is an AMD Ryzen 7 3800x (under-volted w/ no OC applied). Global C-State Control is enabled in my BIOS, along with PBO ("on-demand" works as expected). For reference: - "Power Save": All cores sit at ~2.1GHz regardless of idle or load. - "On-Demand": All cores can sit as low as ~2.0GHz and boost/turbo up to ~4.2GHz under load. - "Performance": All cores sit at ~4.4GHz regardless of idle or load.

For my specific issue, I think it has to do with the ASUS router (RT-AX58U) that I purchased (I've seen some other VPN-related comments on Google). Since there is 3rd-party firmware support, I switched over to Merlin (who makes a modified stock firmware), which added additional support for router-level VPN connections. Previously, it was all or none. Now, I can route specific IP addresses through it (similar to how you can do it on pfSense), and have the rest of the traffic flow through the regular internet. - I'm just not 100% certain if all of the outbound traffic for those specific docker IP's are going through the tunnel (which I'll have to verify via terminal sessions).

Ok. I'm currently banging my head trying to figure out a networking issue. - When VPN is enabled for this docker container, I lose all ability to access it via it's webpage (http://docker ip:8080; ICMP still works). However, once I turn VPN off, access is immediately restored. The only thing that has changed in my environment is that my wireless router was replaced today (my previous router died last night, and I had to run out to the store for a new one). - All of the IP configuration has been carried over and the CIDR notation is still correct in the container variables. I've even tried a different VPN provider to see if it was an issue with their split tunneling. I'm also running into this same problem with "binhex-qbittorrentvpn" as well. supervisord.log

I love how Unraid operates in that it is not a true RAID setup. This has made it extremely easy to expand storage and even migrate to new PC hardware (where drive order and other factors matter in traditional RAID). I would really like it if iSCSI (LUN) support could be added. Mapped drives in Windows has proven to be unreliable (in the sense that they do not always reconnect and I have to rely on scripts), which can cause issues with applications like Steam (if they are set to automatically start w/ Windows) where the file paths have to be manually re-added. - Furthermore, other launchers like the Epic Games Store and even the Windows App Store will either not play nicely with the mapped drives or not even support them at all (and even symbolic links are not 100% reliable). - I would rather not have to dedicate an actual HDD via Unassigned Devices to my gaming VM and would prefer to put it to use within my Unraid Array instead. Having this type of support would also keep me from having to purchase either a small standalone NAS (i.e.: QNAP or Synology) or even building a secondary server w/ FreeNAS. - Neither of which I have done yet, but have considered.

Ok. - Keeping the VM config in XML view did the trick, and I was able to boot directly off of the NVME SSD w/o having to enter the boot mgr. - I also, per your recommendation, went back to only 10 cores enabled and left CPU0 & HT6 unchecked. Not sure if that was causing some frame drops in the most recent game I'm playing, but it was worth a shot.

I actually (previously) tried adding the boot order tag to the nvme controller entry (1:0.0), and modifying the original drive to boot #2. However, it didn't seem to stick. - I'll have to try it again leaving the XML view enabled.

I recently added an NVME drive for pass-through in my Win10 VM, which can successfully boot. However, I have to manually select it from within OVMF BIOS everytime, regardless of what I manually set the boot order to in the VM XML view. - What appears to be happening is that another SATA drive (that I'm passing through via mount point) is being set to the top of the boot loader by the hypervisor. Any thoughts on how I can fix the boot order w/o removing the 2nd drive? Current config: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>Windows 10</name> <uuid>677e1385-e254-54d2-6c28-adbaccb5c69e</uuid> <description></description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>20971520</memory> <currentMemory unit='KiB'>20971520</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>12</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='6'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='7'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='8'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='9'/> <vcpupin vcpu='8' cpuset='4'/> <vcpupin vcpu='9' cpuset='10'/> <vcpupin vcpu='10' cpuset='5'/> <vcpupin vcpu='11' cpuset='11'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/677e1385-e254-54d2-6c28-adbaccb5c69e_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='12' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/sdd1'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </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='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x16'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0x17'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0x18'/> <alias name='pci.9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='10' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='10' port='0x19'/> <alias name='pci.10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> </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> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Windows 10 (GamingSr/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> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x27' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/vBIOS/GTX-1660ti_Modified.rom'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x27' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <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='0x03' slot='0x00' function='0x0'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x24' slot='0x00' function='0x0'/> </source> <alias name='hostdev4'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x26' slot='0x00' function='0x0'/> </source> <alias name='hostdev5'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x28' slot='0x00' function='0x2'/> </source> <alias name='hostdev6'/> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0bda'/> <product id='0x8153'/> <address bus='3' device='3'/> </source> <alias name='hostdev7'/> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

I think we finally got all of the issues resolved. - About 31hrs after my last reboot, and the logs are only at 1%.

I didn't think that last one through. The vdd would be on the "domains" share. So, I'm going to swap the values around so that "appdata" has a lower threshold, and "domains" is higher.

You were definitely right about it being the "appdata" share. I brought it down to 100gb, which matches the vdd size of my only running/remaining VM. - You think that will work, or should I bring it down lower, per your comment above?

Thanks. The cache drive itself (unformatted) is 512gb, but odd that its configured to require that much space to be available.

Attached. wadewilson-diagnostics-20190901-2237.zip

Not sure what the normal growth rate is for the logs, but its currently at 15% three hours later.

Ok. Made the cron adjustments and deleted the IPv6 static gateway yesterday, but still wound up hitting 100% on the logs a little under 24hrs later. Therefore, I went ahead and switched the IPv6 config to auto (DHCP), as recommend.

If I remove the static gateway, wouldn't that cause issues w/ the statically assigned IPv6 address that I already have configured? When looking at another one of my PC's that is pulling IPv6 via DHCP, I'm seeing the following format "fe80::b239:56ff:fef6:ade4%19".

I'm actually using IPv6 for one of my VMs.

Thanks. I'll look into the cron issue. Any ideas on the ICMPv6 router discovery issue?

Posting diag logs per recommendation from the "Fix Common Problems" plugin. - Logs typically do not fill up immediately after reboot, but will do so after a day or two of runtime. diagnostics-20190831-1643.zip