Cannot scan a network drive

by **turls** » Sat Jan 20, 2007 6:06 am

I still would like to see MM incorporate some kind of a timeout so situations like this don't just hang/crash MM, as I was fine on every other app for months even with the jumbo frame issue (if that is for sure what the issue was). That's why I'm interested to see what other NAS with jumbo frames do, because I don't see why their implementation would be that different from other vendors using Linux/Samba.

by **Hexland** » Fri Jan 19, 2007 8:21 pm

This might be the answer to my thread too

http://www.mediamonkey.com/forum/viewto ... highlight=

by **turls** » Fri Jan 19, 2007 6:39 pm

Watch out there is a glitch in current software on ReadyNAS, don't mess with the speed (leave it on auto-negotiate)--just change MTU to 1492 and turn off Jumbo Frames. You may want to just try turning off Jumbo Frames first.

I had to get beta firmware to correct my mistake of switching to 100mb instead of auto-negotiate.

Also, I'm wondering if anybody has a NAS with jumbo frame support that they haven't had this issue on.

I've got too many devices that aren't jumbo-frame compatible to be messing with that anyway, good time to turn it off.

by **jiri** » Fri Jan 19, 2007 5:12 pm

To clarify: As far as we know (and we are pretty sure about it), it isn't a problem of MM, it's a problem of the device that's just sometimes triggered by MM scanning tracks.

Jiri

by **Lowlander** » Fri Jan 19, 2007 4:16 pm

@Developers
Are you planning to solve possible this issue with jumbo frames?

by **rusty** » Fri Jan 19, 2007 12:41 am

Received word of the following from turls. Hopefully it'll help others out there:

I've turned off Jumbo Frames, set MTU to 1492, and everything with scanning and MediaMonkey seems much faster. Files that hung it up before now complete scanning just fine.

-Rusty

by **turls** » Fri Jan 12, 2007 11:11 am

Unfortuantely, on the Infrant front, MediaMonkey support has passed the issue back to them and they haven't given me a hint of any solution in weeks. I hope this isn't a trend as they (infrant) were always responsive in the past. They've got too much competition to go downhill on support.

by **Kos** » Fri Jan 12, 2007 8:40 am

My 12000+ songs stored on a Maxtor Shared Storage Plus were detected quickly by MediaMonkey. To make the MediaMonkey package complete all we need now is a MediaMonkey media server!

Kos

by **turls** » Sat Oct 21, 2006 5:24 am

Looks like MediaMonkey support is going to try to figure out the deal with Samba shares in the future, in the meantime, if this issue affects you (I have it with a Infrant ReadyNAS), try

http://ccollomb.free.fr/unlocker/

To unlock the folder when it gets hung. This should allow MediaMonkey to get past the file locking issue and complete the scan.

by **turls** » Sat Sep 23, 2006 10:36 am

I have an Infrant ReadyNAS--I'm still having issues. Debug logs don't help because they don't show enough detail even with the debug version. (I've been working with Russell but he told me he was kind of busy with the new release version and hasn't worked with me much yet).

A similar/same issue is also covered in this thread. Is anybody else noting this type of behavior? ("doesn't always stop same place", "have to kill the process manually")

I'm hoping others with the same issue with a SMB device will respond here or contact support--I think this is going to be a hard one to track down. It is very intermittent for me, but I can't narrow it down to consistent behavior for any certain file/track.

I think we can get Infrant to help as they have worked with software developers before.

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

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).

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!

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.

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.

Cannot scan a network drive

Post a reply

Expand view Topic review: Cannot scan a network drive

Solution to NAS scanning problems

Just for your information

Possible workaround

Still issues

Fixed in MediaMonkey 2.5.4.971 (beta 2)