Posts made by Jormungandr89

@jonas My apologies, I meant to follow up on this on GitHub and hadn't found time. I took a look at the code links, I have some background in reading code at least, but I was out of my depth to be honest.

So, I've tried this a couple of different ways. I have the NAS server in the closet, and I can access it on my Linux PC via NFS (which is set up to automount on demand via autofs, and unmount after inactivity), as well as a more traditional SMB. The SMB I have set up to mount in fstab. I've tried setting my full library to one or the other and I do see the same issue via both protocols. Well, with subsequently added folders since changing the mount point results in a new library.

To add some more confusion: I recently shrunk my Linux partition and installed Windows in a dual-boot configuration since I had need for it. I decided to try Strawberry on Windows, accessing the share via SMB. I have it set as a networked drive (M:), and my library is pointed to M:. I do not encounter the issue on Windows -- it seems to add new directories just fine on startup when set to scan for changes.

I also experience this issue on Arch Linux. The library scan will detect new albums in existing artist folders but not new artist folders.

My general fix is the same as the other user mentioned -- deleting the Strawberry database and then rebuilding the library. However, this is suboptimal because I lose play counts etc. and the it takes a long time to rescan the library. My files are on an NFS share. In <share>/music, there are ~770 artist folders, with varying amounts of subfolders.

I tried running Strawberry from terminal with verbose flags, doing a full collection scan, and dumping the output to a file (which ended up quite large). When I searched the file, there weren't any entries for the new artist folders that weren't getting added -- meaning, there were not any errors produced by the scanner for those files. Additionally, once I've deleted the database and performed a rescan, the files are then added correctly and function correctly, so I don't believe that the files are an issue.

I've had to do this workaround a number of times to get new artists added, so I went looking for some troubleshooting or a fix. When I had the files stored on a local drive rather than NFS, I did not encounter this issue. There were a few less artist folders at that time, but still in excess of 725 or so.