Hi

I'm wondering what steps are needed to get a bittorent client working on a drive outside of the array.

I read about people using an cache drive for it, but I don't really need an cache drive.

 

I'm pretty much a linux noob but am willing to learn to get the job done

 

maybe someone would be kind enough to point me in the right direction

 

 

is this what needs to be done?

- make sure the disk mounts on startup

- format the disk

- install the software (haven't yet figured out  what client is best to use)

- make the disk accessible through user shares

- figure out how to safely shutdown the software when shutting down the server

 

I'm thinking s.n.a.p. can be good to use for this

 

 

 

any help is really appreciated

Ok nearly done preclearing the drive.

does it matters how it is formatted when you want to install programs to it?  

 

nvm

 

installed reiserfs in it using unmenu, time will tell

 

update

Was able to mount and share the disk from the unmenu diskmanagement page. it seems s.n.a.p. is not needed afterall

 

 

will wait for a new release of transmission before continuing 

 

i use transmission from unmenu install works great..no problems

I'm planning on doing that also now that its is updated

i'm still wondering about mounting the drive tho

 

to permanently mount the drive options seem to be to add it a cache drive and "disable" it by accessing the disk shares instead of the user shares.

 

or to edit the fstab files to permantly mount the drive not sure if this is could lead to problems tho i seems the most elegant solution.

You should be able to add some stuff to the go file to mount the drive.  Don't know the exact command off hand, just do some searching here or via google.

I think you are better off just using the cache drive and a hidden folder (via . in front of it) for the torrent folder.

This way it is brought online when the raid array comes up and unmounted when shut down.

Eventually the unRAID 5.x event system can have hooks in it to start/stop the torrent client at the proper time.

 

If you want to write directly to the array use the disk share

If you want to use the cache for updating the array use the user share.

 

As far as mounting via go script.

When you do a mkreiserfs use the -l to put a label on the drive.

 

mkreiserfs -l torrent /dev/sd?

 

Then you can add a mount command in your go script to mount via a name rather then a hard coded path.

This way adds/removes of your drives do not for you to edit the go script.

 

 

mkdir /mnt/torrent

mount -l torrent /mnt/torrent

 

mount -l torrent /

Thanks for the replies.

I was indeed wondering about unmounting the drive when shutting down. if I understand correctly now it will not unmount atomatically.

it seems the safe solution for now is indeed using the cache drive.

I don't want to do too much linux experimenting on a production server ^^.

 

 

Thanks for the replies.

I was indeed wondering about unmounting the drive when shutting down. if I understand correctly now it will not unmount atomatically.

it seems the safe solution for now is indeed using the cache drive.

I don't want to do too much linux experimenting on a production server ^^.

 

 

not really.  The unRAID array will not stop if the cache drive is busy either. It too must be un-mounted.

Basically, if you hit the unRAID stop button the interface will just show the cache disk as "unmounting". It will continue to show this and you will have no access to the start/stop/shutdown/reboot buttons until the drive unmounts. So, you stop the application and then the drive unmounts and everything is fine.

 

When you run an application with a web based interface it's pretty easy. You just pull up the interface and shut it down. You can also create a button for the user scripts page in unMENU to stop and start the application.

 

unRAID 5.x will include the capability to run extra commands when the unRAID stop button is pressed. This means you can properly shut-down applications when you stop the array. Until then, the easiest is to just know you have to stop the application to stop the array.

 

You can fix the array stopping issue by putting the applications onto another drive or another partition not part of the array. However, the application should still be stopped and the drive should still be properly unmounted before shutting down or rebooting.

 

I don't consider it a big deal. My array has been up for 60 days now. I guess some people start and stop more often but I'm not sure why unless they are powering it down every day.

 

Peter

 

so if i understand correctly  for any drive the order would be

stop activity (programs)

unmount

shutdown

 

just out of curiosity

if you somehow automatically mounted the drive by editing fstab or adding something to the go script,

before shutting down you would still need to manually unmount it?

thanks for all the replies they have been very informative, labelling the drive would indeed be very handy too.

I decided for now to stick to the cache drive. and using "." in front of the folders

even tho my curiosity is big to figure out how to make it work otherwise.

 

I might pickup this idea when 5.0 is released and by then hopefully i understand a little more on linux.

for now every answer raises a lot more questions. and I don't want to mess things up.