Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

How to upgrade betas

Featured Replies

I have the pro version running with 4 drives on beta 5. 7. I see a new beta has been released. Sorry if I offend anyone.  Not ment to. however, I have not been able to find instructions on how to upgrade to the latest beta's. Could someone point me in the right direction please?

 

Many thanks

 

Ed

Read the release notes linked to in the first post of each new release announcement.

  • Author

Thanks,  I called myself having done that!  I will take another look. Im sure I missed something.

 

Ed

More specifically the 5.0beta7 release notes links to the following information [ http://lime-technology.com/wiki/index.php?title=UnRAID_Server_Version_5.0-beta7_Release_Notes ]

 

Upgrade Instructions

 

Important:

 

    Only upgrade a server that has all disks enabled with valid parity: no missing disk(s), no disabled disk, etc. Verify everything is working correctly with your current release before proceeding.

    Backup the entire contents of your Flash device before upgrading. If something goes wrong or a major problem is uncovered in the release this will make it easier for you to downgrade.

    Record the model, serial number, and position of each of your hard disks. Perhaps the easiest way to do this is take a screen capture of the Disk Status page.

    Disable or un-install all non-stock unRAID add-ons. Only use add-ons that have been verified to work properly with this release by the add-on author.

 

If you are currently running:

 

    Any release before 4.7

 

    Upgrade your server to version 4.7 and verify your server boots properly into 4.7 and your configuration appears valid.

    Now follow instructions for upgrading from 4.7 in next section.

 

    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.

 

    Version 5.0-beta1 or 5.0-beta2

 

    Follow all steps above for upgrading from 4.7 with the exception of step 4 (because presumably you already did this). Yes, you have to re-enter your users again, this is necessary for proper operation of avahi (Zeroconf, a.k.a., Bonjour).

 

    Version 5.0-beta3, 5.0-beta4, 5.0-beta5, 5.0-beta5a, 5.0-beta5b

 

    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.

        Delete the file config/super.dat. You will need to re-assign all your hard drives.

    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).

 

    Version 5.0-beta6

 

    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.

    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).

 

    Version 5.0-beta6a

 

    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.

    Reboot your server. Once boot-up has completed, you should see "Stopped. Configuration valid." array status with all disks assigned correctly.

    Click on each disk link on the Main page and examine the Partition format field. 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.

 

  • Author

Thanks BRiT.  Got the upgrade done!

 

Ed

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.