Connection to Shared Folders and Media

[Jessica Moran]

I have been having a problem where my connection to a storage location through the "shared folders and Media" feature seems to only work intermittently. From the VirtualBox Manager it shows that I have mounted a location and have full access, but when I launch BitCurator often the location doesn't appear. I haven't been able to figure out any pattern for why it is or isn't appearing, but I wonder if anyone else has experienced this? Or if I should be trouble shooting from VirtualBox or my network permissions rather than from BitCurator?

Thanks!

Jessica Moran

[Jarrett Drake]

Hi Jessica,

What's your host operating system and which version of the BitCurator VM are you running? I've only tried to share a folder between the BitCurator VM and a folder on my host machine's Desktop, but your mention of a storage *location* makes me wonder if you're trying to connect with a folder on a remote server or on a computer other than the host machine? If so, one possibility might be a permissions issue with that network connection where it's not allowing the VM to map its connection. But, then again, that doesn't seem likely given that you see the folder intermittently. If you start the BitCurator VM, launch the Nautilus file browser, click on Computer, then double-click the media, you should see a folder that reads sf_[folder name]. Is this the case for you?

Alternatively you can launch a terminal window in BitCurator and enter the command df -h to populate a list of all available drives. A successfully shared folder will appear there as well. If you see the folder in this Terminal output, I'd check the permissions of the folder by changing into the media directory (cd /media) and entering the command ls -l (that's a lowercase "L"). The permissions appear first. For instance, mine reads:

drwxrwx--- 1 root vboxsf 136 Jul 15 02:15 sf_Accessions

This output means:

1) this file is a directory named "sf_Accessions"

2) the directory's owner ("root") has read, write, and execution privileges

3) the directory's group ("vboxsf") has read, write, and execution privileges

4) no one other than the two aforementioned users has read, write, or execution privileges.

Depending on your output, you may try amending the permissions of the destination folder accordingly. I hope this helps!

Best,

Jarrett

--
You received this message because you are subscribed to the Google Groups "BitCurator Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcurator-use...@googlegroups.com.
To post to this group, send email to bitcurat...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcurator-users/b1cfc646-08cf-43f2-a6cb-16a243b046b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jessica Moran]

Hi Jarrett thanks for your notes.

I'm on Windows7 and was using BitCurator .9.13 and I was trying to connect to a remote server. Like you I did have suspecions that it could have been a permissions issue, however that would seem weird as it does connect some of the time.

However in the meantime I've installed the later 9.20 version of BitCurator and was able to connect on the first try so I'll hope that it was a fluke for now, but thanks for the notes on how to check my permissions if I run into the same issue again.

Jessica