Bugzilla – Bug 16112
Postpone scanner until after mapped network drives and USB drives are mounted
Last modified: 2011-08-24 01:44:27 UTC
When running Squeezebox Server as a service, it is possible for Squeezebox Server to start scanning before the USB hard drive or Network mapped drive is mounted on the system, resulting in a [There is no disk in the drive. Please insert a disk into drive \Device\Harddisk#\DR#.] Error which continues to spawn until the drive is mounted. Scanning continues as normal after this.
I have the same issue. please fix as I have multiple playlists
Where do you see the error? Is it in the console, Windows event logs, Sbs logs? Since scanning is a manual operation in 7.5.0, how does that happen, or is SbS simply looking for the Music Library folder at startup time? What happens if you create an empty folder on a permanent drive and then use shortcuts in that folder to your mapped network drives and USB drives?
not all scans are manual, like when u get newer versions or change certain options. SBS should check to see if it can mount a location and warn if it can't, prior to scanning, regardless of location type, imo.
> not all scans are manual, like when u get newer versions or change certain > options. SBS should check to see if it can mount a location and warn if it > can't, prior to scanning, regardless of location type, imo. Jim's question still is valid: when would you be able to trigger those options before the disks on the server are mounted? I'd assume that mounting drives is done pretty early in the boot process. You'd have to time your change pretty precisely to hit those few seconds when SBS web UI is available, but the drives are not yet.
i wasn't saying Jim's question wasn't valid, but did you read the first post? b/c you seem to be missing my point... since a previous USB/network drive might not be there at all, or since drives can be remapped, or since on windows machines mounting network and even internal drives CAN take a long time well after logging in, and/or not be reliable, then i believe that SBS should first check to see if the area known to SBS is in fact available and mountable, and if not, it should stop the action its trying to do, and give a visible "drive not available" warning to the user. it should only give the notice once, and not respawn, and instead go idle, until the user prompts it manually via whatever action. i was adding it should do that for ANY location, not just usb/network ones, imho. if i am missing the point, i apologize, but thats what i'm taking from what i've read so far...?