Synology DSM 6.1

yes i think yhe small ones are multicore -- the monster most definitely is :-)

Hi Mike,

the ram usage at my nas server is around 45 proc right now. Do you think it's way too much?

45% should be fine as the audio streams require very little RAM (just as they only use a small proportion of the available network and disk bandwidth).

HI Kacper,  45% is not too much,  with other UPnP software its normal.  But you have the same DS214 as me so why is your RAM %% different    I know my NAS is normally 18 to 22%,  this might be because I only have packages running that are required to do the jobs I want.  File Station is a must have & can't be uninstalled,  Search is also locked.  My only other packages are Media Server & Hyper Backup,  & I could even uninstall Backup as I do that manually & its only needed to be running at that time.   I do not need (for example) Audio Station because I don't play my music from the web.   So maybe you need to take a look at what you have installed & consider if they are really needed to do what you need,  then I would Restart (reboot) the NAS if you haven't already done that after 6.1 install.

Huge, thanks for your reply. I know that sometimes people are upgrading ram capacity at the nas servers but I'm not sure if those units require more ram capacity.

Yes Mike, honestly I have some more application at my NAS than you. I will try to uninstall some

Right. The 415play has been updated.

Before you start you get a dire warning that Minimserver is not supported and will be disabled! Consulting the Minim forum, I was reassured by the message from Simon that if you're on 8.4.2 it'll be fine....and it is. 

http://forum.minimserver.com/s...p;pid=24873#pid24873

Some initially horrid CPU usage stats of ~99% soon calmed down to 2%. RAM usage at 50%.

Minim working fine.

Kacper posted:

Huge, thanks for your reply. I know that sometimes people are upgrading ram capacity at the nas servers but I'm not sure if those units require more ram capacity.

 

The main reasons for upgrading RAM are video transcoding or running a lot of 'always on' type applications on the NAS (there are also some other reasons, but audio isn't one of them).

Hi folks -

I'm now nearing "end of life" with a 213+: the new OS upgrade breaks MinimServer and Plex, neither of which are maintaining updates for the Qorl (PowerPC) engine. The OS updates continue (likely for at least two more years if history is a guide) so perhaps now is the time for me to buy an Intel device and divert the Qorl 213+ to backup duties only.

There was no notification of MediaStation breaking but I have not yet checked operation or functionality or processor impact. If I find issues (single core race conditions on multithreaded code as postulated above) I will post again.

I have a different view than Mike-B re: enabling automatic updates for "fit and forget", and the reasons become more important as things age...not that I'm advising anyone to change settings, but perhaps alerting folks to the possibility of aggravation when an update you may not desire gets a one-way installation on your system (cf recent one-way firmware updates on Asus and other routers that add restrictions which can break "normal" applications like wireless bridging...but in that case there is an external admin privilege tool to roll back and live at the last working firmware level in perpetuity). A little extra manual labour now, with a bit of reading about early adopter experiences, can save a lot of trouble later!

Best wishes.  

Regards, alan

Thank you for the info as I own a DS213+, too. I did not yet update and now I certainly will not do because minimserver is not running as you say. Is there a minimserver info that the powerpc version is no longer maintained? I am going to check this now...

Alan, Gert,

The 213+ is a dual core CPU, so if I'm right, you may well be OK with Synology Media Server (although OS V6.1 may still break MinimServer and/or Plex due to the CPU architecture issue).

 Even If i'm wrong and the same problem occurs, reverting to Synology Media Server V1.6.2 will fix the problem.

I very much prefer minimserver over the synology media server because of some features. It would be very sad to loose minimserver. So I will keep back the update until Simon, the minimserver developer, gives green light for the powerpc platform...

Huge posted:

After 22 hours now, still FUBAR.

Restarted the network: DNS, Switch, DHCP, Synology, 272.

No change, no improvement

Removed Media Server - Intermittent high CPU load reduced.

Finally worked out how to install an old Media Server (1.6.2)
      This one works: Music restored (Corelli Op6 currently playing); suicide risk abated.

I've found other people have had the same problem and I was right: The issue is confined to single core devices so almost certainly a threading / race error problem.  This is utter crap: this release simply cannot have been tested properly on single core devices; completely unfit for purpose.  Absolutely unforgivable disregard for their customers.

If it had been the OS I'd have totally given up on Synology and defected to QNAP, advising everyone else to do the same.

I am genuinely relieved that you found a solution.  

SongStream posted:

I am genuinely relieved that you found a solution.  

Thanks, I was really not in a good place right then.

If anyone else has a problem with Synology Media Server, then hopefully, the same solution will work for them.

Huge,  is it 100% confirmed as caused by the single core CPU ??  and has it been reported to & acknowledged by Synology Support with a Support Ticket number ???. 

It has been reported to Synology, and a ticket raised.

We don't have positive confirmation of it being a single core issue, but everyone who has reported the problem and mentioned their device type has a single core CPU.

Hi guys -

Confirming Media Station seems fine on 213+, CPU load close to 50% but dominated by synoavscan.

Confirming Minim Server web site discontinued support for PowerPC because Oracle had terminated Java embedded SDK for this platform (this was true prior to latest Minim update). No idea if this is the same reason it became incompatible with DSM...but MinimWatch had stopped working as well, and no DSM issues there (but probably cross-jdk versions would be a factor). 

Regards alan

If it helps,  Simon the Minimserver man wrote on his forum:  If you have MinimServer 0.8.4.2 installed, you can safely ignore this (warning)  message and click OK to continue with the DSM 6.1 update. After the update and restart, MinimServer should be running normally.

A user post say it's worked OK then Simon followed up with:   I just tried updating from DSM 6.0.2 to DSM 6.1 on a NAS with MinimServer 0.8.4.2 installed. I got the "not compatible" message before doing the update and MinimServer was started automatically after the update.   
If you didn't have MinimServer 0.8.4.2 installed before doing the update, there is a known issue that could prevent MinimServer from starting automatically after doing the update. You can check the current level of MinimServer by viewing your installed packages in the Package Center.
I don't know whether this bogus error message is caused by something in the DSM 6.1 update or by something in the Synology package database.
My experience with Synology on previous occasions when I have reported problems like this is that it might be some time before they fix the problem, if at all. There was a similar problem with DSM 6.0 and it has never been fixed.  

Seems like 0.8.4.2 before the update is the answer.

Mike-B posted:

Seems like 0.8.4.2 before the update is the answer.

Hi Mike -

In case your tip is in reference to my comments and experience above...

Agreed for those that can: but 213+ isn't supported at 0.8.4.2 or beyond (perhaps due to non-availability of updated jdk, perhaps because maintaining a version for a dwindling number of boxes isn't feasible. 

Regards alan

My post is not in reference to anything Alan,  I saw the MinimServer Forum post & thought it might be helpful.   I did not realise 213+ & 0.8.4.2 had a problem.  

This is a bit of a mess, it's a real shame for those affected.  I can understand in some part that Synology are not supporting every 3rd party program they have in their package,  they do seem to have a hell of a lot & they've played catch up with new DSM & 3rd parties before.  But I also understand Simon (Minim) position (I think) as its been obvious that he has issues getting cooperation with Synology.  I suspect it will get sorted in time, & none more able than Simon,  meanwhile it's a mess.

Alan, can you give me more details about the minimserver issues on your ds213+? Does it really not work or was it just a warning when starting the upgrade?

Simon, the developer of minimserver, wrote that minimserver still should work on powerpc as long as java still is working. Oracle does not support this platform with new java version anymore. But on my ds213+ with dsm 6.0.2 I stil can run java 1.8.0. so that minimserver and bubbleUPnPServer still do work. Do you have java still installed on dsm 6.1 or is this the problem?

Thank you
Gert

gert posted:

Alan, can you give me more details about the minimserver issues on your ds213+? Does it really not work or was it just a warning when starting the upgrade?

Simon, the developer of minimserver, wrote that minimserver still should work on powerpc as long as java still is working. Oracle does not support this platform with new java version anymore. But on my ds213+ with dsm 6.0.2 I stil can run java 1.8.0. so that minimserver and bubbleUPnPServer still do work. Do you have java still installed on dsm 6.1 or is this the problem?

Thank you
Gert

Hi Gert -

Thanks for this. Like you, I have Java 1.8.0 running; it still runs under DSM 6.1. There was no report about Java during the upgrade and it did not need a manual re-start. 

MinimServer 0.8.3.4 is installed; it does not run and now that I've looked again it says "repair required". There was an alert that MinimServer, Plex and TimeBackup would not work (without re-start I assumed) and that TimeBackup was no longer supported. TBH, I don't recall if all three were not supported or if they just looked like needing a re-start according to the pre-upgrade reminder. 

After upgrade, indeed MinimServer (and Plex and TimeBackup) did not re-start...but there is no "run" option any longer. I'm at the mobile interface at the moment but the message is "repair required". EDIT: in Desktop mode, the status says "The package version installed is not compatible with your DSM"

Perhaps Ive over-reacted, and I will try a complete Uninstall (the only option available in Package Center; same as for Plex and TimeBackup) then look to see if I can do a clean Reinstall of 0.8.3.4. Am about to do an early morning drop-off run, will try this later and report back with results. 

Thanks for help to you and Mike-B!

Regards alan

Hi Mike,

I have disabled  some applications at my NAS and ram usage went down to 35%. Thanks for your tip.

"Time Backup and HiDrive Backup will not be supported in DSM 6.1 and above."

https://www.synology.com/de-de/releaseNote/DS213+

Alan,

see
http://forum.minimserver.com/s...p;pid=24927#pid24927

"The post from Alan says that he has MinimServer 0.8.3.4 installed. If he updates to the current version 0.8.4.2, there will be no problem."