Docker: Failed to initialize VA

[intersect 5]

Hello,
 

I am running Emby with Premiere subscription on my new unraid server have installed Intel-GPU-TOP and see the graphics card under "/dev/dri".

I tried everything I could find on your board/youtube/reddit/documentation but it didn't work and spend over 6 hours on the issue.

Entering "getent group video | cut -d: -f3" into the emby container gives me 985 back. And unraid as well as the container can access "/dev/dri" which didn't help either.

The hardware detection throws several errors one of them for the Intel iGPU is:

„Failed to initialize VA /dev/dri/renderD128. Error -1.“

I attached the hardware detection protocol as well as screenshots of everything which seems important.

Not sure if is important: If I go in unraid to "System Devices" - "PCI Devices and IOMMU Groups" and activate some IOMMU groups and then click on "Bind selected to VFIO at Boot" with a monitor plugged in but it does not boot and gets stuck at: "NET: Registration PF_UNIX/PF_LOCAL protocol family" with the  cursor stop blinking. Already tried a lot in the bios without success. Every time I try it, I  need to delete a file from my boot stick to boot into unraid . I know this is not the unraid community but I want to give as much information as possible.

This is really driving me nuts.. would appreciate support here!!

Thanks for your attention.

Best regards
Intersect

 

hardware_detection-63852176827.txt

Edited May 25, 2024 by intersect
fixed typo

[Luke 42077]

Hi, please attach the main Emby server log as well. Thanks.

[Q-Droid 989]

The device group in your /dev/dri listing is 18, not 985.

[intersect 5]

1 hour ago, Q-Droid said:

The device group in your /dev/dri listing is 18, not 985.

How do I fix it?

9 hours ago, Luke said:

Hi, please attach the main Emby server log as well. Thanks.

attached the server logs

embyserver.txt

[intersect 5]

I add the user for emby "nobody" to the video group for the iGPU but that didn't change anything. Logs are the same, here is my configuration for the emby container:

[Q-Droid 989]

I think there are different options in unraid to handle devices for containers and most prefer using the host device options for /dev/dri instead of extra parameters. You can search the forums for details if you can't find the container device settings in unraid. I don't use it.

That may or may not change the group 18 for the render devices. If it doesn't you still need to get that resolved for the emby runtime user.

 

 

Edited May 25, 2024 by Q-Droid

[intersect 5]

I tried now with the default UI to add devices, I can see "/dev/dri" within the container but its still not working same logs.

 

 

[intersect 5]

Most recent logs:

embyserver.txt hardware_detection-63852224757.txt

[Q-Droid 989]

The device is visible but the runtime user doesn't have access.

You want to set things up so that the runtime user has access to the render devices. You're using 100 for PUID and PGID. Do these correspond to a real user and group or were they plugged in at random? Based on those variables it looks like you might be running the LSIO docker image for Emby. If you have the option then the official image would be preferable because you can add a GIDLIST variable to include the GIDs for the video and render groups or whichever other values you might have, like 18. But I don't know if the Emby image on unraid comes from a store/repo or if you get to pick which to use.

 

 

[intersect 5]

Thanks you too! It works now, I used binhex-emby as far as I can recall and moved to the official emby - at the time I didn't see it. I just changed the owner of the files and it worked directly without loosing any configurations or data.