Is it possible to install unrar 4 or 5? I was helping a friend install Sick Beard today and it would not let me enable Unpack because unrar 3.9 was not supported. Although my server has unrar 3.9 installed and it works...

Is it possible to install unrar 4 or 5? I was helping a friend install Sick Beard today and it would not let me enable Unpack because unrar 3.9 was not supported. Although my server has unrar 3.9 installed and it works...

 

Unrar 4.2.4 works. But im not sure why sickbeard would need unrar. Do you actually mean sabnzbd?

 

the link

 

http://www.slackware.com/~alien/slackbuilds/unrar/pkg/13.37/unrar-4.2.4-i486-1alien.tgz

 

 

Unrar 4.2.4 works. But im not sure why sickbeard would need unrar. Do you actually mean sabnzbd?

 

the link

 

http://www.slackware.com/~alien/slackbuilds/unrar/pkg/13.37/unrar-4.2.4-i486-1alien.tgz

 

I have been using it independently from sabnzbd for the time being. Do I just copy that file into the packages folder on the flash drive then install it with unmenu?

 

 

Unrar 4.2.4 works. But im not sure why sickbeard would need unrar. Do you actually mean sabnzbd?

 

the link

 

http://www.slackware.com/~alien/slackbuilds/unrar/pkg/13.37/unrar-4.2.4-i486-1alien.tgz

 

I have been using it independently from sabnzbd for the time being. Do I just copy that file into the packages folder on the flash drive then install it with unmenu?

 

you could do that I guess, but I would normally edit the plg itself to include the link to the package, because the unRAID OS always reinstalls the plugins upon reboot, so sickbeard might fail again for your friend if he/she reboots the NAS

2 points:

 

that is the wrong version of slackware to use, it should be 13.1

 

this tells you where to place the file so you dont have to fork the addon https://github.com/limetech/webGui

2 points:

 

that is the wrong version of slackware to use, it should be 13.1

 

this tells you where to place the file so you dont have to fork the addon https://github.com/limetech/webGui

 

I was just linking the version of Unrar used by influencer for his Sab plugin

Indeed. Unfortunately thats the wrong one as well

 

Its not that big a deal but we are getting lazy following bets practice. Package pinning should be the exception and not the rule. Its a pet hate

Yeah, it would be nice if there were more coherency between the plugins made by different devs in this forum.

 

Sent from my SM-N9005 using Tapatalk

 

 

OK just to make sure I understand:

 

1. unRAID uses slackware 13.1 however 13.37 packages can be used if necessary?

 

2. The only way I know how to install .tgz files is with unMenu (ie. I click download, install, install on reboot). So to clarify, if I want to install unrar-4.2.4-i486-1alien.tgz I need to put it in the /boot/packages folder correct? Will unMenu then see the new .tgz file and let me click install and install on reboot?

 

3. Is there a better way to install .tgz files without using unMenu?

 

OK just to make sure I understand:

 

1. unRAID uses slackware 13.1 however 13.37 packages can be used if necessary?

 

2. The only way I know how to install .tgz files is with unMenu (ie. I click download, install, install on reboot). So to clarify, if I want to install unrar-4.2.4-i486-1alien.tgz I need to put it in the /boot/packages folder correct? Will unMenu then see the new .tgz file and let me click install and install on reboot?

 

3. Is there a better way to install .tgz files without using unMenu?

 

1. Yes, you could.

 

2. Not too sure about that as i only use unmenu for SMART and sys info.

 

3. If you really want a fast way, what you could do is put the file in the packages folder, telnet to the NAS, cd to the packages folder then run the installpkg command followed by the exact name of the unrar pkg filename. Should work fine.

 

3. If you really want a fast way, what you could do is put the file in the packages folder, telnet to the NAS, cd to the packages folder then run the installpkg command followed by the exact name of the unrar pkg filename. Should work fine.

 

However that will not survive a reboot correct?

 

3. If you really want a fast way, what you could do is put the file in the packages folder, telnet to the NAS, cd to the packages folder then run the installpkg command followed by the exact name of the unrar pkg filename. Should work fine.

 

However that will not survive a reboot correct?

Which is why you should edit the plg directly with the link i shared previously so it would then survive a reboot.

 

Sent from my SM-N9005 using Tapatalk

 

 

Or you can add the installpkg command to your "go" file and it will survive a reboot as well.

OK just to make sure I understand:

 

1. unRAID uses slackware 13.1 however 13.37 packages can be used if necessary?

 

2. The only way I know how to install .tgz files is with unMenu (ie. I click download, install, install on reboot). So to clarify, if I want to install unrar-4.2.4-i486-1alien.tgz I need to put it in the /boot/packages folder correct? Will unMenu then see the new .tgz file and let me click install and install on reboot?

 

3. Is there a better way to install .tgz files without using unMenu?

You can put .tgz and .txz in the /boot/extra folder and they will be installed automatically on boot, as described in the link provided by NAS above. I have several packages loading that way. You might still need to do something to keep certain plugins from overwriting them (all plugins load after the packages in /boot/extra).

 

Look at README.md at the link NAS provided. That is the way unRAID startup has been working since plugins were invented during v5 betas:

 

1) Install /boot/extra

2) Install /boot/plugins

3) Install /boot/config/plugins

4) Run go script

 

 

 

You can put .tgz and .txz in the /boot/extra folder and they will be installed automatically on boot

 

Oh, well that is awesome (I was starting to modify the old unMenu unrar .conf file then I read this... I didn't realize it was that easy)! Thanks everyone for your help.

Yeah there is quite a bit of deprecated advice kicking about now. The new way is so so easy.

 

To touch on the 13.1 thing briefly. unRAID is based on Slackware, currently unRAID 5.x is based on Slackware13.1.

 

You will see people almost universally ignoring this relationship and installing pretty much any package version they can find, typically thinking newer is better. This result in many people mixing packages from 13.37 slackware with 13.1 packages etc.

 

Is this the end of the world, no. Could this cause instabilities, absolutely and we have seen it.

 

To quote Limetech

 

Note: for unRAID 5.0 these should be from Slackware version 13.1 unless you absolutely need the functionality of a newer package.

 

It is really that simple and we should as a community try harder to follow the simple advice until such time as we have the addon thing nailed down to a slick process.

If anybody needs it, i have compiled an unrar 5.0.14 Package for unRaid 5.x.

Plays nicely together with Influencers sabnzbd etc.

 

http://dl.bintray.com/darkside401/unrar5-unraid/unrar-5.0.14-i486-1cf.txz

If anybody needs it, i have compiled an unrar 5.0.14 Package for unRaid 5.x.

Plays nicely together with Influencers sabnzbd etc.

 

http://dl.bintray.com/darkside401/unrar5-unraid/unrar-5.0.14-i486-1cf.txz

Just found your post, i was under the impression the new sabnzbd (0.7.17) came with unrar 5.01, but it does not, it just uses the unrar that is available. Your package solves a lot of problems thanks!

If anybody needs it, i have compiled an unrar 5.0.14 Package for unRaid 5.x.

Plays nicely together with Influencers sabnzbd etc.

 

http://dl.bintray.com/darkside401/unrar5-unraid/unrar-5.0.14-i486-1cf.txz

Just found your post, i was under the impression the new sabnzbd (0.7.17) came with unrar 5.01, but it does not, it just uses the unrar that is available. Your package solves a lot of problems thanks!

 

It does indeed. But for a non-Linux educated guy like myself can you please explain how to install it and make it suvive a reboot?

Simply put it into the extra folder on your flash drive. Than it will be installed on every reboot.

For the initial install you can simply put it into that folder, than telnet into your unraid box, navigate to that folder and install it via installpkg unrar-5.0.14-i486-1cf.txz.

Simply put it into the extra folder on your flash drive. Than it will be installed on every reboot.

For the initial install you can simply put it into that folder, than telnet into your unraid box, navigate to that folder and install it via installpkg unrar-5.0.14-i486-1cf.txz.

 

So this post is wrong?

http://lime-technology.com/forum/index.php?topic=30563.msg274945#msg274945

 

as it states that plugins are loaded after packages in the extra folder. the sabnzb plugin would need to be edited as it installs an older unrar version?

You could edit influencers Sabnzbd Plugin to load a newer version of unrar, or you take Overbyrn's Sabnzbd Plugin which installs unrar 5 by default: https://github.com/overbyrn/UnRAID

 

By the way i have in the mean time switch to nzbget plugin done by overbryn.

Simply put it into the extra folder on your flash drive. Than it will be installed on every reboot.

For the initial install you can simply put it into that folder, than telnet into your unraid box, navigate to that folder and install it via installpkg unrar-5.0.14-i486-1cf.txz.

 

So this post is wrong?

http://lime-technology.com/forum/index.php?topic=30563.msg274945#msg274945

 

as it states that plugins are loaded after packages in the extra folder. the sabnzb plugin would need to be edited as it installs an older unrar version?

The post is not wrong since it says:

You might still need to do something to keep certain plugins from overwriting them (all plugins load after the packages in /boot/extra).