Cannot scan a network drive

robertiles · Post by **robertiles** » Mon May 22, 2006 1:12 pm

Have been using MM for a while with the music files on an old (otherwise unused) computer on my local network. Today I got a brand new network drive (yummy) and copied all the music files over to it ...

I accept that I cannot monitor such a drive BUT when I try to scan it, or rescan it, it finds only 70 tracks then stops ... there are actually over 2,500 tracks there!

So, if I pull up the rescan window and click on the area of the network drive (\\Storage\MUSIC\) it finds only about 70 tracks, BUT, if I un-check one of the sub-directories it finds all of the remaining 2,500 tracks ....

Hmm ... help!!!

Bex · Post by **Bex** » Mon May 22, 2006 1:16 pm

What MM version are you using? There was some problems regarding this in previous versions which claims to be solved in the latest version released today.

/Bex

robertiles · Post by **robertiles** » Mon May 22, 2006 1:21 pm

Latest .. 2.5.3 build 963 .. I updated as I saw some earlier stuff on this

Bex · Post by **Bex** » Mon May 22, 2006 1:25 pm

Then you might have found a bug. Install the debug version of the latest build and send the log to the MM team!

/Bex

robertiles · Post by **robertiles** » Mon May 22, 2006 2:38 pm

Thanks .. have done that

robertiles · Post by **robertiles** » Mon May 29, 2006 8:14 am

Emailed the bug report and debug log as per the posting above but have had no response ....

Bex · Post by **Bex** » Mon May 29, 2006 8:43 am

I dont know how long time it usually takes to get an answer but I'm sure they will get back to you eventually.

Post by **jiri** » Mon May 29, 2006 9:02 am

Actually, I was just studying it. I e-mailed you some info so that we could get to the bottom of this...

Jiri

robertiles · Post by **robertiles** » Mon May 29, 2006 9:16 am

Thanks Jiri ... I wasn't moaning, just concerned it hadn't appeared on a bug list or anything .. mind you, it could still be pilot error rather than a bug!

amigoaz · Post by **amigoaz** » Sun Jul 02, 2006 1:41 am

Confirmed the problem exists on my network storage also. I moved the files back to my local system hard disk and MM found all of them just fine. So I'm guessing it's some kind of error in handling network files. On the full database of 11,000+ tracks, 800+ directories I ended up with a playlist of only 1,200 tracks being found and about 105 directories being used.

I also tried file search instead - same result. Always hit a hard limit of about 1200 tracks and 105 directories on the network storage drive.

Just as a test, a USB connected drive did not have any issues - it found all files without any problems.

This network storage drive is using SMB as a connection protocol - fairly standard stuff. For a quick run down, this site has some good info: http://66.102.7.104/search?q=cache:EyTh ... =firefox-a

thanks

illiniguy73 · Post by **illiniguy73** » Thu Jul 06, 2006 11:42 pm

i'm using a buffalo linkstation without any problems. i have about 8000 songs on it, all appear in mm. i believe the drive simulates an NT4 server.

amigoaz · Post by **amigoaz** » Sat Jul 08, 2006 1:48 am

What format for communication does the Linkstation use? Is it SMB or something else such as CIFS (common internet file system)?

I'm using something more basic - Landisk by Bytecc. Unit works great in windows explorer and using it on other programs. This box uses a short form linux to operate effectively as a NAS with SMB protocol.

It appears the mode of access is causing the SMB communications to terminate before the filelist can be completed. I've been researching on it and apparently there's a fast mode and a slow access mode (which verifies) for file access under SMB. There's a number of articles on SMB problems on Windows boxes on Microsoft's tech forum.

Best rundown on SMB/CIFS and the evolution of the protocol can be found here: http://ubiqx.org/cifs/SMB.html .. apparently the SMB/CIFS protocol is a loose set of standards.

Guest · Post by **Guest** » Sat Jul 08, 2006 1:59 am

amigoaz wrote:What format for communication does the Linkstation use? Is it SMB or something else such as CIFS (common internet file system)?

(jumping in here . . .) I looked at the Buffalo system at a network attached storage (NAS) solution for backup, but I ruled it out because it required proprietary drivers and was limited to less than 4GB file sizes for the backup software.

Tracking down these types of bugs is near impossible unless the developer has access to the same hardware. MM's track record for trying to track down these issues is admirable, though!

Post by **Lowlander** » Sat Jul 08, 2006 10:37 am

Please create debug logs as described in the bug forum when you use some form of network storage and have difficulties. This will help the developers figure out how they can improve MediaMonkey to work better with these drives.

I myself use Ximeta which seems to work without problems (I have problems with one, but I blame that on the drive not MediaMonkey).

Post by **rusty** » Fri Aug 04, 2006 12:31 pm

We've improved the scanning code so that it may work better on such devices.

Please confirm whether the problems have been resolved.

Thx.

-Rusty

Cannot scan a network drive

Cannot scan a network drive

Network storage problem on 2.5.968 also

Fixed in MediaMonkey 2.5.4.971 (beta 2)