Bottom line: Choose the intended release path before treating an available update as the approved target. Keep the update profile, intervening major versions and restart window in the same change request.
\nThe TrueNAS update guide describes update profiles intended for different use cases and distinguishes those profiles from major-version release trains. Its major-version guidance says to follow the upgrade path of major versions until the desired major release is reached. It warns that the Developer profile is unsuitable for production use and can expose systems to bugs. The documented update process restarts the system, so the guide advises scheduling updates when the system is idle and users are disconnected.
\nThis article does not select the currently recommended TrueNAS release for a particular workload or approve a prerelease channel. Configuration and data recovery remain separate requirements; an available update and a completed restart do not establish workload compatibility.
\nThe following steps are DSE recommendations based on the cited source.
\nDSE recommends a release-path record listing the current version, proposed target and each required intermediate major version. Check the current official release and software-status references before approval. Keep the profile choice explicit rather than relying on whichever update the interface happens to display.
\nHave the storage owner explain why the chosen channel fits the workload’s stability requirements. Exclude the Developer branch from this production plan. Treat a test or prerelease evaluation as a different activity with its own disposable system and data restrictions.
\nPlan a proposed representative upgrade rehearsal against the actual service inventory. Name the SMB, NFS, iSCSI or other workload owners who must observe the result, selecting only the services actually used. Keep the recovery package and restore authority available through the organization’s separate recovery procedure.
\nSchedule each approved restart as a deliberate change point. Record the maintenance contact, client-disconnection plan and condition for stopping before the next version. Avoid combining unrelated storage-layout changes with the release transition merely because a maintenance window is available.
\nProposed verification: inspect the effective installed version and update profile before the run, then compare each completed transition with the approved release path. Preserve the actual update and restart observations, including warnings and incomplete steps. Do not label an intermediate system finished while another required transition remains unreviewed.
\nAfter each approved stage, run the named harmless workload checks and confirm client access through the intended paths. Have the application owners record their observations separately from the updater’s completion status. Retain unresolved failures and keep the recovery decision open until the agreed service checks are accepted.
\nSource review completed October 29, 2026. Recheck the official documentation and deployment-specific applicability before a production change.
\n", "content_text": "Bottom line: Choose the intended release path before treating an available update as the approved target. Keep the update profile, intervening major versions and restart window in the same change request.\nSource fact: what the authority says\nThe TrueNAS update guide describes update profiles intended for different use cases and distinguishes those profiles from major-version release trains. Its major-version guidance says to follow the upgrade path of major versions until the desired major release is reached. It warns that the Developer profile is unsuitable for production use and can expose systems to bugs. The documented update process restarts the system, so the guide advises scheduling updates when the system is idle and users are disconnected.\nWhat the source does not establish\nThis article does not select the currently recommended TrueNAS release for a particular workload or approve a prerelease channel. Configuration and data recovery remain separate requirements; an available update and a completed restart do not establish workload compatibility.\nApplicability questions\n\nWhat exact version and update profile are installed now?\nWhich supported upgrade path reaches the proposed target?\nWhat services and users require a coordinated interruption window?\nWhich recovery evidence and application checks must be accepted before production resumes?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends a release-path record listing the current version, proposed target and each required intermediate major version. Check the current official release and software-status references before approval. Keep the profile choice explicit rather than relying on whichever update the interface happens to display.\nHave the storage owner explain why the chosen channel fits the workload’s stability requirements. Exclude the Developer branch from this production plan. Treat a test or prerelease evaluation as a different activity with its own disposable system and data restrictions.\nPlan a proposed representative upgrade rehearsal against the actual service inventory. Name the SMB, NFS, iSCSI or other workload owners who must observe the result, selecting only the services actually used. Keep the recovery package and restore authority available through the organization’s separate recovery procedure.\nSchedule each approved restart as a deliberate change point. Record the maintenance contact, client-disconnection plan and condition for stopping before the next version. Avoid combining unrelated storage-layout changes with the release transition merely because a maintenance window is available.\nVerification and evidence\nProposed verification: inspect the effective installed version and update profile before the run, then compare each completed transition with the approved release path. Preserve the actual update and restart observations, including warnings and incomplete steps. Do not label an intermediate system finished while another required transition remains unreviewed.\nAfter each approved stage, run the named harmless workload checks and confirm client access through the intended paths. Have the application owners record their observations separately from the updater’s completion status. Retain unresolved failures and keep the recovery decision open until the agreed service checks are accepted.\nOfficial references\n\nTrueNAS — Updating TrueNAS — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 29, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "content_markdown": "Bottom line: Choose the intended release path before treating an available update as the approved target. Keep the update profile, intervening major versions and restart window in the same change request.\n\n## Source fact: what the authority says\n\nThe [TrueNAS update guide](https://www.truenas.com/docs/scale/25.10/scaletutorials/systemsettings/updatescale/) describes update profiles intended for different use cases and distinguishes those profiles from major-version release trains. Its major-version guidance says to follow the upgrade path of major versions until the desired major release is reached. It warns that the Developer profile is unsuitable for production use and can expose systems to bugs. The documented update process restarts the system, so the guide advises scheduling updates when the system is idle and users are disconnected.\n\n## What the source does not establish\n\nThis article does not select the currently recommended TrueNAS release for a particular workload or approve a prerelease channel. Configuration and data recovery remain separate requirements; an available update and a completed restart do not establish workload compatibility.\n\n## Applicability questions\n\n- What exact version and update profile are installed now?\n\n- Which supported upgrade path reaches the proposed target?\n\n- What services and users require a coordinated interruption window?\n\n- Which recovery evidence and application checks must be accepted before production resumes?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends a release-path record listing the current version, proposed target and each required intermediate major version. Check the current official release and software-status references before approval. Keep the profile choice explicit rather than relying on whichever update the interface happens to display.\n\nHave the storage owner explain why the chosen channel fits the workload’s stability requirements. Exclude the Developer branch from this production plan. Treat a test or prerelease evaluation as a different activity with its own disposable system and data restrictions.\n\nPlan a proposed representative upgrade rehearsal against the actual service inventory. Name the SMB, NFS, iSCSI or other workload owners who must observe the result, selecting only the services actually used. Keep the recovery package and restore authority available through the organization’s separate recovery procedure.\n\nSchedule each approved restart as a deliberate change point. Record the maintenance contact, client-disconnection plan and condition for stopping before the next version. Avoid combining unrelated storage-layout changes with the release transition merely because a maintenance window is available.\n\n## Verification and evidence\n\nProposed verification: inspect the effective installed version and update profile before the run, then compare each completed transition with the approved release path. Preserve the actual update and restart observations, including warnings and incomplete steps. Do not label an intermediate system finished while another required transition remains unreviewed.\n\nAfter each approved stage, run the named harmless workload checks and confirm client access through the intended paths. Have the application owners record their observations separately from the updater’s completion status. Retain unresolved failures and keep the recovery decision open until the agreed service checks are accepted.\n\n## Official references\n\n- [TrueNAS — Updating TrueNAS](https://www.truenas.com/docs/scale/25.10/scaletutorials/systemsettings/updatescale/) — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 29, 2026. Recheck the official documentation and deployment-specific applicability before a production change." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/review-the-truenas-update-profile-before-a-major-version-change/", "url": "https://update.dsesecurity.com/updates/review-the-truenas-update-profile-before-a-major-version-change/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-29" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/review-the-truenas-update-profile-before-a-major-version-change/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Cybersecurity", "item": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "ListItem", "position": 3, "name": "Review the TrueNAS update profile before a major-version change", "item": "https://update.dsesecurity.com/updates/review-the-truenas-update-profile-before-a-major-version-change/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/review-the-truenas-update-profile-before-a-major-version-change/#article", "identifier": "https://update.dsesecurity.com/updates/review-the-truenas-update-profile-before-a-major-version-change/", "url": "https://update.dsesecurity.com/updates/review-the-truenas-update-profile-before-a-major-version-change/", "headline": "Review the TrueNAS update profile before a major-version change", "description": "TrueNAS distinguishes update profiles and requires major upgrades to follow the documented path.", "abstract": "TrueNAS distinguishes update profiles and requires major upgrades to follow the documented path. Review the selected channel, ordered releases and restart window before scheduling the change.", "articleBody": "Bottom line: Choose the intended release path before treating an available update as the approved target. Keep the update profile, intervening major versions and restart window in the same change request.\nSource fact: what the authority says\nThe TrueNAS update guide describes update profiles intended for different use cases and distinguishes those profiles from major-version release trains. Its major-version guidance says to follow the upgrade path of major versions until the desired major release is reached. It warns that the Developer profile is unsuitable for production use and can expose systems to bugs. The documented update process restarts the system, so the guide advises scheduling updates when the system is idle and users are disconnected.\nWhat the source does not establish\nThis article does not select the currently recommended TrueNAS release for a particular workload or approve a prerelease channel. Configuration and data recovery remain separate requirements; an available update and a completed restart do not establish workload compatibility.\nApplicability questions\n\nWhat exact version and update profile are installed now?\nWhich supported upgrade path reaches the proposed target?\nWhat services and users require a coordinated interruption window?\nWhich recovery evidence and application checks must be accepted before production resumes?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends a release-path record listing the current version, proposed target and each required intermediate major version. Check the current official release and software-status references before approval. Keep the profile choice explicit rather than relying on whichever update the interface happens to display.\nHave the storage owner explain why the chosen channel fits the workload’s stability requirements. Exclude the Developer branch from this production plan. Treat a test or prerelease evaluation as a different activity with its own disposable system and data restrictions.\nPlan a proposed representative upgrade rehearsal against the actual service inventory. Name the SMB, NFS, iSCSI or other workload owners who must observe the result, selecting only the services actually used. Keep the recovery package and restore authority available through the organization’s separate recovery procedure.\nSchedule each approved restart as a deliberate change point. Record the maintenance contact, client-disconnection plan and condition for stopping before the next version. Avoid combining unrelated storage-layout changes with the release transition merely because a maintenance window is available.\nVerification and evidence\nProposed verification: inspect the effective installed version and update profile before the run, then compare each completed transition with the approved release path. Preserve the actual update and restart observations, including warnings and incomplete steps. Do not label an intermediate system finished while another required transition remains unreviewed.\nAfter each approved stage, run the named harmless workload checks and confirm client access through the intended paths. Have the application owners record their observations separately from the updater’s completion status. Retain unresolved failures and keep the recovery decision open until the agreed service checks are accepted.\nOfficial references\n\nTrueNAS — Updating TrueNAS — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 29, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "datePublished": "2026-10-29T19:49:36+00:00", "dateModified": "2026-10-29T19:50:08+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/review-the-truenas-update-profile-before-a-major-version-change/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/review-the-truenas-update-profile-before-a-major-version-change/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Review the TrueNAS update profile before a major-version change" }, "articleSection": [ "Cybersecurity", "Networks & Infrastructure" ], "keywords": [ "Cybersecurity", "Networks & Infrastructure", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 512, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "TrueNAS — Updating TrueNAS", "url": "https://www.truenas.com/docs/scale/25.10/scaletutorials/systemsettings/updatescale/" } } ] } }