Ok thanks for the info- I was afraid that was going to be the issue. I'll try to plug the drive into another computer and boot up using a live CD to see if I can at least access anything off of it- when I used the live USB on the actual server, it was able to (sort of) load the drive because I could...

So I have a bad feeling the answer to this problem is going to be i'm SOL, but I have a failing (failed?) harddrive in my server that's currently added to the greyhole share. I'm all set to remove it from the greyhole share and pop in a new one, but I can't seem to mount/access files on the harddriv...

Well here's some multiple updates- short version, I had a combination of file permissions and file name mismatch that was preventing the previously downloaded torrents from starting. Issue 1: Some files were owned by root and not by the correct user. I was using the incorrect form of the change perm...

:) Ok that worked mostly- I was able to start two new torrents without problems. When I added an existing one, however, it started to verify the existing files and then stopped, giving me a "Permission Denied" error. I suspect this is related to transmission user accessing the files (which...

I am using the Amahi transmission app- I tried doing a manual install of transmission but hit a wall. Uninstalled packages and tried the Amahi Tranmission app.

As a slight update- when I try to start new torrents, it runs for a few seconds and then does the same thing (gives the error "No Data Found...")

So I installed transmission and followed most of the directions on the wiki (for some reason, it's not finding the user "transmission", so I can't change the user permissions/groups). Transmission seems to be up and running, but when I try to restart torrents for the which the files are on...

Well I reinstalled Ubunta/Amahi on the other hard drive (I'll call it drive B) and everything is working nice, but now I want to move the files from the old drive (drive A) onto the drive B. I recreated the shares via http://hda and then followed the directions to mount shares locally (https://wiki....

In Ubuntu when you attempt to boot after installing new drives and having edited /etc/fstab, if you have monitor hooked up directly to the machine and a drive fails to mount a prompt will come up detailing which drive failed to mount and asking you to either skip or reattempt the mount. Because it ...

First of all, always a good idea to make a backup of the /etc/fstab file before editing it. If the only line added was the one you commented out, then all should be working. It is possible to correct the /etc/fstab but you need to know how it appeared before making edits. Maybe try removing that on...