Install

The iXsystems Security Team cryptographically signs TrueNAS ISO files so that users can verify the integrity of their downloaded file. This section demonstrates how to verify an ISO file using the Pretty Good Privacy (PGP) and SHA256 methods.

You need an OpenPGP encryption application for this method of ISO verification. There are many different free applications available, but the OpenPGP group provides a list of available software for different operating systems at https://www.openpgp.org/software/. The examples in this section show verifying the TrueNAS .iso using gnupg2 in a command prompt, but Gpg4win is also a good option for Windows users.

To verify the .iso source, go to https://www.truenas.com/download-tn-core/ , expand the Security option, and click PGP Signature to download the Gnu Privacy Guard (.gpg) signature file. You can download the PGP Public Key from either pgp.mit.edu (search for security-officer@ixsystems.com) or keys.openpgp.org.

Open the PGP Public key link and note the address in your browser and Search results for string.

Use one of the OpenPGP encryption tools mentioned above to import the public key and verify the PGP signature.

Go to the .iso and .iso.gpg download location and import the public key using the keyserver address and search results string:

q5sys@athena /tmp>  gpg --keyserver keys.openpgp.org --recv-keys 0xc8d62def767c1db0dff4e6ec358eaa9112cf7946
gpg: requesting key 12CF7946 from hkp server keys.openpgp.org
gpg: key 358EAA9112CF7946: "IX SecTeam <security-officer@ixsystems.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
q5sys@athena /tmp>

Use command gpg --verify to compare the .iso and .iso.gpg files:

q5sys@athena /tmp>  gpg --verify TrueNAS-12.0-BETA2.1.iso.gpg TrueNAS-12.0-BETA2.iso
gpg: Signature made Thu Aug 27 10:06:02 2020 EDT using RSA key ID 12CF7946
gpg: Good signature from "IX SecTeam <security-officer@ixsystems.com>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: C8D6 2DEF 767C 1DB0 DFF4  E6EC 358E AA91 12CF 7946
q5sys@athena /tmp>

This response means the signature is correct but still untrusted. Go back to the browser page that has the PGP Public key open and manually confirm that the key was issued for IX SecTeam <security-officer@ixsystems.com> (iX Security Team) on October 15, 2019 and is signed by an iXsystems account.

The command to verify the checksum varies by operating system:

• BSD: sha256 isofile
• Linux: sha256sum isofile
• Mac: shasum -a 256 isofile
• Windows or Mac users can install additional utilities like HashCalc or HashTab.

The value produced by running the command must match the value shown in the sha256.txt file. Different checksum values indicate a corrupted installer file that you should not use.

Physical hardware typically requires burning the TrueNAS installer to a physical device. In general a CD or removable USB device is used. This device is temporarily attached to the system to install TrueNAS to the system’s permanent boot device.

Headless, or remote, installation is possible when the system has IPMI available and can create a virtual media CD-ROM using a locally stored .iso.

The method of writing the installer to a device varies between operating systems. Click Windows or Linux to see instructions for your Operating System, or CD for generic CD burning guidance.

If the system does not boot into TrueNAS, there are several things you can check 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 does 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.
• If 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 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 fails as Windows does not understand the partition written from the image file. Be very careful to specify the correct USB stick when using a wipe utility!

Because TrueNAS is built and provided as an .iso file, it works on all virtual machine solutions (VMware, VirtualBox, Citrix Hypervisor, etc). This section demonstrates installing with VMware Workstation Player on Windows.

Regardless of virtualization application, use these minimum settings:

• RAM: at least 8192MB (8GB)
• DISKS: one virtual disk with at least 8GB for the operating system and boot environments and at least one additional virtual disk with at least 4GB to be used as data storage.
• NETWORK: Use NAT, Bridged, or Host-only depending on your host network configuration.

For most hypervisors, the procedure for creating a TrueNAS VM is the same:

1. Create a new Virtual Machine as usual, taking note of the following settings.
   • The virtual hardware has a bootable CD/DVD device pointed to the TrueNAS installer image (this is usually an .iso).
   • The virtual network card is configured so your network can reach it. bridged mode is optimal as this treats the network card as if it is plugged into a simple switch on the existing network.
   • Some products require identifying the OS installed on the VM. The ideal option is FreeBSD 12 64 bit. If this is not available, try options like FreeBSD 12, FreeBSD 64 bit, 64 bit OS, or Other. Do not choose a Windows or Linux related OS type.
   • For VMWare hypervisors, install in BIOS mode.
   • The VM has sufficient memory and disk space. TrueNAS needs at least 8 GB RAM and 20 GB disk space. Not all hypervisors allocate enough memory by default.
2. Boot the VM and install TrueNAS as usual.
3. After installation completes, shut down the VM instead of rebooting, and disconnect the CD/DVD from the VM before rebooting the VM.
4. After rebooting into TrueNAS, install VM tools if applicable for your VM, and if they exist for FreeBSD 12, or ensure they are loaded on boot.

After creating the virtual machine, select it from the virtual machine list and click Edit virtual machine settings. Click Add and select Hard Disk. Select SCSI as the virtual disk type. Select Create a new virtual disk. Specify the maximum size of this additional virtual disk. This disk stores data in TrueNAS. If desired, allocate the disk space immediately by setting Allocate all disk space now. Select *Store virtual disk as single file. Finally, name and chose a location for the new virtual disk.

Repeat this process until enough disks are available for TrueNAS to create ideal storage pools This depends on your specific TrueNAS use case. See Pool Creation for descriptions of the various pool (vdev) types and layouts

Select the virtual machine from the list and click Play virtual machine. The machine starts and boots into the TrueNAS installer. Select Install/Upgrade.

Select the desired disk for the boot environments.

Select Yes. This erases all contents on the disk!

Next, set a password for the TrueNAS administrative account, named root by default. This account has full control over TrueNAS and is used to log in to the web interface. Set a strong password and protect it.

Select Boot via BIOS.

After the TrueNAS installation is complete, reboot the system. The Console Setup Menu displays when the system boots successfully.