July 24, 201213 yr Author forgive my ignorance on the attached screenshot: but how do I know when the chown process is complete? Will I see a new line below the green cursor of: root@unraid:~# ? I invoked the chmod in a putty telnet session about 10 minutes ago....see attached.
July 24, 201213 yr forgive my ignorance on the attached screenshot: but how do I know when the chown process is complete? Will I see a new line below the green cursor of: root@unraid:~# ? I invoked the chmod in a putty telnet session about 10 minutes ago....see attached. As I recall, you will get the Linux prompt back again. Btw, the '^C' on the screen, is the symbol for a Control-C which is the kill command for the currently running process. I show that while the newprem script was running. That would have kill that process and prevent it from finishing. Allow the chown to run with interupting it! Then we will see where we are...
July 24, 201213 yr You can always press enter, that won't hurt anything. It should return a new line when it's done. Running chown is changing the ownership of all files and folders in the directory specified. It does this one file at a time. The more files you have, the longer it will take. Once it is done all files and folders should be owned by nobody.
July 24, 201213 yr Author You can always press enter, that won't hurt anything. It should return a new line when it's done. Running chown is changing the ownership of all files and folders in the directory specified. It does this one file at a time. The more files you have, the longer it will take. Once it is done all files and folders should be owned by nobody. Thank you sureguy, I'll give it some time, as I have a lot of files on it.
July 24, 201213 yr You will need to run the New Permissions script. Currently everything is owned by root, but it should be owned by the user "nobody". I've done the new perms script in the utils tab of 5.0 RC4 but to confirm; is it the same as the below? "unraid" being the name of my network share newperms /mnt/user/unraid/ What does newperms output? Telnet (putty) to the server and run the command again. Then copy and paste the terminal session into a post. from a telnet putty session, I see: processing /mnt/user/unraid/ ... chmod -R go-rwx,u-x,g+u,ug+X /mnt/user/unraid/ Does it complete? It may take a while.
July 24, 201213 yr Author You will need to run the New Permissions script. Currently everything is owned by root, but it should be owned by the user "nobody". I've done the new perms script in the utils tab of 5.0 RC4 but to confirm; is it the same as the below? "unraid" being the name of my network share newperms /mnt/user/unraid/ What does newperms output? Telnet (putty) to the server and run the command again. Then copy and paste the terminal session into a post. from a telnet putty session, I see: processing /mnt/user/unraid/ ... chmod -R go-rwx,u-x,g+u,ug+X /mnt/user/unraid/ Does it complete? It may take a while. It's still going, I guess. I still see the green cursor below the chmod line. I'll just let it cook for a couple hours maybe and then reboot the array as well as reboot my win7 machine.
July 24, 201213 yr Author forgive my ignorance on the attached screenshot: but how do I know when the chown process is complete? Will I see a new line below the green cursor of: root@unraid:~# ? I invoked the chmod in a putty telnet session about 10 minutes ago....see attached. As I recall, you will get the Linux prompt back again. Btw, the '^C' on the screen, is the symbol for a Control-C which is the kill command for the currently running process. I show that while the newprem script was running. That would have kill that process and prevent it from finishing. Allow the chown to run with interupting it! Then we will see where we are... ahh - ok! Good to know that. I highlighted the text and did the ctrl+c for the forum, not knowing that would kill any processes. The chmod is going and I aint gonna touch the telnet putty till I see a new line! EDIT: I meant chown not chmod...
July 24, 201213 yr Run the permissions utility again. It may take anywhere from minutes to hours to complete, depending on how many files you have.
July 25, 201213 yr Run the permissions utility again. It may take anywhere from minutes to hours to complete, depending on how many files you have. Yes. Do this. Wait for it to complete.
July 25, 201213 yr Author You could try issuing the following: chown -R nobody:users /mnt/user/unraid This is what fixed it for me. Thank you to all who helped. I'm definitely saving this in the bag of tricks.
July 25, 201213 yr "newperms /mnt/user/unraid" is the correct method to fix permissions. The New Permissions icon must be clicked after upgrading and it takes a long time to complete on large arrays. The command line method allows a single file or directory to be fixed and thus is much faster. The newperms command has completed when the command line returns. Let it run overnight.
July 25, 201213 yr "newperms /mnt/user/unraid" is the correct method to fix permissions. The New Permissions icon must be clicked after upgrading and it takes a long time to complete on large arrays. The command line method allows a single file or directory to be fixed and thus is much faster. The newperms command has completed when the command line returns. Let it run overnight. That example would only work if you have a share named "unraid" Joe L.
July 25, 201213 yr "newperms /mnt/user/unraid" is the correct method to fix permissions. The New Permissions icon must be clicked after upgrading and it takes a long time to complete on large arrays. The command line method allows a single file or directory to be fixed and thus is much faster. The newperms command has completed when the command line returns. Let it run overnight. That example would only work if you have a share named "unraid" Joe L. Joe, you are completely correct. The original poster did have only a single share and it spanned all of the disks in the array on the server in question. The TRUE problem was that he didn't wait until the the New Permission's script had had time to complete. As was pointed out (and I am sure you realize), this can take hours on arrays which have very large numbers of files and directories. (The size of the array in TB is not an true indicator of the time that will be required.) Too many of us expect that computers can do any task almost instantaneously.. and they do in most cases. When they can't, we expect that the process displays some sort of progress indicator. I suspect that the New Permission's script does not do this. (I have never run it since I started out with one of the ver 5 betas.) First, while there is a message ("This process can take a long time if you have many files."), I don't believe that the message is quite forceful enough. It should say something more like this--- "This process can take many hours to run if you have a large number of files. YOU HAVE TO BE PATIENT". If there is not a progress bar or some indication that it is running, there should be. If nothing else, a running total of files and directories changed. Anything to indicate that something is happening... If something is not done, we are going to see more and more of this type of problems as all the people, who waiting on version 5.0, upgrade after its release.
July 25, 201213 yr Author "newperms /mnt/user/unraid" is the correct method to fix permissions. The New Permissions icon must be clicked after upgrading and it takes a long time to complete on large arrays. The command line method allows a single file or directory to be fixed and thus is much faster. The newperms command has completed when the command line returns. Let it run overnight. That example would only work if you have a share named "unraid" Joe L. Joe, you are completely correct. The original poster did have only a single share and it spanned all of the disks in the array on the server in question. The TRUE problem was that he didn't wait until the the New Permission's script had had time to complete. As was pointed out (and I am sure you realize), this can take hours on arrays which have very large numbers of files and directories. (The size of the array in TB is not an true indicator of the time that will be required.) Too many of us expect that computers can do any task almost instantaneously.. and they do in most cases. When they can't, we expect that the process displays some sort of progress indicator. I suspect that the New Permission's script does not do this. (I have never run it since I started out with one of the ver 5 betas.) First, while there is a message ("This process can take a long time if you have many files."), I don't believe that the message is quite forceful enough. It should say something more like this--- "This process can take many hours to run if you have a large number of files. YOU HAVE TO BE PATIENT". If there is not a progress bar or some indication that it is running, there should be. If nothing else, a running total of files and directories changed. Anything to indicate that something is happening... If something is not done, we are going to see more and more of this type of problems as all the people, who waiting on version 5.0, upgrade after its release. I agree with that, as that's what happened. After activating the new perms script the page showed me a line referencing disk 1 (I have 5 disks). After about 20 minutes, the page refreshed and I thought it was done, but apparently it wasn't. Then, I used a telnet putty session to do the new perms command line manually. I then did a CTRL + C to copy that line to post here to show all what I was doing. The CTRL+C (unknown to me) had killed that process. So I then did the CHOWN command on the actual console (keyboard / monitor attached to my unraid) and let it go most of the day yesterday. Coming back in late last night, I see that it DID return a new command line when it was done and then in checking unraid access on my windows 7 machine, all is well. So for users like me who aren't familiar with linux or command line stuff, it'd be nice for the newperms script to have a progress indicator or have it return on screen what it is doing so that the user can guestimate how far along it is without unknowingly cancelling it like I did.
July 30, 201213 yr So for users like me who aren't familiar with linux or command line stuff, it'd be nice for the newperms script to have a progress indicator or have it return on screen what it is doing so that the user can guestimate how far along it is without unknowingly cancelling it like I did. The problem is that the new permissions script is simply running commands like chown, or chmod, and they don't return a progress status, just a command line when they're done, and error output if they encounter issues. Possibly a line of output indicating that for arrays with many files the process may take an extremely long time. Considering it took so long on your array, I suspect you have many small files stored on it. New permissions on my 7TB of actual data, only takes a minute or so, but almost all of my data is rips of my blu-ray and dvd collection, so the individual files are rather large.
Archived
This topic is now archived and is closed to further replies.