Steve Insley

This isn't a solution to the problem. In fact, I said that I did that in my original post, but the problem would recur again straight away. Did you read my post?! To say again - this turned out NOT to be a Subsonic bug, but rather a problem caused by StableBit Drivepool.

UPDATE: After a LOT of investigation, it turns out that the issue is with StableBit Drivepool. I have a pooled drive on which I keep all my music. Unfortunately, unless all files are all under one folder that exists on one drive (in the pool) only, the timestamps of the folders are not reported properly and Subsonic cannot "see" the changes when it scans. So either: a) StableBit need to fix this (what I believe to be) bug and Subsonic should work ok, or/and b) Subsonic needs to be updated to be a...

My content file is 3.62GB. To be clear, my content file is read in about 30 seconds. It the initial scan of disks (which I guess is cataloging the files on then prior to sync) that takes 23-24 mins.

I have 3.75 million files that are 50TB in total over 7+1 disks. Snapraid uses 5800MB of memory for the filesystem during operations. When kicking off a sync, the loading of the content files and scanning of the disks takes about 24 minutes regardless of how many files need to sync. I'd say having lots of files is a disadvantage, but what can you do?! I guess putting lots of the smaller files into archives would help, but that might not suit all use cases.

I have been through three disk upgrade cycles now (1TB->4TB->8TB->12TB disks) and have done it the way you described a few times. Since I have eight disks in my array and I always upgrade and check one at a time, that's a lot of effort! On a couple of occasions, I got far more files needing to be synced than expected though - this was in the days before I ran "check" after swapping the disks as I hadn't appreciated the need. What I've found to be far more reliable and faster is to use an external...

Based on your comments above, I decided try the following: 1) stop subsonic service 2) create a new folder to contain all my music 3) move all folders from my old music folder to the new one 4) delete the old music folder 5) rename the new folder with the same name as the old one 6) restart Subsonic This seems to have helped the situation in that new artist folders (and albums within) are now detected by Subsonic when I run a scan! However, there seems to be a few minutes of lag between the scan...

FURTHER UPDATE: If I manually add an entry into the MEDIA_FILE table in the database through the db.view page using (my specific case example): insert into media_file values (46015, 'R:\Media\Music\Perturbator', 'R:\Media\Music', 'DIRECTORY', null, null, null, 'Perturbator', null, null, null, null, null, null, false, null, null, null, null, null, 'R:\Media\Music', 0, null, null, 0,0,0,0, true, 5) ...and then re-scan the library, the album that exists in that folder now shows up!! I think the (potential)...

Extra info: - Running 6.1.3 - Premium licence - Windows Server 2012R2 - up to date with all updates To elaborate after some additional testing, another use case is: I have a new album for a new artist for which I have no other albums I add a new folder at the root of my music folder for the artist and a sub-folder for the album that contains the tracks. Scanning does not update the library with the new album I add a new folder for the new artist's album into an EXISTING folder for a different artist....