Synology DSM 6.1

Synology released DSM 6.1 yesterday, & put into the auto release hopper overnight & it should auto-update this morning or anytime now if you have you system set to do so,  if not, you need to get a copy from their "Support" web page to manually load.    The new stuff is all Synology OS features, business & security related, nothing much for music/audio replay functions.     A minor change is in 'File  Services', to enable Windows Explorer & Mac Finder views on your PC/Mac, the 'File View' check box is now renamed 'SMB' & when enabled it opens up the familiar Windows Explorer & Mac Finder screen views.       

Also released prior to DSM 6.1 were new revisions of Media Server & Search to enable them to work better with DSM 6.1,  that said the old versions worked OK on 6.1 beta & RC,  whatever its best to have everything set to auto-update - fit & forget.      

If you find one of you usual programs (like Media Server or Minimserver) disappears from the web page desktop view when you restart with 6.1,  this has happened before so don't panic,  go to Package Centre, open the missing program,  touch the Actions button to 'Stop' (turn it off)  & then 'Running'  (restart)  

Original Post
Kacper posted:

  just uploaded a new version DSM 6.1

Goedenavond Kacper,  what UPnP media server software are you using  ???  Synology Media Server or Minimserver??

If Media Server have you installed the latest rev. Version: 1.7.0-2810  (released yesterday)  Did it install OK or like me, disappear until rebooted.   

If Minimserver how is it??  Synology made a point during beta testing of making it clear its up to Minimserver to ensure no problems & they cannot ensure all will be OK when DSM 6.1-15047 is released (today) 

Media Server stayed installed and restarted itself (at 1.7.0-2810) but stopped functioning instead...

HDD demand of the new system seems so high that after about 30s - 5min it just gives up and kills the stream.  Great result: the NAS is now FUBAR.

Huge,  don't understand - are you saying DSM 6.1 is installed & MS updated at the same time to 1.7.0.   HHD demand ??? are you saying RAM is O/L ???   Mine went frm ~26% to 20% & sometimes now goes down to 18-19% with 6.1,  CPU is now at 1-2% when nothing is going on.   I would go for a reboot & see what that changes.

I also see your DS115j is 32 bit & 256MB,  did Synology auto-update - i.e. Its pre- approved the update - or did you manually load it  ???   

MS updated previously but was still running after 6.1 install

RAM previously 25% ->   now 45% typical

CPU previously 15% - 25% ->   now 17% - 75% variable, some evidence of cycling.

Rebooted twice (from Web Admin client) and from front panel.  No change.

Now trying the wait and see approach (not fixed after 1.5 hours, but may still fix itself yet).

I just looked into DS115j & see DSM 6.1 is OK,  so interested to read what you find is the problem.

Re blood tests:  I'm a volunteer for a national (Oxford Uni) survey & give a sample of about 15 separate container bottles every year,  its taken out in one go via one needle & as each sample bottle contains a vacuum its a matter of seconds per sample to 'suck' out.    I hate the needle insert bit,  I'm a big wimp & can't watch.  But I'm more than happy doing just that & a lot worse to others.

Huge, I noticed this in the release notes -- perhaps this is pertinent? It could be that your NAS is re-indexing, or trying to re-index?

"Manual re-indexing is required for all files after upgrading to DSM 6.1. The file indexing service in Control Panel has been moved to the preference settings in Synology Universal Search."

Might well be the case,  I always manually run a reindex, irrespective of an auto-update or as I did with 6.1 a manual update.    

Re File indexing moving to Search,   Media Indexing is still in the Indexing Service folder in Control Panel

Mike-B posted:
Kacper posted:

  just uploaded a new version DSM 6.1

Goedenavond Kacper,  what UPnP media server software are you using  ???  Synology Media Server or Minimserver??

If Media Server have you installed the latest rev. Version: 1.7.0-2810  (released yesterday)  Did it install OK or like me, disappear until rebooted.   

If Minimserver how is it??  Synology made a point during beta testing of making it clear its up to Minimserver to ensure no problems & they cannot ensure all will be OK when DSM 6.1-15047 is released (today) 

Hi Mike,

I'm using media server (minimserver i have installed but don't use it). Yes I have installed the lates version. Some applications  disappeared, after server has been rebooted everything came back again. Music library was visible via naim app already before rebooting- immediately after installing the latest software.

Hi Adrian and Mike,

That's the first thing I did after the NAS came up.  I did it again 2 hours later, after the second re-boot, in case the first one had failed because the OS optimisation wasn't done.  Yes I did the media indexing, rather than the general file indexing.

I then uninstalled and reinstalled Media Server (and re-indexed it again!).

Another re-boot late last night and another this morning.

Still a brick

It can't even manage to keep the 272's buffer full with a 16/44.1 WAVE stream.

Looks like it's only good enough for MP3 now, but there again I'm not sure it's even good enough for that.

 

Oh yes, and the disk passes its internal SMART test, albeit with a lot of waiting for the OS to catch up.

Mike-B posted:

...
Re blood tests:  I'm a volunteer for a national (Oxford Uni) survey & give a sample of about 15 separate container bottles every year,  its taken out in one go via one needle & as each sample bottle contains a vacuum its a matter of seconds per sample to 'suck' out.    I hate the needle insert bit,  I'm a big wimp & can't watch.  But I'm more than happy doing just that & a lot worse to others.

Unfortunately I'm a Marfan, so my veins sometimes collapse with the vacuum tubes.

How about trying another DSM 6.1 install ???  It might overwrite whatever is causing this.  

I would then contact Synology www Support - the UK office is MK - I've found them pretty good   (except non-comprehension over MS transcode downsample & gapless problems)  

The OS isn't downgradable - and that includes re-installs (and that's sheer stupidity).

OK, further observation.

It seems like the people who wrote this OS may be incompetent.

With the NAS at rest, the CPU activity cycles from 5% to 99% every few minutes, and the disk light shows an almost constant high level of activity.  My guess is that the OS was written for multi-core CPUs and gives appalling race error problems on single core devices rendering them useless.

 

Unfortunately for reasons of other things going on, unless I can find an alternative solution, this risks becoming an iminent threat to my mental health

Pretty sure the OS is downgradable - just not through the GUI.  If you google for 'synology assistant' and run it on your PC / Mac it'll scan your network, find the device and from there you can use that tool to install an OS.  It's usually used for bricked devices but should allow a downgrade. (interestingly, you can use it to install the Synology OS on other hardware, but that's another story)

The only fly in the ointment might be your data on the box, however good practice would suggest we all have backups of our NAS devices on another drive / volume stored elsewhere to restore from as / when / if things go awry... ;-) 

How long is it since you have upgraded? Maybe the system just needs a day or two to sort things up? The release notes say that after upgrading it can take an hour for the system to calm down. Maybe it takes a bit longer on a slower system depending on the number of files?

Eeek. I've upgraded my 214 (used only for backups) and am getting 2-7% CPU and 24% RAM (so that seems perfectly fine), though goodness only knows what it was before as every OS upgrade to date has been pretty seamless (thanks to people like Mike thoroughly testing them).

I'm sure the 415play (without which life is just a misery) will be fine, but I might just hold back a few days!

Hi Gary,  at the moment my DS214 runs 19 to 21% RAM.  When I updated on Monday it was 26 to 28%.   I've now 'Uninstalled' (back in the Package Centre) the programs I had to use for beta testing & now have only File Station, Media Server & Hyper Backup installed.  Search is also installed but you can't do anything with that.   I then ran a Restart (Reboot) & it recovered the RAM to around 20%,  CPU now its doing nothing is 0 to 2% 

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.

Hi Jon, then you have multi core CPUs, which is very likely (or you were just lucky!) - the monster will definitely be multi core, probably quad core.

But I've got music again OK now and I can start to drain the tension out of my head, so I just have to wait for a fixed 1.7.x media server release.

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.

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.  

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

I now have updated my DS213+. Everything is ok. minimserver and bubbleupnpserver are running. They only reported that the java installation was corrupted and I had to reinstall java again.

After minimserver did state this, I did so. The restart of minimserver after reinstalling java was fine. But when starting bubbleupnpserver after this for the first time, it did tell me the same java-corrupted-warning. So I just stopped and restarted bubbleupnpserver again. The second run did work ok without any warning. I do not know what this problem might be. Seems not to be a real problem.

CPU usage of the NAS currently is at 4%. (the most recent version of the mediaserver is installed. But the powerpc is a dual core processor anyway.)

Greetings
Gert

gert posted:

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."

Thanks a million for this Gert. I think I must have had dyslexia reading MikeB's reports earlier,..but anyway SUCCESS at my end with the 213+ and DSM6.1 and MinimServer.

Apologies for the fuss over a false alarm!

Please also extend my thanks to Simon on the forum for his support and quick recommendation.

(EDIT: Thanks again Gert...I just sent Simon a "thank you" Donation...long overdue, but a great program and a great community.)

Regards, 

alan

Hello, 

I have a Synology DS212 and upgraded to DSM 6.1 last Weekend. Unfortunately before I read this thread

Same problems with media streaming like member "Huge" described. Many thanks for the really good advise to downgrade the Media Server app to 1.6.2. That worked for me and streaming is now possible without interrupts. Just created a support ticket at Synology and asked them for a solution concerning the Media Server, also I asked whether DSM 6.1 is fully compatible to Single-Core CPUs in Synology Diskstation or not. 

Best regards,

Olaf

DS413J here.  MARVEL Kirkwood 88F6282, 1.6 GHz, single core, 512 MB RAM; 4/8 TB free.  DSM 6.1-15047 installed last night and left to run.  This morning, Disk Station Media Server was up, MinimServer was down as expected.  Uninstalled and reinstalled Java SE Embedded 8, then restarted MinimServer 0.8.4.2.  All looks OK.  CPU is bouncing a little, between 7-82%, RAM is steady at 30%.  Looking OK to me.

I did set up Search indexes manually, as recommended in release notes.  That has pushed CPU up to 99%, RAM at 75%,  as I kicked it off.  

Nick

For those of you with single core CPU's who had install problems with 6.1,  a new DSM release has just gone in the hopper for regional auto-updates (& that includes DS115j  Huge).      Release notes say  Version: 6.1-15047-1  (2017/02/25)      Fixed a security vulnerability with the Auto Block function that could allow remote attackers to bypass the current IP blocking mechanism.

Nothings changed with Media Server yet.   

Up to you,  I'm leaving mine to auto-update as & when UK gets scheduled.   If you don't want it, suggest you turn off auto-update.  

Huge posted:

Nick,

Did you install Synology Media Server 1.7, and have you tested it (rather than just using MinimServer)?  If so did it work without dropouts and lost connection issues?

Hi, Huge.

Affirmative.  Synology Media Server is set to auto-update, and is currently at v 1.7.0-2810.  I find the first try playing a series of tracks always stops mid-song, after about a minute; then a second try is completely successful.  First try failures appear to be consistent.  MinimServer is a better performer, at some cost to fiddling with Java updates etc.  Also, the metadata and general operation under MinimServer seem slightly better -- I cannot recall precisely why that was my impression.  

MinimServer has never been perfect either, though.  The most noticeable annoyance is that when shifting from e.g. NDX-FM to UPnP > MinimServer, the first load of an album series usually fail utterly (and this was the case before and after the move from DSM 6.0 to 6.1) -- I am in the habit of loading the transition album twice; subsequent album picks are fine.  Just when I got this routine down, I showed it to my wife and the transition-album failed to fail!  Of course, She had forgotten the NDX played anything other than Spotify, so was only confused at my surprise.

I only had the NAS for a while before I decided MinimServer was a worthwhile upgrade over Media Server, so the latter is may fallback.  I will say that, initially, getting MinimServer installed was difficult.  Once I documented the installation and update routines (including that installing Java 8 form a Mac REQUIRES Firefox!), all has gone very smoothly.

I hope this is helpful.

Nick

Mike-B posted:

For those of you with single core CPU's who had install problems with 6.1,  a new DSM release has just gone in the hopper for regional auto-updates (& that includes DS115j  Huge).      Release notes say  Version: 6.1-15047-1  (2017/02/25)      Fixed a security vulnerability with the Auto Block function that could allow remote attackers to bypass the current IP blocking mechanism.

Mine auto-updated with DSM 6.1-15047-1 this morning per its scheduled event prog.     The only difference was it requested a manual restart,  never done that before.  

Play is fine, all working: no dropouts, no lost connections.

DSM 6.1.15047 - update 1
Media Server 1.6.2.2770

Interestingly Media Server 1.6.2.2770 is now shown as the latest version for my device - so they've realised the problem and which machines are affected.

Huge posted:

..............  Interestingly Media Server 1.6.2.2770 is now shown as the latest version for my device - so they've realised the problem and which machines are affected.

Ah ha,   maybe we can expect more developments to bring MS software back to a common stnd for all.    (thks) 

Hello,

I received an answer from the german synology support board today. The problem with media server 1.7.0-2810 is known to their developers and it will be fixed with an future update. Unfortunately, they are not able to tell me at which date this update will be released. For the meantime, they recommend to install media server 1.6.2-2770, just the same version "huge" tried. On my Syno DS212 this combination works fine, at the moment. Streaming of 720p video material and of FLACs in 16/44 works fine, HD Flacs not tried yet.

They also recommended me to switch off the automatic update for media server as well, unless the future release update is not yet available.

Best regards,

Olaf

Nope, uninstalling Media Server removes the media indices (or renders then inaccessible), so after reversion to an earlier version it needs to reindex (it's good practice anyway, even if it wasn't absolutely necessary).

If it's taking a day or so to re-index, then it sounds as through you should be using a 4 bay NAS and a stripe set (i.e. RAID 0).

Nick, that's true, however...

1 Failure of the disk controller leads to failure of the whole array even in RAID 1 (mirror set), so you still need proper backups in any event.

2 If you're worried about that use a 5 bay NAS and use RAID 5 - that's both faster AND more secure.

3 'Proper' NAS drives (WD Red, Segate NAS etc) are very reliable, very often the people who have problems are using 'desktop' drives in NAS enclosures.

OK stripe sets...

Distribute the data over multiple HDDs (say 4), and use a hardware controller that can read and write from all the disks at the same time (i.e. in parallel).

To create the index it needs to read all the files on the disk(s) and look at the tags then write the index back onto the disk.  With a single disc, shuttling the heads around all the time makes re indexing very slow, with 4 drives 3 of them are just continuously reading files for most of the time.  Same applies to RAID 5.

Nick, Barracudas are desktop drives, really not ideal for NAS use.

Don't forget that if disks are bought at the same time from the same place they are likely to be from the same batch, and that increases the chance of them failing at around the same time (but you'd be extremely unlucky for them to fail at exactly the same time unless there was an external reason for it).

If the drives are >3 years old, then with desktop drives in a NAS, I'd be getting very concerned about failures.


Note that running (cheaper) desktop drives in a NAS, running as RAID 1 and accepting the more frequent failures that results from this (i.e. always have a spare drive available), is also a perfectly valid approach.

nickpeacock posted:

 

Ah well, a complete re-index will only take a day or so.

     a day or so !!!   How much have you got stuffed in there.     My DS214 (2 bay - RAID-1) with 2TB takes 15-20 minutes,  I run a reindex when I think of it & have time just before my aprx monthly back up (just hit the reindex as I write)  

RE (reminds me I must run health check),  mine is set to automatic & its runs a check & sends me a monthly report by e-mail.   Plus the web page widget tells me its OK each time I open it 

Message for you folks who had issues with the last DSM & Media Server updates working together within a single core CPU.   A new DSM  Version: 6.1-15047-2 is in the hopper ready to auto release.   The fix list does NOT show anything related to your Media Server problems.  see  .....  https://www.synology.com/en-uk/releaseNote/DS115j  ..... Its up to you.  

The new DSM 6.1-15047-2 has been released for auto update,  mine did so at its pre scheduled time this morning.    No news yet on the Media Server updates to work with the new DSM on single core CPU's.   I also found a Hyper Backup update downloaded & waiting for a manual update this morning. 

Mike,

Do you know if they've sorted out the state error in Hyper Backup.  After doing the backup, the current one unmounts a drive that it didn't mount in the first place, leaving it inaccessible to the next backup.  In other words if you schedule a regular backup on an external drive, it can only ever do the first one in the series...  all subsequent backups in the series fail...   And that's a classic state error problem.

(A computer service should de-allocate resources it allocated itself but should never de-allocate resources allocated by another service - the other service may still need them and the called service cannot know if the resources are still required.)

Sorry if this is a bit of a basic question -- recent bought a Mu-so Qb and noticed when I stream to it from Audio Station using Airplay very scratchy audio.  No problems though with uPnP (either from Audio Station or pulling tracks to the Qb from the Naim App using Media Server).

The Airplay otherwise works from my iPhone and also a Mac.

Anyone else have issues with Synology's Airplay?  Or should I just ignore it, would the uPnP provide a better quality stream (such as with 24-bit FLACs, etc.)?

Thanks.

 

jjcantab, you probably won't find an  answer to your questions on here.  I'm not sure anyone uses Airplay,  & Audio Station is to enable streaming from your NAS across www, you are using the wrong application to feed NAS to Muso.      Playing music in the home from Synology to Muso (or any player) is done with Media Server (DLNA/UPnP)  or the 3rd party alternative Minimserver.  

Mike-B: Thanks, will use those going forward.  Though that said I did use Audio Station / DS Audio on the iPhone to stream to an Airport Express connected to an older hifi, so I expected that the Muso Qb would have worked with that.  But anyway, if uPnP will deliver a more "authentic" stream I'm all for it.

My uprade to DSM 6.1 partly killed my Unity Qute streaming from a Synology NAS via Synology Media Server.

I was getting "cannot connect", "cannot play track", all sorts of weird errors I had never seen before. Naturally I tried everything, reboots, re-indexing, etc, but to no avail.  I uninstalled and re-installed Media Server - no difference.

Finally (a bit random this) I unticked "Enable SMB Service" (accepted the warnings, etc) and then re-enabled it.  Everything has worked fine since. No idea why this should work or what the underlying issue was but it's fine now.

Hope this helps somebody!

 

Strange one that Cpt Black,  I've not heard that problem associated with SMB before.   I leave my SMB Service un-enabled as it causes a lot of hibernation wake ups.  I just enable it each time I want to have my PC or laptop get into NAS files  such as to upload a new album,  when thats done I un-enable again.  It's not needed for UPnP access to NAS files.  

CaptainBlack posted:

In case anyone is still tracking this thread the combination below is working fine now:

DS112+
DSM 6.1-15047 Update 2
Media Service 1.171.-2820.

Captain

 

I did this DSM update recently on my DS115 with no problems. There was a warning that Minim wouldn't work any more if I did the update, but this turned out to be untrue, as Minim continued to work as normal afterwards.

Heads up you guys that had issues with DSM 6.1 on single core CPU

This morning some updates have come down the chute:

DSM 6.1.1-15101.     This has a whole list of changes.  ...........  bug & security fixes, support for scheduled RAID scrubbing & upgrade Samba to version 4.4.9.    Then it goes on to list 24 itemised fixes. 

Also in this release are some updates to the packages & includes a new Media Server  1.7.2-2830.   The release notes say its to make it compatible compatible with DSM 6.1.1.

Over to you,  hope it works OK this time

Further to the above.   The new DSM needs to be updated manually for some reason & not the usual auto-update.  I really don't know why as apart from pressing the go button it does it all itself,  needed me to sign in tho',   Not having done a manual update for a while, it did seem to take longer than I recall from the past.   Whatever its all working OK.

The Media Server software was installed 3 days ago & I had not noticed but when I opened up the 'Package Centre' it asks to acknowledge new terms & conditions.

Likes (0)
×
×
×
×