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.