Difference between revisions of "Greyhole updating"
| Line 42: | Line 42: | ||
'''Can't access your shares after you upgraded ?''' | '''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<br> | 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<br> | ||
| − | {{Code|rpm -Uvh --force http://www.greyhole.net/releases/rpm/`uname -i`/hda-greyhole | + | {{Code|rpm -Uvh --force http://www.greyhole.net/releases/rpm/`uname -i`/`rpm -qa hda-greyhole`.rpm}} |
| − | |||
Use the following command to verify that the Samba symlink was indeed created: | Use the following command to verify that the Samba symlink was indeed created: | ||
{{Code|ls -l /usr/lib*/samba/vfs/greyhole.so}} | {{Code|ls -l /usr/lib*/samba/vfs/greyhole.so}} | ||
Revision as of 23:37, 17 September 2011
Contents
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.
All the steps below should be executed as root.
Option 1 - Use the Greyhole YUM repository
1. If you didn't already, add the Greyhole YUM repository to your YUM configuration.
| bash code |
|---|
curl -o /etc/yum.repos.d/greyhole.repo http://www.greyhole.net/releases/rpm/greyhole.repo.disabled
|
2. If you want to use this repository every time yum is used (including for Amahi automatic updates), change /etc/yum.repos.d/greyhole.repo from:
| Text |
|---|
enabled=0
|
to
| Text |
|---|
enabled=1
|
NOTE: You can safely skip this step if you want to manually update in the future.
3. Update hda-greyhole to the latest version:
| bash code |
|---|
yum --enablerepo=greyhole update hda-greyhole
|
Option 2 - Manually install the latest RPM
1. Find current version:
| bash code |
|---|
rpm -q hda-greyhole
|
2. Is there a new version?
3. Browse the archive and copy the link for the latest hda-greyhole (Amahi needs hda-greyhole, the regular greyhole will conflict)
4. Back to terminal, make sure you are root (su). Example update command:
| bash code |
|---|
rpm -Uvh http://www.greyhole.net/releases/rpm/`uname -i`/hda-greyhole-0.9.13-1.`uname -i`.rpm
|
5. Check the GH log for any errors that might have occurred after the upgrade
| bash code |
|---|
tail -f /var/log/greyhole.log
|
6. Re-check the version of your newly updated Greyhole install, and enjoy!
| bash 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
| bash code |
|---|
rpm -Uvh --force http://www.greyhole.net/releases/rpm/`uname -i`/`rpm -qa hda-greyhole`.rpm
|
Use the following command to verify that the Samba symlink was indeed created:
| bash code |
|---|
ls -l /usr/lib*/samba/vfs/greyhole.so
|
