TrueNAS® provides two methods for performing an upgrade: a GUI upgrade (preferred) and an upgrade using IPMI and ISO redirection. This section describes how to upgrade using the preferred GUI method.
Before upgrading the system to 9.3, perform the following steps:
Note
when upgrading a HA unit, you must first upgrade the passive node. In Step 1 of the GUI upgrade, you must select “Memory device” for the “Place to temporarily place firmware file”. Once the update on the passive node is complete, it cannot sync configuration changes until the active node is upgraded, so adding an NFS share to the active node is a very bad idea. Next, upgrade the active node. Once the active node reboots after the upgrade, the passive node will become active on the new image.
To perform the upgrade, go to System –> Settings –> Advanced –> Firmware Update as shown in Figure 13.1a.
Use the drop-down menu to select an existing volume to temporarily place the firmware file during the upgrade. Alternately, of if this is the passive node of a HA unit, select “Memory device” to allow the system to create a temporary RAM disk to be used during the upgrade. After making your selection, click the “Apply Update” button to see the screen shown in Figure 13.1b.
Figure 13.1a: Step 1 of Upgrade
Figure 13.1b: Step 2 of Upgrade
This screen again reminds you to backup your configuration before proceeding. If you have not yet, click the “click here” link.
Browse to the location of the downloaded .txz file, then paste its SHA256 sum.
When finished, click the “Apply Update” button to begin the upgrade progress. Behind the scenes, the following steps are occurring:
If your disks are encrypted and you have created a passphrase and saved the recovery key, the volume will automatically be locked during an upgrade. This is to prevent an unauthorized user from using an upgrade procedure to gain access to the data on the encrypted disks. After the upgrade, the locked volumes will be unavailable until they are unlocked with the passphrase and recovery key.
To unlock the volume, go to Storage –> Volumes –> View Volumes and highlight the locked volume. As seen in Figure 13.1c, clicking the “Unlock” icon will prompt for the passphrase or recovery key. You can also select which services to start when the volume is unlocked.
Figure 13.1c: Unlocking an Encrypted Volume
If the TrueNAS® system does not become available after the upgrade, use IPMI or the physical console of the system to find out what went wrong. From the console menu you can determine if it received an IP address and use option “1) Configure Network Interfaces” if it did not.
If this does not fix the problem, go into option “9) Shell” and read the system log with this command:
more /var/log/messages
If the database upgrade failed, a file called /data/upgrade-failed should be created with the details.
If the problem is not obvious or you are unsure how to fix it, contact your iXsystems support engineer.
TrueNAS® supports two operating systems on the operating system device: the current operating system and, if you have performed an upgrade, the previously installed version of the operating system. This allows you to reboot into the previous version should you experience a problem with the upgraded version.
The upgrade process automatically configures the system to boot from the new operating system. If the system remains inaccessible and you wish to revert back to the previous installation, type reboot from the shell or select “10) Reboot” from the console menu. Watch the boot screens and press the other boot option (typically F2) from the TrueNAS® console when you see the following options at the very beginning of the boot process. In this example, Boot: F1 refers to the default option (the newly upgraded version), so pressing F2 will boot into the previous version.:
F1 FreeBSD
F2 FreeBSD
Boot: F1
If the upgrade completely fails, don’t panic. The data is still on your disks and you still have a copy of your saved configuration. You can always:
The upgrade process will not automatically upgrade the version of existing ZFS pools. iXsystems recommends to wait a few weeks to ensure that the upgrade went smoothly before upgrading the pools.
Before upgrading the existing ZFS pools, be aware of the following caveats:
To perform the ZFS version upgrade, open `Shell`_.
First, verify that the status of all of the pools is healthy:
zpool status -x
all pools are healthy
Note
do not upgrade the pool if its status does not show as healthy.
Then, upgrade the pools:
zpool upgrade -a
The upgrade itself should only take a seconds and is non-disruptive. This means that you do not need to stop any sharing services in order to upgrade the pool. However, you should choose to upgrade when the pool is not being heavily used. The upgrade process will suspend I/O for a short period, but should be nearly instantaneous on a quiet pool.