J05u

This is my output 00:02.0 "VGA compatible controller [0300]" "Intel Corporation [8086]" "Arrow Lake-S [Intel Graphics] [7d67]" -r06 -p00 "Micro-Star International Co., Ltd. [MSI] [1462]" "Device [7e32]" 80:14.5 "Non-VGA unclassified device [0000]" "Intel Corporation [8086]" "Device [7f2f]" -r10 -p00 "Micro-Star International Co., Ltd. [MSI] [1462]" "Device [7e32]" 84:00.0 "VGA compatible controller [0300]" "Intel Corporation [8086]" "DG2 [Arc A380] [56a5]" -r05 -p00 "Unknown vendor [172f]" "Device [3941]"

We have kernel 6.6.66, should core Ultra Igpu working with ARC gpu?

How did you managed this to work? Want to bring my core ultra igpu to life

Thank you, so it means igpu not working for unraid? Or just sr iov?

Is it any way to check GPU power state? Now I am tired to fight with the fan rump ups for the arc GPU's Do I need to do something in bios to send arc to sleep?)

yeah, I understand about arc, I was thinking that igpu on core ultra can be splitted for plex, and arc cards I wanted to use with Tdarr, but In the end in gpu top gpu is in the list, in gpu top -l, not, I don't understand latest intel generation

Hello, trying to understand why my Arc cards and IGPU not working in Unraid Not sure if this related - but SR-IOV blacklist i915, can this be a case? And why it blacklists igpu? I have core ulta cpu

I did scrub couple of times, it fixes some errors, but this keeps happening. My cache don't have much load on them, mainly appdata for my containers, I had to recreate docker image already couple of times Probably I need try to repair, currently pool is in Raid1 If this won't help, I will replace drive Apparently now server UI not responding, but i still works, I see errors written on my other box via remote syslog fortress-diagnostics-20241125-0334.zip

Hello, what should be done if I have so much errors in my BTRFS cache pool? Accordingly scrutiny both drives are fine, both are NVME drives. Do I need to replace the drive? I already did RAM replacement, running currently other set with stock speed syslog.log

Thank you, it was jellyseer, strange as I haven't done any changes to it

Hello, My logs full of this messages, what is happening there? Can you please advice? Sick and tired to fight with this issues Nov 23 02:30:18 Fortress kernel: veth255b525: renamed from eth0 Nov 23 02:30:18 Fortress kernel: br-e17c32f9f0df: port 24(vethf09f57a) entered disabled state Nov 23 02:30:18 Fortress kernel: br-e17c32f9f0df: port 24(vethf09f57a) entered disabled state Nov 23 02:30:18 Fortress kernel: vethf09f57a (unregistering): left allmulticast mode Nov 23 02:30:18 Fortress kernel: vethf09f57a (unregistering): left promiscuous mode Nov 23 02:30:18 Fortress kernel: br-e17c32f9f0df: port 24(vethf09f57a) entered disabled state Nov 23 02:31:18 Fortress kernel: br-e17c32f9f0df: port 24(veth72773e2) entered blocking state Nov 23 02:31:18 Fortress kernel: br-e17c32f9f0df: port 24(veth72773e2) entered disabled state Nov 23 02:31:18 Fortress kernel: veth72773e2: entered allmulticast mode Nov 23 02:31:18 Fortress kernel: veth72773e2: entered promiscuous mode Nov 23 02:31:20 Fortress kernel: eth0: renamed from veth98ac14c Nov 23 02:31:20 Fortress kernel: br-e17c32f9f0df: port 24(veth72773e2) entered blocking state Nov 23 02:31:20 Fortress kernel: br-e17c32f9f0df: port 24(veth72773e2) entered forwarding state Nov 23 02:31:22 Fortress kernel: br-e17c32f9f0df: port 24(veth72773e2) entered disabled state Nov 23 02:31:22 Fortress kernel: veth98ac14c: renamed from eth0 Nov 23 02:31:22 Fortress kernel: br-e17c32f9f0df: port 24(veth72773e2) entered disabled state Nov 23 02:31:22 Fortress kernel: veth72773e2 (unregistering): left allmulticast mode Nov 23 02:31:22 Fortress kernel: veth72773e2 (unregistering): left promiscuous mode Nov 23 02:31:22 Fortress kernel: br-e17c32f9f0df: port 24(veth72773e2) entered disabled state

PSU is more than enough, and it was also without parity checks

Basically tried to play with ram, remove gpu and etc, same story. During parity check or it's either crashing or losing internet What is this story in logs? I have this kind of messages all over the place and I assume this is somehow related. Docker network is ipvlan Nov 1 11:35:05 Fortress kernel: br-a6738b7a6f98: port 24(veth40099c4) entered disabled state Nov 1 11:36:05 Fortress kernel: br-a6738b7a6f98: port 24(veth1c797a4) entered blocking state Nov 1 11:36:05 Fortress kernel: br-a6738b7a6f98: port 24(veth1c797a4) entered disabled state Nov 1 11:36:05 Fortress kernel: veth1c797a4: entered allmulticast mode Nov 1 11:36:05 Fortress kernel: veth1c797a4: entered promiscuous mode Nov 1 11:36:05 Fortress kernel: eth0: renamed from veth4da3b2a Nov 1 11:36:05 Fortress kernel: br-a6738b7a6f98: port 24(veth1c797a4) entered blocking state Nov 1 11:36:05 Fortress kernel: br-a6738b7a6f98: port 24(veth1c797a4) entered forwarding state Nov 1 11:36:06 Fortress kernel: br-a6738b7a6f98: port 24(veth1c797a4) entered disabled state Nov 1 11:36:06 Fortress kernel: veth4da3b2a: renamed from eth0 Nov 1 11:36:06 Fortress kernel: br-a6738b7a6f98: port 24(veth1c797a4) entered disabled state Nov 1 11:36:06 Fortress kernel: veth1c797a4 (unregistering): left allmulticast mode Nov 1 11:36:06 Fortress kernel: veth1c797a4 (unregistering): left promiscuous mode Nov 1 11:36:06 Fortress kernel: br-a6738b7a6f98: port 24(veth1c797a4) entered disabled state Nov 1 11:37:06 Fortress kernel: br-a6738b7a6f98: port 24(veth6c853ce) entered blocking state Nov 1 11:37:06 Fortress kernel: br-a6738b7a6f98: port 24(veth6c853ce) entered disabled state Nov 1 11:37:06 Fortress kernel: veth6c853ce: entered allmulticast mode Nov 1 11:37:06 Fortress kernel: veth6c853ce: entered promiscuous mode Nov 1 11:37:06 Fortress kernel: eth0: renamed from veth5c6f622 Nov 1 11:37:06 Fortress kernel: br-a6738b7a6f98: port 24(veth6c853ce) entered blocking state Nov 1 11:37:06 Fortress kernel: br-a6738b7a6f98: port 24(veth6c853ce) entered forwarding state Nov 1 11:37:07 Fortress kernel: br-a6738b7a6f98: port 24(veth6c853ce) entered disabled state Nov 1 11:37:07 Fortress kernel: veth5c6f622: renamed from eth0 Nov 1 11:37:07 Fortress kernel: br-a6738b7a6f98: port 24(veth6c853ce) entered disabled state Nov 1 11:37:07 Fortress kernel: veth6c853ce (unregistering): left allmulticast mode Nov 1 11:37:07 Fortress kernel: veth6c853ce (unregistering): left promiscuous mode Nov 1 11:37:07 Fortress kernel: br-a6738b7a6f98: port 24(veth6c853ce) entered disabled state Nov 1 11:38:07 Fortress kernel: br-a6738b7a6f98: port 24(veth0afbe5b) entered blocking state Nov 1 11:38:07 Fortress kernel: br-a6738b7a6f98: port 24(veth0afbe5b) entered disabled state Nov 1 11:38:07 Fortress kernel: veth0afbe5b: entered allmulticast mode Nov 1 11:38:07 Fortress kernel: veth0afbe5b: entered promiscuous mode Nov 1 11:38:07 Fortress kernel: eth0: renamed from vethc884152 Nov 1 11:38:07 Fortress kernel: br-a6738b7a6f98: port 24(veth0afbe5b) entered blocking state Nov 1 11:38:07 Fortress kernel: br-a6738b7a6f98: port 24(veth0afbe5b) entered forwarding state Nov 1 11:38:07 Fortress kernel: br-a6738b7a6f98: port 24(veth0afbe5b) entered disabled state Nov 1 11:38:07 Fortress kernel: vethc884152: renamed from eth0 Nov 1 11:38:07 Fortress kernel: br-a6738b7a6f98: port 24(veth0afbe5b) entered disabled state Nov 1 11:38:07 Fortress kernel: veth0afbe5b (unregistering): left allmulticast mode Nov 1 11:38:07 Fortress kernel: veth0afbe5b (unregistering): left promiscuous mode Nov 1 11:38:07 Fortress kernel: br-a6738b7a6f98: port 24(veth0afbe5b) entered disabled state

Thanks This will be a hard task

syslog-192.168.0.78 (4).log

Recently I rebuilded my NAS after my motherboard failure Now I am having issue that on daily basis my server just completely freezing I am running 7.0.0-beta.4 I have AMD 7900x and X670E Gigabyte Aorus Master with Arc 380 and one HBA card. I am having my logs written to other nas, and last record was on 13:29 during mover doing it's job Can you please advice what can be wrong? fortress-diagnostics-20241031-1540.zip

Funniest thing that while I was away my server got frozen and I had to force reboot. And now GPU is showing in Plex and also GPU statistics, apart of power usage From what I have in Plex settings is: Extra parameters: --device=/dev/dri/renderD128 And 2 devices just in case with value: /dev/dri /dev/dri/renderD128 intel_gpu_top reply with intel-gpu-top: Intel Dg2 (Gen12) @ /dev/dri/card0 - 1566/2448 MHz; 0% RC6; 1011 irqs/s intel_gpu_top -L reply with attached I have a feeling that re-installing intel_gpu_top and my accidental force reboot helped to GPU start working

I apologize, had to leave pc This is what I have

Unlucky me 03:00.0 VGA compatible controller: Intel Corporation DG2 [Arc A380] (rev 05) 04:00.0 Audio device: Intel Corporation DG2 Audio Controller

7.0.0-beta.4

I have dev/dri in plex, no luck I think something is missing for me

root@Fortress:/dev/dri# ls by-path/ card0 renderD128 root@Fortress:/dev/dri# in dev dri seems card is visible

I have Intel GPU top, hw transcode in enabled, but I can only select Raphael (I have 7900x as CPU) However I tried to-reinstall plugin and type in console intel_gpu_top In response I have that "No device filter specified and no discrete/integrated i915 devices found" But in GPU statistics and devices I can see my Arc GPU, strange

I finally moved to latest beta hopping that I can use my Arc 380 with Plex official docker and unfortunatelly no luck Any advice what can be done? GPU statistics reply with Vendor command returned no data when I select Arc GPU Arc gpu and audio in different IOMMU groups In plex container extra parameters I put --device=/dev/dri and as device /dev/dri also tried as device /dev/dri/renderD128 No idea how to make GPU to work for me ^(

both of them, VM with Home Assistant and Plex docker Will be nice to hear something from support