Installing and Upgrading FreeNAS. In other words, you can not install FreeNAS® into the same USB stick that you boot the installer from. After installation.

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: • • • • • •. Note FreeNAS ® requires 64-bit hardware. The download page contains these types of files: •.iso: this is a bootable installer that can be written to either a CD or USB flash as described in. •.GUI_Upgrade.txz: this is a compressed firmware upgrade image. To upgrade FreeNAS ®, download this file and see the section on. Each file has an associated sha256.txt file which should be 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 sha256 name_of_file • on a Linux system use the command sha256sum name_of_file • on a Mac system use the command shasum -a 256 name_of_file • Windows or Mac users can install additional utilities like or The value produced by running the command must match the value shown in the sha256.txt file. Checksum values that do not match indicate a corrupted installer file that should not be used. Note 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. Dd if=FreeNAS-9.10-RELEASE-x64.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/sd X, 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. On OS X Insert the USB thumb drive. In the Finder, go to Applications → Utilities → Disk Utility. 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 Free space when creating the partition works fine.

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, the USB thumb drive is /dev/disk1, which is first unmounted. The dd command uses /dev/rdisk1 (note the extra r) to write to the raw device, which is faster. When running these commands, substitute the name of the installation file and the correct path to the USB thumb drive.

Note If the error “Resource busy” is shown when the dd command is run, go to Applications → Utilities → Disk Utility, 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-9.10-RELEASE-x64.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. Note 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. Wait for the menu to time out or press Enter to boot into the installer. After the media boots, the console setup menu is displayed as shown in. 2.3.3 Selecting the Install Drive Use the arrow keys to highlight the destination USB drive, SSD, DOM (Disk on Module), Compact Flash device, 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, press 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. Note 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. Note 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. BIOS booting is recommended for legacy and enterprise hardware.

UEFI is used on newer consumer motherboards. 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. 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. 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!

Upgrading 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 9.10.2.

After 9.10.2 has been installed, use the instructions in to keep the system updated. Caveats: Be aware of these caveats before attempting an upgrade to 9.10.2: • 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, you will need to create a ZFS volume using other disks after the upgrade, then use the instructions in to mount the UFS-formatted disk to 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, you will not be able to import that data to the ZFS volume.

Instead, back up that data before the upgrade, create a ZFS volume after the upgrade, then restore the data from backup. • The will not recognize an encrypted ZFS pool. If the ZFS pool is GELI-encrypted and the starts after the upgrade, cancel the and use the instructions in to import the encrypted volume. The can be run afterwards to use it for post-configuration, and it will recognize that the volume has been imported and will not prompt to reformat the disks.

• DO NOT upgrade the ZFS pool unless you are absolutely sure that you will never want to go back to the previous version. For this reason, the update process will not automatically upgrade the ZFS pool, though the system shows when newer feature flags are available for the pool. Unless you need a new feature flag, it is safe to leave the ZFS pool at its current version and uncheck the alert. If you do decide to upgrade the pool, you will not be able to boot into a previous version that does not support the newer feature flags.

• The mps driver for 6 G Avago SAS HBAs is version 21, which requires phase 20 firmware on the controller and the mpr driver for 12 G Avago SAS HBAs is version 13 which requires P12 firmware. It is recommended to upgrade the firmware before installing FreeNAS ® or immediately after upgrading FreeNAS ®, using the instructions in. Download Free Play Red Code 3 Hacked Software Codes there.

Running older firmware can cause many woes, including the failure to probe all of the attached disks, which can lead to degraded or unavailable arrays. While you can mismatch your firmware version with a higher version and things will “probably still work”, there are no guarantees as that driver and firmware combination is untested.

• If upgrading from 9.3.x, please read the first. Initial Preparation Before upgrading the operating system, perform the following steps: • Back up the FreeNAS ® configuration in System → General → Save Config. • 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 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 Services → Control Services. Warning 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, use System → Boot to 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. 2.5.2 Install in New Boot Environment or Format 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. The database file that is preserved and migrated contains your FreeNAS ® configuration settings. 2.5.3 Preserve and Migrate Settings Press 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 Settings → General and use the Upload Config button to upload the configuration that you saved before starting the upgrade.

If Something Goes Wrong If an update fails, an alert is issued and the details are written to /data/update.failed. 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, the first boot menu entry, FreeNAS (default), refers to the initial installation, before the update was applied. The second boot entry, FreeNAS-, 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. 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 your 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. It is not necessary to upgrade the pool if you do not need newer feature flags or if you want to keep the possibility of reverting to an earlier version of FreeNAS ® or repurposing the disks in another operating system that supports ZFS.

If you decide to upgrade the pool 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 Storage → Volumes → View Volumes and highlight the volume (ZFS pool) to upgrade.

Click the Upgrade button as shown in. Virtualization 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. If you decide to use FreeNAS ® within a virtual environment, 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. 2.6.7 Select File Name and Size of Virtual Disk 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. 2.6.9 Storage Settings of the Virtual Machine 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 and ). 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. VMware ESXi Before using ESXi, read for an explanation of why iSCSI will be faster than NFS. ESXi is 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.

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 File → New → Virtual Machine.

The New Virtual Machine Wizard will launch as shown in. 2.6.16 Virtual Machine Settings Increase the Memory Configuration to at least 8192 MB. To create a storage disk, click Hard disk 1 → Add. In the Device Type menu, highlight Hard Disk and click Next. Select Create a new virtual disk and click Next. In the screen shown in, 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.

2.6.17 Creating a Storage Disk 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 Options → Advanced → General → Configuration Parameters. Change hpet0.present from true to false, then click OK twice to save the setting.

For Workstation or Player, while in Edit Settings, click Options → Advanced → File Locations. Locate the path for the Configuration file named filename.vmx.

Open that file in a text editor, change hpet0.present from true to false, and save the change.