TrueNAS 26 Nightlies Emerge!

It’s happening — we’re switching to TrueNAS 26 nightly builds tonight!

If you’re on a recent 26.04 Nightly, you’re good to go — updates will just keep rolling in as normal.

If you’re on an older 26.04 Nightly, you might get a message saying your system is newer than the available update. If that happens, just grab a recent update file and use manual update to upgrade to a newer nightly, and you’ll be back on track.

Chris and Kris talked about this change coming — catch up here if you missed it: https://www.youtube.com/watch?v=z8HEdSU5OBw

8 Likes

Is TrueNAS 26 expected to support secure boot?

Just updated Test system on a VM running Nightly 26.04.0-MASTER-20260204-020154
Update went through aok to 26.0.0-MASTER-20260226-020147

Uneventful so to speak. Only a test system for playing with raidz2 for special vdev here.

3 Likes

Interesting. I had the same nightly but got the message for newer version & had to use manual update.

I am on “26.0.0-MASTER-20260225-114041” and simply got “System is up to date!”. No indication of available updates.

Regarding .update file, is it ok to simply extract it from the .iso? It’s not provided by https://download.truenas.com/TrueNAS-26-Nightlies/

Do you have an earlier boot environment to use? I booted back to 20250223 and the update works from that.

That’s how you would typically do the manual update, extract the .update file and update

So firstly, noted there was an issue on the first build pushed for 26, with a path to the updates being incorrect. I’ve adjusted the infrastructure side, so you should now see an update available that will resolve this issue going forward.

If you need to download an update, to install manually, please use https://update-public.sys.truenas.net/

Thanks for the reports!

It’s in process, but relies on external approvals which may not be available in time.

What is you use-case for needing this?

I forget where I saw that TrueNAS was waiting for Microsoft shim signing.

In other words, TrueNAS distribution method is very suitable for using Secure Boot to prevent system files from being tampered with.

1 Like

M$ control approval for secure boot makes me not wat to use secure boot​:rofl:

4 Likes

As long as I can continue to use and upgrade TN with Secure Boot disabled, without having to change anything in my workflow, I’m don’t really mind the new functionality.

If instead I suddenly get a bad shim error after an update, I will be very nonplussed.

2 Likes

Why exactly not? Details?

You do know that it is a REQUIREMENT for any big corporation or government, right!?

MS invented it. Many ignorant Linux wannabes trashed it and now that Ubuntu implemented it, they changed their groupie minds…

well then you can persuade all the motherboard manufacturers to include additional root certs, any OS vendor is free to do that

you are also free to build your own OS build and create your own certs, sign your build and add that to your motherboads certs

Compiling your own UEFI bios with Secure Boot

there is no lockin here to microsoft, its just way easier to have MS sign an OS root cert than manage it all oneself

also M$? are you like 13 and from a decade ago? rofl

and lastly no one is forcing or requiring you use secure boot, so whats the issue, none thats right, if you want a less secure machine, go for it, no one is stopping you.

Seems my response has upset some people & I’m not sure why.

And MS becomes the gatekeeper of who and what is allowed. Seems like unethical business practice, but working in both entities, I’ve seen the game played many times. Requirements doesn’t always equate to better security.

You’re just enforcing the point of my comment, but see my statement above. M$ becomes the gatekeeper in partnership with key entities that forces central management = M$$$$.

you should reflect on that a bit and you find your answer

utter uninformed and simplistic garbage. and nice job moving the goal posts, this is about truenas and their choice to support secure boot, a good choice irrespective of any the points you mention, as i said YOU dont have to use it and if you can provide a better and cheaper way to the ISVs and mobo manufacturers for a root cert you can do that - no one is forcing anyone to do anything here

and you think at S and TS levels all gove entities use the standards certs on their hardware, cute

I know the answer, I’m just being courteous. You’re too emotionally vested and being way too defensive. I not stating there aren’t benefits to secure boot, but there are also areas of concern. Again, you are making my point, if TN wishes to enter into corp or gov, they must get approval through the one gatekeeper.