Won't Update Music Library, Part 2

All along I've felt it's that @John B , the files just aren't shared correctly and Sonos is not related to this.

Which was why I asked if they were accessible from a Windows explorer menu.

Yes, I think the seamusic folder is perhaps more to do with its DLNA server service, which is visible in the windows network area in the screenshot posted earlier, rather than an smb share. That was why my thoughts were to maybe try dropping a few music files in a different folder called ‘Music’ to see if that was then shareable and viewable as a Sonos library, once the path is switched to it and has been indexed.

The steps in that link are exactly what I’ve done. If you look at the screenshots of the router interface, it’s labeled “Network/Media Server Name”. (Additionally, it shows up in WIndows Explorer Network as a “Media Device”.)

I was feeling optimistic:

• I put a new higher-gauge extension cord on the router
• I put a new, shorter data cord on the drive
• I mapped to the entire drive (“\\rjbmusic\g\” not “\\rjbmusic\g\seatunes”
• It worked!
  So, like a complete idiot, I:
• Created a new subdirectory called “Music”
• Put one album (Nebraska, if you must know) in Music
• Added that as a library (\\rjbmusic\g\Music)
• It did not work - because it was a subset of the larger Library
  So, like someone who has been dropped on his head repeatedly, I:
• Deleted the working Library and added that single-album folder
• It worked!
  So I
• Added some new albums - about nine
• Tried “Update Music Library”
• It did not work
  But this is kinda what happens sometimes, for a while I could delete the Library and re-add it when it wouldn’t update (essentially from Novemberish 2021 through August 2022)
  So, like a mouth-breathing flat-earther, I:
• Deleted (\\rjbmusic\g\Music) and tried re-adding it
• Effin NOTHING. Cannot add.
• Cannot re-add the whole drive - which is what worked 12 hours ago

I thought, by definition, any storage device attached to and accessed via network devices (e.g., routers, switches) was a “Network Attached Storage” device, a/k/a NAS. Since the router actively supports and encourages attaching storage devices, what clever parsing of the semantics am I missing?

Back at Square One, again.

Going to try the SanDisk solid stick now.

Last thing before getting the USB stick out.

I added “Music” as an empty folder. Easy-peasy.

I added Nebraska (album) to it.

Now - both when I tried to update, and when I deleted and tried to re-add - I am getting this message:

Although, again, every other device on my network can access \\rjbmusic\g\

Have you checked with TP-Link? It sure sounds like there is something odd in their side of things. If Sonos can read a single folder, then it’s working properly. If it can’t read sub folders, then the TP-Link is doing something odd with SMB permissions. 

I await with great interest (genuinely) news of what happens with the stick.  Given what has happened so far, I can only be described as hopeful rather than optimistic.

Last thing before getting the USB stick out.

I added “Music” as an empty folder. Easy-peasy.

I added Nebraska (album) to it.

Now - both when I tried to update, and when I deleted and tried to re-add - I am getting this message:

 

Although, again, every other device on my network can access \\rjbmusic\g\

 

It is probably of no significance, but interesting that the error message says it cannot find the computer “rjbmusic”, rather than the folder or drive.

Yes - it looks like it was an attempt to link using the http protocol from a desktop Sonos app, rather than an attempt to link via SMB… http will not work unless the NAS has an http/https server.

So I guess I can’t multi-quote in this board. I thought that was weird, too, John. But since it was mapping it as an entire drive, I thought, welll…. Ken, I have no idea what you’re saying/suggesting.

I almost exclusively use the desktop app, I only use the Android when I’m forced to, or for something simple like volume (i.e., doesn’t require typing).

UPDATE

• Added the stick - SEADRIVE
• Created a folder - SEATUNES
• Added one album
• Success

Well, “Success” = it accepted Libary. Could not play file (1002 error I think). Restarted Sonos app. Played file.

Got cautious.

• Added one more album (copied over WiFi)
• “Update Music Library Now”
• Success

Got curious.

• Added one more album (copied over WiFi)
• Let the nightly scheduled update run
• Success

Got cocky.

• Added a handful of artists (copied over ethernet, little faster than WiFi) - just the “A”s (by first name, so “ABBA” and “Amanda Shires” go, but “Herb Alpert” doesn’t [\sidenote])
  • Can confirm via Windows Network and Android FTP the files are there
• “Update Music Library Now”
• //seadrive/g/seatunes is no longer available. The device where the files are stored may no longer be available….
  • I get that same message if I try to update via Android app

George Carlin did not have the vocabulary I am using right now. The amount of time (and money) I have thrown at this is staggering.