QNAP QTS 4.4.1 Causing Roon Crashes?

I’ve been running Roon Server on a QNAP TS-677 for 6 months or so. It’s never crashed.

About 10 days ago I updated the QNAP QTS software to version 4.4.1 1064 and since then I have had 3 Roon crashes, i.e. no Roon remotes can connect to the server and the only way to fix it is to restart the server process on the QNAP.

Nothing else has changed in my setup.

Anyone else updated to QTS 4.4.1 and had similar problems?

Cheers
Jamie

Sounds like a question for NAS master Chris … @crieke

I am running 4.4.1 on a QNAP TVS-471. The QNAP runs my core. I have had no Roon issues since the update. Did you by any chance upgrade the memory in your QNAP?

Not recently - I upgraded to 48GB but that was months ago.

Not saying that this is your issue, but I had something similar to this earlier this year. After I updated my QNAP to a new rev I started getting reboots and crashes. It turned out to be the memory I used to upgrade my QNAP from 4GB to 16GB. The memory had been in there for more than two years with no issues. Once I replaced my memory with new RAM the issues went away. Took me weeks to sort it out. There is a thread in this forum that details what I did.

Ah interesting - I will keep an eye on that if it keeps happening. The RAM I bought is still under warranty so if it’s faulty I can exchange.

How did you identify the fault, or do you have a link to the thread?

Here is the link:

Have been using a TS-470 Pro and noticed that 4.4 isn’t yet available for that model. Seems unusual not to update all models at the same time, which raises suspicions about the stability of 4.4 on some models. Installed 4.4.1 on a new TVS-1282 today and Roon has been smooth as silk for several hours.

Might be worth considering rolling back the firmware to the previous version and wait for 4.4.2 before updating. Bear in mind the risks of rolling back, however.

QNAP have started to do that quite a lot now - release new QTS versions for different architectures at different times. It is a strange way of doing things, but they have such a (pointlessly) diverse hardware range now that maybe they have to.

I’ll stick with 4.4.1 for the moment - downgrading when I have a very complex NAS environment is probably too high risk: it’s not like it’s crashing every day, and it might not even be related to 4.4.1. but hopefully 4.4.2 will make it more stable.

1 Like

I’m getting this more frequently now - 2 or 3 times this week. Starting to become annoying.

@crieke can you be of any assistance here?

Cheers
Jamie

Don’t think this will be of any help to you but I’ve been running QNAP version 4.4.1 and the latest revision since they both came out and haven’t had any issues. Hope you get to the bottom of it.

Me too. All solid here. Did you ever try swapping the memory upgrade with the original stock memory?

I think your memory problems were causing deeper issues weren’t they - your whole NAS was crashing. It’s only Roon that’s dying for me, nothing is having problems and I use this qnap pretty intensively. The NAS itself isn’t crashing.

I’m also wondering now though if iOS 13 has anything to do with it, as that update was around the same time.

I am running IOS13 also. I am running 4.4.1 too. Nothing is crashing here. This is gonna be tough to find since it’s not happening everywhere.

Yes indeed, which is why I’m worried about it. Hopefully either the next iOS or QTS update will fortuitously fix it…

That is wishful thinking.

Hi @Jamie_Tudor,
Sorry for not replying yet.
Could you send e a zip file of the RoonServer logs? (in the Roon Server Web UI -> ambulance icon -> Download logs). I’ll send you the email address in a PM…

QNAP has an update to 4.4.1 available in case you didn’t get notified.

Yes, I updated QTS a couple of days ago: no crashes yet, fingers crossed.

Unfortunately my Roon is still crashing on the new QTS.

I managed to catch it in a crash today. The process has gone crazy: see the attached screenshot of top running on the server. Given this is an 8 core NAS, the process has taken up an entire core and 8GB of memory, and is just chewing it over.top

I’ve also discovered that if I leave it for about 5 minutes, it recovers without the need for a restart.