Mount Shares Locally

	WARNING
	This is recommended only for advanced users, proceed with caution.

NOTE: Recommend not using copy and paste for the steps below. It often introduces hidden characters which causes failure in the script.

Mounting your Samba shares locally is useful when you are using Greyhole, and want to write or in any way work with those files locally. Greyhole data should only be accessed through shares, so mounting those shares locally is an easy way to work with Greyhole data safely.

Download and Setup

• As root: Install the mount_shares_locally initd script:

On Ubuntu

sudo apt-get install cifs-utils curl
sudo curl -o /etc/init.d/mount_shares_locally http://dl.amahi.org/mount_shares_locally
sudo chmod +x /etc/init.d/mount_shares_locally
sudo update-rc.d mount_shares_locally defaults

On Fedora

curl -o /etc/init.d/mount_shares_locally http://dl.dropboxusercontent.com/u/3022105/Amahi/mount_shares_locally
chmod +x /etc/init.d/mount_shares_locally
chkconfig --add mount_shares_locally

Configuration

• Edit /etc/init.d/mount_shares_locally (as user root) in a text editor, and replace your_username (on line 12) with your username. Example username="amahi"

bash code
​nano /etc/init.d/mount_shares_locally​

• Create the /home/your_username/.smb_credentials file. This is a simple text file (use your favorite text editor).

bash code
​nano /home/YourHDA_username/.smb_credentials​

• Enter the following:

username=your_username
password=your_password
domain=HOME

NOTE: your_username and your_password in the .smb_credentials file needs to be the original username and password you created when you installed fedora.

• To test your new mounts, you can execute service mount_shares_locally start (as root user)
  

service mount_shares_locally stop (as root user) will unmount the local shares.

NOTE: If you used /etc/rc.local and /etc/fstab to mount shares locally in the past, you can remove what you added in those files now (DO NOT remove the drive mount lines). The above initd script replaces all this.

Re-mount to Add new shares

If you added new share to greyhole via the web admin. This does not automatically mount locally. You need to restart your mount script by running service mount_shares_locally restart. This will unmount and remount all your shares, adding all the new shares you added.

Where everything is mounted

You will find the mounted shares in /mnt/samba/*
For example, your "Pictures" share would be located at /mnt/samba/Pictures.

NOTE: When working with files on the HDA, access them via this share and NOT the traditional /var/hda/files/pictures location.

Unable to mount locally after upgrading to Amahi6

If you try to run mount using this script after you upgraded to Amahi6 you might get greeted by this type of error.

[root@localhost ~]# /etc/init.d/mount_shares_locally start
Mounting Samba shares locally: /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
                                                          [  OK  ]

It's easily fixed by installing the missing dependency.

bash code
​yum install cifs-utils​

Now it should work fine to run

bash code
​/etc/init.d/mount_shares_locally start​

MySQL Problems With Newer Versions of Greyhole

Since Greyhole moved from SQL Lite to MySQL, you may hit a problem where Greyhole and the mount_shares_locally script both attempt to start before MySQL in bootup, leading to the services not starting properly. If this happens, you can try this to fix it:

bash code
​ls /etc/rc.d/rc3.d/​

• Look for any entries marked S-1. If there are any, they need to be removed. Run the following as root:

bash code
​rm S-1*​