Skip to content

Instantly share code, notes, and snippets.

@Agurri
Last active January 20, 2020 17:15
Show Gist options
  • Save Agurri/1813ac5f1852e6c0bdd6 to your computer and use it in GitHub Desktop.
Save Agurri/1813ac5f1852e6c0bdd6 to your computer and use it in GitHub Desktop.
FreeNAS Sickrage - Help & Info Web Page Fix
After switching to the new repo and updating, I lost the ability to see the SickRage Version, branch and commit on the Help & Info page. After trying seveal methods, I've came down to this ... It might not be the only way to do it, but it worked for me as of today (01/29/2016)
Credits go to neoatomic and delfrogo (https://forums.freenas.org/index.php?threads/new-sickrage-repo.39368/)
Step 1.
Do a backup with the Sickrage GUI. The procedure should not break anything but let's be cautious.
Step 2.
Stop Sickrage plugin in the FreeNAS GUI by going in Plugins, Installed, Stop.
Step 3.
Via command line, enter your Sickrage Jail (after logging in your FreeNAS, type "jls" to find the Sickrage jail number. After use the command "jexec 'jail number without quotes' tcsh")
Step 4.
Move to a tmp folder and download the sickrage zip from the github.
cd /tmp
git clone git://github.com/SickRage/SickRage.git
Step 5.
Delete the old SickRage folder.
rm -R /usr/pbi/sickrage-amd64/share/sickrage/SickRage
Step 6.
Copy the newly downloaded SickRage folder from the tmp folder to the one you just deleted.
cp -R /tmp/SickRage /usr/pbi/sickrage-amd64/share/sickrage/
Step 7.
From there, you need to give permission to the new sickrage folder. I tried giving 755 but it didn't work, 777 did the job. I know it might be dangerous, but it's the way I found.
chmod -R 777 /usr/pbi/sickrage-amd64/share/sickrage/SickRage
Step 8.
Restart Sickrage from the FreeNAS GUI. In Sickrage, you should see no difference except for the Help & Info page. Pressing the Check for Update button should work without any problem.
Screenshot before : http://imgur.com/rTDHlRf
Screenshot after : http://imgur.com/xwXdcv4
Cheers,
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment