I followed the relase Notes and the system appears to have booted okay.

 

I started "New Permissions" and it seems to have stalled on disk 4 out of 5.  The screen looks as follows:

 

processing /mnt/disk1

... chmod -R go-rwx,u-x,g+u,ug+X /mnt/disk1

... chown -R nobody:users /mnt/disk1

processing /mnt/disk2

... chmod -R go-rwx,u-x,g+u,ug+X /mnt/disk2

... chown -R nobody:users /mnt/disk2

processing /mnt/disk3

... chmod -R go-rwx,u-x,g+u,ug+X /mnt/disk3

... chown -R nobody:users /mnt/disk3

processing /mnt/disk4

... chmod -R go-rwx,u-x,g+u,ug+X /mnt/disk4

 

I can navigate to the other tabs in the gui, but when I come back to utilities new permissions it always wants me to restart the process at which time it races through the first 3 disks and stalls on disk 4

There are 5 data disks plus the parity disk and 3 disks not in the array but installed and precleared.

 

If I try to access data on the unraid system from a windows machine I can see all the shared directories in windows but if I try to open one I get:

 

//Tower/xxx refers to  a location that is unavailable. . . .

 

I would appreciate any help so I can use my system.

 

I assume I can just revert back to 4.7 with no issue but am trying to avoid doing that.

 

I have attached a log file

Log_File.txt

My experience was similar...I took a shower and it was still processing.  Eventually it completed~15-30 minutes I believe.

 

What's in your go script?

I pulled everything out of the Go script. No unMenu, no loading of special packages, tried to make it is as vanilla as possible. I tried to go back to 4.7 and it stalled (4.7) with the original go file waiting for the array to start.

 

I will do as you say, give it time. 

 

I trust the fact that I think I restarted, did not kill it but left the util tab and then came back and went to new permissions and the check box was not checked and start was not dimmed, so I "started" it again; 4-5 times should have no effect.

 

I think disk 4, the one it is stalled on, has a very high file count (tens of thousands of files) as it is where backups are stored along with music; whereas all the others have a low file count since they are holding movies.

I tried to go back to 4.7 and it stalled (4.7) with the original go file waiting for the array to start.

 

 

I had the same thing happen to me. The super.dat file is not compatible between 4.7 and 5x. I had my original 4.7 files backed up and it booted normally.

You are being very helpful. Thank You.  If I want to revert back to 4.7 do I have to remove the Super.dat file? in addition to restoring bizroot and bizimage to the 4.7 versions. Anything else I need to do/worry about

 

I actually have two flash drives as I originally bought two licenses. I want to set one up for 4.7 so I can go back to it very easily and use the other one for 5.0.  One of them won't boot so I need to reformat it and make it bootable again. I always back up up my flash drive configs, so I can load it with the 4.7 backup.  I notice in the config folder there is a ProKey file. I assume this key is needed for license verification, and I need to use the correct one for the falsh drive.

 

I just hope with all my fidling around, I do not destroy my disk data.

Restore the entire config directory. Changes on the flash should not effect data.

What dgaschk said.

I just removed the entire 5x stuff (since I was just testing) and copied the 4.7 files over the network, then rebooted.

I think disk 4, the one it is stalled on, has a very high file count (tens of thousands of files) as it is where backups are stored along with music; whereas all the others have a low file count since they are holding movies.

 

That's most likely your answer right there - thousands of files to apply new permissions to, so yeah just give it time   IIRC, the new permissions process shows up via telnet/SSH in something like top/htop (I prefer the latter) if you want to see if it's still in action.

I suspect you are right.  One I do a PC vackup each backup folder gets about 100,000  files.  There are at least 20 or so back up folders.  The files are all small, but there re a lot of them.  It is the file count not there size that makes the difference in permissions.  I will let it run for a overnight.

 

The disks that it did finish processing all seem to be okay.  I wish I could tell it explicitly which disks I wanted it to process and in what order.  Oh well it is only a one time thing

I have not yet been able to get through disk4. I leave it for a few hours and when I come back there is a message that the web page is no longer available.  I can go nack to main then utils and start it again, but the definition of an insane person is one who does the same thing agaian and again expecting a different output.

 

Since most of the backups are quite old and no longer needed I decided to remove them using the console and "rm -r directoryname".  That worked fine and I have gotten rid of an awful lot of files. an "ls" from the console shows just what I expect to see in the backup folder; However when I go to windows and network those directories I removed are still showing up, but can not be accessed. Any ideas on why?

 

I have just restarted the New Permissions process and it is once again on disk 4 but it has only been there a few minutes and hopefully it will get through it this time.

 

I think all is now well.  The only issue(s) I believe that this has shown in 5.0 RC4 are:

 

1) The web disconnect in the middle of performing the resetting of permissions and owners when there are hundreds of thousands of files to process

 

2) It would be very helpful if somehow a running count of the number of files to be processed was shown to indicate progress.  Ideally starting at the total number of files to process and counting down every N seconds with a page refresh until complete.  This would help those of us that have little or no patience. I will probably rewrite my Backup system to automatically build a compressed archive instead of what it does now (image copy).

 

Thanks to all who advised me!

 

Next step is to let it run for a while and then install either Simple Features or unMenu or both.  Any advice on these installations would, as usual, be appreciated.

 

I assume if I remove the Simple Features stuff from /boot/extra the original menu system will come back ??

I went with Simple Features..instructions were easy, just like unMENU. I removed my unMENU install after upgrading, and haven't had a reason to re-install. 

 

If you use APCUPSD with Simple Features, I ended up using this version as there were some problems with the previous plug-in:

http://lime-technology.com/forum/index.php?topic=15583.msg180759#msg180759 (remove .txt and replace with .plg)

 

Edit: btw, unMENU and Simple Features can be used in conjunction. 

I had a blank screen when first booting with unMENU and v5 installed; this is the fix:

http://lime-technology.com/forum/index.php?topic=20371.0