2. Installing and Upgrading¶
Please note that the FreeNAS® operating system must be installed on a separate device from the drives which hold the storage data. In other words, with only one disk drive, the FreeNAS® graphical interface is available, but there is no place to store any data. And storing data is, after all, the whole point of a NAS system. Home users experimenting with FreeNAS® can install FreeNAS® on an inexpensive USB thumb drive and use the computer’s disks for storage.
This section describes:
- Getting FreeNAS®
- Preparing the Media
- Performing the Installation
- Installation Troubleshooting
2.1. Getting FreeNAS®¶
The latest STABLE version of FreeNAS® 11.1 can be downloaded from https://download.freenas.org/stable/.
FreeNAS® requires 64-bit hardware.
The download page contains an .iso file. This is a bootable installer that can be written to either a CD or USB flash as described in Preparing the Media.
The .iso file has an associated
sha256.txt file which is
used to verify the integrity of the downloaded file. The command to
verify the checksum varies by operating system:
- on a BSD system use the command
- on a Linux system use the command
- on a Mac system use the command
shasum -a 256 name_of_file
- Windows or Mac users can install additional utilities like HashCalc or HashTab
The value produced by running the command must match the value shown
sha256.txt file. Checksum values that do not match
indicate a corrupted installer file that should not be used.
2.2. Preparing the Media¶
The FreeNAS® installer can run from either a CD or a USB memory stick.
A CD burning utility is needed to write the
.iso file to a
.iso file can also be written to a USB memory stick. The
method used to write the file depends on the operating system. Examples
for several common operating systems are shown below.
To install from a USB stick to another USB stick, two USB ports are needed, each with an inserted USB device. One USB stick contains the installer. The other USB stick is the destination for the FreeNAS® installation. Take care to select the correct USB device for the FreeNAS® installation. It is not possible to install FreeNAS® onto the same USB stick containing the installer. After installation, remove the installer USB stick. It might also be necessary to adjust the BIOS configuration to boot from the new FreeNAS® USB stick.
Make sure that the boot device order in the BIOS is set to boot from the device containing the FreeNAS® installer media, then boot the system to start the installation.
2.2.1. On FreeBSD or Linux¶
On a FreeBSD or Linux system, the dd command can be used to
.iso file to an inserted USB thumb drive. This
example demonstrates writing the image to the first USB device
(/dev/da0) connected to a FreeBSD system. Substitute the filename of
.iso file and the device name of the device to write.
The dd command is very powerful and can
destroy any existing data on the specified device. Make
absolutely sure of the device name to write to and do not
mistype the device name when using dd! If you are
uncomfortable using this command, write the
.iso file to a
dd if=FreeNAS-11.0-RELEASE.iso of=/dev/da0 bs=64k 6117+0 records in 6117+0 records out 400883712 bytes transferred in 88.706398 secs (4519220 bytes/sec)
When using the dd command:
- if= refers to the input file, or the name of the file to write to the device.
- of= refers to the output file; in this case, the device name of
the flash card or removable USB drive. Note that USB device numbers
are dynamic, and the target device might be da1 or da2 or
another name depending on which devices are attached. Before
attaching the target USB drive, use ls /dev/da*. Then
attach the target USB drive, wait ten seconds, and run ls
/dev/da* again to see the new device name and number of the target
USB drive. On Linux, use
/dev/sdX, where X refers to the letter of the USB device.
- bs= refers to the block size, the amount of data to write at a time. The larger 64K block size shown here helps speed up writes to the USB drive.
2.2.2. On Windows¶
Microsoft provides the USB/DVD Download Tool to create a USB bootable
image from an
.iso file. Follow
but enter the name of the downloaded
.iso into the
SOURCE FILE box.
Image Writer and Rufus are alternate programs for writing images to USB sticks on a computer running Windows. When using Rufus, check Create a bootable disk using and select DD Image from the drop-down menu.
2.2.3. On OS X¶
Insert the USB thumb drive. In the Finder, go to Free space when creating the partition works fine.. Unmount any mounted partitions on the USB thumb drive. Check that the USB thumb drive has only one partition, or partition table errors will be shown on boot. If needed, use Disk Utility to set up one partition on the USB drive. Selecting
Determine the device name of the inserted USB thumb drive. From TERMINAL, navigate to the Desktop, then type this command:
diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI 209.7 MB disk0s1 2: Apple_HFS Macintosh HD 499.2 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *8.0 GB disk1 1: DOS_FAT_32 UNTITLED 8.0 GB disk1s1
This shows which devices are available to the system. Locate the
target USB stick and record the path. If you are not sure which path
is the correct one for the USB stick, remove the device, run the
command again, and compare the difference. Once sure of the device
name, navigate to the Desktop from TERMINAL, unmount the USB stick,
and use the dd command to write the image to the USB stick.
In this example, the USB thumb drive is
/dev/disk1. It is
first unmounted. The dd command is used to write the
image to the faster “raw” version of the device (note the extra
/dev/rdisk1). When running these commands,
substitute the name of the installation file and the correct path to
the USB thumb drive.
diskutil unmountDisk /dev/disk1 Unmount of all volumes on disk1 was successful dd if=FreeNAS-11.0-RELEASE.iso of=/dev/rdisk1 bs=64k
If the error “Resource busy” is shown when the dd command is run, go to, find the USB thumb drive, and click on its partitions to make sure all of them are unmounted. If the error “dd: /dev/disk1: Permission denied” is shown, run the dd command by typing sudo dd if=FreeNAS-11.0-RELEASE.iso of=/dev/rdisk1 bs=64k. This will prompt for your password.
The dd command can take some minutes to complete. Wait until the prompt returns and a message is displayed with information about how long it took to write the image to the USB drive.
2.3. Performing the Installation¶
With the installation media inserted, boot the system from that media. The FreeNAS® installer GRUB menu is displayed as is shown in Figure 2.3.1.
The Serial Enabled option is useful on systems which do not have a keyboard or monitor, but are accessed through a serial port, Serial over LAN, or IPMI.
If the installer does not boot, verify that the installation
device is listed first in the boot order in the BIOS. When booting
from a CD, some motherboards may require connecting the CD device
to SATA0 (the first connector) to boot from CD. If the installer
stalls during bootup, double-check the SHA256 hash of the
.iso file. If the hash does not match, re-download the
file. If the hash is correct, burn the CD again at a lower speed or
write the file to a different USB stick.
The installer will start automatically after a few seconds, or an
option can be chosen by moving the highlight bar to it with the up and
down arrow keys and pressing
Enter. After booting, the
installer menu is displayed as shown in
Enter to select the default option,
1 Install/Upgrade. The next menu, shown in
lists all available drives. This includes any inserted USB thumb
drives, which have names beginning with da.
A minimum of 8 GB of RAM is required and the installer will present a warning message if less than 8 GB is detected.
In this example, the user is performing a test installation using VirtualBox and has created a 16 GB virtual disk to hold the operating system.
Use the arrow keys to highlight the destination USB drive, SSD, DOM
(Disk on Module), or virtual disk. Press the
spacebar to select
it. To mirror the boot device, move to the second device and press
spacebar to select it also. After making these selections,
Enter. The warning shown in
is displayed, a reminder not to install the operating system on a
drive that is meant for storage. Press
Enter to continue on to
the screen shown in
A minimum of 8 GB of space on the boot device is required. However, 32 GB is recommended to provide room for future additions and boot environments. When using mirrored boot devices, it is best to use devices of the same size. If the device sizes are different, the mirror is limited to the size of the smaller device.
The installer recognizes existing installations of previous versions
of FreeNAS® 8.x or 9.x. When an existing installation is present, the
menu shown in
is displayed. To overwrite an existing installation, use the arrows
to move to Fresh Install and press
Enter twice to
continue to the screen shown in
The screen shown in Figure 2.3.6 prompts for the root password which is used to log in to the administrative graphical interface.
Setting a password is mandatory and the password cannot be blank.
Since this password provides access to the administrative GUI, it
should be hard to guess. Enter the password, press the down arrow key,
and confirm the password. Then press
Enter to continue with the
For security reasons, the SSH service and root SSH logins are disabled by default. Unless these are set, the only way to access a shell as root is to gain physical access to the console menu or to access the web shell within the administrative GUI. This means that the FreeNAS® system should be kept physically secure and that the administrative GUI should be behind a properly configured firewall and protected by a secure password.
FreeNAS® can be configured to boot with the standard BIOS boot mechanism or UEFI booting as shown Figure 2.3.7. BIOS booting is recommended for legacy and enterprise hardware. UEFI is used on newer consumer motherboards.
Most UEFI systems can also boot in BIOS mode if CSM (Compatibility Support Module) is enabled in the UEFI setup screens.
The message in Figure 2.3.8 is shown after the installation is complete.
Enter to return to the first menu, shown in
Highlight 3 Reboot System and press
booting from CD, remove the CDROM. As the system reboots, make sure
that the device where FreeNAS® was installed is listed as the first
boot entry in the BIOS so the system will boot from it. FreeNAS® boots
into the Console Setup menu described in
2.4. Installation Troubleshooting¶
If the system does not boot into FreeNAS®, there are several things that can be checked to resolve the situation.
Check the system BIOS and see if there is an option to change the USB emulation from CD/DVD/floppy to hard drive. If it still will not boot, check to see if the card/drive is UDMA compliant.
If the system BIOS does not support EFI with BIOS emulation, see if it has an option to boot using legacy BIOS mode.
When the system starts to boot but hangs with this repeated error message:
run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
go into the system BIOS and look for an onboard device configuration for a 1394 Controller. If present, disable that device and try booting again.
If the system starts to boot but hangs at a mountroot> prompt, follow the instructions in Workaround/Semi-Fix for Mountroot Issues with 9.3.
If the burned image fails to boot and the image was burned using a Windows system, wipe the USB stick before trying a second burn using a utility such as Active@ KillDisk. Otherwise, the second burn attempt will fail as Windows does not understand the partition which was written from the image file. Be very careful to specify the correct USB stick when using a wipe utility!
FreeNAS® provides flexibility for keeping the operating system up-to-date:
- Upgrades to major releases, for example from version 9.3 to 9.10, can still be performed using either an ISO or the graphical administrative interface. Unless the Release Notes for the new major release indicate that the current version requires an ISO upgrade, either upgrade method can be used.
- Minor releases have been replaced with signed updates. This means that it is not necessary to wait for a minor release to update the system with a system update or newer versions of drivers and features. It is also no longer necessary to manually download an upgrade file and its associated checksum to update the system.
- The updater automatically creates a boot environment, making updates a low-risk operation. Boot environments provide the option to return to the previous version of the operating system by rebooting the system and selecting the previous boot environment from the boot menu.
This section describes how to perform an upgrade from an earlier version of FreeNAS® to 11.1. After 11.1 has been installed, use the instructions in Update to keep the system updated.
Be aware of these caveats before attempting an upgrade to 11.1:
- Warning: upgrading the ZFS pool can make it impossible to go back to a previous version. For this reason, the update process does not automatically upgrade the ZFS pool, though the Alert system shows when newer feature flags are available for a pool. Unless a new feature flag is needed, it is safe to leave the pool at the current version and uncheck the alert. If the pool is upgraded, it will not be possible to boot into a previous version that does not support the newer feature flags.
- The Wizard does not recognize an encrypted ZFS pool. If the ZFS pool is GELI-encrypted and the Wizard starts after the upgrade, cancel the Wizard and use the instructions in Importing an Encrypted Pool to import the encrypted volume. The Wizard can be run afterward for post-configuration. It will then recognize that the volume has been imported and not prompt to reformat the disks.
- Upgrading the firmware of Broadcom SAS HBAs to the latest version is recommended.
- If upgrading from 9.3.x, please read the FAQ: Updating from 9.3 to 9.10 first.
- Upgrades from FreeNAS® 0.7x are not supported. The system has no way to import configuration settings from 0.7x versions of FreeNAS®. The configuration must be manually recreated. If supported, the FreeNAS® 0.7x volumes or disks must be manually imported.
- Upgrades on 32-bit hardware are not supported. However, if the system is currently running a 32-bit version of FreeNAS® and the hardware supports 64-bit, the system can be upgraded. Any archived reporting graphs will be lost during the upgrade.
- UFS is no longer supported. If your data currently resides on one UFS-formatted disk, create a ZFS volume using other disks after the upgrade, then use the instructions in Import Disk to mount the UFS-formatted disk and copy the data to the ZFS volume. With only one disk, back up its data to another system or media before the upgrade, format the disk as ZFS after the upgrade, then restore the backup. If the data currently resides on a UFS RAID of disks, it is not possible to directly import that data to the ZFS volume. Instead, back up the data before the upgrade, create a ZFS volume after the upgrade, then restore the data from the backup.
- The VMware Tools VMXNET3 drivers are no longer supported. Configure and use the vmx(4) driver instead.
2.5.2. Initial Preparation¶
Before upgrading the operating system, perform the following steps:
- Back up the FreeNAS® configuration in .
- If any volumes are encrypted, make sure that you have set the passphrase and have a copy of the encryption key and the latest recovery key. After the upgrade is complete, use the instructions in Importing an Encrypted Pool to import the encrypted volume.
- Warn users that the FreeNAS® shares will be unavailable during the upgrade; you should schedule the upgrade for a time that will least impact users.
- Stop all services in .
2.5.3. Upgrading Using the ISO¶
To perform an upgrade using this method,
.iso to the computer that will be used to prepare the
installation media. Burn the downloaded
.iso file to a CD or
USB thumb drive using the instructions in
Preparing the Media.
Insert the prepared media into the system and boot from it. After the
media finishes booting into the installation menu, press
to select the default option of 1 Install/Upgrade. The
installer presents a screen showing all available drives.
All drives are shown, including boot drives and storage drives. Only choose boot drives when upgrading. Choosing the wrong drives to upgrade or install will cause loss of data. If unsure about which drives contain the FreeNAS® operating system, reboot and remove the install media. In the FreeNAS® GUI, useto identify the boot drives. More than one drive is shown when a mirror has been used.
Move to the drive where FreeNAS® is installed and press the
Spacebar to mark it with a star. If a mirror has been used for
the operating system, mark all of the drives where the FreeNAS®
operating system is installed. Press
Enter when done.
The installer recognizes earlier versions of FreeNAS® installed on the boot drive or drives and presents the message shown in Figure 2.5.1.
If you choose a Fresh Install, the backup of your configuration data must be restored using after booting into the new operating system.
To perform an upgrade, press
Enter to accept the default of
Upgrade Install. Again, the installer will remind you that
the operating system should be installed on a disk that is not used
The updated system can be installed in a new boot environment,
or the entire boot device can be formatted to start fresh. Installing
into a new boot environment preserves the old code, allowing a
roll-back to previous versions if necessary. Formatting the boot
device is usually not necessary but can reclaim space. User data and
settings are preserved when installing to a new boot environment and
also when formatting the boot device. Move the highlight to one of the
options and press
Enter to start the upgrade.
The installer unpacks the new image and displays the menu shown in Figure 2.5.3. The database file that is preserved and migrated contains your FreeNAS® configuration settings.
Enter. FreeNAS® indicates that the upgrade is complete and
a reboot is required. Press OK, highlight
3 Reboot System, then press
Enter to reboot the
system. If the upgrade installer was booted from CD, remove the CD.
During the reboot there may be a conversion of the previous configuration database to the new version of the database. This happens during the “Applying database schema changes” line in the reboot cycle. This conversion can take a long time to finish, sometimes fifteen minutes or more, and might have to reboot the system again afterwards. Please be patient and the system will start normally. If database errors are shown but the graphical administrative interface is accessible, go to Upload Config button to upload the configuration that you saved before starting the upgrade.and use the
2.5.4. Upgrading From the GUI¶
To perform an upgrade using this method, go to.
After the update is complete, you will temporarily lose your connection as the FreeNAS® system reboots into the new version of the operating system. The FreeNAS® system will normally receive the same IP address from the DHCP server. Refresh your browser after a moment to see if you can access the system.
2.5.5. If Something Goes Wrong¶
If an update fails, an alert is issued and the details are written to
To return to a previous version of the operating system, physical or IPMI access to the FreeNAS® console is needed. Reboot the system and watch for the boot menu. In the example shown in Figure 2.5.4, the first boot menu entry, FreeNAS (default), refers to the initial installation, before the update was applied. The second boot entry, FreeNAS-1415259326, refers to the current version of the operating system, after the update was applied. This second entry is highlighted and begins with a star, indicating that this is the environment the system will boot unless another entry is manually selected. Both entries include a date and timestamp showing when that boot environment was created.
To boot into the previous version of the operating system, use the up
or down arrow to select it and press
If a boot device fails and the system no longer boots, don’t panic. The data is still on the disks and there is still a copy of the saved configuration. The system can be recovered with a few steps:
- Perform a fresh installation on a new boot device.
- Import the volumes in .
- Restore the configuration in .
It is not possible to restore a saved configuration that is newer than the installed version. For example, if you reboot into an older version of the operating system, you cannot restore a configuration that was created in a later version.
2.5.6. Upgrading a ZFS Pool¶
In FreeNAS®, ZFS pools can be upgraded from the graphical administrative interface.
Before upgrading an existing ZFS pool, be aware of these caveats first:
- the pool upgrade is a one-way street, meaning that if you change your mind you cannot go back to an earlier ZFS version or downgrade to an earlier version of the software that does not support those feature flags.
- before performing any operation that may affect the data on a storage disk, always back up all data first and verify the integrity of the backup. While it is unlikely that the pool upgrade will affect the data, it is always better to be safe than sorry.
- upgrading a ZFS pool is optional. Do not upgrade the pool if the the possibility of reverting to an earlier version of FreeNAS® or repurposing the disks in another operating system that supports ZFS is desired. It is not necessary to upgrade the pool unless newer ZFS feature flags are required. If a pool is upgraded to the latest feature flags, it will not be possible to import that pool into another operating system that does not yet support those feature flags.
To perform the ZFS pool upgrade, go to Upgrade button as shown in Figure 2.5.5.and highlight the volume (ZFS pool) to upgrade. Click the
If the Upgrade button does not appear, the pool is already at the latest feature flags and does not need to be upgraded.
The warning serves as a reminder that a pool upgrade is not reversible. Click OK to proceed with the upgrade.
The upgrade itself only takes a few seconds and is non-disruptive. It is not necessary to stop any sharing services to upgrade the pool. However, it is best to upgrade when the pool is not being heavily used. The upgrade process will suspend I/O for a short period, but is nearly instantaneous on a quiet pool.
FreeNAS® can be run inside a virtual environment for development, experimentation, and educational purposes. Please note that running FreeNAS® in production as a virtual machine is not recommended. If you decide to use FreeNAS® within a virtual environment, read this post first as it contains useful guidelines for minimizing the risk of losing data.
To install or run FreeNAS® within a virtual environment, create a virtual machine that meets these minimum requirements:
- at least 8192 MB (8 GB) base memory size
- a virtual disk at least 8 GB in size to hold the operating system and boot environments
- at least one additional virtual disk at least 4 GB in size to be used as data storage
- a bridged network adapter
This section demonstrates how to create and access a virtual machine within VirtualBox and VMware ESXi environments.
is an open source virtualization program originally created by Sun
Microsystems. VirtualBox runs on Windows, BSD, Linux, Macintosh, and
OpenSolaris. It can be configured to use a downloaded FreeNAS®
.iso file, and makes a good testing environment for practicing
configurations or learning how to use the features provided by
To create the virtual machine, start VirtualBox and click the New button, shown in Figure 2.6.1, to start the new virtual machine wizard.
Click the Next button to see the screen in Figure 2.6.2. Enter a name for the virtual machine, click the Operating System drop-down menu and select BSD, and select FreeBSD (64-bit) from the Version dropdown.
Click Create to launch the Create Virtual Hard Drive Wizard shown in Figure 2.6.5.
Select VDI and click the Next button to see the screen in Figure 2.6.6.
Choose either Dynamically allocated or Fixed-size storage. The first option uses disk space as needed until it reaches the maximum size that is set in the next screen. The second option creates a disk the full amount of disk space, whether it is used or not. Choose the first option to conserve disk space; otherwise, choose the second option, as it allows VirtualBox to run slightly faster. After selecting Next, the screen in Figure 2.6.7 is shown.
This screen is used to set the size (or upper limit) of the virtual disk. Increase the default size to 8 GB. Use the folder icon to browse to a directory on disk with sufficient space to hold the virtual disk files. Remember that there will be a system disk of at least 8 GB and at least one data storage disk of at least 4 GB.
After making a selection and pressing Next, a summary of the configuration options chosen is shown. Use the Back button to return to a previous screen if any values need to be modified. Otherwise, click Finish to complete the wizard. The new virtual machine is listed in the left frame, as shown in the example in Figure 2.6.8.
Create the virtual disks to be used for storage. Click the Storage hyperlink in the right frame to access the storage screen seen in Figure 2.6.9.
Click the Add Attachment button, select Add Hard Disk from the pop-up menu, then click the Create New Disk button. This launches the Create New Virtual Hard Drive Wizard (seen in Figure 2.6.5 and 2.6.6). This disk will be used for storage, so create a size appropriate to your needs, making sure that it is at least 4 GB. To practice with RAID configurations, create as many virtual disks as needed. Two disks can be created on each IDE controller. For additional disks, click the Add Controller button to create another controller for attaching additional disks.
Create a device for the installation media. Highlight the word “Empty”, then click the CD icon as shown in Figure 2.6.10.
Click Choose a virtual CD/DVD disk file… to browse to
the location of the
.iso file. If the
.iso was burned
to CD, select the detected Host Drive.
Depending on the extensions available in the host CPU, it might not be
possible to boot the VM from
“your CPU does not support long mode” is shown when trying to boot
.iso, the host CPU either does not have the required
extension or AMD-V/VT-x is disabled in the system BIOS.
If you receive a kernel panic when booting into the ISO, stop the virtual machine. Then, go to System and check the box Enable IO APIC.
To configure the network adapter, go to Attached to drop-down menu select Bridged Adapter, then choose the name of the physical interface from the Name drop-down menu. In the example shown in Figure 2.6.11, the Intel Pro/1000 Ethernet card is attached to the network and has a device name of em0.. In the
After configuration is complete, click the Start arrow and
install FreeNAS® as described in Performing the Installation. Once
FreeNAS® is installed, press
F12 when the VM starts to boot to
access the boot menu. Select the primary hard disk as the boot option.
You can permanently boot from disk by removing the CD/DVD
device in Storage or by unchecking CD/DVD-ROM
in the Boot Order section of System.
2.6.2. VMware ESXi¶
Before using ESXi, read this post for an explanation of why iSCSI will be faster than NFS.
ESXi is a bare-metal hypervisor architecture created by VMware Inc. Commercial and free versions of the VMware vSphere Hypervisor operating system (ESXi) are available from the VMware website. After the operating system is installed on supported hardware, use a web browser to connect to its IP address. The welcome screen provides a link to download the VMware vSphere client which is used to create and manage virtual machines.
Once the VMware vSphere client is installed, use it to connect to the ESXi server. To create a new virtual machine, click Figure 2.6.12.. The New Virtual Machine Wizard will launch as shown in
Click Next and enter a name for the virtual machine. Click Next and highlight a datastore. An example is shown in Figure 2.6.13. Click Next. In the screen shown in Figure 2.6.14, click Other, then select a FreeBSD 64-bit architecture.
Click Next and create a virtual disk file of 8 GB to hold the FreeNAS® operating system, as shown in Figure 2.6.15.
Click Next and Finish. The new virtual machine is listed in the left frame. Right-click the virtual machine and select Edit Settings to access the screen shown in Figure 2.6.16.
Increase the Memory Configuration to at least 8192 MB.
To create a storage disk, click Device Type menu, highlight Hard Disk and click Next. Select Create a new virtual disk and click Next. In the screen shown in Figure 2.6.17, select the size of the disk. To dynamically allocate space as needed, check the box Allocate and commit space on demand (Thin Provisioning). Click Next, then Next, then Finish to create the disk. Repeat to create the amount of storage disks needed to meet your requirements.. In the
For ESX 5.0, Workstation 8.0, or Fusion 4.0 or higher, additional configuration is needed so that the virtual HPET setting does not prevent the virtual machine from booting.
If you are running ESX, while in Edit Settings, click . Change hpet0.present from true to false, then click OK twice to save the setting.
For Workstation or Player, while in Edit Settings,
Locate the path for the Configuration file named
Open that file in a text editor, change hpet0.present from
true to false, and save the change.