Existing users have already jumped over all the hurdles to install TrueNAS. They can keep using their proven/familiar techniques.
Our focus is on enabling more future users by reducing the hurdles:
No IPMI needed
No keyboard and monitor needed
No certificate management
No email/POP server needed
No TrueCommand set-up needed for monitoring
No VPN needed for remote status monitoring
WebUI not CLI
We agree that the USB creation is still an annoying step needed. We’d like to improve this, but it’s more difficult because of the diversity of client software and OS versions.
Do you honestly think anyone–anyone at all–cares that the installation be accomplished via a web UI? I can easily understand wanting a graphical installation, and to a lesser extent wanting a headless installation–though the latter really is an edge case, I think. But web-based? I’ve asked several times now, but you (plural) have been unable or unwilling to answer: who wants this? Especially, who wants this in significant numbers?
The biggest of those hurdles by observation of this forum is properly creating the bootable installer.[1] TN Connect does nothing at all to address this. The second-biggest–and it’s a distant second–is hitting the space bar to select the installation target. The installer isn’t pretty, but it isn’t like it’s hard to use.
Sure, if you want a URL like https://192-168-1-176.cr49fa5fij885c9jhncnkquoin20d23t52an3ug.l226e8evc5ldjcspgcppqt378sj9n4btef62ojo.truenas.direct. You took a page from Plex’s playbook, several years after the fact–better late than never, I guess (and like them, you require a subscription to your web service to use it, and given their recent history, that isn’t a favorable comparison). If you want a URL you might actually remember, you’re back to where you were in 25.04 and before, except that “create your own certificate” is no longer an option because you’ve removed it.
And, of course, the certificate isn’t used for the core, file-sharing functions of the NAS.
…and you’d never need to get into the “BIOS” (or as HPE more accurately calls it, the ROM-based setup utility), of course. You’d never need to alter the boot order. BIOS defaults for virtualization, VT-d, bifurcation, etc., wouldn’t need to be checked.
Sure, some systems truly are headless. It’s nice to have an option to install on those. It’d be nicer yet if that option didn’t depend on your service that’s quite expensive for anything more than the barest minimums. But I can’t imagine this represents more than the tiniest of fractions of installations.
Really, you have two client OSs to deal with: Windows and *nix.
I haven’t found this to be difficult, but it’s the most-common issue I see here. ↩︎
I encountered a failure during upgrade from 25.04 to 25.10.
I must admit I have a special setup, my TrueNAS system is running on a HP MicroServer 8, this needs to have a bootable USB drive in order to make all four HD locations available to the vdev.
If anyone with a similar setup encounteres the error I was seeing, and can’t find a viable solution like I was struggeling to locate, now my solution should be searchable through this submission.
The issue I was seeing was that the boot from this USB bootable flash drive after upgrading resulted in a grub error.
grub grub_disk_native_sectors not found
This landed me in grub rescue mode, whatever I tried to do to gain access with any load/init command from the grub rescue resulted in this error.
I knew the underlying system should be 100% functioning and it was “only” an error in how grub was accessing the /boot location, so I needed to recreate the grub.
My final solution was to fetch Super Grub2 and create a bootable USB drive from that, once booted from it I selected to search for bootable systems.
After a while it ended with showing a possible “TrueNAS 25.10” boot selection.
Once selected it booted fine into TrueNAS 25.10, then I selected to be droped into a Linux CLI, once there I confirmed which disk was my bootable USB drive, and ran the command
/sbin/grub-install /dev/xxx
I exchanged the “xxx” for the drive location of my USB.
After this there were no issues booting into TrueNAS 25.10
Facts. I always wait until after several point releases before upgrading to a new major release version. That is way I’m still on macOS 15 even though 26 has been out for months. I want them to release a few patches before I upgrade.
Yeah…I’ll give it a whirl, Shirl. But this is all getting OT on the 25.10 release, so happy to discuss the merits or otherwise elsewhere. But just wanted to point out there’s at least someone - anyone at all - who is interested, since you asked.
I have upgraded two servers yesterday. It went well, but this afternoon one of them rebooted for no apparent reason. It never happened before; this server has been in service for 1.5 year.
Currently, I suspect the following factors may cause the abnormal restart: containers using libtorrent 2.0(such as qBittorrent), OpenWrt virtual machines, and starting a new process that consumes a lot of resources when the system’s CPU and memory usage are high.
Is anyone else experiencing SMB sharing issues after 25.10? I’ve had instances where I open up a directory in Windows 11 and either get a blank or incomplete file list.
Did you check for memory errors using e.g. memtestx86+ ? Just asking cause i found errors on my DXP 6800 plus when both memory slots were being used. Usually errors started showing up on test 5. Effects were errors on zfs checksums (which showed up in scubs) and reboots without any hints in any log. But the 6800 uses an i5 so it might not help. Fix was to either to use 1 memory slot, turn of CPU boost completely or tune down boosting to 4000 Mhz from 4400 Mhz in bios. You get into Ugreen Bios by ctrl+f12 and inside bios ctrl+f1 to allow access to all settings, if i remember it right…
