Trending Lyricist I

Answered

I can no longer add full music library - only 20GB of 125GB

Forum|Forum|1 year ago
October 10, 2024
45 replies
1114 views

Before the new app, I was able to listen to my home music library which was kept on a usb hard drive that was attached to a D-Link router. The music library is about 125 GB and consists of around 25,000 files (a mix of mp3 song files, as well as a few jpg for album art, plus each song had an .info file associated with it). Everything played well. I mostly avoided the debacle of the new app rollout as I disabled all software/firmware updates, but unfortunately a firmware update made it through anyway, so I had to update to the new app, rendering my music library unreachable; I believe the issue was the smbv1 was no longer supported with my router. So, I recently updated my router to a TP-Link that also had a usb port so I could continue using the external hard drive I had my music on. Long story short - I can only add a total of 20GB of my original music library.

If I try to add the whole folder in one shot, it seems like it’s doing something for about 10 minutes, then I get an error saying: “[myfolder] is no longer available. The device where music files are stored may not be powered on, or the path may have changed.”

If I set up a folder with a just few artist/abums, Sonos will index it without the error, and they show up on the Sonos app and play fine. If I add more artists/albums to that folder and ask Sonos to update the library, they are added, but only up to 20GB of music. The second I add any additional music (either to the same folder, or a second folder) I almost immediately get the same error message. What is happening? Where is this limit coming from? It shouldn’t be the 65,000 song limit, since I have much less files than that, plus everything played great before all the changes.

Anyone have a similar issue that figured it out? Or is there someone with a similar recently added library set-up (usb drive to router, i.e. not a NAS), that has a library larger than 20GB that works? Then at least I’d know it’s not a purposeful Sonos imposed limitation.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

Best answer by Ken_Griffiths

I understand the 65,000 track limit you refer too is not a track limit, but what I will term as ‘memory slots’ and some tracks may take up more than one slot. There are also these limitations which I found in other threads here in the community…

Field Name Character Limits

Artists - 76
Album - 92
Track - 100
Genre - 22
File name - 100

So maybe you’re exceeding some limitation that’s causing you an issue, but maybe contact Sonos Support Staff via this LINK and see if they can perhaps assist you further.

Show previous replies

I

IzzybonesAuthor

Trending Lyricist I

@DGR1 Thanks for your comment. I think my file and tagging structure is pretty clean as well. I took great pains when originally ripping my CD collection to use a tagging software to make everything consistent and simple. If the problem was something like a bad file then you’d think I wouldn’t be able to add it at all, whereas files that won’t get indexed if I’m at 20 GB with the existing share, will get indexed if I first remove some files from the music share. I also have a One which I unplugged along with the Play3, but still no change. I’m glad to know that you’ve got a larger share - is it also on a usb drive connect to your router? I assume you haven’t had to delete and re-add the entire library at any point since the new app? I’m wondering if this indexing issue is primarily affecting people who had to start over with indexing, rather than those who never did any big changes in the first place. I hope it’s not my new router limitation; it works great otherwise. My older router was cheap but seemed to play nicely with the Sonos library before they took away the SMBv1 support.

DGR1

Chromatic Producer I

@DGR1 Thanks for your comment. I think my file and tagging structure is pretty clean as well. I took great pains when originally ripping my CD collection to use a tagging software to make everything consistent and simple. If the problem was something like a bad file then you’d think I wouldn’t be able to add it at all, whereas files that won’t get indexed if I’m at 20 GB with the existing share, will get indexed if I first remove some files from the music share. I also have a One which I unplugged along with the Play3, but still no change. I’m glad to know that you’ve got a larger share - is it also on a usb drive connect to your router? I assume you haven’t had to delete and re-add the entire library at any point since the new app? I’m wondering if this indexing issue is primarily affecting people who had to start over with indexing, rather than those who never did any big changes in the first place. I hope it’s not my new router limitation; it works great otherwise. My older router was cheap but seemed to play nicely with the Sonos library before they took away the SMBv1 support.

Hi @Izzybones Yes, I have a USB thumb drive plugged into my main router node. And yes, I have removed and re-added the library a few times since May. I don’t link this particular issue to the new architecture that’s been deployed.

I always use the desktop app as opposed to mobile because you get no indication of progress on the mobile app. My music is split into 11 folder (ABC etc) because that has been recommended, but at present I only have a single entry for path/music that is working. Whenever I see the error, I also see an SMB credits error reported in my router’s log.

TBH, sometimes when I add an album to my collection (I love buying cheap CDs from ebay and ripping them), and then use ‘Update Music Library Now’ from the desktop app, I can get an error almost instantly. Other times it will work. So I haven’t entirely convinced myself that this isn’t an Asus issue. However, I saw the same issue when using an old WD MYBOOKLIVE NAS. It supported SMBv2, but a full index would often fail.

I can access and use shared folders from my USB drive from other devices with no issues.

Your issue is slightly different in that you can recreate the problem at will, just by breaching a size limit.

Are you able to see your TP-Link router logs anywhere to check for any SMB credit messages?

I

IzzybonesAuthor

Trending Lyricist I

@DGR1 I use the desktop app as well. Prior to this I was using a router with the SMB1 protocol and didn’t experience issues, although my library has remained static so never needed to update my library, and I was able to avoid all the updates until recently when somehow my speakers got an update (tho I had those updates turned off, along with app updates, so not sure how that happened). It’s the change to SMBv2 that seems to be the problem, so maybe you’re right that this is a separate issue from the new architecture, and as someone else pointed out is just becoming more evident since more people are forced to move away from SMBv1.

I can see a general log on my router, and there’s a bunch of entries that relate to various processes starting stopping, including some references to USB3 and Samba processes, but nothing that stands out as an obvious error message. And no evident correlation between times I can successfully index vs not, but I’m no expert in these things.

buzz

Grand Maestro

@buzz yes, I have tried splitting into more than one share, I can delete and add between the shares and Sonos will index properly, but if the amount of music the the shares are indexing goes over the 20GB limit I can no longer add additional music to any share - even if I add a single album to brand new share, it will error out if I already have reached 20 GB between the other shares. I tried unplugging the Play3 to see if that was the speaker doing the indexing, but it didn’t change anything.

For the idxtrx you were referring to, is it found when I go to that http://ipaddress.. link you mentioned earlier? When I do that, I get a list of all my speakers that are online, and can click on each entry to expand for more info, but none of them have anything pertaining to idtrx. The list beneath each speaker is identical, actually, and no reference to idtrx.

Appreciate your input, thus far. Thanks.

I

IzzybonesAuthor

Trending Lyricist I

@buzz I see, I’d didn’t expand them enough for the additional info. Thanks.

I checked all the speakers and they are all blank in the idxtrk column, so does that mean they are not getting hung up on any particular files?

If nothing else, I’m learning random info about my speakers…

I

Ian_S

Prodigy III

If you’re ok with doing it, can you plug in the USB drive to a PC or Mac and share the folder over the network? Then point Sonos to that network share and see if it indexes from there? That would help narrow down if it is a problem with indexing or the router.

If you use the desktop app, do NOT use either of the first two of three options for sharing your local music library or an external drive. They don’t work and never will again…!!

buzz

Grand Maestro

It means that the indexer has not flagged some sort of invalid character and aborted the run.

Note: I’m assuming that the updated firmware still uses this flag. Originally, I thought that you were using S1. I would not have posted the comment if I had known that you were using S2.

I

IzzybonesAuthor

Trending Lyricist I

If you’re ok with doing it, can you plug in the USB drive to a PC or Mac and share the folder over the network? Then point Sonos to that network share and see if it indexes from there? That would help narrow down if it is a problem with indexing or the router.

If you use the desktop app, do NOT use either of the first two of three options for sharing your local music library or an external drive. They don’t work and never will again…!!

I attached the drive to my PC and Sonos indexed it properly. So at least I know it’s not a Sonos size limitation, or a problem with the hard drive itself.

I checked with TPLink (via email) and they confirmed my router is SMBv2. An interesting note they made was that TPLink supports 10,000 media files…I’m trying to confirm that they mean that limit is for the router’s built-in media server, not a samba connection. I provided them more detail on my situation to see if they have any further insight on the possible issue. Although 10,000 media files would be still be more than what Sonos is currently indexing via the router before it starts misbehaving.

I

Ianp

Collaborator II

If you’re ok with doing it, can you plug in the USB drive to a PC or Mac and share the folder over the network? Then point Sonos to that network share and see if it indexes from there? That would help narrow down if it is a problem with indexing or the router.

If you use the desktop app, do NOT use either of the first two of three options for sharing your local music library or an external drive. They don’t work and never will again…!!

I attached the drive to my PC and Sonos indexed it properly. So at least I know it’s not a Sonos size limitation, or a problem with the hard drive itself.

I checked with TPLink (via email) and they confirmed my router is SMBv2. An interesting note they made was that TPLink supports 10,000 media files…I’m trying to confirm that they mean that limit is for the router’s built-in media server, not a samba connection. I provided them more detail on my situation to see if they have any further insight on the possible issue. Although 10,000 media files would be still be more than what Sonos is currently indexing via the router before it starts misbehaving.

This really sounds like another issue with the SMB credits issue I had asked the moderators to flag as a bug. Try running the indexing operation/re-adding the share a few times as that eventually worked for me, and some others as outlined in other threads here.

S

sambrosius

Trending Lyricist I

On a Level 2 support call now

And yet they seem to imply I am the only one with this problem. So sad.

Show more replies

Sign up

Login to the community