Readme updated today:

This repository is no longer actively maintained.  

The TrueNAS build system previously hosted here has been moved to an internal infrastructure. This transition was necessary to meet new security requirements, including support for Secure Boot and related platform integrity features that require tighter control over the build and signing pipeline.  

No further updates, pull requests, or issues will be accepted. Existing content is preserved here for historical reference only.  

https://github.com/truenas/scale-build

Wondering if this is just the first step towards doing a minio in the future.

all 51 comments

sorted by: hot top controversial new old
[–] 113 points 8 months ago* (11 children)

Always blaming security bullshit. I anxiously await a community fork.

Next step is requiring a subscription.

  • source
  • hideshow 11 child comments
  • [–] 64 points 8 months ago (10 children)

    Volker Theile (lead dev of FreeNAS 2006-2009) maintaines OpenMediaVault, based on debian, version 8 was released recently. Not a drop in replacement, and it has its own quirks, but no evil company in the background

  • source
  • parent
  • hideshow 10 child comments
  • [–] 3 points 8 months ago (8 children)
  • [–] 5 points 8 months ago (2 children)

    I question why this gets recommended so much when we discuss truenas.

    Without a doubt zfs is one of if not THE reason to go truenas. It does so much more for you than other filesystems.

    I guess OMV at least has btrfs but not the same thing.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 8 months ago (1 child)

    ZFS is in the omv extras repo: https://wiki.omv-extras.org/doku.php?id=omv8%3Aomv8_plugins%3Azfs

    As it's just plain debian under the hood you can use any basic debian stuff, e.g. I use zfs-auto-snapshot from apt, and the zfs plugin can list and manage the snapshots perfectly.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 8 months ago (3 children)

    I have it on my installation, you've got to replace the kernel with the proxmox one, it's fairly easily done by installing a plugin

  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 8 months ago* (last edited 8 months ago) (2 children)

    Since omv 7 it works with the default kernel, you can install the proxmox one though if you want that.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 8 months ago (1 child)

    Weird, some time ago it booted with the default kernel by mistake and it couldn't see my zfs pool

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 8 months ago

    From the docs:

    The Standard Debian Kernel (selectable) can be used for ZFS. However, since ZFS kernel modules are not installed in the Debian kernel by default, they must be built by the ZFS plugin when it is installed. While this process works, building the modules is a long process that requires continuous access to online repos. Accordingly, the potential for a build error exists. For this reason, while the Standard Kernel is very usable for ZFS, it is not ideal.

  • source
  • parent
  • [–] 48 points 8 months ago

    XigmaNAS is still being developed and is a fork of the original FreeNAS code before iX acquired the name.

    There are alternatives

  • source
  • [–] 65 points 8 months ago (2 children)

    I found a post on the forum:

    https://forums.truenas.com/t/scale-build-git-repo-going-closed-source/64313

    This is only their old build system which they weren't using themselves, the rest of the OS will remain open source. However they also said some worrying stuff about including "proprietary pieces of the OS".

  • source
  • hideshow 2 child comments
  • [–] [S] 7 points 8 months ago*

    In a years time will the public be able to build trueNAS for themselves without developing their own build tools?

    If not then the TrueNAS is no longer Open Source as people can't practically build it for themselves

    (or verify that during the build some code wasn't injected)

  • source
  • parent
  • [–] 40 points 8 months ago (7 children)

    Truenas went to shit when they killed BSD support, the OS it was founded on

  • source
  • hideshow 7 child comments
  • [–] 11 points 8 months ago* (5 children)

    I ordered a TrueNAS system from iXsystems a few years ago, and the reasoning they gave me is that Linux has better driver support, especially for home users.

    Whether that was actually the reason, I have no clue. But that’s what they said.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 12 points 8 months ago (4 children)

    The reason they gave me is people can run apps with docker on Linux, and docker isn't compatible with FreeBSD jails...

  • source
  • parent
  • hideshow 4 child comments
  • [–] 12 points 8 months ago (3 children)

    And yet they went with K3s at first, a crappy implementation at that, and refused to even consider adding Docker for like a year, then suddenly it became super important to replace their k3s stack with docker in the next release, barely giving people 2-3 months to get all their apps updated.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 5 points 8 months ago (1 child)

    Not only that but there wasn't even a notification on the dashboard for me after updating the OS that k3s were being replaced, I found out after updating when my apps wouldn't work. When did I update? About 2 weeks after the migration deadline. Had to rebuild my Plex, Jellyfin and Immich apps.

    Don't get me wrong, I don't like notifications from the OS developer in my system, but that would've been a great heads up and a worthy exception. "Hey migrate your apps now or your shit will break" would've worked.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 8 months ago*

    They are very hostile to users and I moved to a pure FreeBSD self managed storage and deployment solution

    TrueNAS doesn't add anything to ZFS or what the OS can do. There's a couple graphs and reporting features but the rest just adds more work

  • source
  • parent
  • [–] 17 points 8 months ago

    Odd choice of timing… I wonder if they are sitting on a cache of hard drives.

  • source
  • [–] 12 points 8 months ago

    Oh so they are going to use the Puppet excuse to move away from open source?

    we must move to have our code internal only for now. Totally just for security reasons nothing to do with us also changing licensing to make it harder for those building things for us

    no don't bring up the security incident we're referring to that shows us as the issue not having code visible! (ie they cheaped out on people/set up and vendor had keys visible)

  • source
  • [–] 10 points 8 months ago (1 child)

    Damn man. Technology kinda fucking sucks now. Everything I use is imploding in on itself. Yay!

  • source
  • hideshow 1 child comment
  • [–] 8 points 8 months ago

    Why are they always coming up with some kind of bullshit excuse? :D

  • source
  • [–] 26 points 8 months ago (7 children)

    Security through obscurity isn't security.

    There goes my excuse for not giving up and just paying for Unraid.

  • source
  • hideshow 7 child comments
  • [–] 17 points 8 months ago (5 children)

    Unraid pay system switch made me never want to use them

  • source
  • parent
  • hideshow 5 child comments
  • [–] 7 points 8 months ago (4 children)

    you can always just bypass their security.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 7 points 8 months ago (3 children)
  • [–] 4 points 8 months ago (2 children)

    Unraid uses a pretty whacky "license" checking system. There's cracks for it out there that hook into the core license system and use it to generate a valid one for the current version.

    One key note is that you HAVE to update the crack before updating Unraid itself.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 13 points 8 months ago* (7 children)

    Are they lying about secure boot being a reason or can I go back to thinking SB is part of Microsoft's EEE attack on software freedom?

  • source
  • hideshow 7 child comments
  • [–] 16 points 8 months ago*

    @tabular @Ek-Hou-Van-Braai They are lying. Debian supports Secure Boot and remains open.Although "related platform integrity" stuff might be something they're being forced to include by a government agency or paid to include by another company.

  • source
  • parent
  • [–] 9 points 8 months ago (5 children)

    It can be a bit of both.

    I don't think secureboot is an attack on freedom exactly (and it's certainly not an instance of EEE), but I definitely think it shouldn't be Microsoft holding the keys.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 8 points 8 months ago (4 children)

    Literally today Chris Titus released a video where he emphasized that no one should be using secure boot because the default backend is Microsoft and no one changes their secure boot config.

    If that's true there's an argument that the name "secure boot" is hardly detachable from the defaults and thus that name is kid of burnt and shouldn't be recommended out of an abundance of caution for new users.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 8 months ago (2 children)

    Do you know the name of this video? I keep trying to search for a secure boot video by Chris Titus released today/yesterday but I'm not finding anything.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -1 points 8 months ago*

    So... nobody changes the default settings, therefore everyone should change the default settings... to the wrong option?

    edit: Why is it that homo sapiens is always willing to go an extra mile just to hurt itself?

  • source
  • parent
  • [–] 6 points 8 months ago*

    Been running my own storage boxes off of rocky w/ zfs, samba and nfs for years simply for the ease of integration of samba + freeipa.

    Especially being able to use ipasam.so to allow password authentication for shares on machines that aren't easy/reasonable to use kerberos keytabs from (think android clients, and off domain boxes)

    Plus last time I tried truenas you couldn't use a keyfile to encrypt drives unless it was stored on the root dataset which for some reason couldn't be encrypted. Meaning each array had to have its own password instead.

    I won't lie I had to write several wiki articles to document this lol.

  • source
  • [–] 8 points 8 months ago

    So glad I went with OpenMediaVault so many years ago

  • source
  • [–] 4 points 8 months ago

    Uggh, I just got to the point where I'm as familiar with TrueNAS as my old Synology, but I want to move towards more freedom. TrueNAS beats Synology, but where is this going?

  • source
  • [–] [B] 9 points 8 months ago* (last edited 7 months ago) (1 child)

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

    Fewer Letters More Letters
    Git Popular version control system, primarily for code
    LTT Linus Tech Tips YouTube channel
    NAS Network-Attached Storage
    PIA Private Internet Access brand of VPN
    VPN Virtual Private Network
    ZFS Solaris/Linux filesystem focusing on data integrity

    [Thread #153 for this comm, first seen 10th Mar 2026, 00:40] [FAQ] [Full list] [Contact] [Source code]

  • source
  • hideshow 1 child comment
  • [–] -2 points 8 months ago

    Link to article?

  • source