[ SOLVED ] Permissions Problems

[1080p]

Hi unRAID community,

 

I am running into some problems with my current setup. I have an unRAID Pro server (5.0-beta13) which I use as a central media repository. Files are downloaded and seeded from this server via my Mac Mini running the µTorrent beta. I would like to run the torrent client on my server but it appears that Transmission is my only option and it isn't a good one. There are various reasons I choose to use µTorrent, the main one being that Transmission is pure garbage when running anything over a couple of hundred torrents but that is a separate issue.

 

My problem is that µTorrent encounters file permission errors when trying to read and write from/to the server. These errors seem to be random, I can run some torrents fine and others will fail with "Error: Permission denied", repeating the error even after completely removing and re-adding both torrent file and actual files.

 

My server and Mac Mini are both connected via gigabit ethernet to a switch so bandwidth and connection drops are no issue.

 

I connect to my server from the Mini via SMB as "Guest", as I have never been fond of username/password on my local network and as I understand it all files/folders written to the unRAID server are owned by "nobody" so anybody should be able to read and write to them.

 

What could be causing permission errors like this? I am tempted to try logging in to my server via SMB as root and seeing if this fixes the errors but can't imagine that being a workable solution.

[ubuntuaddicted]

So your unRAID torrent server is headless or what? I could help possibly as I run the transmission-deamon on my server at home. I run it on my Ubuntu headless server but just found unRAID (thru tapatalk app within the categories) and I am going to building a better server for my media server using unRAID.

 

What is the owner and group your torrents get saved as when adding new torrents to the server? For example I upload torrent links thru the web tranmission GUI (anywhere i have internet) by accessing it thru an a ssh secure tunnel and pointing my web browser to use the tunnel port I designated (socks proxy)

when starting my ssh client (192.168.0.6:9091) and I know the rar set gets downloaded to a predefined folder on the server which I am the owner of BUT the owner of the rar set is transmission and group is policy-kit. Not sure how to change the default owner and group it gets saved as BUT thats probably where your issue is. so I need more details to help.

 

 

Sent from my iPhone using Tapatalk

[prostuff1]

Hi unRAID community,

 

I am running into some problems with my current setup. I have an unRAID Pro server (5.0-beta13) which I use as a central media repository. Files are downloaded and seeded from this server via my Mac Mini running the µTorrent beta. I would like to run the torrent client on my server but it appears that Transmission is my only option and it isn't a good one. There are various reasons I choose to use µTorrent, the main one being that Transmission is pure garbage when running anything over a couple of hundred torrents but that is a separate issue.

A couple hundred torrents at a time? You sir have a problem 

 

Anyway, I have never loaded that many torrents into transmission as once... never had the need, nor saw the point really.  The most I have ever had going at one was probably 50 but that has been cut back considerably since moving to SABnzbd+ and SickBeard.

 

My problem is that µTorrent encounters file permission errors when trying to read and write from/to the server. These errors seem to be random, I can run some torrents fine and others will fail with "Error: Permission denied", repeating the error even after completely removing and re-adding both torrent file and actual files.

 

My server and Mac Mini are both connected via gigabit ethernet to a switch so bandwidth and connection drops are no issue.

 

I connect to my server from the Mini via SMB as "Guest", as I have never been fond of username/password on my local network and as I understand it all files/folders written to the unRAID server are owned by "nobody" so anybody should be able to read and write to them.

 

What could be causing permission errors like this? I am tempted to try logging in to my server via SMB as root and seeing if this fixes the errors but can't imagine that being a workable solution.

As mentioned by the poster above, it is probably group related but without and "ls -al" or the directory where the files reside we can't do a lot or suggest further action.

[1080p]

My unRAID server is headless, I hadn't actually tried adding any new torrents as I was adding old ones I already had which was when I started encountering errors. I tried adding a new one and it began downloading fine but as soon as my torrent client tried to write data to disk it failed with the error I described earlier.

 

This seemed strange to me so as a test I tried creating a folder via my Windows 7 computer and it also failed with a read only error. I checked the unRAID system log and sure enough:

 

Nov 26 12:05:15 passionfruit shfs/user: shfs_mkdir: mkdir: /mnt/disk2/film/untitled folder (30) Read-only file system

 

From a little reading on the forums I understand that file systems are put into read only mode when corruption is detected, I found the reiserfsck information on the Wiki and after testing /dev/md1 and /dev/md2 I see that /dev/md1 passed fine but /dev/md2 failed with thirteen corrupt sectors. I am given the option to correct them but only through --rebuild-tree. I was warned not to go ahead with that without consultation by the Wiki so what does the community think?

 

The data copied to this server was originally from another unRAID server which had some unexplained hard drive errors. The old server is still intact and will eventually act as a test server after I find the problem.

 

 

As for the ls -al output, I ran that command on my 'films' directory. The following is a file in that directory:

 

-rw-rw---- 1 nobody users  6786475571 2011-11-26 11:24 file.mkv

 

This file is fine and I am writing to it now. A folder which I am also able to write to in that directory:

 

drwxrwx--- 1 nobody users        296 2011-11-25 08:59 folder/

 

Now a folder that has permission denied problems when I try to write to it:

 

drwxrws--- 1 nobody users          80 2011-11-25 10:07 folder/

 

I had never seen an 's' as part of file/folder permissions before but understand it is a setgid feature. Should all my folders contain the 's' in their permissions?

[1080p]

I went ahead with the reiser-fsck --rebuild-tree and it aborted with an error

 

The error message mentions a second run, do I need to add any options to the original command or can I run the same one again?

[dgaschk]

Did you do a reiserfsck scan first?

 

http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

[1080p]

I ran reiserfsck --check on /dev/md1 which passed and /dev/md2 which failed with thirteen corrupt sectors. I tried reiserfsck --rebuild-tree /dev/md2 and it failed part way through and suggested I try a second run. I'm not sure if there is a different command for the second run (not mentioned in the Wiki article) or if I just run the same command again. Either way there appears to be some problem with the drive or hardware.

 

What should my next steps of investigation be?

[dgaschk]

Just do what it says.

[1080p]

As far as I can tell I have done what the article instructed. I ran reiserfsck --rebuild-tree /dev/md2 a second time and it failed again.

 

This has caused me a little frustration already and I am nearly ready to begin from scratch. What should my steps be if I wanted to revert this array to a 'factory' state? By that I mean back to zero data on any of the drives and ready to have data copied or written to it. I have another backup of all of the data I really need to protect so I am not worried about saving anything on this server.

[ubuntuaddicted]

Wouldn't you just follow the wiki section where it talks about removing a drive from the array where you don't plan on replacing it? It talks about rebuilding the array without a new drive going in the place of the 1 u removed. IF you do want to start over for a fact, I don't see why you could just redo the whole setup of unRAID?

 

 

Tapatalk is tha shizzle