Difference between revisions of "Greyhole updating"
| Line 28: | Line 28: | ||
== Troubleshooting == | == Troubleshooting == | ||
'''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 | + | 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>32-Bit</code> | + | <blockquote><code>32-Bit</code> |
{{Code|rpm -Uvh http://www.greyhole.net/releases/hda-greyhole-0.9.10-1.i386.rpm --force}} | {{Code|rpm -Uvh http://www.greyhole.net/releases/hda-greyhole-0.9.10-1.i386.rpm --force}} | ||
<code>64-Bit</code> | <code>64-Bit</code> | ||
| − | {{Code|rpm -Uvh http://www.greyhole.net/releases/hda-greyhole-0.9.10-1.x86_64.rpm --force}} | + | {{Code|rpm -Uvh http://www.greyhole.net/releases/hda-greyhole-0.9.10-1.x86_64.rpm --force}}</blockquote> |
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 00:34, 2 September 2011
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:
| bash 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:
| bash code |
|---|
uname -i
|
4. Back to terminal, make sure you are root (su). Example update command:
32-Bit
| bash code |
|---|
rpm -Uvh http://www.greyhole.net/releases/hda-greyhole-0.9.10-1.i386.rpm
|
64-Bit
| bash code |
|---|
rpm -Uvh http://www.greyhole.net/releases/hda-greyhole-0.9.10-1.x86_64.rpm
|
5. Check the GH log for any errors that might have occurred after the upgrade
| bash code |
|---|
nano /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
32-Bit
bash code rpm -Uvh http://www.greyhole.net/releases/hda-greyhole-0.9.10-1.i386.rpm --force
64-Bit
bash code rpm -Uvh http://www.greyhole.net/releases/hda-greyhole-0.9.10-1.x86_64.rpm --force
Use the following command to verify that the Samba symlink was indeed created:
| bash code |
|---|
ls -l /usr/lib*/samba/vfs/greyhole.so
|
