Error transcoding mkv using Proxmox

[joshuas_79]

Did you add the mount to /etc/fstab?  That file contains all your permanent mounts.  Any mounts specified in that file are mounted during boot up.

I've been able to set the mount folder again, and now it seems like I watch the files again   Now I must learn how to do what you talked about to make it persistant

It seems also like I have to deal about how to solve the message UNCONFIGURED FSTAB FOR BASE SYSTEM when editing fstab

[joshuas_79]

Can you share your ffmpeg logs with us via pastebin?

Oh, after solving the issue with the shared folder, it seems I'm having now real issue with codecs:

https://pastebin.com/NZ15hDCg

[TheDreadPirate]

Did you follow our instructions here? The Intel instructions specifically for proxmox?

https://jellyfin.org/docs/general/admini...on-proxmox

Is your LXC privileged?

[joshuas_79]

Did you follow our instructions here?  The Intel instructions specifically for proxmox?

https://jellyfin.org/docs/general/admini...on-proxmox

Is your LXC privileged?

I'm going to have a look at the link. And I also will try to create a new unprivileged LXC because mine is privileged and I've read it's better in the other way. Am I right?

[3216]

Did you follow our instructions here?  The Intel instructions specifically for proxmox?

https://jellyfin.org/docs/general/admini...on-proxmox

Is your LXC privileged?

As of Proxmox v8.2 released a week or so back, you can pass through the GPU on an unprivileged LXC.

I set up a quick test LXC this morning using the Jellyfin script from https://tteck.github.io/Proxmox/ and everything worked cleanly once I’d got my NFS permissions sorted for the shared media folder.

[joshuas_79]

Today I tried again. I followed another guide. I could add the mount properly but my container crashes when I add this line inside of container conf file:

lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file

here is the entire conf file:
https://pastebin.com/L8ysAgLX

the render GID in the lxc console is 106

Can you help me to find the issue out?

thanks again

[joshuas_79]

Did you follow our instructions here?  The Intel instructions specifically for proxmox?

https://jellyfin.org/docs/general/admini...on-proxmox

Is your LXC privileged?

Sorry again, I was not succesful using other full guides, because I didn't want to be too annoying asking here. I checked the link, but I needed more details. The info was not enough for noobs llike me.
For example here in step 2: it says I must edit conf file and use my gid in the example:
lxc.cgroup2.devices.allow: c 226:0 rwm
lxc.cgroup2.devices.allow: c 226:128 rwm
lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file.
My gid is 118: do I need to use it instead of 226?


For the step nr 4 I will need more information.

Thanks again

[joshuas_79]

well, it seems like I got it to work. I still have to find how to keep access to shared folders when privileged lxc, but this I'll keep checking somewhere else for this.

I only notice I get error when I activate HECV in hardware aceleration and I get this log. Any tip?
https://pastebin.com/W0NEMwNu

---

my processor is a intel 8250u.

[TheDreadPirate]

I've seen some of the low power Intel CPUs not have completely identical Quick Sync capabilities as the rest of that generation's lineup and I'm wondering if that is the case here. Coffee Lake supports 10-bit HEVC and, AFAIK, there aren't any restrictions on resolution or profile/level in general.

My only suggestion is to uncheck HEVC 10-bit in the Playback settings.

---

Just noticed that the 8250u is Kaby Lake R and not Coffee Lake like the rest of the 8000 series. That might explain it. But Kaby Lake also supported HEVC 10-bit, wtf!

[joshuas_79]

I've seen some of the low power Intel CPUs not have completely identical Quick Sync capabilities as the rest of that generation's lineup and I'm wondering if that is the case here.  Coffee Lake supports 10-bit HEVC and, AFAIK, there aren't any restrictions on resolution or profile/level in general.

My only suggestion is to uncheck HEVC 10-bit in the Playback settings.

---

Just noticed that the 8250u is Kaby Lake R and not Coffee Lake like the rest of the 8000 series.  That might explain it.  But Kaby Lake also supported HEVC 10-bit, wtf!

Ok, thank you very much for taking your time. I guess there's not much I can do about this so I'll just uncheck the option like you said.