Won't Update Music Library, Part 2

I decided to check some of those assumptions.

I broke the “Seatunes” subdirectory into even smaller subdirectories.

The first three mounted A-OK, the rest did not.

The three that mounted were 29.6GB, 26.1GB, and 6.7GB. The ones that did not were 29.1GB, 39.0GB, and 25.4GB. So nothing consitent about the size of the subdirectories.

Of course, during all this is when the system did its semi-weekly “I think I’ll just start dropping speakers at random” ****, so I had to go and do the unplug-all-the-speakers-unplug-the-router-plug-everything-back-in-and-spend-the-rest-of-the-night-screaming-at-the-speakers-that-just-keep-dropping-out-at-random.

I have had this system for over four years. I don’t think it has behaved correctly for 14 consecutive days.

*Moderator Note: Modified in accordance with the Community Code of Conduct.*

Most people, when they use the term ‘NAS drive’, mean a device with one or more disk drives and an operating system. I would guess that 99% upwards of Sonos users who store their music on a ‘NAS’ have a device that connects by Ethernet, although I would not wish to claim that ‘NAS’ implies an Ethernet connection.  I can give you no reason why what you are doing is not working, but maybe you could consider the sort of device and connection that works for so many of us.

I’ve not been following this thread, and have just attempted to skim read it so my comment may be inappropriate.

I’m curious. Why does “…/g/...” keep featuring in the UNC path after the device name? I don’t see a partition named “g”. 

In one screenshot there was a label “G:” which was presumably the Windows mapping. This means nothing to Sonos.

Any mapping is neither here nor there. It has no meaning outside of Windows, where it’s merely a temporary shortcut to a shared folder.

I’ve used flash drives mounted in TP-Link, Asus and Netgear devices (as well as BT routers OEM’d from different manufacturers).

The path to the top level folder is always something like //routername/partitionname or //routername/volumename, or more often in my case //routerIP/volumename etc.

Sometimes the router assigns the volume name, e.g. “usb” in the case of a Netgear running stock firmware. Sometimes it uses the device name from the drive itself e.g. “//192.168.2.1/corsair” on that same R7000, but running FreshTomato.

Sonos is currently pointed at 5 different subfolders of “//192.168.2.1/corsair”.

I tried pointing at //192.168.0.1/ and every suffix I could think of.

As far as I can tell, “G” is just something the router is using to navigate up its own arse. My previous router it was “sda1” (i.e., //RJB-MEDIADRIVE/sda1/Seattle Music Library)

My brother in law has two speakers. If he keeps them separate and only on Sirius, he loves it. When he tries to do anything more sophisticated, it freezes on him.

I have a friend who, like me, hooked up his turntable via Connect. He can get it to work to his wired speakers in one room, and we have never been able to get the speakers in other rooms to work.

I recognize I’m pushing the limits of the system - multiple speakers, analog inputs, Music Library, but FFS I live in a 1200 sq ft single-level apartment in the year George Jetson was born. This should work.

You, your brother-in-law, or your friend are likely not pushing anything to even being close to their limits @Alonzo Mosley  - a line-in source will, under normal circumstances, happily play to every Sonos speaker in the same system - you can even adjust the audio buffer to cater for such line-in audio and can compress that audio too… plus when playing across grouped rooms there is an option to set the size of an audio buffer - but without detail, it’s still difficult to pass comment about the issues faced, as you are only presenting scant detail about your friends and brother-in-law’s issues.

All I can say is, if it’s possible to do something in Sonos, then in my own experience, it will usually work well and in ‘most’ cases where it doesn’t, it’s usually either a network issue, or sometimes a hardware issue …and of course it can sometimes be a users understanding of how things work. 

Your NAS however and the way it’s setup is not anything I’ve ever come across before and as @ratty mentions the G partition when connected to the router plus the path //RJBMUSIC/g/seamusic is very unusual to the extent I would go back to the device manufacturers support desks and ask them how to access the SMB share… it clearly does not work the way most ‘similar’ shared SMB drives work.

Many here have tried to help, but it’s time to speak with the makers of your hardware and see if they can put you on the right track.

More detail will be needed to solve you’re friends and brother-in-law issues. I recommend you advise them to post in the forum separately, or perhaps contact Sonos Support via this LINK

I’m not trying to diagnose anyone’s problems but mine, I’m just demonstrating that in my subset of “real” people I know with Sonos equipment, no one is happy with their purchase. But, to paraphrase Churchill, it may be the worst but it’s better than the alternative.

It just strains credulity that this issue - the lack of updating, then the lack of adding - is rooted in network hardware, which has been replaced twice; controllers, four of which have been replaced and run on three different operating systems; or storage hardware, which has been replaced twice. The only thing that has remained constant - and which has so far remained blameless - is the software. (I know it hasn’t remained constant constant, there have been updates, but I have no way of tracking that…!)

I have managed to mount all of my mini-subdirectories, save one, but they will not “Update” - either on the 2AM scheduled or when I push an Update. From Android:

I have a router coming - not the Netgear but an Asus AX6000 -  and the ethernet MyCloud coming tonight. I will open one. Which? @sjw comes in with a last-second vote for the drive. Anyone else?

(The documentation on my existing router is weak. Which of course is why I’m currently stuck with that weird “partition” (in quotes because I don’t think that means what they think it means) and why I can’t answer any of the router-related questions. The old router - a TP-Link AC1900 - is already at Goodwill. And caused problems anyway).

A “real” NAS has its own operating system, CPU,  memory, and settings, none of which exist in a thumb drive attached to a router that is “treating” the external memory as an NAS is some simulated fashion. 

The only reason I chose that word is based on the sporadic nature of the connection - sometimes it makes it, sometimes it doesn’t; it seems to be kinda sorta related to the size of the data read (a low r value, for sure, but it seems more than just coincidence).

Sounds like @Airgetlam is advocating to hook up the MyDrive vs. the router.

(Although now I’m worried -  This is the one I bought, and everything I read yesterday made it seem like it would fit the bill. But I just saw on the WD site “Unlike a NAS...” It does have an RJ45 connection, but that doesn’t sound like that’s the distinction that I need.

So should I return that and get something like this one or this one? (I can’t begin to attempt to fathom something like @Ken_Griffiths ‘ “old Netgear NAS boxes (mirrored drives), which I added more RAM too to keep them going - currently running the latest Netgear OS6 operating system (Linux-based)”…

The one I mentioned to get from your links specifically said Network Attached Storage (i.e. NAS) (the black one) but looks like you went with the other one.  That then fell off a truck.  That seems NAS-like too so not sure about the ‘Unlike a NAS' comment, other than it appears to have Cloud based options now.  Which most NASs nowadays have anyway.

It appears you're also looking at Synology now which would be my preference all day long - except would be a 2 Bay one.

These devices do hook up to the router - but via RJ45, not USB.  They also can have USB drives attached too and I've never experienced issues accessing them this way either - but for sure you should be using the ‘internal' storage preferentially.