This is the first stable release of TrueNAS SCALE 24.10 (Electric Eel).
It includes numerous software component updates and polished features, as well as fixes for issues discovered in 24.10-RC.1 and 24.10-RC.2.
Rewrite enclosure plugin in 24.10 to match performance improvements in 13.3 (NAS-123474).
Prevent phantom partitions that TrueNAS erroneously reported as disconnected pools (NAS-131171).
Revised Docker networking logic for applications (NAS-131617).
Enable editing of custom YAML applications (NAS-131147).
Prevent the TrueNAS UI from sending an improper payload for the Outboard Activity option when re-saving an edit to global network settings (NAS-131787).
When moving from an existing applications pool to a new pool, TrueNAS does not present the option to Migrate applications to the new pool because the underlying functionality is not present in the new Docker apps framework (NAS-131610). Users who need to redeploy the applications pool can either choose to leave existing applications on the previous location, remove existing applications and reinstall on the new pool, or manually relocate and clean up data.
Documentation Hub Update: To reflect the continuing process of application maintenance and updates as separate from TrueNAS major version releases, all application Tutorials are moved from the Tutorials section in TrueNAS version documentation to a dedicated and unversioned TrueNAS Apps section.
Thank you for using TrueNAS SCALE! As always, we appreciate your feedback!
1 Easy migration
1 Less than easy - but still achieved. One app failed to migrate successfully and as a result vanished. Took me a while to put it back in place.
Jailmaker still works - eventually. It didn’t work at first, but another reboot seemed to fix that. Further reboots and it still works.
CPU use much reduced. No major faults found as yet - but I am now into the nitty details of custom scripts and similar
I forgot that Syncthing has Host Path with ACL enabled and now it can’t migrate. What should I do?
[{"name": "syncthing", "error": "Failed to create app: [EINVAL] app_create.storage.additional_storage.0.host_path_config.acl: /mnt/mainpool/nas/Syncthing: path contains existing data and `force` was not specified\n", "successfully_migrated": false}]
Return to Dragonfish using System → Boot to reactivate your 24.04 environment and set the Force flag under ACL Options for your Syncthing installation - then you should be able to upgrade again.
Host Path ACLs:
Users with applications installed on 24.04 using host path volume mounts and ACL Entries defined in the app configuration screen must go to the app edit screen and set the Force Flag checkbox under ACL Options before updating to 24.10. This ensures the app fully migrates and doesn’t encounter issues when the mount point has existing data.
I changed boot enviroment, start a Reboot and now my system does not boot (stuck on B2 post code, supermicro board). Is this related or just a coincidence?
According to the Supermicro FAQ, B2 has to do with problems addressing legacy USB devices on boot.
If you are using a KVM switch for the monitor and USB keyboard/mouse, please remove it and plug the monitor directly to the motherboard. Plug the keyboard and mouse to the rear IO USB ports. Please try to boot it up again. B2 has to do with legacy devices, and sometimes the KVM might cause the system to be stuck on B2 at boot-up. If you are still having problems, please try to use another monitor, or mouse, or keyboard.
