sorg

Hello and thanks for the very detailed guide. Unfortunately, my VM is still detected by EAC (in Rocket League). I am stil investigating how EAC managed to do it.

I have been using your rtl8168 driver for ages , including with unraid 7 beta until beta4. Since upgrading to 7rc2, i have unstable network. "timeout" message showing in the console. Is there something i could do except downgrading unraid ?

Hi, I am running unraid 7.0.0beta2 . I can't use borgbackup anymore: root@Tower:~# borg -v Traceback (most recent call last): File "/usr/lib64/python3.9/site-packages/borg/archiver.py", line 37, in <module> from . import helpers File "/usr/lib64/python3.9/site-packages/borg/helpers/__init__.py", line 9, in <module> from .checks import * # NOQA File "/usr/lib64/python3.9/site-packages/borg/helpers/checks.py", line 4, in <module> from .errors import Error File "/usr/lib64/python3.9/site-packages/borg/helpers/errors.py", line 3, in <module> import borg.crypto.low_level ImportError: libcrypto.so.1.1: cannot open shared object file: No such file or directory Any pointer ?

Hello again, To whom i may concern: I finally solved my issue. I have resetted my bios to the defaults, and reactivated the minimum option i needed to use the Virtualization, and since then unraid and my UHD630 have been running smoothly. My best bet is that i had an option activated in the bios that made the energy saving mode of the uhd630 unstable, but i have not been able the specific option that causes the issue. I will now mark the issue has solved.

Hello again, I am still trying to find the factors involving this crash. I have two containers using this iGPU: (container mapped with access to /dev/dri ). - Plex - Frigate Based on my tests made during the last days, i came to the conclusion that this crash only occur if Frigate is running. (from time to time, it happens as soon as i start my frigate container). If plex is running alone, i have no crash. If frigate is running alone or in parrallel to plex, the crash will happen sooner or later.

I think i have the same issue. My servers run smoothly since i have switched all my docker setting to /mnt/cache/appdata instead of /mnt/user/appdata

Well i am still struggling with random crashes of my iGPU. It does not happen when i remove the discrete GPU (nvidia 3060Ti) from its PCIe socket. The nvidia GPU is used only by my gaming VM. Its bound to VFIO and there is no nvidia driver loaded on unraid.

I replaced my SATA card with a chinese clone of LSI2208 : no more errors, and parity check rate has increased from 80 to 240 Mb/s. Super Happy ! Thanks

Thanks, I have not tried the safe mode yet. (I can't shut unraid down before tonight). Closing all browser windows open on to the GUI stop the messages spamming the logs; but unraid remains quite unresponsive. As soon as I open a the webgui in my browser, i have the messages back in the logs.

Hi, For the second time in a few days, my unraid webUI is extra slow and unusable. ssh is barely workable too. My log is filled with these lines: Oct 29 09:19:12 unraid php-fpm[10837]: [WARNING] [pool www] child 17986 exited on signal 9 (SIGKILL) after 203.580264 seconds from start Oct 29 09:19:14 unraid php-fpm[10837]: [WARNING] [pool www] child 18278 exited on signal 9 (SIGKILL) after 196.504053 seconds from start Oct 29 09:19:16 unraid php-fpm[10837]: [WARNING] [pool www] child 18345 exited on signal 9 (SIGKILL) after 197.866661 seconds from start Oct 29 09:19:18 unraid php-fpm[10837]: [WARNING] [pool www] child 19563 exited on signal 9 (SIGKILL) after 173.875494 seconds from start Oct 29 09:19:27 unraid php-fpm[10837]: [WARNING] [pool www] child 24211 exited on signal 9 (SIGKILL) after 63.032834 seconds from start Oct 29 09:19:44 unraid php-fpm[10837]: [WARNING] [pool www] child 24267 exited on signal 9 (SIGKILL) after 78.877745 seconds from start Oct 29 09:19:45 unraid php-fpm[10837]: [WARNING] [pool www] child 24268 exited on signal 9 (SIGKILL) after 80.480307 seconds from start Oct 29 09:19:48 unraid php-fpm[10837]: [WARNING] [pool www] child 24269 exited on signal 9 (SIGKILL) after 82.705773 seconds from start Oct 29 09:19:49 unraid php-fpm[10837]: [WARNING] [pool www] child 24271 exited on signal 9 (SIGKILL) after 84.482557 seconds from start Oct 29 09:20:00 unraid php-fpm[10837]: [WARNING] [pool www] child 24272 exited on signal 9 (SIGKILL) after 95.624149 seconds from start Oct 29 09:20:03 unraid php-fpm[10837]: [WARNING] [pool www] child 24273 exited on signal 9 (SIGKILL) after 97.915289 seconds from start Oct 29 09:20:04 unraid php-fpm[10837]: [WARNING] [pool www] child 24274 exited on signal 9 (SIGKILL) after 99.672677 seconds from start Oct 29 09:20:16 unraid php-fpm[10837]: [WARNING] [pool www] child 24276 exited on signal 9 (SIGKILL) after 110.876703 seconds from start Oct 29 09:20:21 unraid php-fpm[10837]: [WARNING] [pool www] child 24280 exited on signal 9 (SIGKILL) after 115.985952 seconds from start Oct 29 09:20:24 unraid php-fpm[10837]: [WARNING] [pool www] child 26116 exited on signal 9 (SIGKILL) after 71.547135 seconds from start Oct 29 09:20:26 unraid php-fpm[10837]: [WARNING] [pool www] child 26197 exited on signal 9 (SIGKILL) after 71.815479 seconds from start Oct 29 09:20:30 unraid php-fpm[10837]: [WARNING] [pool www] child 26253 exited on signal 9 (SIGKILL) after 73.846352 seconds from start Oct 29 09:21:05 unraid php-fpm[10837]: [WARNING] [pool www] child 28309 exited on signal 9 (SIGKILL) after 49.805320 seconds from start I have attached the diagnostics if this can help. I have found no other solution than rebooting to solve the problem, but this is only temporary and eventually it will happen again. Do you know what could have trigger this behaviour ? unraid-diagnostics-20231029-0921.zip

Last night, i had another crash but with a different error in the log: Oct 26 02:45:48 unraid kernel: pcieport 0000:00:1c.3: AER: Uncorrected (Non-Fatal) error received: 0000:00:1c.3 Oct 26 02:45:48 unraid kernel: pcieport 0000:00:1c.3: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Receiver ID) Oct 26 02:45:48 unraid kernel: pcieport 0000:00:1c.3: device [8086:06bb] error status/mask=00200000/00010000 Oct 26 02:45:48 unraid kernel: pcieport 0000:00:1c.3: [21] ACSViol (First) Oct 26 02:45:48 unraid kernel: ahci 0000:04:00.0: AER: can't recover (no error_detected callback) Oct 26 02:45:48 unraid kernel: pcieport 0000:00:1c.3: AER: device recovery failed once again, this is about my SATA controller. root@unraid:/mnt/user/logs# lspci -k [...] 00:1c.3 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #4 (rev f0) Subsystem: ASUSTeK Computer Inc. Device 8694 Kernel driver in use: pcieport [...] 04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) Subsystem: ASMedia Technology Inc. ASM1062 Serial ATA Controller Kernel driver in use: ahci Kernel modules: ahci [...] I guess i need to stop using this sata card urgently

I have 4 ports.

I use an ASM1062 card. How can i know if i have a port multiplier ?

Hello, Last night, my unraid machine crashed during the parity check. The last log messages are the following: Oct 23 22:06:01 unraid kernel: ata5.00: failed to read SCR 1 (Emask=0x40) Oct 23 22:06:01 unraid kernel: ata5.01: failed to read SCR 1 (Emask=0x40) Oct 23 22:06:01 unraid kernel: ata5.02: failed to read SCR 1 (Emask=0x40) Oct 23 22:06:01 unraid kernel: ata5.02: exception Emask 0x100 SAct 0x3e0 SErr 0x0 action 0x6 frozen Oct 23 22:06:01 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED Oct 23 22:06:01 unraid kernel: ata5.02: cmd 60/40:28:c0:f4:4c/05:00:97:00:00/40 tag 5 ncq dma 688128 in Oct 23 22:06:01 unraid kernel: res 40/00:30:00:fa:4c/00:00:97:00:00/40 Emask 0x100 (unknown error) Oct 23 22:06:01 unraid kernel: ata5.02: status: { DRDY } Oct 23 22:06:01 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED Oct 23 22:06:01 unraid kernel: ata5.02: cmd 60/40:30:00:fa:4c/05:00:97:00:00/40 tag 6 ncq dma 688128 in Oct 23 22:06:01 unraid kernel: res 40/00:30:00:fa:4c/00:00:97:00:00/40 Emask 0x100 (unknown error) Oct 23 22:06:01 unraid kernel: ata5.02: status: { DRDY } Oct 23 22:06:01 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED Oct 23 22:06:01 unraid kernel: ata5.02: cmd 60/40:38:40:ff:4c/05:00:97:00:00/40 tag 7 ncq dma 688128 in Oct 23 22:06:01 unraid kernel: res 40/00:30:00:fa:4c/00:00:97:00:00/40 Emask 0x100 (unknown error) Oct 23 22:06:01 unraid kernel: ata5.02: status: { DRDY } Oct 23 22:06:01 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED Oct 23 22:06:01 unraid kernel: ata5.02: cmd 60/40:40:80:04:4d/05:00:97:00:00/40 tag 8 ncq dma 688128 in Oct 23 22:06:01 unraid kernel: res 40/00:30:00:fa:4c/00:00:97:00:00/40 Emask 0x100 (unknown error) Oct 23 22:06:01 unraid kernel: ata5.02: status: { DRDY } Oct 23 22:06:01 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED Oct 23 22:06:01 unraid kernel: ata5.02: cmd 60/c0:48:c0:09:4d/04:00:97:00:00/40 tag 9 ncq dma 622592 in Oct 23 22:06:01 unraid kernel: res 40/00:30:00:fa:4c/00:00:97:00:00/40 Emask 0x100 (unknown error) Oct 23 22:06:01 unraid kernel: ata5.02: status: { DRDY } Oct 23 22:06:02 unraid kernel: ata5.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Oct 23 22:06:03 unraid kernel: ata5.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Oct 23 22:06:03 unraid kernel: ata5.01: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Oct 23 22:06:03 unraid kernel: ata5.02: hard resetting link Oct 23 22:06:04 unraid kernel: ata5.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Oct 23 22:06:04 unraid kernel: ata5.00: configured for UDMA/133 Oct 23 22:06:04 unraid kernel: ata5.01: configured for UDMA/133 Oct 23 22:06:04 unraid kernel: ata5.02: configured for UDMA/133 Oct 23 22:06:04 unraid kernel: ata5: EH complete Oct 23 22:07:20 unraid kernel: ata5.00: failed to read SCR 1 (Emask=0x40) Oct 23 22:07:20 unraid kernel: ata5.01: failed to read SCR 1 (Emask=0x40) Oct 23 22:07:20 unraid kernel: ata5.02: failed to read SCR 1 (Emask=0x40) Oct 23 22:07:20 unraid kernel: ata5.02: exception Emask 0x100 SAct 0xe00 SErr 0x0 action 0x6 frozen Oct 23 22:07:20 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED Oct 23 22:07:20 unraid kernel: ata5.02: cmd 60/40:48:80:9a:b3/05:00:97:00:00/40 tag 9 ncq dma 688128 in Oct 23 22:07:20 unraid kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 23 22:07:20 unraid kernel: ata5.02: status: { DRDY } Oct 23 22:07:20 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED Oct 23 22:07:20 unraid kernel: ata5.02: cmd 60/40:50:c0:9f:b3/05:00:97:00:00/40 tag 10 ncq dma 688128 in Oct 23 22:07:20 unraid kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 23 22:07:20 unraid kernel: ata5.02: status: { DRDY } Oct 23 22:07:20 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED Oct 23 22:07:20 unraid kernel: ata5.02: cmd 60/80:58:00:a5:b3/00:00:97:00:00/40 tag 11 ncq dma 65536 in Oct 23 22:07:20 unraid kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 23 22:07:20 unraid kernel: ata5.02: status: { DRDY } Oct 23 22:07:22 unraid kernel: ata5.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Oct 23 22:07:22 unraid kernel: ata5.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Oct 23 22:07:22 unraid kernel: ata5.01: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Oct 23 22:07:22 unraid kernel: ata5.02: hard resetting link Oct 23 22:07:23 unraid kernel: ata5.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Oct 23 22:07:23 unraid kernel: ata5.00: configured for UDMA/133 Oct 23 22:07:23 unraid kernel: ata5.01: configured for UDMA/133 Oct 23 22:07:23 unraid kernel: ata5.02: configured for UDMA/133 Oct 23 22:07:23 unraid kernel: ata5: EH complete Oct 23 22:24:34 unraid kernel: ata5.00: failed to read SCR 1 (Emask=0x40) Oct 23 22:24:34 unraid kernel: ata5.01: failed to read SCR 1 (Emask=0x40) Oct 23 22:24:34 unraid kernel: ata5.02: failed to read SCR 1 (Emask=0x40) Oct 23 22:24:34 unraid kernel: ata5.02: exception Emask 0x100 SAct 0x60000000 SErr 0x0 action 0x6 frozen Oct 23 22:24:34 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED Oct 23 22:24:34 unraid kernel: ata5.02: cmd 60/40:e8:58:ad:9a/05:00:a1:00:00/40 tag 29 ncq dma 688128 in Oct 23 22:24:34 unraid kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 23 22:24:34 unraid kernel: ata5.02: status: { DRDY } Oct 23 22:24:34 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED Oct 23 22:24:34 unraid kernel: ata5.02: cmd 60/10:f0:98:b2:9a/00:00:a1:00:00/40 tag 30 ncq dma 8192 in Oct 23 22:24:34 unraid kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 23 22:24:34 unraid kernel: ata5.02: status: { DRDY } Oct 23 22:24:36 unraid kernel: ata5.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Oct 23 22:24:36 unraid kernel: ata5.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Oct 23 22:24:37 unraid kernel: ata5.01: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Oct 23 22:24:37 unraid kernel: ata5.02: hard resetting link Oct 23 22:24:37 unraid kernel: ata5.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Oct 23 22:24:37 unraid kernel: ata5.00: configured for UDMA/133 Oct 23 22:24:37 unraid kernel: ata5.01: configured for UDMA/133 Oct 23 22:24:37 unraid kernel: ata5.02: configured for UDMA/133 Oct 23 22:24:37 unraid kernel: ata5: EH complete Oct 23 22:54:45 unraid kernel: ata5.00: failed to read SCR 1 (Emask=0x40) Oct 23 22:54:45 unraid kernel: ata5.01: failed to read SCR 1 (Emask=0x40) Oct 23 22:54:45 unraid kernel: ata5.02: failed to read SCR 1 (Emask=0x40) Oct 23 22:54:45 unraid kernel: ata5.02: exception Emask 0x100 SAct 0xf80 SErr 0x0 action 0x6 frozen Oct 23 22:54:45 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED Oct 23 22:54:45 unraid kernel: ata5.02: cmd 60/40:38:70:f2:0a/05:00:b3:00:00/40 tag 7 ncq dma 688128 in Oct 23 22:54:45 unraid kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 23 22:54:45 unraid kernel: ata5.02: status: { DRDY } Oct 23 22:54:45 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED Oct 23 22:54:45 unraid kernel: ata5.02: cmd 60/40:40:b0:f7:0a/05:00:b3:00:00/40 tag 8 ncq dma 688128 in Oct 23 22:54:45 unraid kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 23 22:54:45 unraid kernel: ata5.02: status: { DRDY } Oct 23 22:54:45 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED Oct 23 22:54:45 unraid kernel: ata5.02: cmd 60/40:48:f0:fc:0a/05:00:b3:00:00/40 tag 9 ncq dma 688128 in Oct 23 22:54:45 unraid kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 23 22:54:45 unraid kernel: ata5.02: status: { DRDY } Oct 23 22:54:45 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED Oct 23 22:54:45 unraid kernel: ata5.02: cmd 60/40:50:30:02:0b/05:00:b3:00:00/40 tag 10 ncq dma 688128 in Oct 23 22:54:45 unraid kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 23 22:54:45 unraid kernel: ata5.02: status: { DRDY } Oct 23 22:54:45 unraid kernel: ata5.02: failed command: READ FPDMA QUEUED Oct 23 22:54:45 unraid kernel: ata5.02: cmd 60/80:58:70:07:0b/00:00:b3:00:00/40 tag 11 ncq dma 65536 in Oct 23 22:54:45 unraid kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Oct 23 22:54:45 unraid kernel: ata5.02: status: { DRDY } Oct 23 22:54:47 unraid kernel: ata5.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Oct 23 22:54:47 unraid kernel: ata5.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Oct 23 22:54:48 unraid kernel: ata5.01: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Oct 23 22:54:48 unraid kernel: ata5.02: hard resetting link Oct 23 22:54:48 unraid kernel: ata5.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Oct 23 22:54:48 unraid kernel: ata5.00: configured for UDMA/133 Oct 23 22:54:48 unraid kernel: ata5.01: configured for UDMA/133 Oct 23 22:54:48 unraid kernel: ata5.02: configured for UDMA/133 Oct 23 22:54:48 unraid kernel: ata5: EH complete Oct 23 23:36:58 unraid kernel: DMAR: DRHD: handling fault status reg 2 Oct 23 23:36:58 unraid kernel: DMAR: [DMA Write NO_PASID] Request device [04:1a.0] fault addr 0x0 [fault reason 0x02] Present bit in context entry is clear It looks like i have SATA issues (how can i check which controller/drives is ata5.xx ?) Based on the last line, the PCI device 04:xx is my additional SATA controller 04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02). I can't find any obvious description of what may cause this DMAR fault reg 2. Any pointers ? I have attached my diagnostics files. unraid-diagnostics-20231024-0737.zip

It's an i5-10500 (10th gen). I'll try the suggested fix though.

From time to time, my uhd630 crash, and it "disapear" from lspci and becomes unavailable for my dockers. I found this in the logs: Sep 19 14:47:57 unraid kernel: ------------[ cut here ]------------ Sep 19 14:47:57 unraid kernel: pci 0000:00:02.0: pm_runtime_get_sync() failed: -13 Sep 19 14:47:57 unraid kernel: WARNING: CPU: 10 PID: 20545 at drivers/gpu/drm/i915/intel_runtime_pm.c:358 __intel_runtime_pm_get+0x62/0x7e [i915] Sep 19 14:47:57 unraid kernel: Modules linked in: ipvlan af_packet bluetooth ecdh_generic ecc xt_connmark xt_mark xt_comment iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat xt_addrtype br_netfilter xfs xt_MASQUERADE ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag nct6775 nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc intel_rapl_msr i915 mei_hdcp mei_pxp intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iosf_mbi drm_buddy i2c_algo_bit ttm Sep 19 14:47:57 unraid kernel: drm_display_helper wmi_bmof kvm drm_kms_helper intel_wmi_thunderbolt mxm_wmi drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd cryptd intel_gtt i2c_i801 agpgart i2c_smbus rapl syscopyarea intel_cstate intel_uncore nvme i2c_core ch341 sysfillrect apex(O) mei_me r8168(O) ahci gasket(O) nvme_core video sysimgblt mei libahci usbserial fb_sys_fops thermal fan wmi backlight intel_pmc_core acpi_tad acpi_pad button unix Sep 19 14:47:57 unraid kernel: CPU: 10 PID: 20545 Comm: ffmpeg Tainted: P O 6.1.49-Unraid #1 Sep 19 14:47:57 unraid kernel: Hardware name: ASUS System Product Name/PRIME Z490-P, BIOS 1602 01/14/2021 Sep 19 14:47:57 unraid kernel: RIP: 0010:__intel_runtime_pm_get+0x62/0x7e [i915] Sep 19 14:47:57 unraid kernel: Code: f4 1e 00 01 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 34 53 dc e0 44 89 e1 4c 89 ea 48 c7 c7 d6 4e 92 a0 48 89 c6 e8 85 cf 89 e0 <0f> 0b 40 0f b6 f5 48 89 df e8 6c ff ff ff 83 c8 ff 5b 5d 41 5c 41 Sep 19 14:47:57 unraid kernel: RSP: 0018:ffffc9000713fcc0 EFLAGS: 00010282 Sep 19 14:47:57 unraid kernel: RAX: 0000000000000000 RBX: ffff888136c4a328 RCX: 0000000000000027 Sep 19 14:47:57 unraid kernel: RDX: 0000000000000002 RSI: ffffffff820ed4af RDI: 00000000ffffffff Sep 19 14:47:57 unraid kernel: RBP: 0000000000000001 R08: 0000000000000000 R09: ffffffff82245ed0 Sep 19 14:47:57 unraid kernel: R10: 0000000000000013 R11: ffffffff82958563 R12: 00000000fffffff3 Sep 19 14:47:57 unraid kernel: R13: ffff8881018cc100 R14: ffff8882d21b5600 R15: 0000000000000000 Sep 19 14:47:57 unraid kernel: FS: 0000000000000000(0000) GS:ffff88885f480000(0000) knlGS:0000000000000000 Sep 19 14:47:57 unraid kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 19 14:47:57 unraid kernel: CR2: 000000c003d6303f CR3: 0000000579024002 CR4: 00000000003706e0 Sep 19 14:47:57 unraid kernel: Call Trace: Sep 19 14:47:57 unraid kernel: <TASK> Sep 19 14:47:57 unraid kernel: ? __warn+0xab/0x122 Sep 19 14:47:57 unraid kernel: ? report_bug+0x109/0x17e Sep 19 14:47:57 unraid kernel: ? __intel_runtime_pm_get+0x62/0x7e [i915] Sep 19 14:47:57 unraid kernel: ? handle_bug+0x41/0x6f Sep 19 14:47:57 unraid kernel: ? exc_invalid_op+0x13/0x60 Sep 19 14:47:57 unraid kernel: ? asm_exc_invalid_op+0x16/0x20 Sep 19 14:47:57 unraid kernel: ? __intel_runtime_pm_get+0x62/0x7e [i915] Sep 19 14:47:57 unraid kernel: i915_driver_release+0x22/0x71 [i915] Sep 19 14:47:57 unraid kernel: drm_dev_put+0x31/0x62 [drm] Sep 19 14:47:57 unraid kernel: singleton_release+0x1f/0x26 [i915] Sep 19 14:47:57 unraid kernel: __fput+0xff/0x1d2 Sep 19 14:47:57 unraid kernel: task_work_run+0x68/0x80 Sep 19 14:47:57 unraid kernel: do_exit+0x3b4/0x923 Sep 19 14:47:57 unraid kernel: do_group_exit+0x7a/0x7a Sep 19 14:47:57 unraid kernel: get_signal+0x622/0x65a Sep 19 14:47:57 unraid kernel: arch_do_signal_or_restart+0x36/0x607 Sep 19 14:47:57 unraid kernel: ? do_futex+0xcd/0x143 Sep 19 14:47:57 unraid kernel: exit_to_user_mode_prepare+0x58/0x10d Sep 19 14:47:57 unraid kernel: syscall_exit_to_user_mode+0x18/0x2c Sep 19 14:47:57 unraid kernel: do_syscall_64+0x77/0x81 Sep 19 14:47:57 unraid kernel: entry_SYSCALL_64_after_hwframe+0x64/0xce Sep 19 14:47:57 unraid kernel: RIP: 0033:0x154752f73d36 Sep 19 14:47:57 unraid kernel: Code: Unable to access opcode bytes at 0x154752f73d0c. Sep 19 14:47:57 unraid kernel: RSP: 002b:000015474f9fec10 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca Sep 19 14:47:57 unraid kernel: RAX: fffffffffffffe00 RBX: 0000000000000000 RCX: 0000154752f73d36 Sep 19 14:47:57 unraid kernel: RDX: 0000000000000000 RSI: 0000000000000189 RDI: 000055aeb71f14c0 Sep 19 14:47:57 unraid kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 00000000ffffffff Sep 19 14:47:57 unraid kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 000055aeb71f1528 Sep 19 14:47:57 unraid kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 000055aeb71f14c0 Sep 19 14:47:57 unraid kernel: </TASK> Sep 19 14:47:57 unraid kernel: ---[ end trace 0000000000000000 ]--- The only solution after that is to reboot. Do you have a pointer or something i should investigate ?

24h later, the VM is still running smoothly. Thank you so much for your help !

Thanks for the advice ! I have made the modification. We'll see tomorrow if the VM is stable .

no, i don t think i am using virtiofs, v7t i have tried it in the past. Here is my current xml: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>W11</name> <uuid>6fa990ea-6d35-aa1c-f70e-42adc836226e</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>13107200</memory> <currentMemory unit='KiB'>13107200</currentMemory> <memoryBacking> <nosharepages/> <source type='memfd'/> <access mode='shared'/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='7'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='5'/> <vcpupin vcpu='5' cpuset='11'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/6fa990ea-6d35-aa1c-f70e-42adc836226e_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='3' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <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='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/W11/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/domains/W11/vdisk2.img'/> <target dev='hdd' bus='virtio'/> <serial>vdisk2</serial> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.229-1.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <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'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <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'/> <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'/> <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'/> <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='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='9' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:2e:42:cd'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> </tpm> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x1'/> </hostdev> <memballoon model='none'/> </devices> </domain>

deep sleep and monitor sleep are both disabled in windows settings.

Hello, I have a windows 11 VM with GPU (nvidia RTX3060Ti ) passthrough. The VM runs well, but if i left it unattended, after a while the VM becomes unresponsive (i can't ping the VM) however, Unraid sees the VM as running normally, there are no entry in the logs and the only way to have the VM working again is to force close it and restart it. Any pointer to help me troubleshoot this ? I have attached my unraid diagnostics, but let me know if you want me to provide specific details about my setup. unraid-diagnostics-20230910-1549.zip

Hi ! Have you been able to succesfully use the plugin Shairtunes2 (fork) from this docker image ? It seem to work (no errors in the logs) but apparently the airply players are not really published through bonjour and my apple devices do not see the airplay output devices.