These are the typical culprits (and remedies) for a failure to mount a network drive in Linux:
- A stale mount left over from a previous run of Jungle Disk. This occasionally happens when Jungle Disk isn't given an opportunity to shut down gracefully. As root, run umount /path/to/jungle/disk/mount/point.
- Make sure the local path you're trying to mount to actually exists, and has read-write-execute permissions for the user who is running JungleDisk.
- The mount point should have no contents. Sometimes stuff gets in here when you think a Jungle Disk Network Drive is mounted and it isn't (and you subsequently copy files to what turns out to be a plain ol' local directory). In this case, you'll typically see a "Mount point not empty" message. Shutdown Jungle Disk, and remove the files and folders you see in this location then attempt to mount the drive.
- More than one instance of Jungle Disk is running. Note that prior to V2.90, you cannot run "jungledisk" and "junglediskmonitor" simultaneously. Also note that an instance of jungledisk runs if you add an entry to /etc/fstab to mount drives automatically at boot time. Type "ps aux | grep jungledisk" at a command prompt, and shut down any extra processes that are running.
- fuse should be activated in your kernel. If this is the issue, and if you're running the GUI version of jungle disk, you will typically see a message telling you to run "modprobe fuse" in the Errors and Warnings sections of the Jungle Disk activity monitor. See the INSTALL text file (part of the Jungle Disk download) for more information on setting up fuse.
These are the typical culprits for a failure to mount a network drive in Windows:
- A device is already mounted to the drive letter specified in the JungleDisk configuration. Change the drive letter of the JungleDisk drive. See "My Computer" for current letters in use. Symptoms include failure of the JungleDisk service from starting properly.