QNAP 453BE Transcode Crash

Plex Media Server NAS & Devices
1

Server Version#: 1.22.2.4282
Player Version#:

Good morning,

Newb here, but I’ve been having a crash issue since I starting using plex for qnap in 2019. Its become an every day crash now and QNAP is saying its because of a plex transcode issue and they provided the logs. I’m not sure where to start and any guidance is very much appreciated.

As far as the issue, it looks like our developers did point out that the issue is stemming directly from Plex server. You can see from the logs in the first line that the crash happens due to the Plex Transcoder. Included are two different times, one from the first set of logs when you first submitted the issue. Then the bottom portion is one you’ve just submitted. The latest Plex version directly from their website should be the correct one to use. Our developers have suggested you to reach out to Plex for further assistance in this matter.

Plex crash.txt (14.5 KB)

1 Like
2

Anyone?

3

it’s a GPU hang.

this is how you fix it on bare linux, no idea how on qnap

Please do as root:

  1. EDIT /etc/default/grub

  2. Find the line that starts with GRUB_CMDLINE_LINUX and append i915.enable_rc6=0 , giving you for example: GRUB_CMDLINE_LINUX="splash quiet i915.enable_rc6=0"

  3. EXECUTE: update-grub

  4. REBOOT

  5. (optional step) EXECUTE systool -m i915 -av | grep enable_rc6 to check whether you have set this option correctly

if you google the below you’ll get a lot more info on it. The below is basically just the first line of your log, minus the Plex Transcoder bit, as it just happened to be the binary running on it when it hung.

[drm] GPU HANG: ecode 9:1:0xeeffefa1 reason: Hang on bcs0, action: reset

4

also,

if this is still your bios and QTS versions there are newer versions available for both

2021-03-06 22:59:00 -05:00 <4> [179403.890031] CPU: 3 PID: 2570 Comm: Plex Transcoder Tainted: P U O 4.14.24-qnap #1
2021-03-06 22:59:00 -05:00 <4> [179403.898517] Hardware name: Default string Default string/Aptio CRB, BIOS QY47AR54 09/21/2017

5

I’m currently on Firmware Version 4.5.2.1630 for the qnap 453be. So its up to date, and I’m also using the latest qpkg from Plex’s website for qnap.

6

I will try the command line, probably need to ssh into my server but that’s not an issue.

7

@BobSnot

While we appreciate your grub references.

QNAP doesn’t use grub.

It is a proprietary implementation which does not conform to any of the known “Desktop” models.

Please refrain from using generalized Linux recommendations in QNAP or Synology threads

8

@zacky

May I have the XML of the item you’re trying to play ?

I suspect this is the iHD driver faulting on the specific codec.

If you wish, you can experiment by selecting the more conservative driver (which is better for the J3455 CPU anyway).

In “Preferences.xml”, we add VaapiDriver="i965"

There are two ways to do this:

  1. SSH command line , editing Preferences.xml when PMS stopped
  2. PlexData shared folder + QNAP Text Editor , editing Preferences.xml when PMS stopped.

PS: Sorry for not seeing this until now. The forum has been ‘wonky’ about notifications.

9

Ok so I added that to the end of the file before the closing bracket. Did it matter where or as long as it’s inside it’s fine?

10

Zacky,

It must be within the /> closing XML marker.

It will look like:

SomeOtherPref="Value"  VaapiDriver="i965" />

When done.

1 Like
11

and the bios? it still looks to be a few versions old…

2021-03-06 22:59:00 -05:00 <4> [179403.898517] Hardware name: Default string Default string/Aptio CRB, BIOS QY47AR54 09/21/2017

ver QY47AR58 is available from here → TS-453Be - Download Center | QNAP

1 Like
12

I’ll have to check that. I assumed, my fault, that the device bios was updated via the updates in the OS. And from what I’ve read updating the bios is a whole process requiring me to remove the drives and hook up a monitor and use a flash drive. I would hope qnap simplifies this process somehow, but I will be doing that now.

13

they keep them separate for some reason which is odd as other vendors do combine them and it makes things much easier…

14

I did the bios update, and now my server will not boot up at all. So I call qnap, they answer ask what the issue is and hung up on me, and when I call back its after hours. So now I’m without a server until they open.

15

@zacky

What did you do?

Did you install a BIOS manually and separate from QTS ?

16

I followed qnaps instructions website on the download page for my models available software. Downloaded the file, put it on a flash drive, it flashed successfully according to the display output and then when I went to boot back up nothing happens.

17

Do you have a USB keyboard and HDMI output to tv attached to the NAS ?

Manual BIOS updates are very dangerous in that they can lose the boot device list.

You must be prepared to set those values again after update.

At this point, you must connect a monitor and keyboard to confirm the machine at least is making it to the BIOS level.

If not, then it’s bricked and must be sent to QNAP for repair.

18

Yes, I have had the keyboard and mouse and external monitor hooked up. It does nothing when it starts up. F7 repeatedly does nothing when I plug it back in.

One thing that I am not sure about being a issue because it didn’t say anything about it is I did have the qnap m.2 expansion card in the system.

I have a feeling it probably did but the instructions didn’t mention removing it.

19

you shouldn’t have needed to remove any hardware.

BIOS / DOM updates are independent of other hardware.

My fear is you compromised the DOM in this which is a QNAP-only repair.

20

Well, I’m assuming at this point it’s the worst. I can’t get it to respond to anything. I’ve done bios updates before on other systems and never had issues but I guess I’ll see tomorrow.

At this point I’ve sunk wayyy to much money into qnap. If they can’t fix it I’m just giving up on the brand.