tonyriv3 · Nov 6, 2026 · Oct 28, 2026 · Nov 4, 2026 · Nov 5, 2026
@@ -421,7 +421,7 @@ The TrueNAS team is pleased to release TrueNAS 25.10.1!
 * Adds automatic validation for SMB share audit logging configurations.
   TrueNAS 25.10.1 automatically disables SMB shares when auditing is enabled and watch or ignore lists contain invalid groups (deleted/renamed groups or groups that are no longer SMB-type). This protective measure prevents auditing misconfigurations that could cause security or compliance issues. The system generates alerts identifying affected shares and problematic groups. See [Configuring SMB Auditing](ManageSMBShares#configuring-smb-auditing) for configuration details and troubleshooting steps.
 * Adds REST API usage monitoring alert.
-  TrueNAS now displays a daily alert when deprecated REST API endpoints are accessed, helping identify integrations that need migration. TrueNAS deprecated the REST API in version 25.04. Full removal is planned for TrueNAS 26. For more information about the JSON-RPC 2.0 over WebSocket API, see the [API documentation](https://api.truenas.com/v25.10/jsonrpc.html).
+  TrueNAS now displays a daily alert when deprecated REST API endpoints are accessed, helping identify integrations that need migration. TrueNAS deprecated the REST API in version 25.04. Full removal is planned for TrueNAS 27. For more information about the JSON-RPC 2.0 over WebSocket API, see the [API documentation](https://api.truenas.com/v25.10/jsonrpc.html).
 * Adds **Clear Config** button to the directory services configuration form.
   This button allows users to easily remove existing directory service configurations. This is useful for troubleshooting, reconfiguration, or switching between directory service types.
 * Updates Samba from 4.22.5 to 4.22.6 ([NAS-138644](https://ixsystems.atlassian.net/browse/NAS-138644)).
@@ -683,7 +683,7 @@ Failover moves to the **Advanced Settings** screen ([NAS-135469](https://ixsyste
   Existing configurations using **AUTORID** are automatically migrated to **RID** during upgrade.
   Users should review their ACLs and permissions after upgrade and might need to reconfigure them in some edge cases.
 * Completes the transition to the versioned JSON-RPC 2.0 over WebSocket API by migrating all remaining jobs and events from the deprecated REST API ([NAS-133984](https://ixsystems.atlassian.net/browse/NAS-133984)).
-  Full removal of the REST API is planned for the TrueNAS 26 release.
+  Full removal of the REST API is planned for the TrueNAS 27 release.
 * Removes the SMART UI ([NAS-134927](https://ixsystems.atlassian.net/browse/NAS-134927)).
   * Removes the built-in SMART test scheduling and monitoring interface to improve user flexibility while maintaining smartmontools binaries for continued third-party script compatibility ([NAS-135020](https://ixsystems.atlassian.net/browse/NAS-135020)).
     Existing scheduled SMART tests are automatically migrated to cron tasks during upgrade, and users can install the Scrutiny app for advanced SMART monitoring.
@@ -720,7 +720,7 @@ These are ongoing issues that can affect multiple versions in the 25.10 series.
 
   Workaround: After saving STIG settings, wait until the standby controller is fully online before rebooting the active controller. Rebooting the active controller while the standby is still booting can cause disrupt production.
 
-  This issue is resolved in TrueNAS 26.
+  This issue is resolved in TrueNAS 27.
 {{< /enterprise >}}
 
 * Apps using SMB/NFS storage can experience race condition during boot.
@@ -757,7 +757,7 @@ These are ongoing issues that can affect multiple versions in the 25.10 series.
 
   Workaround: Restart the SMB service in **System > Services**, or disconnect and reconnect the SMB client (unmount and remount the server).
 
-  This issue is resolved in TrueNAS 26.
+  This issue is resolved in TrueNAS 27.
 
 * Fibre Channel iSCSI initiator changes do not apply to the running configuration until the iSCSI service is restarted.
   When updating a Fibre Channel initiator on an iSCSI share, SCST updates with the change but the running configuration file does not reflect the update until the iSCSI service is stopped and started.
@@ -774,7 +774,7 @@ These are ongoing issues that can affect multiple versions in the 25.10 series.
 
   Workaround: Reboot the system after changing the update profile to clear the error message.
 
-  This issue is resolved in TrueNAS 26.
+  This issue is resolved in TrueNAS 27.
 
 * The **Reload** button in the new license confirmation dialog does not reload the web interface ([NAS-140931](https://ixsystems.atlassian.net/browse/NAS-140931)).
   After applying a new license, the confirmation dialog appears with a **Reload** button. Clicking **Reload** does not trigger a page reload; the license is applied correctly but the web interface continues to display the pre-license state until the page is manually refreshed.

@@ -612,21 +612,22 @@ After upgrading to a release that shows the **Virtual Machines** screen and the
 
 8. Return to the **Virtual Machines** screen, click on the VM to expand it, then use the **Running** toggle to start it and verify it opens as expected and has network access.
 
-### Preparing to Upgrade to TrueNAS 26
+### Preparing to Upgrade to TrueNAS 27
 
 Legacy virtual machines created using the **Instances** screen in 25.04.0 and 25.04.1 are still shown on the **Containers** screen in 25.10.
-TrueNAS 26 removes them from the **Containers** screen entirely.
+TrueNAS 27 removes them from the **Containers** screen entirely.
 No migration tool, wizard, or notification exists to move them automatically.
 Complete the following steps while still running TrueNAS 25.10.
-None of these steps are available after upgrading to TrueNAS 26.
+None of these steps are available after upgrading to TrueNAS 27.
 
 {{< hint type=important >}}
-TrueNAS does not delete a legacy VM disk during the upgrade to 26.
+TrueNAS does not delete a legacy VM disk during the upgrade to 27.
 The disk remains on the pool, but TrueNAS does not preserve the VM configuration, UEFI variables, or Trusted Platform Module (TPM) state.
 {{< /hint >}}
 
 1. Go to **Containers**, and identify which instances are VMs.
-   Only VMs require this procedure. Containers migrate automatically during the upgrade to TrueNAS 26.
+   Only VMs require this procedure. Containers do not.
+   See [Containers]({{< ref "/scaletutorials/containers/" >}}) for which systems migrate containers automatically.
 
 2. Open each VM and record the CPU count, memory, disk size, network interface, MAC address, guest operating system, and secure boot setting.
    A screenshot of the VM configuration is sufficient. You need these values to re-create the VM after upgrading.
@@ -644,11 +645,11 @@ The disk remains on the pool, but TrueNAS does not preserve the VM configuration
 
 5. Go to **Datasets**, select the pool used by instances, and take a recursive snapshot.
 
-   The snapshot preserves a copy of the data. Recovering from the snapshot requires renaming datasets back by hand. There is no single rollback that undoes the procedure in [Migrating a Legacy VM Disk](https://www.truenas.com/docs/scale/26/virtualmachines/managingvms/#migrating-a-legacy-vm-disk) in the TrueNAS 26 documentation.
+   The snapshot preserves a copy of the data. Recovering from the snapshot requires renaming datasets back by hand. There is no single rollback that undoes the procedure in [Migrating a Legacy VM Disk](https://www.truenas.com/docs/scale/27/virtualmachines/managingvms/#migrating-a-legacy-vm-disk) in the TrueNAS 27 documentation.
 
-6. Upgrade to TrueNAS 26.
+6. Upgrade to TrueNAS 27.
 
-   After the upgrade, complete [Migrating a Legacy VM Disk](https://www.truenas.com/docs/scale/26/virtualmachines/managingvms/#migrating-a-legacy-vm-disk) in the TrueNAS 26 documentation to re-create the VM and attach the disk.
+   After the upgrade, complete [Migrating a Legacy VM Disk](https://www.truenas.com/docs/scale/27/virtualmachines/managingvms/#migrating-a-legacy-vm-disk) in the TrueNAS 27 documentation to re-create the VM and attach the disk.
 
 ## Virtual Machines Contents
 

@@ -11,4 +11,13 @@ Legacy VMs on the **Containers** screen do not autostart in 25.10 or later.
 Users with existing VMs on the **Containers** screen should consider migrating associated zvols to the **Virtual Machines** screen at this time to ensure compatibility with future TrueNAS releases.
 For information on migrating your zvol storage volume to a new VM created in 25.10 or later, see **[Migrating Legacy VMs to Virtual Machines]({{< ref "/SCALETutorials/VirtualMachines/#migrating-legacy-vms-to-virtual-machines" >}})**.
 
+Due to backend technology changes in TrueNAS 27, containers on the **Containers** screen require migration when you upgrade from TrueNAS 25.10.
+Containers migrate automatically at the first boot after upgrading, except on HA-capable TrueNAS Enterprise systems.
+Containers on a passphrase-encrypted pool do not migrate, because the pool is still locked at first boot and the migration does not retry.
+Switch the pool to key encryption before you upgrade.
+Contact [TrueNAS Enterprise Support](https://www.truenas.com/support/) if you have containers on a TrueNAS Enterprise system that does not migrate them.
+
+Legacy VMs on the **Containers** screen are not migrated automatically and are removed from the **Containers** screen in TrueNAS 27.
+Complete the steps in [Preparing to Upgrade to TrueNAS 27]({{< ref "/SCALETutorials/VirtualMachines/#preparing-to-upgrade-to-truenas-27" >}}) before you upgrade.
+
 {{< /hint >}}
@@ -1,8 +1,8 @@
 &NewLine;
 
 {{< hint type="info" title="REST API Deprecation Notice" >}}
-The TrueNAS REST API was deprecated in TrueNAS 25.04.
-Full removal of the REST API is planned for TrueNAS 26.
+The TrueNAS REST API is removed in TrueNAS 27.
+Systems still using the REST API must migrate to the WebSocket API before upgrading.
 
 Starting with TrueNAS 25.10.1, the system displays alerts when deprecated REST API endpoints are accessed to help identify integrations that require migration to the JSON-RPC 2.0 over WebSocket API.
 {{< /hint >}}