01
Confirm the TrueNAS edition and image
Tungsto lists TrueNAS without naming a release or edition. Selection records the intended OS, not completed imaging. Confirm Community or Enterprise edition, architecture, checksum, boot mode, update path, licensing, and support.
Use the TrueNAS product and version selector because development and stable instructions differ. Enterprise features and vendor support are not included unless a quote states otherwise.
02
Verify memory, controllers, and disk visibility
TrueNAS publishes x86-64 guidance for memory, boot devices, controllers, disks, and networking. It strongly recommends ECC as another integrity defense, but ECC does not replace redundancy or backup. Verify the exact Tungsto configuration.
ZFS should receive individual disks. TrueNAS recommends HBA, passthrough, or JBOD-style exposure instead of a hardware RAID virtual disk. Confirm controller mode, disk visibility, SMART access, and boot targets.
03
Treat installation as a destructive, queued workflow
The official installer erases the selected drive. Keep the boot target separate from data disks, record device identities, and keep configuration and data copies off-server. For custom media, verify publisher, URL, size, architecture, and checksum.
Accepted, Provisioning, or Queued confirms a recorded request, not an installed or reachable system. A KVM request does not create a console session. After explicit completion, verify release, boot pool, interfaces, and access before creating a data pool.
04
Design the ZFS pool and recovery path before storing data
Choose vdev width, redundancy, capacity, spares, datasets, shares, and encryption for the workload and recovery objective. Raw capacity is not usable capacity; redundancy does not protect against deletion, ransomware, operator error, or site incidents.
Configure monitoring, scrubs, snapshots, configuration export, and independent backup, then test restoration. One host is not high availability. Tungsto does not manage pools, shares, replication, encryption keys, or failover.
05
Separate OS compatibility from storage-server rental
This page covers TrueNAS installation. The storage-server page covers drive count, raw capacity, memory, network, price, and alternatives. Confirm that the controller exposes disks correctly and that boot devices remain outside the data pool.
After delivery, you operate updates, accounts, network configuration, shares, permissions, pool health, alerts, snapshots, backups, and restores. Do not expose the management interface publicly without suitable access controls, and preserve a recovery path before changing network or storage settings remotely.
Direct answers
Questions before you order
Is TrueNAS installed as soon as I select it?
No. The selection records the requested OS. Accepted, Provisioning, or Queued does not confirm imaging or delivery. Verify the installed release and disk layout after explicit completion.
Should ZFS run behind hardware RAID?
Generally no. TrueNAS recommends direct disk exposure through an HBA, passthrough, or JBOD-style mode. Confirm controller behavior before ordering or creating a pool.
Is TrueNAS Enterprise licensing or support included?
Not unless a quote explicitly says so. Confirm the offered edition, its license, compatible hardware, update channel, and vendor-support entitlement before installation.