Difference between revisions of "UnRAID OS version 6 Upgrade Notes"
(→My OVMF VM doesn't boot correctly)
m (Limetech moved page UnRAID OS version 6 Upgrade Instructions to UnRAID OS version 6 Upgrade Notes without leaving a redirect)
Revision as of 23:53, 3 February 2017
- 1 Prerequisites
- 2 Possible upgrade issues
Before upgrading to version 6.3, please ensure you have made a complete back up of your USB flash device. You can do this by copying the entire contents of the "Flash" share to a separate computer.
From version 5.x or earlier
Please see this forum post for information on upgrading.
From version 6.x
- Boot your server up and login to the web interface
- Click the Plugins tab
- Click the Check for updates button
- Click the "Update" button next to unRAID Server OS
- Once the upgrade is complete, reboot your server for it to take affect
Possible upgrade issues
Having problems after the update? See below for common issues and solutions.
My array / docker apps are taking a really long time to start after the upgrade
There is a one-time update procedure that each container will need to go through in order to point it towards the new Docker Hub API going forward, even if the container itself truly isn't in need of an update. This process will happen automatically the first time your containers are started after upgrading. The Docker change log describes it like this:
Docker 1.10 uses a new content-addressable storage for images and layers. A migration is performed the first time docker is run, and can take a significant amount of time depending on the number of images present.
See here for more information from Docker on this.
My containers aren't working right after the upgrade
If you run into any issues with your containers after this procedure completes (such as the "layers from manifest don't match image configuration" error), you will need to rebuild your docker image file. To do this:
- Stop Docker from the Settings > Docker page
- Click the checkbox and then click the button to delete the image
- Start Docker again and the image will be recreated
- Go to the Docker tab and click Add Container
- From the Template drop down, select one of your previous templates (prefixed with "my-") and then click Apply
- Repeat the previous step for each of your containers
- You will not need to reconfigure your apps after this is complete
My VMs get an error of "cannot get interface MTU..."
A change that was made in version 6.2 eliminated the customization of the bridge name used for virtual machines. Users that have a custom bridge name set will need to fix their VMs to point to the new default of 'br0'. To fix this, perform the following steps:
- Navigate to the VMs tab.
- Edit each VM and turn on Advanced View mode.
- Locate the network section and from the dropdown, select br0 and then click apply.
- Once all VMs are set to use the 'br0' bridge, go to the Settings -> VM Manager page, turn on Advanced View, and set the default network bridge on this page to also be 'br0' and click apply.
VNC access to my VMs is not working or performing poorly
VMs created in earlier releases of unRAID Server OS may be set to use an outdated graphics device driver for VNC access. To fix this, perform the following steps:
- For each affected VM, go to the VMs tab, click the VM's icon, and select the Edit option
- Turn on "Advanced View" in the top right of the Edit VM page
- If you are using VNC for the primary graphics card, adjust the VNC Video Driver field to QXL
- Click Apply
My OVMF VM doesn't boot correctly
OVMF-based virtual machines that were created under version 6.1 or earlier will most likely require a one-time process to boot up properly on the new release. If you are presented with an EFI shell instead of your OS booting appropriately, type the following commands in order to boot your VM:
- cd efi/boot
If this doesn't work, try changing the first command from fs0: to fs1:. If that doesn't work, please post in the forums for further assistance. This procedure should only need to be performed the first time you boot OVMF VMs that were previously created using unRAID 6.1 or earlier.