{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/prepare-the-marker-for-a-read-only-truenas-migration-source/", "item": { "id": "https://update.dsesecurity.com/updates/prepare-the-marker-for-a-read-only-truenas-migration-source/", "slug": "prepare-the-marker-for-a-read-only-truenas-migration-source", "url": "https://update.dsesecurity.com/updates/prepare-the-marker-for-a-read-only-truenas-migration-source/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/prepare-the-marker-for-a-read-only-truenas-migration-source.md", "json": "https://update.dsesecurity.com/api/v1/posts/prepare-the-marker-for-a-read-only-truenas-migration-source/" }, "title": "Prepare the marker for a read-only TrueNAS migration source", "summary": "Provide an approved source marker before expecting the documented read-only Syncthing Enterprise ingest to synchronize.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-30T06:04:41+00:00", "modified_at": "2026-10-30T06:05:13+00:00", "reviewed_on": "2026-10-30", "reading_minutes": 3, "word_count": 531, "potentially_affected": "Licensed TrueNAS Enterprise third-party NAS migration through the documented Syncthing Enterprise application workflow.", "dse_recommendation": "Plan the remote marker through the approved source-owner or existing-marker method without making the ingest share writable.", "primary_source": { "name": "TrueNAS — Third-Party Data Migration", "url": "https://www.truenas.com/docs/scale/25.10/gettingstarted/thirdpartymigration/", "published_on": null, "authority": "www.truenas.com" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Bottom line: Prepare the remote marker before starting the read-only ingest. Keep the source’s read-only boundary intact and resolve marker creation through the documented source-owner or existing-marker branch.

\n

Source fact: what the authority says

\n

The TrueNAS 25.10 third-party migration guide scopes ingest to Enterprise customers with TrueNAS 24.04 or newer and the appropriate application license. The guide requires one-way migration with remote shares mounted read-only and excludes read-write or bidirectional synchronization. Syncthing needs a source marker to confirm the mounted volume, but the read-only SMB mount prevents creating its default .stfolder there. Its alternatives are a source-authorized client creating .stfolder at the share root, or the ingest instance’s Marker Name pointing to an existing source file or folder.

\n

What the source does not establish

\n

This article covers the marker prerequisite in the licensed migration workflow. It does not approve a general-purpose two-way sync, prove metadata completeness or replace the guide’s identity, SMB and destination-permission prerequisites.

\n

Applicability questions

\n\n

DSE recommendation: controlled next steps

\n

The following steps are DSE recommendations based on the cited source.

\n

DSE recommends resolving the marker plan before starting an ingest trial. Record the remote share, mounted root and ingest instance together. Confirm the licensing, SMB, identity and destination-permission prerequisites through the complete guide rather than treating the marker fix as approval for an otherwise unreviewed migration design.

\n

Choose one documented marker branch with the source owner. For a newly created marker, use an expressly authorized source client and record the intended share-root location. For an existing object, agree the exact reference and its owner. Avoid granting the ingest mount write access merely to bypass the prerequisite.

\n

Use a small disposable remote share for the initial exercise. Include harmless representative data and identify the marker separately from the data intended for migration. Keep the read-only one-way requirement explicit, and do not extend this procedure to bidirectional synchronization or general-purpose shared-folder administration.

\n

Review the ingest instance’s actual mount and marker setting together before the trial. Preserve the source’s original configuration and agree who controls cleanup of any temporary marker. Keep the broader migration acceptance plan, including identity and metadata checks, independent of a successful marker observation.

\n

Verification and evidence

\n

Proposed verification: inspect the remote mount and selected marker reference, then observe the ingest instance’s actual synchronization status in the disposable exercise. Compare a missing-marker case with the approved configured-marker case without modifying important source data. Record the actual messages and the precise selected path for each observation.

\n

Confirm that the trial still follows the approved read-only one-way design. Have the source owner account for any temporary marker and retain redacted mount and setting evidence. Treat successful synchronization startup as one prerequisite result, not proof that all files, permissions or migration objectives have been accepted.

\n

Official references

\n\n

Source review completed October 30, 2026. Recheck the official documentation and deployment-specific applicability before a production change.

\n", "content_text": "Bottom line: Prepare the remote marker before starting the read-only ingest. Keep the source’s read-only boundary intact and resolve marker creation through the documented source-owner or existing-marker branch.\nSource fact: what the authority says\nThe TrueNAS 25.10 third-party migration guide scopes ingest to Enterprise customers with TrueNAS 24.04 or newer and the appropriate application license. The guide requires one-way migration with remote shares mounted read-only and excludes read-write or bidirectional synchronization. Syncthing needs a source marker to confirm the mounted volume, but the read-only SMB mount prevents creating its default .stfolder there. Its alternatives are a source-authorized client creating .stfolder at the share root, or the ingest instance’s Marker Name pointing to an existing source file or folder.\nWhat the source does not establish\nThis article covers the marker prerequisite in the licensed migration workflow. It does not approve a general-purpose two-way sync, prove metadata completeness or replace the guide’s identity, SMB and destination-permission prerequisites.\nApplicability questions\n\nDoes this deployment meet the licensed Enterprise migration workflow’s prerequisites?\nWhich remote share root is actually mounted by the ingest instance?\nWho may create a source marker through an authorized client?\nIf an existing marker is chosen, what exact file or folder will be referenced?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends resolving the marker plan before starting an ingest trial. Record the remote share, mounted root and ingest instance together. Confirm the licensing, SMB, identity and destination-permission prerequisites through the complete guide rather than treating the marker fix as approval for an otherwise unreviewed migration design.\nChoose one documented marker branch with the source owner. For a newly created marker, use an expressly authorized source client and record the intended share-root location. For an existing object, agree the exact reference and its owner. Avoid granting the ingest mount write access merely to bypass the prerequisite.\nUse a small disposable remote share for the initial exercise. Include harmless representative data and identify the marker separately from the data intended for migration. Keep the read-only one-way requirement explicit, and do not extend this procedure to bidirectional synchronization or general-purpose shared-folder administration.\nReview the ingest instance’s actual mount and marker setting together before the trial. Preserve the source’s original configuration and agree who controls cleanup of any temporary marker. Keep the broader migration acceptance plan, including identity and metadata checks, independent of a successful marker observation.\nVerification and evidence\nProposed verification: inspect the remote mount and selected marker reference, then observe the ingest instance’s actual synchronization status in the disposable exercise. Compare a missing-marker case with the approved configured-marker case without modifying important source data. Record the actual messages and the precise selected path for each observation.\nConfirm that the trial still follows the approved read-only one-way design. Have the source owner account for any temporary marker and retain redacted mount and setting evidence. Treat successful synchronization startup as one prerequisite result, not proof that all files, permissions or migration objectives have been accepted.\nOfficial references\n\nTrueNAS — Third-Party Data Migration — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 30, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "content_markdown": "Bottom line: Prepare the remote marker before starting the read-only ingest. Keep the source’s read-only boundary intact and resolve marker creation through the documented source-owner or existing-marker branch.\n\n## Source fact: what the authority says\n\nThe [TrueNAS 25.10 third-party migration guide](https://www.truenas.com/docs/scale/25.10/gettingstarted/thirdpartymigration/) scopes ingest to Enterprise customers with TrueNAS 24.04 or newer and the appropriate application license. The guide requires one-way migration with remote shares mounted read-only and excludes read-write or bidirectional synchronization. Syncthing needs a source marker to confirm the mounted volume, but the read-only SMB mount prevents creating its default .stfolder there. Its alternatives are a source-authorized client creating .stfolder at the share root, or the ingest instance’s Marker Name pointing to an existing source file or folder.\n\n## What the source does not establish\n\nThis article covers the marker prerequisite in the licensed migration workflow. It does not approve a general-purpose two-way sync, prove metadata completeness or replace the guide’s identity, SMB and destination-permission prerequisites.\n\n## Applicability questions\n\n- Does this deployment meet the licensed Enterprise migration workflow’s prerequisites?\n\n- Which remote share root is actually mounted by the ingest instance?\n\n- Who may create a source marker through an authorized client?\n\n- If an existing marker is chosen, what exact file or folder will be referenced?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends resolving the marker plan before starting an ingest trial. Record the remote share, mounted root and ingest instance together. Confirm the licensing, SMB, identity and destination-permission prerequisites through the complete guide rather than treating the marker fix as approval for an otherwise unreviewed migration design.\n\nChoose one documented marker branch with the source owner. For a newly created marker, use an expressly authorized source client and record the intended share-root location. For an existing object, agree the exact reference and its owner. Avoid granting the ingest mount write access merely to bypass the prerequisite.\n\nUse a small disposable remote share for the initial exercise. Include harmless representative data and identify the marker separately from the data intended for migration. Keep the read-only one-way requirement explicit, and do not extend this procedure to bidirectional synchronization or general-purpose shared-folder administration.\n\nReview the ingest instance’s actual mount and marker setting together before the trial. Preserve the source’s original configuration and agree who controls cleanup of any temporary marker. Keep the broader migration acceptance plan, including identity and metadata checks, independent of a successful marker observation.\n\n## Verification and evidence\n\nProposed verification: inspect the remote mount and selected marker reference, then observe the ingest instance’s actual synchronization status in the disposable exercise. Compare a missing-marker case with the approved configured-marker case without modifying important source data. Record the actual messages and the precise selected path for each observation.\n\nConfirm that the trial still follows the approved read-only one-way design. Have the source owner account for any temporary marker and retain redacted mount and setting evidence. Treat successful synchronization startup as one prerequisite result, not proof that all files, permissions or migration objectives have been accepted.\n\n## Official references\n\n- [TrueNAS — Third-Party Data Migration](https://www.truenas.com/docs/scale/25.10/gettingstarted/thirdpartymigration/) — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 30, 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/prepare-the-marker-for-a-read-only-truenas-migration-source/", "url": "https://update.dsesecurity.com/updates/prepare-the-marker-for-a-read-only-truenas-migration-source/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-30" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/prepare-the-marker-for-a-read-only-truenas-migration-source/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Business Continuity", "item": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "ListItem", "position": 3, "name": "Prepare the marker for a read-only TrueNAS migration source", "item": "https://update.dsesecurity.com/updates/prepare-the-marker-for-a-read-only-truenas-migration-source/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/prepare-the-marker-for-a-read-only-truenas-migration-source/#article", "identifier": "https://update.dsesecurity.com/updates/prepare-the-marker-for-a-read-only-truenas-migration-source/", "url": "https://update.dsesecurity.com/updates/prepare-the-marker-for-a-read-only-truenas-migration-source/", "headline": "Prepare the marker for a read-only TrueNAS migration source", "description": "Provide an approved source marker before expecting the documented read-only Syncthing Enterprise ingest to synchronize.", "abstract": "Provide an approved source marker before expecting the documented read-only Syncthing Enterprise ingest to synchronize.", "articleBody": "Bottom line: Prepare the remote marker before starting the read-only ingest. Keep the source’s read-only boundary intact and resolve marker creation through the documented source-owner or existing-marker branch.\nSource fact: what the authority says\nThe TrueNAS 25.10 third-party migration guide scopes ingest to Enterprise customers with TrueNAS 24.04 or newer and the appropriate application license. The guide requires one-way migration with remote shares mounted read-only and excludes read-write or bidirectional synchronization. Syncthing needs a source marker to confirm the mounted volume, but the read-only SMB mount prevents creating its default .stfolder there. Its alternatives are a source-authorized client creating .stfolder at the share root, or the ingest instance’s Marker Name pointing to an existing source file or folder.\nWhat the source does not establish\nThis article covers the marker prerequisite in the licensed migration workflow. It does not approve a general-purpose two-way sync, prove metadata completeness or replace the guide’s identity, SMB and destination-permission prerequisites.\nApplicability questions\n\nDoes this deployment meet the licensed Enterprise migration workflow’s prerequisites?\nWhich remote share root is actually mounted by the ingest instance?\nWho may create a source marker through an authorized client?\nIf an existing marker is chosen, what exact file or folder will be referenced?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends resolving the marker plan before starting an ingest trial. Record the remote share, mounted root and ingest instance together. Confirm the licensing, SMB, identity and destination-permission prerequisites through the complete guide rather than treating the marker fix as approval for an otherwise unreviewed migration design.\nChoose one documented marker branch with the source owner. For a newly created marker, use an expressly authorized source client and record the intended share-root location. For an existing object, agree the exact reference and its owner. Avoid granting the ingest mount write access merely to bypass the prerequisite.\nUse a small disposable remote share for the initial exercise. Include harmless representative data and identify the marker separately from the data intended for migration. Keep the read-only one-way requirement explicit, and do not extend this procedure to bidirectional synchronization or general-purpose shared-folder administration.\nReview the ingest instance’s actual mount and marker setting together before the trial. Preserve the source’s original configuration and agree who controls cleanup of any temporary marker. Keep the broader migration acceptance plan, including identity and metadata checks, independent of a successful marker observation.\nVerification and evidence\nProposed verification: inspect the remote mount and selected marker reference, then observe the ingest instance’s actual synchronization status in the disposable exercise. Compare a missing-marker case with the approved configured-marker case without modifying important source data. Record the actual messages and the precise selected path for each observation.\nConfirm that the trial still follows the approved read-only one-way design. Have the source owner account for any temporary marker and retain redacted mount and setting evidence. Treat successful synchronization startup as one prerequisite result, not proof that all files, permissions or migration objectives have been accepted.\nOfficial references\n\nTrueNAS — Third-Party Data Migration — official product documentation; confirm the installed release and configuration.\n\nSource review completed October 30, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "datePublished": "2026-10-30T06:04:41+00:00", "dateModified": "2026-10-30T06:05:13+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/prepare-the-marker-for-a-read-only-truenas-migration-source/" }, "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/prepare-the-marker-for-a-read-only-truenas-migration-source/#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": "Prepare the marker for a read-only TrueNAS migration source" }, "articleSection": [ "Business Continuity", "Networks & Infrastructure" ], "keywords": [ "Business Continuity", "Networks & Infrastructure", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 531, "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 — Third-Party Data Migration", "url": "https://www.truenas.com/docs/scale/25.10/gettingstarted/thirdpartymigration/" } } ] } }