matew

Hi, Thank you. Points to USB coral TPU, plugged into the same USB bus as unraid USB. Some problems with LPM. Oct 20 20:39:31 unraid kernel: usb 1-2: reset full-speed USB device number 2 using xhci_hcd Oct 20 20:42:26 unraid kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Oct 20 20:42:26 unraid kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Oct 21 00:38:18 unraid kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Oct 21 00:38:18 unraid kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Oct 21 00:46:18 unraid kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Oct 21 00:46:18 unraid kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Oct 21 03:20:48 unraid kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Oct 21 03:20:48 unraid kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Oct 21 03:29:28 unraid kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Oct 21 03:29:28 unraid kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Oct 21 04:04:31 unraid kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Oct 21 04:04:31 unraid kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Oct 21 04:44:51 unraid kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Oct 21 04:44:51 unraid kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Oct 21 06:52:32 unraid kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Oct 21 06:52:32 unraid kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM.

Hello, running 6.12.10. Few days ago my server started to become completely unresponsive , GUI, CLI, all services, all ports. Hard physical reboot brings it back to life. For obvious reasons I wasn't able to do a system diagnostics dump. However, I have enabled external syslog, today finally I got something. attached Does it look like usb flash drive issue? Or should I be looking for a HW issues somewhere else? Thank you. syslog_20241020.txt

Hi, is anybody else experiencing issues after upgrading Frigate container to ver 0.14 during ffmpeg decoding using iGPU the whole container starts to be unresponsive and iGPU crashes as well? Meaning to output from the onboard graphic card. In case you are using GPU statistics plugin this causes as well GUI unresponsiveness. Setup is AMD ryzen 7900. Unraid version 6.12.10. With older version of Frigate there were no issues, it was stable for months.

So, it was not a solution. It still keeps re-appearing. Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:24 vmid:4 pasid:32771, for process ffmpeg pid 15489 thread ffmpeg:cs0 pid 15658) Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: in page starting at address 0x00008001072fb000 from client 0x12 (VMC) Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00403831 Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: Faulty UTCL2 client ID: VCN (0x1c) Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: RW: 0x0 Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:24 vmid:4 pasid:32771, for process ffmpeg pid 15489 thread ffmpeg:cs0 pid 15658) Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: in page starting at address 0x00008001072fb000 from client 0x12 (VMC) Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00000000 Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: Faulty UTCL2 client ID: MP0 (0x0) Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: MORE_FAULTS: 0x0 Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 30 21:20:29 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: RW: 0x0 Aug 30 21:20:39 unraid kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_dec_0 timeout, signaled seq=18111395, emitted seq=18111397 Aug 30 21:20:39 unraid kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process ffmpeg pid 15489 thread ffmpeg:cs0 pid 15658 Aug 30 21:20:39 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: GPU reset begin! Aug 30 21:20:39 unraid kernel: [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x00000001 != 0x00000002 Aug 30 21:20:40 unraid kernel: [drm] Register(0) [mmUVD_RBC_RB_RPTR] failed to reach value 0x00000360 != 0x00000320 Aug 30 21:20:40 unraid kernel: [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x00000001 != 0x00000002 Aug 30 21:20:40 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: free PSP TMR buffer Aug 30 21:20:40 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: MODE2 reset Aug 30 21:20:40 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: GPU reset succeeded, trying to resume Aug 30 21:20:40 unraid kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F41FC00000). Aug 30 21:20:40 unraid kernel: [drm] PSP is resuming... Aug 30 21:20:40 unraid kernel: [drm] reserve 0xa00000 from 0xf41e000000 for PSP TMR Aug 30 21:20:40 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: RAS: optional ras ta ucode is not available Aug 30 21:20:40 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: RAP: optional rap ta ucode is not available Aug 30 21:20:40 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Aug 30 21:20:40 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: SMU is resuming... Aug 30 21:20:40 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: smu driver if version = 0x00000004, smu fw if version = 0x00000005, smu fw program = 0, smu fw version = 0x00544fde (84.79.222) Aug 30 21:20:40 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: SMU driver if version not matched Aug 30 21:20:40 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: SMU is resumed successfully! Aug 30 21:20:40 unraid kernel: [drm] DMUB hardware initialized: version=0x05000C00 Aug 30 21:20:40 unraid kernel: [drm] kiq ring mec 2 pipe 1 q 0 Aug 30 21:20:40 unraid kernel: amdgpu 0000:0e:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring vcn_dec_0 test failed (-110) Aug 30 21:20:40 unraid kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <vcn_v3_0> failed -110 Aug 30 21:20:40 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: GPU reset(1) failed Aug 30 21:20:40 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: GPU reset end with ret = -110 Aug 30 21:20:40 unraid kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* GPU Recovery Failed: -110 Aug 30 21:20:41 unraid kernel: [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x00000001 != 0x00000002 Aug 30 21:20:41 unraid kernel: [drm] Register(0) [mmUVD_RBC_RB_RPTR] failed to reach value 0x00000010 != 0x00000000 Aug 30 21:20:41 unraid kernel: [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x00000001 != 0x00000002 Aug 30 21:20:43 unraid kernel: [drm] Fence fallback timer expired on ring sdma0 ### [PREVIOUS LINE REPEATED 3 TIMES] ### Aug 30 21:20:51 unraid kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_dec_0 timeout, signaled seq=18111397, emitted seq=18111397 Aug 30 21:20:51 unraid kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process ffmpeg pid 15489 thread ffmpeg:cs0 pid 15658 Aug 30 21:20:51 unraid kernel: amdgpu 0000:0e:00.0: amdgpu: GPU reset begin! Aug 30 21:23:39 unraid php-fpm[12845]: [WARNING] [pool www] server reached max_children setting (50), consider raising it

Same here, so far for me at least it points either to GPU statistics plugin or (most likely) frigate container (ver 0.14)

Seems that the root caue of these symptoms was caused by frigate 0.14 container, running on br0, causing nginx to misbehave. Re-installing frigate container and using bridge for it fixed the issue with nginx. Now to find the reason why.

Well, honestly I thought it would be plugin or a docker problem. Tried to /etc/rc.d/rc.nginx restart and /etc/rc.d/rc.php-fpm restart, then installed dynamix safe mode plugin to disable all plugins and so far so good and stable GUI. The reason why I have not booted into proper safe mode is that the parity check is still running, because apparently I did not rebooted unraid properly from the cli.

Yes, 192.168.1.8 is the PC from where I am trying to reach the GUI. Also I tried multiple browsers and multiple machines, multiple OS, including win10, win7 and android. While testing it from other system the browser in this case firefox 129.0.2 on system 192.168.1.8 (win10) was closed.

HI all, any idea why I could be getting 500 internal server error from unraid GUI nginx? No, changes or updates to the server done. Also, docker containers which are using br0 are of course having the same problem. Diagnostics attached. unraid-diagnostics-20240821-0949.zip After the reboot it worked for 30 minutes or so. But then error got back. Also tried to restart nginx and php, so it helped for a while, but then it went back to the original error. After that made a second diagnostics unraid-diagnostics-20240821-1745.zip Did few packet captures basically it reflect logs as well. Any ideas please? unraid-diagnostics-20240821-0949.zip unraid-diagnostics-20240821-1745.zip

Hi JorgeB, SATA cable was replaced with a brand new one. Attached diagnostics. Seems to me that the disk is dead. unraid-diagnostics-20240707-2042.zip

uploaded, thank you. unraid-diagnostics-20240703-0215.zip

Hello fellow unraiders, disk approx, one month old, precleared before adding into array, was disabled and content emulated. It happened during its first monthly parity check. Fine, no big deal, I will replace it, or RMA it. Sure, I can change SATA cable. No harm to my data, as all important data are backup-ed to offsite spare unraid server. Odd thing is that I cannot perform/nor see SMART report data. I want to understand possible reasons. I would like to ask for your opinion please here. Thank you very much. Also to mention disk is now available under unassigned disks, it can be formatted or precleared, I have not done any of those. It all started with these messaged in logs: Jul 1 01:14:47 unraid kernel: ata5.00: failed command: READ FPDMA QUEUED Jul 1 01:14:47 unraid kernel: ata5.00: cmd 60/40:f8:b0:17:5d/05:00:06:00:00/40 tag 31 ncq dma 688128 in Jul 1 01:14:47 unraid kernel: res 43/40:40:28:18:5d/00:05:06:00:00/00 Emask 0x409 (media error) <F> Jul 1 01:14:47 unraid kernel: ata5.00: status: { DRDY SENSE ERR } Jul 1 01:14:47 unraid kernel: ata5.00: error: { UNC } Jul 1 01:14:47 unraid kernel: ata5.00: configured for UDMA/133 Jul 1 01:14:47 unraid kernel: sd 6:0:0:0: [sdd] tag#31 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=5s Jul 1 01:14:47 unraid kernel: sd 6:0:0:0: [sdd] tag#31 Sense Key : 0x3 [current] Jul 1 01:14:47 unraid kernel: sd 6:0:0:0: [sdd] tag#31 ASC=0x11 ASCQ=0x4 Jul 1 01:14:47 unraid kernel: sd 6:0:0:0: [sdd] tag#31 CDB: opcode=0x88 88 00 00 00 00 00 06 5d 17 b0 00 00 05 40 00 00 Jul 1 01:14:47 unraid kernel: I/O error, dev sdd, sector 106764328 op 0x0:(READ) flags 0x0 phys_seg 153 prio class 2 Jul 1 01:14:47 unraid kernel: md: disk2 read error, sector=106764264

@jace055 11% GPU utilization seems to me pretty low, are we sure that plex is not utilizing the CPU somehow as well?

Hello, @jace055 - was anything published by plex in e.g. release notes, saying that amd iGPUs are finally fully supported? Many thanks.