Installing TrueNAS

23 minute read.

Last Modified 2025-04-25 15:14 EDT

After you download the .iso file, you can start installing TrueNAS!

This article describes verifying the .iso file, then installing TrueNAS using that file, and selecting the type of installation as either on physical hardware or a virtual machine (VM).

TrueNAS Enterprise
TrueNAS Enterprise customers should receive their systems already installed and ready for UI configuration. If any issues require you to install or re-install TrueNAS, contact TrueNAS Enterprise Support for assistance.
Enterprise customers with High Availability (HA) systems should not attempt to re-install their systems on their own. The dual controller install process is complicated and the risk of causing serious network issues is high. Contact TrueNAS Enterprise Support for assistance!
Contacting Support
Customers who purchase TrueNAS hardware or that want additional support must have a support contract to use TrueNAS Support Services. The TrueNAS Community forums provides free support for users without a TrueNAS Support contract.
TrueNAS Customer Support
Support Portal https://support.ixsystems.com
Email support@ixsystems.com
Telephone and Other Resources https://www.ixsystems.com/support/

TrueNAS Customer Support
Support Portal	https://support.ixsystems.com
Email	support@ixsystems.com
Telephone and Other Resources	https://www.ixsystems.com/support/

ISO Verification

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

Performing PGP ISO Verification

You need an OpenPGP encryption application for this method of ISO verification.

Click here for the verification process.

Obtain an OpenPGP encryption application to use. There are many free applications available. 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-scale/, expand the Security option, and click PGP Signature to download the Gnu Privacy Guard signature file. This file can be a (.gpg) or a (.sig) file. 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 the .iso.gpg or .iso.sig download location and import the public key using the keyserver address and search results string:

user@ubuntu /tmp> gpg --keyserver keys.gnupg.net --recv-keys 0xc8d62def767c1db0dff4e6ec358eaa9112cf7946
gpg: DBG: Using CREATE_BREAKAWAY_FROM_JOB flag
gpg: key 358EAA9112CF7946: public key "IX SecTeam <security-officer@ixsystems.com>" imported
gpg: DBG: Using CREATE_BREAKAWAY_FROM_JOB flag
gpg: Total number processed: 1
gpg:               imported: 1
user@ubuntu /tmp>

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

user@ubuntu /tmp>  gpg --verify TrueNAS-SCALE-21.04-ALPHA.1.iso
gpg: Signature made Thu May 27 10:49:02 2021 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
user@ubuntu /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 is issued for IX SecTeam <security-officer@ixsystems.com> (iX Security Team) on October 15, 2019, and is signed by an iXsystems account.

Using SHA256 Verification

SHA256 verification uses the checksum to validate/verify the file.

Click here for the verification process.

The command to verify the checksum varies by operating system:

BSD: use command sha256 isofile
Linux: use command sha256sum isofile
Mac: use command shasum -a 256 isofile

Freeware or online checksum utilities are available for Windows users.

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.

Installing TrueNAS

You can install TrueNAS on either physical hardware or a virtual machine.

Before starting the update process, confirm that the system storage has enough space to handle the update. The update stops if there is insufficient space to complete.

Installing on Physical Hardware

TrueNAS is flexible and can run on any x86_64 compatible (Intel or AMD) processor. TrueNAS requires at least 8GB of RAM (more is better) and a 20GB Boot Device.

Preparing the Install File

Physical hardware requires burning the TrueNAS installer to a device, typically a CD or removable USB device. This device is temporarily attached to the system to install TrueNAS to the system permanent boot device.

Writing the TrueNAS installer to a USB stick on Linux

To write the TrueNAS installer to a USB stick on Linux, plug the USB stick into the system and open a terminal.

Start by making sure the USB stick connection path is correct. There are many ways to do this in Linux, but a quick option is to enter the command lsblk -po +vendor,model and note the path to the USB stick. This shows in the NAME column of the lsblk output.

Next, use the dd command to write the installer to the USB stick.

Be very careful when using dd, as choosing the wrong of= device path can result in irretrievable data loss!

Enter this command dd status=progress if=path/to/.iso of=path/to/USB in the CLI.

If this results in a permission denied error, use the command sudo dd with the same parameters and enter the administrator password.

TrueNAS allows using other methods to create boot media such as:

Ventoy for Windows and Linux operating systems
TINU for MacOS Operating systems
DiskMaker X for MacOS
Rufus for Windows and Linux operating systems, or by creating a Windows VM in your Mac
Universal USB Installer (UUI) similar to Rufus
Your Universal Multiboot Installer (YUMI) for multiple operating systems
MultiBootUSB for Windows, Linux operating systems

The following sections provide more information on a few of these options.

Using Ventoy

Ventoy is an open-source tool TrueNAS users can use when creating a bootable USB or other local drive for an ISO image file when installing TrueNAS. After installing Ventoy on a USB or local drive, users can copy the install media multiple times onto this same device with the Ventoy executable file. Ventoy provides a directory tree that allows users to browse to or select the iso .

How does Ventoy work?

The Ventoy executable, Ventoy2Disk.exe, is installed on a device such as a USB drive or a local drive. The Ventoy executable creates partitions formatted with the exFAT file system on the device. It creates a master boot record (MBR) layout on the disk.

The default MBR layout consists of a minimum of three partitions:

Part 1 - Main partition of 32 GB to 33 MB for the ISO or other file types.
Part 2 - EFI system partition (ESP) of 32 MB, for the EFI boot and to hold the Ventoy files.
Part 3 - MBR and gap partition of 1 MB, to hold the bootloader in Legacy BIOS system.

Ventoy 1.0.14, allows preserving 2 GB of space at the bottom of the disk where users can create part 3 or 4 during the Ventoy installation process. To create this space in Windows, use the Option > Partition Configuration option. In Linux, use the -r tag with the Ventoy install string.

Ventoy offers several ways to install their executables and to create bootable media. Always use the default method but if you experience issues, try these alternatives to the default mode:

Default Ventoy2Disk.exe, to create bootable media on a USB drive

Alternative methods:

Ventoy LiveCD for Windows
Ventoy Vlnk for Windows and Linux
Ventoy Memdisk mode for Windows and Linux
Ventoy Grub2 mode for Linux

Ventoy2Disk.exe Installations

To install Ventoy on a USB drive, download the installation package. After extracting the Ventoy2Disk.exe file, run it. If using Windows GUI mode, select the device and click Install or Update when updating Ventoy on the drive to a later release.

Ventoy allows using Windows CLI to install the executable file. Refer to Ventoy documentation for more information. After installing Ventoy on the USB drive, copy the TrueNAS iso to the USB. When updating to a new TrueNAS release or clean-installing from an iso, copy the new iso to the USB with Ventoy installed.

Ventoy writes data to a USB drive during the installation and upgrades to the installed version. It writes directly to the physical sector and modifies the MBR and partition table. Because of this, Windows systems might experience failures when using the Ventoy2Disk.exe executable to install Ventoy even after several retry attempts of unplugging and reinserting the USB does not resolve the issue.

Linux systems that use the dd command do not experience the failures instances in Windows installations.

Why does Ventoy fail this way in Windows systems? Ventoy relies on modifying the MBR and partition table during installation, but Windows restrictions on modifying these components impact this operation. The process Ventoy uses can be easily affected by other programs such as anti-virus software, system active protection processes, and others.

Ventoy provides two methods to get around the Windows system issue:

Creating a vtsi file
Using LiveCD

Creating a VTSI File

Enable Option > Generate VTSI File and click Install in the Ventoy UI to create a VentoySparseImg.vtsi file instead of writing to the disk. After creating this file, use Rufus (3.15 or greater) to write the vtsi file to the disk to complete the installation of Ventoy. This requires only selecting the corresponding disk and the vtsi file and leaving the other options in Rufus set to default values.

Rufus only supports USB or removable HDD with a USB interface. A local HDD is not supported. To use the removable HDD pres Alt+F to show the drive option.

The vtsi file can only be written to the corresponding disk but cannot be written to other disks.

Ventoy LiveCD Installations

Ventoy LiveCD is only for Windows users, and only necessary when the Ventoy2.Disk.exe fails to install or upgrade.

The Ventoy LiveCD option provides several options for installing the Ventoy executable and adding a TrueNAS iso.

Option 1 - Download Rufus and write VentoyLiveCD ISO to the USB drive.
Option 2 - Format the USB drive with FAT32 and extract the LiveCD files to the USB drive
Option 3 - Use VMWare to create a VM and add the USB drive as a disk in the VM

After installing Ventoy LiveCD to a device, copy the TrueNAS iso to the USB drive.

Option 1 requires downloading Rufus, then use Rufus to write the iso to the USB drive. After adding Ventoy LiveCD to the USB drive copy the TrueNAS release iso to the USB drive.

Insert the USB into a USB port on the TrueNAS server as described in the installation instructions.

Option 2 requires formatting the USB drive in FAT32 type by system command or third-party tool. In Windows systems, USB drives with large capacity might not have a FAT32 formatting option. In this case, create a small partition using diskpart and specifying a partition size of 4 GB, then format that partition with FAT32. After formatting the USB drive, extract the Ventoy LiveCD files to the USB drive.

Option 3 is the best option when installing an iso in a VM. It requires VMWare to create a VM with a default configuration, and then delete the default drive before adding the USB drive as a disk for the VM.

VentoyVlnk.exe Installation

Ventoy supports booting image files such as iso files from a local disk through Vlnks. A VLnk is a file link in Ventoy that is similar to a softlink that creates a pointer or shortcut to the iso location. Vlnks allow Ventoy to boot an image file such as an iso file stored on a local disk rather than copying that iso to the USB drive with Ventoy installed on it. This is particularly useful when dealing with large image files where there is limited space on the USB drive. it saves time and space on the USB drive.

Ventoy offers Windows and Linux methods to create Vlnks. In Windows, Use the VentoyVlnk.exe to generate the Vlnk file by selecting the image on the local disk. In Linux, run a script like VentoyVlnk.sh with a command like sudo bash VentoyVlnk.sh -vc path/to/image.iso to create the Vlnk file.

Vlnks can be used with Ventoy plugins, or like regular image files.

For TrueNAS, store the iso file on a local disk or network-connected drive apart from the USB drive where the VentoyVlnk.exe is installed. Using VentoyVlnk.ext installed on a USB drive, create the Vlnk and specify the path to the iso file location. Ventoy creates the Vlnk shortcut to the file (for example, filename.vlnk.iso) and location on the USB drive. Ventoy uses the Vlnk to locate and boot from the original image file at the local drive location. The TrueNAS system needs access to the location specified in the path, the local disk (or network disk) location.

If security requirements do not allow using Vlnks to a network disk, store the iso on a local disk on the TrueNAS server and create the Vlnk on the USB drive where VentoyVlnk.exe is installed.

Create a Vlnk file for the image file stored on a local disk. You can create the link file in the same directory as the VentoyVlnk.exe file. You cannot specify the name of the vlnk file created by the VentoyVlnk.exe but you can use command-line mode to change it by entering VentoyVlnk.exe -s. A prompt allows you to save the path after selecting the iso. Or use VentoyVlnk.ex -i filename.iso -o linkname.vlnk.iso to directly generate the Vlnk file; and no other interactions are nessesary.

Next copy the Vlnk file to the Ventoy USB and boot from it. You can put the Vlnk file in the root directory or a subdirectory.

Observe the rules in the Ventoy documentation for naming Vlnk files.

To resolve issues with booting files in a local disk, refer to Browse/Boot Files in Local Disk.

Memdisk Mode Installation

Ventoy Memdisk mode is an alternative to the default Ventoy mode when Legacy BIOS modes have problems. When booting, Ventoy normal mode only reads the iso file and just the content needed for boot. Ventoy Memdisk Mode loads the whole ISO image file into memory and boots it.

Activate Ventoy Memdisk mode by pressing Ctrl+d to switch from default to Memdisk mode. Press Ctrl+d again to return to default mode.

Only iso and some IMG files are supported. ISO file size is limited in Memdisk mode (usually less than 1 GB). TrueNAS iso files typically fall under the 1 GB upper limit.

To use Memdisk mode, after installing Ventoy2Disk.exe on a USB drive and copying the iso with one of the available methods, press Ctrl+d before selecting the iso file in the Ventoy boot menu. To return to default mode, press Ctrl+d again.

GRUB2 Installation

Ventoy GRUB2 mode is an alternative for booting Linux iso files, and supports Legacy BIOS and UEFI. It uses a different mechanism to boot an ISO file. It emulates the iso file as a CDROM to boot it. Ventoy GRUB2 is like booting a CD with an optical drive except the physical drive is not there.

The system motherboard firmware must support this, especially in UEFI mode. If the BIOS firmware is non-standard, Ventoy can have problems booting an ios file.

Only use GRUB2 mode if you experience problems with the default Ventoy mode. Ventoy GRUB2 can only be used to boot Linux iso files that contain a grub2 configuration file. TrueNAS iso files have a grub2 configuration file for booting that is required to use Ventoy GRUB2 mode.

To enter GRUB2 mode, press Ctrl+r. Press again to return to default mode.

Using Rufus

Rufus is a Windows program that allows you to create a bootable USB drive from an ISO file.

Rufus supports most Linux and Windows operating systems, including TrueNAS. For a list of supported ISO, see the Rufus non-exhaustive list.

How does Rufus work?

Rufus formats and erases all data from the USB drive. Transfer any files you want to keep off the drive before using Rufus.

Rufus usually auto-detects the USB drive, but you can manually select the drive in the Devices field of the Rufus UI. In most cases, the USB drive shows as No_Label.

Rufus allows selecting the iso file from a file browser.

To use Rufus on a Mac, create a Windows VM on your Mac, then create the bootable USB drive with Rufus.

To create a bootable USB with Rufus:

Download the package from the Rufus downloads page.
Open Rufus by double-clicking on Rufus. Downloaded files are in your Downloads folder.
Insert a USB drive in any free USB port on the system.
Locate and select the iso file to populate the Boot Selection field. Click SELECT and select the ISO file.
Check the settings and adjust any to suit your use case.
Enter a name for the volume Rufus creates in Volume Label.
Click START.

For more information on this tool, refer to Rufus documentation or the user guide.

Using TINU

TINU is an open-source tool to create bootable MacOS installers. It creates bootable MacOS installers capable of running Apple MacOS. The program uses a GU for the createinstallmedia executable found in any MacOS installer app. This allows you to easily create MacOS install media without using the command line or Disk Utility, and it detects and prevents the most common errors when creating bootable MacOS installers

Follow the instructions provided in the GUI to begin creating the bootable media.

This program works with every MacOS installer app with the creteinstallmedia executable inside its internal resources folder. The program does not require special preparation, requirements are:

A computer that runs MacOS X Yosemite or later
A drive or partition to turn into a MacOS installer, of at least 8 GB (some MacOS releases require 9 GB or 12 Gb)
A copy of a “.ap” MacOS/Mac OS x installer

To use:

Download a copy of the TINU app
Launch the program and follow the instructions in the GUI.

Installing From the Device Media

Before you begin:

Locate the hotkey defined by the manufacturer of your motherboard to use in this process.
Disable SecureBoot if your system supports it or set it to Other OS, so you can boot to the install media.

With the installer added to a device (CD or USB), install TrueNAS onto the desired system using the TrueNAS installer.

Insert the install media and restart or boot the system. At the motherboard splash screen, use the hotkey defined by your motherboard manufacturer to boot into the motherboard UEFI/BIOS.

Choose to boot in UEFI mode or legacy CSM/BIOS mode. When installing TrueNAS, make the matching choice for the installation. For Intel chipsets manufactured in 2020 or later, UEFI is likely the only option.

If your system supports SecureBoot, and you have not disabled it or set it to Other OS, do it now, so you can boot the install media.

Select the install device as the boot drive, exit, and restart the system. If the USB stick is not shown as a boot option, try a different USB slot. Slots available for boot differ by hardware. For optimal performance, consider using NVMe S.M.A.R.T. tests to ensure the reliability of your storage devices before installation.

Using the TrueNAS Installer

If you are doing a clean install from the TrueNAS .iso file as part of migrating from a different TrueNAS version, or to recover from a serious issue that requires you to re-install TrueNAS from the .iso, have your network configuration information ready to use after the installation completes. Also have your TrueNAS system configuration file and data backups handy, so you can recover your system settings and import your data into the recovered TrueNAS clean-install system.

After the system boots into the installer, follow these steps.

TrueNAS Installer Instructions

Select Install/Upgrade.
Figure 1: Console Setup Screen
Select the desired install drive.
Figure 2: Destination Media Screen
Select Yes to proceed with a clean installation of TrueNAS from the .iso. This erases the contents of the selected drive!
Figure 3: Install Warning Screen
Select option 1 Administrative user (truenas_admin) then OK to install TrueNAS and create the truenas_admin user account and password. TrueNAS has implemented an administrator login as a replacement for the root user login as a security hardening measure. The system retains root as a fallback, but it is no longer the default. The truenas_admin account has full control over TrueNAS and is used to log in to the web interface.
Set a strong password and protect it.
Figure 4: Authentication Method Screen
Next, enter a password for the new truenas_admin user.
Figure 5: Admin Password Screen
Select Yes at the Legacy Boot prompt to allow the system to boot via UEFI, or select No if your system hardware requires legacy BIOS boot. Press Enter to begin the installation.
Figure 6: Legacy Boot Screen
Select OK when the Installation Succeeded screen shows and press Enter to exit from the installer.

After following the installation steps, restart the system, and then remove the install media.

Troubleshooting

If the system does not boot into TrueNAS, there are several things you can check to resolve the situation:

Check the system BIOS for an option to change USB emulation from CD/DVD/floppy to hard drive. After making the change it still does not boot, check to see if the card/drive is UDMA compliant.
Check to see if the system BIOS supports UEFI with BIOS emulation. If not, check for an option to boot using legacy BIOS mode.

If the system starts to boot but hangs with this repeating 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 you burned the image 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!

Installing on a Virtual Machine

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

Minimum Virtual Machine Settings

Regardless of the virtualization application, use these minimum settings:

RAM: at least 8192MB (8GB)
DISKS: two virtual disks with at least 16GB, one for the operating system and boot environments, and at least one additional virtual disk for data storage.
NETWORK: Use NAT, bridged, or host-only depending on your host network configuration.

Networking Checks for VMWare

When installing TrueNAS in a VMWare VM, double-check the virtual switch and VMWare port group. A misconfigured virtual switch or VMWare port group can cause network connection errors for TrueNAS systems with additional applications installed inside the TrueNAS VM. Enable MAC spoofing and promiscuous mode on the switch first, and then the port group the VM is using.

If not using static IP addresses, configure your VM to use DHCP to assign IP addresses for seamless network connectivity.

Jail Networking

If you have installed TrueNAS in VMware, you need functional networking to create a jail.

For the jail to have functional networking, you have to change the VMware settings to allow Promiscuous, MAC address changes, and Forged Transmits.

Setting	Description
Promiscuous Mode	When enabled at the virtual switch level, objects defined within all portgroups can receive all incoming traffic on the vSwitch.
MAC Address Changes	When set to Accept, ESXi accepts requests to change the effective MAC address to a different address than the initial MAC address.
Forged Transmits	When set to Accept, ESXi does not compare source and effective MAC addresses.

Installing on a Generic Virtual Machine

The procedure for creating a TrueNAS VM is the same for most hypervisors.

Generic VM Installation Instructions

Create a new virtual machine as usual, taking note of the following:
- Point a bootable CD/DVD device in the virtual hardware to the TrueNAS installer image (this is usually an .iso).
- Configure the virtual network card to allow your network to reach it. Bridged mode is optimal, as it treats the network card as if it is plugged into a simple switch on the existing network.
- Identify the OS you plan to install on the VM. This is required by some products. The ideal option is Debian 11 64 bit. If not available, try options like Debian 11, Debian 64 bit, 64 bit OS, or other.
- Install in BIOS mode for VMWare hypervisors.
- Ensure the VM has sufficient memory and disk space. For TrueNAS set to at least 8 GB RAM and 20 GB disk space. Not all hypervisors allocate enough memory by default.
Boot the VM and install TrueNAS as usual.
After the installation completes, shut down the VM instead of restarting, and disconnect the CD/DVD from the VM before restarting the VM.
After restarting into TrueNAS, install VM tools if applicable for your VM, and if they exist for Debian 11, or ensure they loaded on boot.

Installing Using VMWare Player 15.5

This example describes installing TrueNAS using VMWare Player 15.5.

Installation Instructions

Open VMware Player and click Create a New Virtual Machine to enter the New Virtual Machine Wizard.

Install the disk image file.
Select the Installer disk image file (.iso) option, click Browse…, and upload the TrueNAS .iso downloaded earlier.
Name the virtual machine.
You can change the virtual machine name and location.
Specify the disk capacity.
Specify the maximum disk size for the initial disk. The default 20GB is enough for TrueNAS.
Next, select Store virtual disk as a single file.
Review the virtual machine configuration.
Review the virtual machine configuration before proceeding. By default, VMware Player does not set enough RAM for the virtual machine.
Click Customize Hardware… > Memory. Drag the slider up to 8GB and click Ok.
Power on the machine after creation if desired. Select Power on this virtual machine after creation.

Adding Virtual Disks

After installing TrueNAS on a virtual machine (VM), add virtual disks to the VM. You need a minimum of two disks, 16 GB each. One disk is for the boot environment the other for data storage.

Adding Virtual Disk Instructions

After creating the virtual machine, select it on 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 for 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.
Enter a name and choose 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.

Using the TrueNAS Installer

Just as with installing TrueNAS on physical hardware, complete the installation in the VM by booting into the TrueNAS installer.

Using the TrueNAS Installer in a Virtual Machine

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

Select Install/Upgrade.
Figure 7: Console Setup Screen
Select the desired install drive.
Figure 8: Destination Media Screen
Select Yes to proceed with a clean installation of TrueNAS from the .iso. This erases the contents of the selected drive!
Figure 9: Install Warning Screen
Select option 1 Administrative user (truenas_admin) then OK to install TrueNAS and create the truenas_admin user account and password. TrueNAS has implemented an administrator login as a replacement for the root user login as a security hardening measure. The system retains root as a fallback, but it is no longer the default. The truenas_admin account has full control over TrueNAS and is used to log in to the web interface.
Set a strong password and protect it.
Figure 10: Authentication Method Screen
Next, enter a password for the new truenas_admin user.
Figure 11: Admin Password Screen
Select Yes at the Legacy Boot prompt to allow the system to boot via UEFI, or select No if your system hardware requires legacy BIOS boot. Press Enter to begin the installation.
Figure 12: Legacy Boot Screen
Select OK when the Installation Succeeded screen shows and press Enter to exit from the installer.

After the TrueNAS installation completes, reboot the system. The Console Setup menu displays when the system boots successfully.

Congratulations, TrueNAS is now installed!

The next step is to configure TrueNAS network and general settings. Experienced users can use the Console Setup Menu to configure network settings, but if you are unfamiliar with the Console setup menu and how network configuration works, we recommend using the TrueNAS UI to configure settings. TrueNAS uses DHCP to assign an IP address to the primary system interface and displays it at the top of the Console Setup menu screen. Use this IP address to log into the web UI.

Use Cases

Industry

Support

Resources

Installing TrueNAS

ISO Verification

Performing PGP ISO Verification

Using SHA256 Verification

Installing TrueNAS

Installing on Physical Hardware

Preparing the Install File

Installing From the Device Media

Using the TrueNAS Installer

Installing on a Virtual Machine

Minimum Virtual Machine Settings

Networking Checks for VMWare

Installing on a Generic Virtual Machine

Installing Using VMWare Player 15.5

Adding Virtual Disks

Using the TrueNAS Installer

Related Content