Bugzilla – Bug 6812
Drive letter or map where to derive the music from
Last modified: 2008-01-28 02:39:29 UTC
This is more a request than a problem, however.... Within the first server setup page you can enter a drive letter or map where the server can find the music files. No problem when you have a NAS running, but with a SFF PC as I have, its becoming a problem. Why? I have aprox. 700GB .wav files and a 500GB and 300GB harddisk, but I can only specify one drive letter. A RAID 0 setup is not the thing I want, because of the fact that all is lost when 1 disk is defect. Software RAID 0 is even less wanted. So the question I would ask is if it is possible to enter at least 2 map names or drive letters for Slimserver to index. It shouldn't be a big change (I think) and it is a real upgrade from the current situation. best regards, Peter.
Michael: do you have a workaround for Peter?
Isn't this a dupe of bug 607, the age-old request to be able to designate multiple music folders? An oldie, but a goodie. The workaround is to create Windows shortcuts or *nix links from the designated music folder to all locations wehre you store your music files. It works, but it's pretty crude.
Thanks Jim. This is a dupe indeed. Workaround as mentioned: put shortcuts from the "other" musc folders to the main music folder. *** This bug has been marked as a duplicate of 607 ***
Dean, Jim, Michael, Thank you for your fast response!! I have read the text entries on bug 607 and I am wondering now about the workaround, because Jim wrote: ------- Comment #17 From Jim Zolx 2007-01-28 11:13 [reply] ------- Here's a very good reason (IMO) to implement this: It would permit SlimServer to actually validate access to all the folders, as it does now for the single music folder. This would test against permission and network access issues that will otherwise go unseen by the user when using shortcuts/links. With shortcuts, all the user knows is "it didn't work". If tested in the settings, SlimServer can flag inaccessible folders and suggest possible causes and fixes. One common problem is the renaming of shares and folders. Without actually trying to follow an old link, the user won't know that it's no longer valid. If instead, users could test access to the folders (ideally, add a button to test access to existing folders to the setings page) within SlimServer, then they could easily see which are still working. Even more difficult are changes in permission - a shortcut/link may be valid for the user, but fail for SlimServer. So, is it really a good workaround? Are there still initiatives to make a definite solution? best regards, Peter
Yes, it's a good workaround. But no more than this. It's a solution to work around a problem. It's not the best solution. The multi-path solution is still an open request. We didn't target it for a release yet, but we didn't close the request neither. Don't know why your re-opened, as it's still a the same duplicate as before. Feel free to add your comments and vote to bug 607. *** This bug has been marked as a duplicate of 607 ***