Isorikk
-
Posts
17 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Isorikk
-
-
I believe my problems were caused my trying to run the VM on top of whatever else is going on. Disabling VM's has eliminated all weird bugs. It's possible the culprit was the unsupported video card. I have since tried an unofficial kernel that adds drivers for the video card and it has been playing well with Docker containers thus far. I'm going to go ahead and mark this thread as resolved, with the solution being don't use VM's with new hardware!
-
1
-
-
On 3/2/2023 at 10:12 AM, Anadoliev said:
What GPU did you use for transcoding with handbrake intel iGPU, nvidia or AMD? Can you compare the quality and the performance between intel arc and the device you used before?
I've used the A770 inside a VM for Handbrake which could transcode 4k h264 mp4 video at around 85 fps. My RTX3080 gets similar numbers. I have a GTX1660Super that averages around 60fps.
Using Tdarr I've seen it hitting several thousand FPS on the A770 so maybe I've just been using Handbrake wrong?
Edit: The several thousand fps was just for remuxing.
I've got the GPU doing full decode and encoding work now at around 140 fps. Attached image of the Intel GPU working within the Tdarr Docker in Unraid.
-
12 hours ago, Anadoliev said:
What did you use in Tdarr for transcoding before Arc gpu? Can you compare it with Arc? I have P400, A380 is great price now and I’m looking forward to AV1 support.
I didn't use Tdarr before, just Handbrake 😁
-
15 hours ago, DeadDevil6210 said:
It's not a support issue, Thor2002 didn't remove anything, It was just my network.cfg file on the flash drive that got messed up (removing it and setting up new one with fresh static ip solvbed the issue). (So if it works with official 6.11.5 build it wil work with his kernel)
DHCP was broken on 6.2 RC5/6 don't know if you now start using the final build if that's the same. And be sure to backup the files you are going to overwrite, If something els messes up you can just put back the original files and your back to where you left before.
Thanks, just tried it and got it working with zero issues! Now if only I could get the Handbrake container to recognize the GPU... Tdarr seems to see it no problem.
-
On 1/25/2023 at 3:04 PM, DeadDevil6210 said:
Hi Guys,
I don't know if this can help us but thor2002 has some unraid kernels ready on variouse 6.x.x linux kernels, My problem is that my servers RTL8125 (Realtek 2.5GBe nic) stops working, I also will receive my A380 tomorrow and was looking in to the arc support. Hope some have succes with the 6.x.x kernels from thor. I will also start testing again tomorrow with a different machine that has the RTL8125 and an intel nic for backup (not the machine that will get the A380)
Do you know if all PCI network cards unsupported with Thor's kernel versions? I'm running a 10GB NIC by TP-Link (TX401).
-
A new development:
The system has not frozen or gone unresponsive, but this morning I discovered that all of the docker and plugin services were unable to reach out to check for updates. I suspect this is directly related to changing from macvlan to ipvlan. I did some further investigation and determined that all of the services were able to reach my local network, including the gateway, but could not reach out to the internet. The Unraid system itself could reach just fine, only the plugin/docker services seemed to be blocked.
A restart resolved the issue. I'm wondering if the issue may be caused by the network card...
I've attached more logs from this morning. It looks like a lot of weird stuff is happening with br0 but I'm not certain if this was just a one-time bug or a symptom of a larger issue.
-
1
-
-
8 hours ago, JorgeB said:
Try switching to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right))
I've updated the configuration to ipvlan, not sure how it got set to macvlan in the first place, but good catch! So far I've encountered no issues. I will let it run for a few days again to see if the issue persists.
-
1
-
-
System froze again with Global C-States disabled and XMP profile turned off. Log doesn't really have anything, this is all it has at the time before it went unresponsive:
QuoteFeb 25 16:32:39 GeminiNAS kernel: vfio-pci 0000:03:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
Feb 25 16:32:39 GeminiNAS kernel: br0: port 2(vnet2) entered blocking state
Feb 25 16:32:39 GeminiNAS kernel: br0: port 2(vnet2) entered disabled state
Feb 25 16:32:39 GeminiNAS kernel: device vnet2 entered promiscuous mode
Feb 25 16:32:39 GeminiNAS kernel: br0: port 2(vnet2) entered blocking state
Feb 25 16:32:39 GeminiNAS kernel: br0: port 2(vnet2) entered forwarding state
Feb 25 16:32:41 GeminiNAS avahi-daemon[7613]: Joining mDNS multicast group on interface vnet2.IPv6 with address fe80::fc54:ff:fed4:45f8.
Feb 25 16:32:41 GeminiNAS avahi-daemon[7613]: New relevant interface vnet2.IPv6 for mDNS.
Feb 25 16:32:41 GeminiNAS avahi-daemon[7613]: Registering new address record for fe80::fc54:ff:fed4:45f8 on vnet2.*.
Feb 25 16:32:42 GeminiNAS acpid: input device has been disconnected, fd 6
Feb 25 16:32:42 GeminiNAS acpid: input device has been disconnected, fd 7
Feb 25 16:32:42 GeminiNAS acpid: input device has been disconnected, fd 8
Feb 25 16:32:53 GeminiNAS kernel: usb 1-9: reset full-speed USB device number 7 using xhci_hcdI've attached the full syslog for today, with it going unresponsive at approximately 4:55pm.
-
20 minutes ago, JorgeB said:
System should still always boot with C-States disabled, sounds like a buggy BIOS.
Tell me about it... 🙃
-
An update to my previous post:
After disabling Global C-State Control in the BIOS, I went to restart the system a little bit later and for some reason it wouldn't POST anymore. It booted exactly one time with C-States disabled and then never again. To resolve the issue I either had to unplug the drives from the SAS HBA's to get it to POST or, what I ended up doing, was flashing the BIOS with a newer version which appears to have reset the config.
I'm going to let it run for a few days with C-States re-enabled after the update, but I have a feeling that the issue will persist...
-
7 hours ago, JorgeB said:
There have been other users with issues with Ryzen 7xxx, try disabling C-states, also XMP on the RAM.
I will try disabling the C-states, however for the XMP on RAM, I originally had it disabled (saw no useful purpose for overclocking RAM on a storage server), but I was getting a different kernel panic with data corruption. It appeared that the bits were sometimes flipping in memory, and enabling XMP seems to have resolved it.
I will follow-up in a few days with the results of disabling C-states.
-
Hi all,
For the past couple months I've been trying to determine the cause of my Unraid system randomly becoming unreachable. Sometimes it'll run with no apparent issues for weeks, and other times it'll last a day or two before freezing again. This system ran flawlessly for years until I made two major changes:
Change 1: Upgraded the hardware. Basically a full transplant of the drives to a new system with a new CPU, new motherboard, new RAM, moved the drives from SATA splitters to SAS HBA's, and added an Intel A770 GPU for future video encoding endeavors.
Change 2: After determining there was no issues with the hardware upgrade, I then upgraded to the version V6.11.5 from V6.9.2 in hopes that it might play better with the A770, which is technically unsupported on Linux 5 (I've since been able to get the GPU to passthrough to a VM with no issues).
I suspect the issues I'm having are related to change #1, but I haven't been able to determine what specifically is the cause. The errors I'm encountering in the logs are beyond my knowledge to troubleshoot and Google has not been helpful. I've run multiple memtests and reseated everything. Another, possibly unrelated, symptom I've encountered is that the Win10 VM I'm running for the A770 only runs for about two hours before locking up and pinning the CPU to 100% until I tell the VM to force shut down. I did not run a VM on the system prior to Change 1 and 2.
I've attached the syslog from today where it most recently froze and the system diagnostics. Thanks for any help you can provide!
-
9 hours ago, SimonF said:
Are you using virtiofs or do you have memoryBacking with memfd and access mode set defined in the VM?
Here's the full XML for the config (redacted private names). I believe it's virtiofs, but gonna be honest, I'm an ESXi guy so the way Unraid runs VM's is bit of a black box for me. This is running on a Ryzen 9 7900X with 32GB DDR5 5200mhz 2x16 (not ECC) memory. I have a VNC video adapter added alongside the GPU, just bridged the network adapter, and have two shares included.
Edit: I should mention that the A770 has a little USB cable plugged into an internal motherboard slot that controls the LED's, which I also have passed through.
<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10</name> <uuid>Redacted</uuid> <description>Transcoder box</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <source type='memfd'/> <access mode='shared'/> </memoryBacking> <vcpu placement='static'>24</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='12'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='13'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='14'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='15'/> <vcpupin vcpu='8' cpuset='4'/> <vcpupin vcpu='9' cpuset='16'/> <vcpupin vcpu='10' cpuset='5'/> <vcpupin vcpu='11' cpuset='17'/> <vcpupin vcpu='12' cpuset='6'/> <vcpupin vcpu='13' cpuset='18'/> <vcpupin vcpu='14' cpuset='7'/> <vcpupin vcpu='15' cpuset='19'/> <vcpupin vcpu='16' cpuset='8'/> <vcpupin vcpu='17' cpuset='20'/> <vcpupin vcpu='18' cpuset='9'/> <vcpupin vcpu='19' cpuset='21'/> <vcpupin vcpu='20' cpuset='10'/> <vcpupin vcpu='21' cpuset='22'/> <vcpupin vcpu='22' cpuset='11'/> <vcpupin vcpu='23' cpuset='23'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-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/redacted_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <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' migratable='on'> <topology sockets='1' dies='1' cores='12' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </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='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <filesystem type='mount' accessmode='passthrough'> <driver type='virtiofs' queue='1024'/> <binary path='/usr/libexec/virtiofsd' xattr='on'> <cache mode='always'/> <sandbox mode='chroot'/> <lock posix='on' flock='on'/> </binary> <source dir='/mnt/user/redacted'/> <target dir='redacted'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <driver type='virtiofs' queue='1024'/> <binary path='/usr/libexec/virtiofsd' xattr='on'> <cache mode='always'/> <sandbox mode='chroot'/> <lock posix='on' flock='on'/> </binary> <source dir='/mnt/user/redacted'/> <target dir='redacted'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='redacted'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' 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='2'/> </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> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x2516'/> <product id='0x01b5'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <memballoon model='none'/> </devices> </domain>
-
11 hours ago, PaulW08 said:
What happens when you restart the VM? Does it still work after that?
Yep, it restarts normally as long as I don't passthrough the GPU audio. The only problem I've been having with it is that it freezes after 2-3 hours of runtime. After a lot of research, I don't think this is related to the GPU passthrough but an issue with Unraid v6.11.5 that I haven't been able to resolve.
-
On 12/23/2022 at 6:55 PM, ram8704 said:
What are your vm settings for the guys getting passthrough working? Any special steps taken? I keep getting code 43 after installing the latest beta drivers.
I didn't do anything special, just a basic Windows 10 VM. I also don't think I'm on beta drivers.
-
I've gotten an A770 working on 6.11.5 in a VM with no audio as suggested previously. However, the VM has randomly crashed or frozen. I assume the culprit is the GPU, although I'm not 100% certain on that. I wouldn't say it's stable enough for Plex, but running Handbrake to transcode files works pretty well!
Looking forward to better driver support in the future.
Intel Arc support
in General Support
Posted · Edited by Isorikk
Added update for pastebin links
I can't tell you what the spec idle usage is for the card, but my system is usually around 100 watts if all the discs are spun down and it is idle.
For Tdarr I wrote my own plugin borrowing a bit from some existing ones, the ones that are provided by the community aren't great for what I wanted... I'll link it as a pastebin but fair warning they are highly particular to my set-up and might not do what you want. Important note: It says QSV but I haven't been able to get the docker to recognize the A770 as a QSV enabled device, so it's currently using VAAPI. I also have an NVENC enabled script that does basically the same stuff if you want to use an Nvidia GPU as well 🙃
The main purpose of these scripts is to find files that aren't in the proper codec, or have annoying letterbox black bars on the top and bottom that show up on ultrawide monitors (which I use), and then remove the letterbox and compress the files to be optimal for Plex playback. You will lose some video quality using these plugins for those who want peak visual fidelity. I am still testing the optimal cutoff for each video type but it seems best to be around 10mbps for H265-4k and 15mbps for H264-1080p.
Intel: https://pastebin.com/sWQiP7tF
Nvidia: https://pastebin.com/PkhpTYdx
Disclaimer: These plugins are intended for private use and I have no intent on providing support to get them working. You are welcome to use or modify them as you wish.
Edit: I've made some improvements to the script since the original post. The original links still work but I've updated the code on them. Might start a repo for code updates on these and continue developing them, but no promises.