10.9 not working on QNAP and container station #6191

New Issue

OVERLORD · 2026-02-07T03:15:08+03:00

OVERLORD commented

2026-02-07 03:15:08 +03:00

Originally created by @fpizzuta on GitHub (Aug 13, 2024).

This issue respects the following points:

This is a bug, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found here.
This issue is not already reported on GitHub (I've searched it).
I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
I agree to follow Jellyfin's Code of Conduct.
This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.

Description of the bug

I recreated my container from 10.8.13 to 10.9.8 and the latest. When 10.9.x starts, it immediately experiences the following error, which continues to appear in the log.

GC: Failed to initialize GCToOSInterface
GC initialization failed with error 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005

I need to be on 10.9.8 or later, or my Google TV app won't connect.

Reproduction steps

On Qnap with container station, recreate the container using 10.9.8 or later, and you will see the error in the container log.

What is the current bug behavior?

Jellyfin is not available.

What is the expected correct behavior?

Jellyfin will be available.

Jellyfin Server version

10.9.9+

Specify commit id

No response

Specify unstable release number

No response

Specify version number

No response

Specify the build version

10.9.8+

Environment

- OS:
- Linux Kernel:
- Virtualization: docker on Qnap container station
- Clients: mobile, pc, and google tv
- Browser: safari, chrome, and jellyfin app
- FFmpeg Version:
- Playback Method: browser and app
- Hardware Acceleration:
- GPU Model:
- Plugins:
- Reverse Proxy:
- Base URL:
- Networking:
- Storage:

Jellyfin logs

GC: Failed to initialize GCToOSInterface
GC initialization failed with error 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005

FFmpeg logs

No response

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

No response

Originally created by @fpizzuta on GitHub (Aug 13, 2024). ### This issue respects the following points: - [X] This is a **bug**, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found [here](https://jellyfin.org/contact/). - [X] This issue is **not** already reported on [GitHub](https://github.com/jellyfin/jellyfin/issues?q=is%3Aopen+is%3Aissue) _(I've searched it)_. - [X] I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue. - [X] I agree to follow Jellyfin's [Code of Conduct](https://jellyfin.org/docs/general/community-standards.html#code-of-conduct). - [X] This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one. ### Description of the bug I recreated my container from 10.8.13 to 10.9.8 and the latest. When 10.9.x starts, it immediately experiences the following error, which continues to appear in the log. ``` GC: Failed to initialize GCToOSInterface GC initialization failed with error 0x80004005 Failed to create CoreCLR, HRESULT: 0x80004005 ``` I need to be on 10.9.8 or later, or my Google TV app won't connect. ### Reproduction steps On Qnap with container station, recreate the container using 10.9.8 or later, and you will see the error in the container log. ### What is the current _bug_ behavior? Jellyfin is not available. ### What is the expected _correct_ behavior? Jellyfin will be available. ### Jellyfin Server version 10.9.9+ ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number _No response_ ### Specify the build version 10.9.8+ ### Environment ```markdown - OS: - Linux Kernel: - Virtualization: docker on Qnap container station - Clients: mobile, pc, and google tv - Browser: safari, chrome, and jellyfin app - FFmpeg Version: - Playback Method: browser and app - Hardware Acceleration: - GPU Model: - Plugins: - Reverse Proxy: - Base URL: - Networking: - Storage: ``` ### Jellyfin logs ```shell GC: Failed to initialize GCToOSInterface GC initialization failed with error 0x80004005 Failed to create CoreCLR, HRESULT: 0x80004005 ``` ### FFmpeg logs _No response_ ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information _No response_

OVERLORD added the bug label 2026-02-07 03:15:08 +03:00

OVERLORD closed this issue

2026-02-07 03:15:09 +03:00

OVERLORD commented

2026-02-07 03:15:12 +03:00

@gnattu commented on GitHub (Aug 13, 2024):

What's the kernel version on your QNAP device? If it is too old it may fail to run dotnet 8 with errors like this.

@gnattu commented on GitHub (Aug 13, 2024): What's the kernel version on your QNAP device? If it is too old it may fail to run dotnet 8 with errors like this.

OVERLORD commented

2026-02-07 03:15:13 +03:00

@fpizzuta commented on GitHub (Aug 13, 2024):

Kernel is 4.2.8.
Model is TS-932PX.

@fpizzuta commented on GitHub (Aug 13, 2024): Kernel is 4.2.8. Model is TS-932PX.

OVERLORD commented

2026-02-07 03:15:14 +03:00

@gnattu commented on GitHub (Aug 13, 2024):

Can you try add env var COMPlus_EnableWriteXorExecute=0 to your container to see if it runs?

If it still fails then probably we can do very little due to the ancient kernel version and the requirements of dotnet8.

@gnattu commented on GitHub (Aug 13, 2024): Can you try add env var `COMPlus_EnableWriteXorExecute=0` to your container to see if it runs? If it still fails then probably we can do very little due to the ancient kernel version and the requirements of dotnet8.

OVERLORD commented

2026-02-07 03:15:15 +03:00

@fpizzuta commented on GitHub (Aug 13, 2024):

Still getting same issue. NAS is only 2 years old. I guess I will have to move Jellyfin to another device. Thank you for the quick response.

@fpizzuta commented on GitHub (Aug 13, 2024): Still getting same issue. NAS is only 2 years old. I guess I will have to move Jellyfin to another device. Thank you for the quick response.

OVERLORD commented

2026-02-07 03:15:16 +03:00

@gnattu commented on GitHub (Aug 13, 2024):

It's QNAP that ships a 2-year-old NAS with a kernel released on December 15, 2015, or roughly 9 years ago, so that's not your fault. Unfortunately, there's very little we can do to overcome this.

@gnattu commented on GitHub (Aug 13, 2024): It's QNAP that ships a 2-year-old NAS with a kernel released on December 15, 2015, or roughly 9 years ago, so that's not your fault. Unfortunately, there's very little we can do to overcome this.

OVERLORD referenced this issue

2026-02-07 06:28:01 +03:00

[PR #6191] [MERGED] Update to dotnet 5.0.7 #10859

Sign in to join this conversation.

Branches Tags

master

release-10.11.z

renovate/skiasharp-monorepo

JPVenson-patch-1

renovate/morestachio-5.x

release-10.9.z

openapi-cache

release-10.10.z

explicit-load

explicit-load-v2

feature/entity-framework

only-count-folder-item

fix/ci-workflow-refactor

release-10.8.z

release-10.7.z

EraYaN-add-management-interface

release-10.6.z

release-10.5.z

release-10.4.z

release-10.3.z

release-10.2.z

release-10.1.0

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#6191