Amahi Wiki - User contributions [en]

Shares troubleshooting

2011-10-25T02:38:06Z

Ccondrup: adding instructions for connecting via cmd

== Access Problems ==

Access issues are caused by one or two things, in order: Windows (SMB/Samba) access (domain works, username works), and Linux permissions access

So, to diagnose things, make sure you can login first from your client operating system, and then if that works, make sure you can access the files you are interested in from Linux.

* First make sure that '''your workgroup or samba domain match between your HDA and your clients'''. For your HDA's workgroup/domain, go to Setup -> Settings and turn on advanced settings, after that, go to Shares -> Settings and check the workgroup name. If the DNS domain is home.com, the workgroup will be just home.
* If only one user can access or write in your shares, and your shares are in a subdirectory of /media, you'll need to unmount your drive from /media, and re-mount it using the instructions found here: [[Adding_a_second_hard_drive_to_your_HDA|How to add additional hard drives in your HDA]].
* In at least Windows 7, we have observed that the operating system tries to use a "Domain" of the name of the computer, which is wrong! Try typing this in the Username field:
YOURWORKGROUP\username
So, if your username is jdoe and the workgroup is HOME, try HOME\jdoe
* Some windows clients for some reason may require the whole DNS path, so if your internal domain is, say, home.com, try:
\\hda.home.com
* Make sure the user has permissions to at least read the share (of course) in the Shares area of your HDA
* Check the Credential manager under Control Panel: Control Panel -> Al Control Panel Items -> Credential Manager: See this [http://forums.amahi.org/viewtopic.php?f=4&t=964&start=11 thread in the forums].

== Permission Problems ==

#If you cannot write to the shares, permissions at the SAMBA and Linux levels must be checked.
*At the SAMBA level, check Setup -> Shares. Make sure the user has access to the share you are looking at.
*At the Linux level, you have to ssh into your HDA or login at the console and try to write a file in to the folder for the share (typically in /var/hda/files/FOO, if you did not change the default path).
#If you cannot access the shares, and you are on a Windows Vista machine, there may be other connections open and you may get this error:
[[File:Errorpermissions.jpeg]]
*So we will try doing this:
**Start -> Type "cmd" into the search bar and press enter
**Type in "net use * /delete" to delete all open shared connections
**Double check nothing is connected: "net use"
**Try connecting to the HDA shares one more time.
*Still getting 'not accessible' errors? Users have had luck connecting via cmd on Windows XP clients:
**Type in "net use \\hda\Pictures /USER:HOME\jdoe password" Be sure to substitute the share name, username and password with your real values.
**Try connecting to the HDA shares one more time.

== Further Debugging ==

For actual debugging, follow the details of the [[Shares Debug]] page.

== Other ==

NOTE: we used to have a bug in [[Amahi 5.0]] where users that use ANY capital letters were not created properly. Please stick to users with all lowercase letters. This was fixed in [[Amahi 5.1]].

(This appears to be a problem in shadow-utils in Fedora. For status, see Amahi bug [http://bugs.amahi.org/issues/show/395 395] and Fedora bug [https://bugzilla.redhat.com/show_bug.cgi?id=550732 550732].)

Mount Shares Locally

2011-10-24T00:01:43Z

Ccondrup: typo in path to rc3.d

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.

* As '''root:''' Install the mount_shares_locally initd script:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; overflow: scroll">
curl -o /etc/init.d/mount_shares_locally http://dl.dropbox.com/u/3022105/Amahi/mount_shares_locally
chmod +x /etc/init.d/mount_shares_locally
chkconfig --add mount_shares_locally
</div>

* 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"'''
{{Code|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).
{{Code|Code= nano /home/YourHDA_username/.smb_credentials}}
*Enter the following:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
username=your_username
password=your_password
domain=HOME
</div>
'''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'''<br/>
You will find the mounted shares in ''/mnt/samba/*''<br/>
'''service mount_shares_locally stop''' will unmount the local shares.<br/>

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. The above initd script replaces all this.

== Unable to mount localy 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.

{{Code|yum install cifs-utils}}

Now it should work fine to run

{{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:

{{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:

{{Code|rm S-1*}}

Upgrade FireFox

2011-09-30T01:17:14Z

Ccondrup: xulrunner7 is out, with firefox 7.0.1

To update FireFox to the latest version in Fedora 14:
* Install the Amahi RPM Fusion[http://www.amahi.org/apps/rpm-fusion-free (Free)] and [http://www.amahi.org/apps/rpm-fusion-non-free (Non-Free)] web applications.
* [http://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], do the following commands:
{{Code|tar -cvzf $HOME/mozilla-firefox-profiles-backup.tar.gz $HOME/.mozilla/firefox/
rpm -Uvh http://rpms.famillecollet.com/remi-release-14.rpm
yum --enablerepo<nowiki>=</nowiki>remi list firefox
yum --enablerepo<nowiki>=</nowiki>remi install firefox xulrunner7}}
* You should now have the latest version.

Greyhole updating

2011-09-01T13:39:02Z

Ccondrup: Added cmds in troubleshooting

== Disclaimer ==
Amahi releases new versions of Greyhole (GH) after they've been tested. If you follow this guide to update your GH install manually you do so on your own risk. If it breaks, it's on you.

== Instructions ==
1. Find current version:
{{Code|rpm -q hda-greyhole}}

2. Is there a new version?
{{Link|http://www.greyhole.net/download/}}

3. Browse the archive and copy the link for the latest hda-greyhole (Amahi needs hda-greyhole, the regular greyhole will conflict)
{{Link|http://www.greyhole.net/download/archives.html}}
: Unsure whether you have i386 or x86_64? Run in terminal:
{{Code|uname -i}}

4. Back to terminal, make sure you are root (su). Example update command:
{{Code|rpm -Uvh http://www.greyhole.net/releases/hda-greyhole-0.9.10-1.i386.rpm}}

5. Check the GH log for any errors that might have occurred after the upgrade
{{Code|nano /var/log/greyhole.log}}

6. Re-check the version of your newly updated Greyhole install, and enjoy!
{{Code|rpm -q hda-greyhole}}

== Troubleshooting ==
'''Can't access your shares after you upgraded ?'''
Try to re-install the same RPM a second time. Sometimes, the script included in the RPM can't create the Greyhole module for Samba where it should, and this will cause your Greyhole pooled shares to become unaccessible. Re-installing the same RPM a second time always fix that issue. Use the same command but add the --force parameter
{{Code|rpm -Uvh http://www.greyhole.net/releases/hda-greyhole-0.9.10-1.i386.rpm --force}}

Use the following command to verify that the Samba symlink was indeed created:
{{Code|ls -l /usr/lib*/samba/vfs/greyhole.so}}

Greyhole

2011-08-31T13:21:55Z

Ccondrup: Added link to newly created Greyhole updating-page

[[Category:apps]]
<div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
'''NEW:''' [http://code.google.com/p/greyhole/wiki/MigrateFromWHS Widows Home Server Drive Extender Migration Guide]

'''NEW:''' [[Greyhole troubleshooting]] guide
</div>

== What is Greyhole ==

[http://greyhole.pommepause.com/ Greyhole] is Amahi's [[Storage pooling]] technology. Storage Pooling combines the space of multiple disk drives and makes them look as if they were all part of a single pool of disk space.
Specifically, Greyhole:
* Combines the space from multiple drives into a single volume
* Distributes files across all drives in the pool
* Creates multiple copies of files in admin-specified shares

This feature is installed by default, but requires a few simple steps to begin utilizing the features.

You can add additional drives to your hda and prepare them for use in Greyhole by following [[Adding a second hard drive to your HDA|this tutorial]].

To add a drive to your Greyhole storage pool. Open your HDA dashboard and navigate to the Shares tab. Then click on the Storage Pool sub-category. You will see a page similar to the one below.

== Important Warnings ==
<div style="color:darkred">You should '''never''' change or delete files in the shared directories (''/var/hda/files/*'' by default) directly on the HDA, using the terminal, or the Gnome file browser, for the shares for which you checked the ''Uses pool'' option in the Amahi dashboard. If you want to work with files on Greyhole shares on the HDA, you should [[Mount Shares Locally]].<br/>
You should be safe reading existing files directly, or adding new files directly, as long as don't care that your new files will only be moved into the storage pool during the next check, which runs automatically at midnight (or manually using ''greyhole --fsck''). Until then, your new files will be stored in your shared directories (normally ''/var/hda/files/share_name/'').

Also, touching anything inside the '''gh''' directories that Greyhole creates at the root of your partitions is a recipe for disaster.

We [[Greyhole not on root | strongly discourage you from using the root partition in a drive pool]].
</div><br/><br/>

== First things first ==

You need to go in the Settings tab, and enable '''Advanced Settings'''.<br/>
Without Advanced Settings enabled, you won't see the following page and options.

== For Storage Pool (Partitions) ==

[[File:Storage_Pool_1.png|600px|thumb|left]]

Select the drives you want available for your storage pool.

== Greyhole options ==

The next step is to select the share you want to replicate across the pool.

From the Shares tab, select the Shares sub-catagory. We chose the Pictures share for this tutorial.

[[File:Greyhole_Options_1.png|600px|thumb|left]]

Check the option for "Uses pool" and choose the number of drives to replicate this share. In this instance we have chosen to use all drives available to the greyhole pool.

Note: Greyhole is not a backup solution. If a file is removed, all copies are removed.

== Greyhole advanced options ==

You can further configure Greyhole by manually editing the following file:<br/>
'''/var/hda/platform/html/config/greyhole.yml'''

To see what options are available, and what they do, refer to the [http://greyhole.googlecode.com/svn/trunk/greyhole.example.conf sample greyhole.conf] provided with Greyhole.

greyhole.yml is in in YAML format. Most of it should be easy enough to modify. The only exception would be the sticky_files (and optional sticky_into) options.<br/>
Here's an example of how those should appear:

To specify the following to Greyhole in greyhole.conf:

sticky_files = Music/
sticky_files = Videos/Movies/
stick_into = /mnt/hdd1/gh
stick_into = /mnt/hdd5/gh
sticky_files = Backups/CrashPlan/
stick_into = /mnt/hdd0/gh

one should specify this in the greyhole.yml file, where '''precise indentation matters''':

sticky_files:
- - Music/
- - Videos/Movies/
- - /mnt/hdd1/gh
- /mnt/hdd5/gh
- - Backups/CrashPlan/
- - /mnt/hdd0/gh

For your changes to be effective, you'll need to force Amahi to regenerate the greyhole.conf file. You can do so by editing a share, clicking it's path, and just clicking the Save button without actually changing the path.

== Copying your data into Greyhole shares the first time ==

When you start using Greyhole, you might want to copy or move all your exiting files into your new shares that use the storage pool.

Note: This is not necessary if your files are already in Amahi shares. If they are there, and you enable the ''Uses pool'' option in the Amahi dashboard, the files will start getting moved around into the drives in your storage pool during the night (starting at midnight), when the nightly storage pool check starts.<br/>
The instructions below are for users who have more data to copy into the Greyhole shares than their currently free space in the /var/hda/files/ folder.

One way to do that is to mount the shares that use the Greyhole storage pool, either on the HDA itself, or on a client computer on your local network, and copy your data from their existing location into the mounted shares.
This can be time consuming, but it is the safest way to use Greyhole.

Another way to move your files from their current location into the storage pool is to share their current location using an Amahi share that ''Uses pool'', then let Greyhole nightly check move the files from there into the pool.

Here's a more detailed walkthrough for this method:

# Setup the Greyhole Storage Pool in the Amahi dashboard, Shares > Storage Pool page.
# Go in the Shares > Shares page. In there, make sure you have an existing share for each share you have data for. Create new ones if you need, remove the ones you don't need.
# Edit the ''path'' of each of those shares, and enter the current location of your existing data. For example, the Movies share could have a path = ''/media/External Drive/Movies''
# Enable the ''Uses pool'' option for each of your shares, and select the number of extra copies you'd like, if any.
# Now, you either need to wait for Greyhole'S nightly check to start, or you can start it manually from a terminal, as root, using this command: greyhole --fsck
# Monitor /var/log/greyhole.log to see when the ''fsck'' operation is done.
# Once ''fsck'' is done, your data has now been moved into the Greyhole storage pool (in the drives you selected in Shares > Storage Pool). All that should be left in the previous location of your data (''/media/External Drive/Movies'' from the previous example) should be symbolic links pointing to the new file copies. If the previous location is just empty directories (no symlinks), do not panic. This is normal if your previous location is an NTFS or FAT partition (drive).
# Move all those directories / symlinks from there into the correct folders in /var/hda/files/share_name
# Back in the Amahi dashboard, edit the path of the shares once again, and put back ''/var/hda/files/share_name'' (i.e. the folders where you moved the symbolic links).
# If you used an NTFS or FAT partition for the previous location, you'll need another fsck to create the symlinks where they should be. Either wait for midnight, or launch it manually, from a command line, as root: ''greyhole --fsck''

You're done. All your existing data is now stored in the various drives included in your storage pool, and are accessible via the Samba shares you have defined in the Amahi dashboard.

== Adding a new drive to your HDA and storage pool ==
This wiki page discusses how to add a new drive to your HDA and to your greyhole storage pool
[[Adding_a_second_hard_drive_to_your_HDA]]

== /media ==
Including any drive mounted as /media/Something in your storage pool is usually a bad idea.<br/>
Those mounts are created by the ''gnome-automounter'', which requires you to be logged in into X (Gnome) to become available.<br/>
This will create issues with Greyhole, which expects drives to always be available, and will take action when some of them are missing.

Follow this guide to [[Adding a second hard drive to your HDA|permanently mount your drives]], before you include them in your storage pool.

== Monitoring Greyhole ==
Sometimes you might want to monitor what Greyhole is doing, for example when writing data to your greyhole shares for the first time. Here are a few commands you can type in a terminal to follow along.

'''Scrolling view of total Greyhole operations queue:'''
while [ 1 == 1 ]; do greyhole --view-queue | grep Total; sleep 60; done

'''Scrolling log of what files Greyhole is working on right now:'''
tail -f /var/log/greyhole.log

== Convert Greyhole from SQLite to MySQL ==
Greyhole is at the time of writing using SQLite as the default database for queueing up tasks on Amahi. This is unqie to Amahi as Greyhole was originally designed to use MySQL for this task.

There are some major performance benefits to using MySQL over SQLite when writing large amounts of files. Switching can be especially useful when moving data to greyhole shares for the first time. For now there is a script you can run if you want to switch over. This script has been tested to be safe while greyhole is working but should be used with discresion.

''To Convert to MySQL, run as root:''

/usr/share/greyhole/db_migration-sqlite2mysql.sh

To see what DB engine is Greyhole using, do this:

grep db_engine /etc/greyhole.conf

== Disable Greyhole ==
For those who do not use Greyhole, you can disable it. This is based on the fact you never have used it by enabling 'Uses pool' on any share. Recommend using extreme caution as this could have unpredictable results.

Perform the following steps as user '''root''':

chkconfig greyhole off
rm /etc/monit.d/greyhole.conf
service monit restart
service greyhole stop

'''DO NOT''' attempt to remove the Greyhole package as it is a dependency of the HDA software. Doing so will break your HDA.

= Testing and Reliability =

Check out the [[Greyhole grinder]] to help make Greyhole rock solid.

= Reconnect the Greyhole storage pool after re-install of Fedora / Amahi =


* Disconnect all data drives before you reinstall. This will prevent you from destroying them by mistake during the Fedora/Amahi install!
* Install Amahi per the regular instructions.
* Connect the data drives, and use hda-diskmount to remount all of them.
Note that if you can, it would be faster if you can re-mount the drives in the same paths they used to have.

'''Example:''' If you have one 1TB and one 2TB, and the 1TB was mounted as /var/hda/files/drives/drive1, and the 2TB was mounted as /var/hda/files/drives/drive2, it would be better to re-mount that like that on your new HDA. If you mount them otherwise, it will still work, but Greyhole will work a while to re-build the links in your share before they can be usable.
* Select the drives in the Amahi Dashboard: Setup > Shares > Storage Pool
* Re-create your shares in the Amahi Dashboard: Setup > Shares.
Make sure to select 'Use Pool', and select the correct number of extra copies.
If you don't remember all the shares you had, just check inside the 'gh' folder found at the root of your drives to get a reminder!

'''Example:'''
ls -1 /var/hda/files/drives/*/gh/ | grep -v : | sort -u

* Launch a fsck to have Greyhole rebuild your shares.
greyhole --fsck

Until this completes, some of your files will be missing from your shares.

= Greyhole Troubleshooting =

Page: [[Greyhole troubleshooting]]

= Landing Zone Considerations =

The landing zone or LZ is the area where files arrive first before being distributed to their final destination. See details in the [[Greyhole landing zone]] page.

= Manually updating Greyhole for Amahi =
Page: [[Greyhole updating]]

= Reference =
Good [http://revxatlarge.blogspot.com/2011/04/restoring-deleted-files-in-greyhole-and.html article] on Greyhole with terms explained.

Greyhole updating

2011-08-31T13:14:56Z

Ccondrup: Created page with "== Disclaimer == Amahi releases new versions of Greyhole (GH) after they've been tested. If you follow this guide to update your GH install manually you do so on your own risk. I..."