BEWARE: Qnap's new QTS 4.3.5 BETA problems with Plex

TVS-1282T

1.13.5 - works
1.13.6 - does not work

Interfaces

4 * 1 GbE
2 * 10 GbE
2 * Thunderbolt

Interface Config:

vSwitch 1:
2 * 1 GbE in 802.11ad trunk
1 IP address in total

vSwitch 2:
2 * Thunderbolt (no trunk)
2 IP addresses in total

vSwitch 3:
2 * 10 GbE (no trunk)
2 IP addresses in total

vSwitch 4:
7 virtual IPs (Virtualization Station)

vSwitch 5:
9 virtual IPs (Container Station)

Note that the IPs in vSwitch 4 and 5 are not always up, or sometimes just a subset of them.

What I haven’t tried yet is binding Plex to a specific NIC and then upgrade to 1.13.6. That’s on my to do list.

@cryptochrome

How many interfaces does PMS see?
And is the first discovered (in your logs) your primary?

Yes, the first vSwitch with the 2*1GbE is my primary interface (default route set).

Plex sees every vSwitch (as interface). So vSwitch 1 is seen as interface qvs0, vSwitch2 as qvs1 and so on. It does not see the two physical interfaces that aren’t attached to any vSwitch, but those interfaces are not configured and down (not connected).

For you then, with qvs0 as the default, and it being enumerated first, you have no problems?

If I paraphrase correctly, this is how it seems to be for everyone regardless of QTS beta, docker or LXC, or just a bunch of adapters. If first enumerated (notice the index number preceding the interface name) is the default, then all is good.

Problems always seem to arise when first enumerated is not the default or when a multi-path situation exists. (two adapters , real or virtual, on the same subnet heading out to the gateway.

No, not good. 1.13.6 does not work! It starts up, but can’t be connected to from clients or Plex/Web. It only works with 1.13.5.

Note though that QTS 4.3.5 has its own issues with interface enumeration. I had trouble with my network config after upgrading to the beta, so I reset the network to defaults (press hardware rest button for 3 seconds). After that, the numbering of my interfaces was messed up. For example, what QTS considered to be Adapter 2 in the UI is actually eth5 when doing an ifconfig. I am also missing eth4 and instead now have an eth7. So something in QNAP’s network stack is severely broken in this beta.

let’s focus this down please? We have 4 possibles;

A. PMS 1.13.5 - QTS 4.3.4
B. PMS 1.13.5 - QTS 4.3.5 Beta
C. PMS 1.13.6 - QTS 4.3.4
D. PMS 1.13.6 - QTS 4.3.5 Beta

How about we mark it off this way, with a “Pass” or “Fail” ?
e.g

A.  Pass
B.  Fail
C.  Pass
D.  Fail

or whatever is being observed ?

Quoting myself here:

This is on QTS 4.3.5 beta

Alright, and 4.3.4 ?

Zero issues with 4.3.4. Problems only started after upgrading to the beta. I had 1.13.6 installed when I upgraded QTS.

Therefore.

4.3.4 == PASS
4.3.5 == FAIL

Nothing can be done about that until QTS is out of beta.

There’s a pretty long standing policy about not being able to support any Beta or “fix” PMS because of problems found in a Beta.

Since I have contact with QNAP, I’m hoping we can help pin down the network stack issues and then I can go back to Engineering and address anything needed for QTS 4.3.5 final.

Sounds good. Thanks for the help!

I’m always here to help if/when I can.

IF we can nail down a finite issue for QNAP which nobody has identified, I’ll make the phone calls needed and forward what’s been collected.

1 Like

There’s no way of knowing if that is or is not applicable.

I think it’s a bad idea to speculate.

So wanted to test some more and did a reinitialize on my nas as if brand new out of box with 4.3.5 beta installed. Only thing I did was setup a raid5 volume and install Plex. Sadly this still didnt fix anything but wanted to make sure it wasnt a configuration I had setup that was causing it. :cry:. At this point I am going to wait for the next QTS beta update then try again.

I had a pretty lengthy chat with tech support today.

This is the first of the ‘Beta’ suite There will be more to come before 4.3.5 is Final Release ready.

I would not be concerned at this time. Try it if you wish. If you do not have good luck, reload 4.3.4

All working fine here with latest releases of Plex and QTS Beta

Ts-879

Plex Version 1.13.7.5369 is available - testing now on tvs-1282 with 4.3.5

1 Like

Attention all:

I am renaming this topic as it’s clear Plex isn’t broken for everyone in 4.3.5.

I’m reducing the The Sky is Falling to a Bad Storm :slight_smile:

2 Likes

Still not working with 1.13.7.5369 on QTS 4.3.5 :frowning: with a TS-870Pro.

Please only post New information. “Me too” is not generally useful