Hi,

 

I have 10 disk array unraid server on intel SASUC8I raid controler

 

I want to upgrade my 4.7 version to 5.0 rc3 because i don't have disk temperature showed on 4.7 version.

 

But.

 

Each time that i try to upgrade (with replacing of bzroot and bzimage on flash drive) 5.0 Version (any beta version) show my disk are Wrong, except one, marked like "new"

 

I attach this post to screen capture of my disk config. one on 4.7 version. Other on 5.0-Rc3 version.

 

 

Any idea to success upgrade ?

 

Thanks.

Do what it says and see if it still happens.

 

http://lime-technology.com/wiki/index.php?title=UnRAID_Server_Version_5.0-beta_Release_Notes

 

    Version 4.7

 

    Prepare the flash: either shutdown your server and plug the flash into your PC or Stop the array and perform the following actions referencing the flash share on your network:

        Copy the files bzimage and bzroot from the zip file to the root of your flash device, overwriting the same-named files already there.

        If present, delete these files from the flash (sorry, you will have to re-enter all your users after booting this release):

            config/passwd

            config/shadow

            config/smbpasswd

    Reboot your server. Once boot-up has completed, you should see "Stopped. Configuration valid." array status with all disks assigned correctly except for the Cache disk. If you previously had a Cache disk assigned, you will need to re-assign it manually and re-apply any unique configuration settings for it.

    Carefully examine the Identification strings for each disk. If you see "MBR: error", or "MBR: unknown" for any disk, do not Start the array; instead post your finding in the Forum announcement thread for this release. If everything looks ok, click Start to bring the array on-line. Note: there is a new configuration setting on the Disk Settings page called "Enable auto start". If you set this to "Yes", then upon next server boot, if the array is valid, then it will be automatically Started (this is the old behavior).

    Go to Utils/New Permissions and execute that utility to change file ownership and permission settings. This is necessary for proper operation of the 5.0 security model.

    Go to Users page and re-enter all of your users. If you plan on using AFP with either Secure or Private security mode, you must enter at least one user because AFP does not permit the 'root' user name.

I have ever read these instructions... and i follow it.

 

I don't have config/passwd shadow or smbpasswd and when i reboot my server i don't see "stopped configuration valid" like i explain on my post.

Make a post on the rc3 thread, point Tom@lime-tech to this thread with your screen captures.

 

It appears to me as if your disk-controller card labels its disks differently under the two versions.  Therefore, existing disks are not recognized.

 

Easiest solution would be to assign the disks as desired, then to go to the "Utils" link and click on "New Config"

 

That should then let you start the array, and it will go through the process of initially calculating parity (basically writing parity with exactly what is there now)

 

before you do anything, make a copy of your existing "config" folder so you can revert to the 4.7 release if desired.

 

Joe L.

 

Those temps look very high to me.  You are in an idle state, and the lowest temp is 40, with 3 drives at 50, and one at 53.  I'd hate to see those temps once you start the parity rebuild!  I'd first take a quick look for any fans that have quit.

 

If you do not want to spend much time now reworking your airflow and cooling, you could take the side panel off, and point a good house fan into it.  It's not very efficient, but I don't think it would do any worse.

Thanks for answers I will try "nex config" solutuion later beacause i have "no parity" enabled because of one disk smart errors. I have a Norco 4U case without sidepanel but high temp are because it seems that idle state do not stop the disks.

I'm not sure what you meant by "without sidepanel" but if you mean you are running without the case closed, then you probably need to close it up. Case fans can't do their job if you have a big gaping hole for the air to go through without being forced over the drive bays. Most cases only cool properly when fully closed.