Conversation
Contributor
📝 WalkthroughWalkthroughExtensive multilingual documentation updates: added descriptive Card text on API index pages, inserted header anchors in many release notes, added new pages (secure-your-boot-drive, internal-boot-faq, 7.3.0 release notes), replaced “flash device” with “boot device” across locales, reformatted JSX style blocks, and assorted localization/spacing edits. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 31
Note
Due to the large number of review comments, Critical severity comments were prioritized as inline comments.
♻️ Duplicate comments (4)
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx (4)
144-144: Anchor removal follows the same link-stability risk as noted above.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx` at line 144, The note "Anchor removal follows the same link-stability risk as noted above." is duplicated under the "## 高级选项" heading; remove the duplicate instance so the guidance appears only once (keep the original earlier occurrence), updating the content under the "## 高级选项" section in vm-setup.mdx to eliminate the repeated sentence.
29-29: Anchor removal follows the same link-stability risk as noted above.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx` at line 29, The change removed or altered the anchor for the section titled "## 创建您自己的虚拟机", which creates the same link-stability risk noted earlier; restore the original anchor (or add an explicit HTML anchor/id) for the "创建您自己的虚拟机" heading so existing links remain stable, and ensure any anchor text/ID matches the previous value or follows the project's anchor naming convention.
459-459: Anchor removal follows the same link-stability risk as noted above.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx` at line 459, The comment is duplicated under the "### 扩展vDisk" heading; remove the duplicate note so the anchor-stability warning appears only once (or consolidate both instances into a single, clearly worded sentence) and ensure the remaining text references the anchor/link stability risk consistently; update the content under "### 扩展vDisk" to keep only the single, consolidated warning about link-stability risk.
424-424: Anchor removal follows the same link-stability risk as noted above.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx` at line 424, The heading "### 停留在UEFI shell" currently lacks a stable anchor which risks link breakage when headings are edited; add an explicit, stable anchor for this section (e.g., an MDX/HTML id like `#uefi-shell`) so links remain stable even if the visible heading text changes, by inserting a persistent anchor immediately before or as part of the "停留在UEFI shell" heading (reference the heading text "停留在UEFI shell" to locate where to add the anchor).
🧹 Nitpick comments (3)
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md (1)
26-26: Use a consistent arrow glyph in UI paths.Line 26 uses
->while Line 62 uses→. Consider standardizing (prefer→) for consistency.Also applies to: 62-62
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md` at line 26, Replace the inconsistent ASCII arrow in the UI path with the preferred glyph: change "Herramientas -> Syslog" (the "->" occurrence in the string "'espejo syslog en flash', ver syslog-previous en Herramientas -> Syslog, y en diagnósticos") to use the Unicode arrow "→" to match the other occurrence on the page; ensure any other "->" occurrences in this markdown file are similarly normalized to "→" for consistency.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx (1)
68-68: Consider using an ASCII slug for the tabvalueattribute.Tab
values can be persisted into URL search parameters; when that feature is enabled, accented characters in the value will be percent-encoded in the URL (e.g.?tab=pr%C3%A9f%C3%A9r%C3%A9). Using an ASCII slug keeps URLs clean and matches the idiomatic pattern from Docusaurus examples.♻️ Proposed refactor
- <TabItem value="préféré" label="Méthode préférée" default> + <TabItem value="preferred" label="Méthode préférée" default>🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx` at line 68, The TabItem uses a non-ASCII value "préféré" which will be percent-encoded in URLs; change the value to an ASCII slug (e.g. value="prefere" or "preferred") while keeping label="Méthode préférée" and the default attribute as-is, and update any code or links that reference the old value ("préféré") to the new ASCII slug so persisted tab parameters and examples continue to work cleanly.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-xfs.mdx (1)
12-12: English text in German locale file.Line 12 is in English while the rest of the file (lines 1–8) remains in German. If this is intentional (e.g., standardizing parity warnings in English across all locales), it would be helpful to add a brief comment or ensure consistency. Otherwise, this should be translated to German.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-xfs.mdx` at line 12, The sentence "Running this command on an %%array|array%% disk outside of **%%Maintenance Mode|maintenance-mode%%** will invalidate %%parity|parity%%." is in English inside a German locale file; either translate it to German or annotate why it must remain English. Replace that line with a German translation that preserves the placeholders/formatting (keep %%array|array%%, %%Maintenance Mode|maintenance-mode%% as bold where present, and %%parity|parity%%) or add a brief inline comment stating the English parity warning is intentionally left untranslated for consistency.
ℹ️ Review info
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (221)
i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/monitor-performance/smart-reports-and-disk-health.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-btrfs.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-xfs.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/local.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.jsoni18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-btrfs.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-xfs.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-zfs.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-btrfs.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-xfs.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-array-to-pool.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-pool-to-array.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-command-line.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-gui.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-device-limit.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-license-issues.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdxi18n/es/docusaurus-plugin-content-docs/current/API/cli.mdxi18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdxi18n/es/docusaurus-plugin-content-docs/current/API/index.mdxi18n/es/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdxi18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdxi18n/es/docusaurus-plugin-content-docs/current/API/upcoming-features.mdxi18n/es/docusaurus-plugin-content-docs/current/contribute/style-guide.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.jsoni18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.jsoni18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdxi18n/zh/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.jsoni18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
💤 Files with no reviewable changes (1)
- i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
Comment on lines
+48
to
+49
| ::: | ||
|
|
Contributor
There was a problem hiding this comment.
Stray ::: will break page rendering.
The :::important block is already closed at line 46. The new ::: at line 48 is an orphaned closing directive with no matching opening. In Docusaurus MDX v2 this will either fail to build or silently wrap all subsequent content into an unclosed admonition, corrupting the rest of the page.
🐛 Proposed fix — remove the stray directive
:::
-
-:::
### Herunterladen und entpacken🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx`
around lines 48 - 49, There is an orphaned closing admonition directive (":::")
after the already-closed ":::important" block that will break MDX rendering;
remove the stray ":::" so the ":::important" block has a single matching closing
delimiter and verify no other unmatched ":::"/admonition markers remain in the
same file (look for the ":::important" opening/closing and the extra standalone
":::").
...-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
Show resolved
Hide resolved
Comment on lines
+21
to
25
| Einige Nutzer berichten von sporadischen Problemen mit Time Machine und Netzlaufwerken auf macOS Sequoia. Sollte es bei Ihnen zu Backup-Fehlern kommen, ziehen Sie in Betracht, den [Time Machine Docker-Container](https://unraid.net/community/apps?q=time+machine#r) als Alternative zu nutzen. | ||
|
|
||
| :::caution[Before Sie beginnen] | ||
| Stellen Sie sicher, dass **%%SMB|samba%%** im %%WebGUI|web-gui%% aktiviert ist: | ||
|
|
Contributor
There was a problem hiding this comment.
Duplicated paragraph and unclosed admonition block.
Line 21 duplicates the macOS Sequoia warning from line 17. Lines 23–24 open a :::caution[Before Sie beginnen] block that is never closed before the ## Erstellen einer Time Machine-Freigabe heading on line 26. This will cause the heading and subsequent content to render inside the caution block.
Additionally, line 23 has a mixed-language title (Before Sie beginnen).
Proposed fix — remove duplicated paragraph and unclosed block
-Einige Nutzer berichten von sporadischen Problemen mit Time Machine und Netzlaufwerken auf macOS Sequoia. Sollte es bei Ihnen zu Backup-Fehlern kommen, ziehen Sie in Betracht, den [Time Machine Docker-Container](https://unraid.net/community/apps?q=time+machine#r) als Alternative zu nutzen.
-
-:::caution[Before Sie beginnen]
-Stellen Sie sicher, dass **%%SMB|samba%%** im %%WebGUI|web-gui%% aktiviert ist:
-
## Erstellen einer Time Machine-Freigabe📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| Einige Nutzer berichten von sporadischen Problemen mit Time Machine und Netzlaufwerken auf macOS Sequoia. Sollte es bei Ihnen zu Backup-Fehlern kommen, ziehen Sie in Betracht, den [Time Machine Docker-Container](https://unraid.net/community/apps?q=time+machine#r) als Alternative zu nutzen. | |
| :::caution[Before Sie beginnen] | |
| Stellen Sie sicher, dass **%%SMB|samba%%** im %%WebGUI|web-gui%% aktiviert ist: | |
| ## Erstellen einer Time Machine-Freigabe |
🧰 Tools
🪛 LanguageTool
[grammar] ~21-~21: Entferne ein Leerzeichen
Context: ...ommen, ziehen Sie in Betracht, den [Time Machine Docker-Container](https://unraid...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~21-~21: Entferne ein Leerzeichen
Context: ...iehen Sie in Betracht, den [Time Machine Docker-Container](https://unraid.net/com...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx`
around lines 21 - 25, Remove the duplicated macOS Sequoia warning paragraph (the
repeated sentence about sporadic Time Machine issues) and fix the unclosed
admonition by changing the mixed-language title token `:::caution[Before Sie
beginnen]` to a German title like `:::caution[Bevor Sie beginnen]` and add a
closing `:::` before the `## Erstellen einer Time Machine-Freigabe` heading so
the caution block is properly terminated.
Comment on lines
+28
to
+29
| :::Vorsicht[Bevor Sie beginnen] | ||
|
|
Contributor
There was a problem hiding this comment.
Invalid admonition keyword :::Vorsicht.
Docusaurus admonition keywords must be in English (note, tip, info, caution, danger, warning, important). :::Vorsicht will not render as an admonition block. This should be :::caution.
Proposed fix
-:::Vorsicht[Bevor Sie beginnen]
+:::caution[Bevor Sie beginnen]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| :::Vorsicht[Bevor Sie beginnen] | |
| :::caution[Bevor Sie beginnen] | |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx`
around lines 28 - 29, Replace the non-English admonition keyword used in the MDX
admonition header (the line starting with ":::Vorsicht") with the supported
Docusaurus keyword ":::caution" so the block renders as an admonition; update
the admonition starter in the file's content to use "caution" instead of
"Vorsicht" (no other structural changes needed).
Comment on lines
+104
to
+106
| ## **Verhinderung von versehentlichem Verlust:** Reduzieren Sie das Risiko von Datenverlusten beim Formatieren oder Ersetzen von Geräten. | ||
|
|
||
| Wenn Ihr Speicherbedarf wächst, möchten Sie vielleicht Ihren Cache-Pool durch das Hinzufügen zusätzlicher Festplatten erweitern. Dieser Prozess ermöglicht Ihnen, sowohl die Kapazität als auch die Leistung zu erhöhen und gleichzeitig den Datenschutz durch RAID-Konfigurationen zu gewährleisten. | ||
| Um eine Festplatte zu einem %%BTRFS|btrfs%%-Pool hinzuzufügen: |
Contributor
There was a problem hiding this comment.
Bullet-point text incorrectly used as H2 heading.
Line 104 uses a bullet-point description as a section heading:
## **Verhinderung von versehentlichem Verlust:** Reduzieren Sie das Risiko von Datenverlusten beim Formatieren oder Ersetzen von Geräten.
This was originally a list item (see line 58) and has been incorrectly promoted to a heading during the Crowdin sync. This will break the page's table of contents and section structure. It should be replaced with the intended heading (likely something like ## Festplatten zu einem Pool hinzufügen / "Adding disks to a pool").
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 104 - 106, The current H2 "## **Verhinderung von versehentlichem
Verlust:** Reduzieren Sie das Risiko von Datenverlusten beim Formatieren oder
Ersetzen von Geräten." was incorrectly promoted from a bullet and breaks the
TOC; replace this heading with the intended section title (e.g., "## Festplatten
zu einem Pool hinzufügen" or "## Hinzufügen von Festplatten zu einem Pool") and
restore the original bullet text as a list item where it belongs (the
descriptive sentence currently following the heading "Um eine Festplatte zu
einem %%BTRFS|btrfs%%-Pool hinzuzufügen:" should remain as supporting copy, not
the H2). Ensure the new H2 matches locale style and keeps the subsequent
instructional content under it.
Comment on lines
+178
to
+190
| :::tip[Optimizing 硬盘数量 | ||
|
|
||
| 这提供了两个主要优点： | ||
|
|
||
| **优化配置示例：** | ||
|
|
||
| - **RAIDZ1**: 3、5 或 9 个硬盘（数据盘 = 2、4 或 8） | ||
| - **RAIDZ2**: 4、6 或 10 个硬盘（数据盘 = 2、4 或 8） | ||
| - **RAIDZ3**: 5、9 或 17 个硬盘（数据盘 = 2、6 或 14） | ||
|
|
||
| 请注意，这些优化是可选的 - 上述建议适用于大多数使用情况。 | ||
|
|
||
| ::: |
Contributor
There was a problem hiding this comment.
Malformed admonition title — missing closing ] will cause an MDX parse error.
Line 178 reads :::tip[Optimizing 硬盘数量 without a closing bracket. Docusaurus MDX requires the syntax :::tip[Title]. This will either fail to parse or render the entire tip body as raw text.
🛠️ Proposed fix
-:::tip[Optimizing 硬盘数量
+:::tip[Optimizing 硬盘数量]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| :::tip[Optimizing 硬盘数量 | |
| 这提供了两个主要优点： | |
| **优化配置示例：** | |
| - **RAIDZ1**: 3、5 或 9 个硬盘（数据盘 = 2、4 或 8） | |
| - **RAIDZ2**: 4、6 或 10 个硬盘（数据盘 = 2、4 或 8） | |
| - **RAIDZ3**: 5、9 或 17 个硬盘（数据盘 = 2、6 或 14） | |
| 请注意，这些优化是可选的 - 上述建议适用于大多数使用情况。 | |
| ::: | |
| :::tip[Optimizing 硬盘数量] | |
| 这提供了两个主要优点： | |
| **优化配置示例：** | |
| - **RAIDZ1**: 3、5 或 9 个硬盘（数据盘 = 2、4 或 8） | |
| - **RAIDZ2**: 4、6 或 10 个硬盘（数据盘 = 2、4 或 8） | |
| - **RAIDZ3**: 5、9 或 17 个硬盘（数据盘 = 2、6 或 14） | |
| 请注意，这些优化是可选的 - 上述建议适用于大多数使用情况。 | |
| ::: |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`
around lines 178 - 190, The admonition opening token `:::tip[Optimizing 硬盘数量` is
missing the closing bracket and will break MDX parsing; update the admonition
header by adding the closing `]` so it reads `:::tip[Optimizing 硬盘数量]` (preserve
the existing content block and closing `:::`) to restore a valid Docusaurus MDX
admonition.
Comment on lines
+65
to
+67
| :::注意 在你替换之前 | ||
|
|
||
| 在更换当前闪存设备之前，请考虑检查其错误： | ||
| :::note 在你替换之前 |
Contributor
There was a problem hiding this comment.
Duplicate admonition opener — :::注意 is invalid syntax.
Line 65 uses :::注意 在你替换之前 which is not a valid Docusaurus admonition type, immediately followed by the valid :::note 在你替换之前 on Line 67. The :::注意 line should be removed.
Proposed fix
-:::注意 在你替换之前
-
:::note 在你替换之前📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| :::注意 在你替换之前 | |
| 在更换当前闪存设备之前，请考虑检查其错误： | |
| :::note 在你替换之前 | |
| :::note 在你替换之前 |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx`
around lines 65 - 67, Remove the invalid duplicate admonition opener by deleting
the line that reads ":::注意 在你替换之前" so only the valid admonition ":::note 在你替换之前"
remains; ensure there are no extra blank lines or duplicate openers around the
remaining ":::note 在你替换之前" block.
| --- | ||
|
|
||
| ## 重新格式化缓存驱动器 {#creating-a-file-system-formatting} | ||
| ## 重新格式化缓存驱动器 |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Search for cross-file references to the removed anchors
rg -n "reformatting-cache-drives|reformatting.cache|converting-to-a-new-file-system|converting.to.new.file" \
--type-add 'mdx:*.mdx' --type mdx --type md -C2Repository: unraid/docs
Length of output: 18366
Cross-document links to removed anchor found—these links are now broken.
The anchor #converting-to-a-new-file-system-type (from line 187, ## 转换到新的文件系统类型) is still being referenced by multiple documents across the repository:
docs/unraid-os/system-administration/secure-your-server/securing-your-data.mdxdocs/unraid-os/release-notes/7.0.0.md,7.2.0.md,7.2.1.mdi18n/zh/,i18n/fr/,i18n/es/,i18n/de/localized versions of the above
No references to #reformatting-cache-drives (from line 140) were found. Restore line 187 or update all cross-document links pointing to the file-systems page.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`
at line 140, The cross-document links reference the removed anchor
`#converting-to-a-new-file-system-type` (heading "## 转换到新的文件系统类型") but the file
now only contains "## 重新格式化缓存驱动器" (anchor `#reformatting-cache-drives`),
breaking links; either restore the original heading/anchor "## 转换到新的文件系统类型"
(re-add the section or its anchor ID in the file-systems.mdx) or update every
external reference (in files listed like securing-your-data.mdx and the release
notes and their i18n counterparts) to point to the new anchor
(`#reformatting-cache-drives`) so all cross-document links resolve.
| --- | ||
|
|
||
| ## 更改文件系统类型 {#changing-a-file-system-type} | ||
| ## 更改文件系统类型 |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, verify the file exists and get its size
wc -l "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx"Repository: unraid/docs
Length of output: 163
🏁 Script executed:
# Read the file to check the relevant lines
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '85,100p'Repository: unraid/docs
Length of output: 634
🏁 Script executed:
# Check line 102 (link change)
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '95,110p'Repository: unraid/docs
Length of output: 771
🏁 Script executed:
# Check line 163 (anchor removed) and surrounding context
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '158,168p'Repository: unraid/docs
Length of output: 194
🏁 Script executed:
# Check line 230 (reference to removed anchor)
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '225,235p'Repository: unraid/docs
Length of output: 377
🏁 Script executed:
# Check line 410 (anchor removed)
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '405,415p'Repository: unraid/docs
Length of output: 570
🏁 Script executed:
# Check line 93 (reference to removed anchor)
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '88,98p'Repository: unraid/docs
Length of output: 478
🏁 Script executed:
# Check line 433 (anchor removed)
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '428,438p'Repository: unraid/docs
Length of output: 314
🏁 Script executed:
# Check line 451 (reference to removed anchor) and line 483 (duplicate heading)
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '446,456p'Repository: unraid/docs
Length of output: 413
🏁 Script executed:
# Check for duplicate heading around line 483
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '478,488p'Repository: unraid/docs
Length of output: 302
🏁 Script executed:
# Search for cross-file references to the removed anchors across the entire codebase
rg -n "changing-a-file-system-type|using-the-unassigned-devices-plugins|checking-a-file-system" \
--type-add 'mdx:*.mdx' --type mdx --type mdRepository: unraid/docs
Length of output: 3662
🏁 Script executed:
# Verify the cache-pools.mdx file exists and check for btrfs-pools anchor
find . -name "cache-pools.mdx" -type fRepository: unraid/docs
Length of output: 542
Anchor removal breaks three intra-document links.
The explicit English anchors removed from these three headings are still referenced within this file:
| Removed anchor (heading line) | Broken link (referencing line) |
|---|---|
{#changing-a-file-system-type} on line 163 |
[更改文件系统类型](#changing-a-file-system-type) at line 230 |
{#using-the-unassigned-devices-plugins} on line 410 |
[Unassigned Devices](#using-the-unassigned-devices-plugins) at line 93 |
{#checking-a-file-system} on line 433 |
[文件系统检查](#checking-a-file-system) at line 451 |
After removal, Docusaurus will auto-generate IDs from the Chinese heading text (URL-encoded), so none of the three English-slug links will resolve. Additionally, ### 检查文件系统 appears twice—at line 433 (changed) and line 483 (unchanged). Without the explicit anchor on line 433, Docusaurus will auto-deduplicate them as #检查文件系统 and #检查文件系统-1, making it impossible for the link at line 451 to reliably reach the intended section.
Restore the explicit English anchors on all three headings:
🐛 Proposed fix — restore removed anchors
-## 更改文件系统类型
+## 更改文件系统类型 {`#changing-a-file-system-type`}-### 使用未分配设备插件
+### 使用未分配设备插件 {`#using-the-unassigned-devices-plugins`}-### 检查文件系统
+### 检查文件系统 {`#checking-a-file-system`}Also applies to: 410-410, 433-433
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`
at line 163, Restore the three explicit English anchors that were removed so
existing intra-document links keep working: re-add the anchor tokens
{`#changing-a-file-system-type`}, {`#using-the-unassigned-devices-plugins`}, and
{`#checking-a-file-system`} to their respective headings (the "更改文件系统类型",
"Unassigned Devices" heading, and the first "检查文件系统" heading) so links like
[更改文件系统类型](`#changing-a-file-system-type`), [Unassigned
Devices](`#using-the-unassigned-devices-plugins`), and
[文件系统检查](`#checking-a-file-system`) resolve correctly and avoid Docusaurus
auto-deduplication.
| --- | ||
|
|
||
| ### 分配方法 {#allocation-method} | ||
| ### 分配方法 |
Contributor
There was a problem hiding this comment.
Removing explicit anchors breaks existing internal fragment links.
{#allocation-method} (line 283) and {#split-level} (line 362) are referenced by explicit #allocation-method and #split-level fragment links on lines 100 and 101 respectively. After removal, Docusaurus generates slugs from the Chinese header text (e.g., #分配方法, #分级水平), which no longer match those link targets.
🐛 Restore the explicit anchors
-### 分配方法
+### 分配方法 {`#allocation-method`}-### 分级水平
+### 分级水平 {`#split-level`}Also applies to: 362-362
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx`
at line 283, Restore the explicit anchor IDs so existing internal fragment links
keep working: re-add the anchor tokens {`#allocation-method`} and {`#split-level`}
to their corresponding headers (the "分配方法" and "分级水平" headers) so the internal
links referencing `#allocation-method` and `#split-level` resolve correctly; ensure
the header lines include those exact anchor IDs immediately after the header
text.
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
unraid-docs | 0cd52c8 | Mar 21 2026, 01:14 PM |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 9
Note
Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx (1)
153-168:⚠️ Potential issue | 🟠 MajorThe Docker/VM WiFi guidance was replaced with duplicated Tailscale copy.
The block under
###### Docker-Container/###### Virtuelle Maschinennow describes the Tailscale settings page twice, even though Line 147 points readers here for WiFi-specific Docker/VM caveats. Please restore Docker/VM guidance in this section.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx` around lines 153 - 168, Replace the duplicated Tailscale caution that was accidentally inserted under the headings "###### Docker-Container" and "###### Virtuelle Maschinen" with the original Docker/VM WiFi-specific guidance: under "###### Docker-Container" restore the three WiFi caveats (when WiFi is enabled the system uses ipvlan and macvlan is not supported; disable Host access for custom networks in Settings → Docker; container network type must not be br0, bond0 or eth0), and under "###### Virtuelle Maschinen" restore the original VM WiFi-specific caveat text that was present before the duplication (i.e., the note referencing WiFi-related network limitations for VMs rather than the Tailscale settings description). Ensure the Tailscale explanation remains only in the dedicated Tailscale section and not duplicated here.
♻️ Duplicate comments (4)
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx (1)
98-99:⚠️ Potential issue | 🔴 CriticalRemove the orphaned
:::on Line 99.Line 97 already closes the
:::infoblock, so the standalone:::on Line 99 leaves the MDX admonition structure unbalanced and can break rendering or the docs build.🐛 Proposed fix
::: -:::Use this read-only check to confirm the extra marker is still present. Expect directive markers on Line 94 (
:::info), Line 97 (:::), and Line 99 (:::); the Line 99 marker is the orphan.#!/bin/bash set -euo pipefail FILE='i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx' printf 'Context around the closing admonition:\n' sed -n '94,100p' "$FILE" | cat -n printf '\nDirective markers in that span:\n' python - <<'PY' from pathlib import Path path = Path("i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx") lines = path.read_text(encoding="utf-8").splitlines() for lineno in range(94, 101): text = lines[lineno - 1].strip() if text.startswith(":::"): print(f"{lineno}: {text!r}") PY🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx` around lines 98 - 99, There is an orphaned closing admonition marker (":::") after the already-closed ":::info" block; open the file and remove the standalone "::: " marker (the extra closing directive that follows the ":::info" / "::: " pair) so the admonition structure is balanced—search for the ":::info" block and delete the subsequent lone ":::".i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx (3)
74-74:⚠️ Potential issue | 🟠 MajorTranslate the remaining synced English paragraphs on this German page.
Line 74 and Line 226 are still English, so the article switches language mid-section. Please replace both paragraphs with German while preserving the MDX tokens and link target.
Also applies to: 226-226
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx` at line 74, Replace the two leftover English paragraphs (the sentence containing "You can configure various access settings..." with MDX tokens %%SSH|ssh%%, %%SSL|ssl%%/%%TLS|tls%%, %%WebGUI|web-gui%% and the link to [Securing your connection](../../system-administration/secure-your-server/securing-your-connection.mdx) at lines 74 and 226) with their German translations while preserving all MDX tokens and the exact link target; ensure tokens remain unchanged (e.g., %%SSH|ssh%%, %%SSL|ssl%%, %%TLS|tls%%, %%WebGUI|web-gui%%) and the relative link path stays identical.
170-186:⚠️ Potential issue | 🟠 Major
Virtuelle MaschinenandBestätigungenare still mapped to the wrong content.Line 172 is the Power Mode description, not VM settings, and Line 182 is user-share copy under
### Bestätigungen. The repeatedsettings-powermode.pngscreenshot on Lines 184-186 confirms this block is still mis-synced.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx` around lines 170 - 186, The headings "### Virtuelle Maschinen" and "### Bestätigungen" are mismatched with their paragraph content and duplicated screenshot; move the Power Mode paragraph (currently under "### Virtuelle Maschinen" and referencing Power Mode) into a correctly named "### Leistungsmodus" (or rename the heading at that block) and replace the VM networking reference (%%VM|vm%% link) with the appropriate topic for Power Mode; then move the user-share paragraph (the text about %%User shares|user-share%% and disk inclusion/exclusion) under "### Bestätigungen" and ensure its screenshot points to the correct image (replace the duplicated /img/settings-powermode.png with the user-share screenshot path). Ensure the headings "### Virtuelle Maschinen" contains VM-specific content and links (e.g., the %%VM|vm%% networking link) and that image files correspond to each section.
188-222:⚠️ Potential issue | 🟠 MajorThis block still mixes console, network-services/NFS, and SMB content under unrelated headings.
### Bestätigungen {#ups-settings}contains console settings, theBenachrichtigungseinstellungenblock contains Network Services/NFS copy, and### Benutzerprogrammeshows an SMB screenshot while duplicating the later plugins text. Please realign headings, anchors, body copy, and images here before merging.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx` around lines 188 - 222, The content blocks are misaligned with their headings: move the console-related paragraph and the /img/settings-console.png block out of "### Bestätigungen {`#ups-settings`}" into a clearly labeled console/UPS settings section (or rename the heading to "Konsoleneinstellungen") and update the anchor; move the Network Services/NFS paragraph and the /img/settings-nfs.png into a "Network Services" or "NFS" section (replace the incorrect "## Benachrichtigungseinstellungen" heading), and ensure the NFS text references the correct tunable; place the SMB screenshot (/img/settings-smb.png) and the SMB-specific copy under an SMB/SMB-Einstellungen heading (not under "### Benutzerprogramme"); keep the plugins description (Community Applications, appdata backups, etc.) under "### Benutzerprogramme" only, remove duplicated or unrelated text, and ensure each image matches its section.
🟡 Minor comments (14)
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md-13-15 (1)
13-15:⚠️ Potential issue | 🟡 MinorTranslate English text to Spanish.
Lines 13 and 15 contain English text in a Spanish documentation file, which is inconsistent with the localization. These sentences should be translated to Spanish to maintain a fully localized experience for Spanish-speaking users.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md` around lines 13 - 15, Replace the two English sentences in the Spanish release notes with accurate Spanish translations: translate "See [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) for issues reported by other testers." and "ReiserFS is no longer supported in modern Linux kernels; you must migrate off ReiserFS before upgrading to this release. See [Converting to a new file system type](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) for details." into Spanish preserving the links and their markdown, and ensure phrasing matches the surrounding locale tone and terminology in this file (i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md).i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md-40-40 (1)
40-40:⚠️ Potential issue | 🟡 MinorTranslate English text to Spanish.
Line 40 contains English text ("To proactively switch to TPM-based licensing, see...") in a Spanish documentation file. This should be translated to Spanish for consistency.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md` at line 40, Replace the English sentence "To proactively switch to TPM-based licensing, see [How can I move from flash-based licensing to TPM-based licensing](../troubleshooting/tpm-licensing-faq.mdx#tpm)." with its Spanish translation, keeping the same link target and anchor; e.g., use "Para cambiar proactivamente a la licencia basada en TPM, consulte [¿Cómo puedo pasar de la licencia basada en flash a la licencia basada en TPM?](../troubleshooting/tpm-licensing-faq.mdx#tpm)." This updates the text in the string on the line containing that English sentence.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx-18-18 (1)
18-18:⚠️ Potential issue | 🟡 MinorAjustez l’article et la formulation pour un français plus naturel.
La phrase de la Line 18 (
dans le Unraid ...) est maladroite, et la Line 33 gagnerait en fluidité avec une minuscule après les deux-points.✏️ Proposition
-Vous utiliserez l’onglet **Principal** dans le Unraid %%WebGUI|web-gui%% pour assigner et vérifier les périphériques, y compris les affectations de %%array|array%% et de pool ainsi que tous les périphériques non assignés et votre périphérique de démarrage (clé USB par défaut). +Vous utiliserez l’onglet **Principal** dans l’interface %%WebGUI|web-gui%% d’Unraid pour assigner et vérifier les périphériques, y compris les affectations de %%array|array%% et de pool ainsi que tous les périphériques non assignés et votre périphérique de démarrage (clé USB par défaut). -- **Périphérique de démarrage :** Le périphérique contenant Unraid OS (clé USB par défaut), qui démarre votre serveur. +- **Périphérique de démarrage :** le périphérique contenant Unraid OS (clé USB par défaut), qui démarre votre serveur.Also applies to: 33-33
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx` at line 18, The French sentence starting "Vous utiliserez l’onglet **Principal** dans le Unraid %%WebGUI|web-gui%% ..." is awkward; reword it for natural French and smooth flow (e.g. use "Dans la WebGUI d'Unraid, onglet **Principal**, vous pouvez..." or similar) and ensure consistent spacing/typography around "Unraid" and the %%shortcodes%%. Also change the text at the later occurrence after a colon to start with a lowercase letter (make the first character after ":" lowercase) to improve flow. Update the lines containing the sentence beginning with "Vous utiliserez l’onglet **Principal**..." and the corresponding line after the colon so both read naturally and consistently.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx-18-18 (1)
18-18:⚠️ Potential issue | 🟡 MinorTranslate the new source strings before merging.
Line 18 and Line 32 add English copy to the zh locale, and Line 18 also reverts the UI label to
Maininstead of主页面. Please localize both additions so this page stays consistent with the Simplified Chinese UI and the rest of the document.💬 Suggested wording
-You’ll use the **Main** tab in the Unraid %%WebGUI|web-gui%% to assign and review devices, including %%array|array%% and pool assignments along with any unassigned devices and your boot device (USB flash by default). +您将在 Unraid %%WebGUI|web-gui%% 的**主页面**选项卡中分配并查看设备，包括 %%array|array%% 和池设备分配、任何未分配设备以及您的**启动设备**（默认为 USB 闪存设备）。 -- **Boot Device:** The device containing Unraid OS (USB flash by default), which starts your server. +- **启动设备：** 包含 Unraid OS 的设备（默认为 USB 闪存设备），用于启动您的服务器。Based on learnings, 在Unraid简体中文界面中，
Main标签页/按钮被翻译为主页面，中文文档应使用主页面而非英文Main以保持与实际用户界面的一致性。Also applies to: 32-32
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx` at line 18, Replace the newly added English strings with their Simplified Chinese equivalents: change the UI label "Main" back to "主页面" wherever it appears (e.g., the phrase "You’ll use the **Main** tab..."), and localize the other English additions including the "%%WebGUI|web-gui%%" and "%%array|array%%" annotated tokens so the sentence reads naturally in Chinese and matches the Simplified Chinese UI; ensure both additions (the one containing "Main"/"主页面" and the other added at the same commit) are translated consistently with the rest of the document.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx-294-296 (1)
294-296:⚠️ Potential issue | 🟡 MinorRemove the duplicated notifications intro paragraph.
Line 296 repeats Line 294 verbatim, so this section renders the same introduction twice.
✂️ Proposed cleanup
### Benachrichtigungseinstellungen Unraid kann Ihnen Benachrichtigungen über wichtige Systemereignisse, Aktualisierungen und Warnungen über Ihren Browser, per E-Mail oder über Drittanbieter-Benachrichtigungsdienste senden. Die Seite für Benachrichtigungseinstellungen ermöglicht es Ihnen, zu steuern, wie und wann Sie diese Benachrichtigungen erhalten. - -Unraid kann Ihnen Benachrichtigungen über wichtige Systemereignisse, Aktualisierungen und Warnungen über Ihren Browser, per E-Mail oder über Drittanbieter-Benachrichtigungsdienste senden. Die Seite für Benachrichtigungseinstellungen ermöglicht es Ihnen, zu steuern, wie und wann Sie diese Benachrichtigungen erhalten.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx` around lines 294 - 296, Remove the duplicated notification-intro paragraph in the MDX content: locate the repeated German paragraph "Unraid kann Ihnen Benachrichtigungen über wichtige Systemereignisse, Aktualisierungen und Warnungen über Ihren Browser, per E-Mail oder über Drittanbieter-Benachrichtigungsdienste senden. Die Seite für Benachrichtigungseinstellungen ermöglicht es Ihnen, zu steuern, wie und wann Sie diese Benachrichtigungen erhalten." and delete the second occurrence so the section contains the paragraph only once.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx-85-85 (1)
85-85:⚠️ Potential issue | 🟡 MinorTranslate the onboarding FAQ callouts.
The new onboarding flow still contains English helper copy in this German page.
Proposed fix
- If you have questions about device counts or mirrored boot, see the [Internal Boot FAQ](./internal-boot-faq.mdx). For TPM-based licensing questions, see the [TPM Licensing FAQ](../../troubleshooting/tpm-licensing-faq.mdx). + Wenn Sie Fragen zur Geräteanzahl oder zum gespiegelten Boot haben, lesen Sie die [FAQ zum internen Boot](./internal-boot-faq.mdx). Bei Fragen zur TPM-basierten Lizenzierung lesen Sie die [FAQ zur TPM-Lizenzierung](../../troubleshooting/tpm-licensing-faq.mdx). @@ -For internal boot questions, see the [Internal Boot FAQ](./internal-boot-faq.mdx). +Bei Fragen zum internen Boot lesen Sie die [FAQ zum internen Boot](./internal-boot-faq.mdx).Also applies to: 112-112
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` at line 85, The page still contains English helper link text "Internal Boot FAQ" and "TPM Licensing FAQ" — update those callouts to their German translations (e.g., "Interne Boot-FAQ" and "TPM-Lizenzierungs-FAQ" or your approved localized strings) in the markdown so the link labels are fully translated while keeping the existing hrefs (./internal-boot-faq.mdx and ../../troubleshooting/tpm-licensing-faq.mdx); apply the same change to the duplicate occurrence mentioned at lines 112-112.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx-83-83 (1)
83-83:⚠️ Potential issue | 🟡 MinorTranslate the onboarding FAQ callouts.
The new onboarding flow still contains English helper copy in this Spanish page.
Proposed fix
- If you have questions about device counts or mirrored boot, see the [Internal Boot FAQ](./internal-boot-faq.mdx). For TPM-based licensing questions, see the [TPM Licensing FAQ](../../troubleshooting/tpm-licensing-faq.mdx). + Si tienes preguntas sobre el número de dispositivos o el arranque en espejo, consulta la [FAQ sobre arranque interno](./internal-boot-faq.mdx). Para preguntas sobre licencias basadas en TPM, consulta la [FAQ sobre licencias TPM](../../troubleshooting/tpm-licensing-faq.mdx). @@ -For internal boot questions, see the [Internal Boot FAQ](./internal-boot-faq.mdx). +Para preguntas sobre arranque interno, consulta la [FAQ sobre arranque interno](./internal-boot-faq.mdx).Also applies to: 110-110
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` at line 83, Replace the English helper copy on the Spanish page by translating the sentence "If you have questions about device counts or mirrored boot, see the [Internal Boot FAQ](./internal-boot-faq.mdx). For TPM-based licensing questions, see the [TPM Licensing FAQ](../../troubleshooting/tpm-licensing-faq.mdx)." into Spanish, keeping the same link targets and markdown structure; ensure the translated string replaces the original in deploy-and-configure-unraid-os.mdx and also update the other occurrence referenced ("Also applies to: 110-110") so both instances use the Spanish translation.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx-83-83 (1)
83-83:⚠️ Potential issue | 🟡 MinorTranslate the onboarding FAQ callouts.
The new onboarding flow still contains English helper copy in this French page.
Proposed fix
- If you have questions about device counts or mirrored boot, see the [Internal Boot FAQ](./internal-boot-faq.mdx). For TPM-based licensing questions, see the [TPM Licensing FAQ](../../troubleshooting/tpm-licensing-faq.mdx). + Si vous avez des questions sur le nombre d’appareils ou le démarrage en miroir, consultez la [FAQ sur le démarrage interne](./internal-boot-faq.mdx). Pour les questions sur les licences basées sur le TPM, consultez la [FAQ sur les licences TPM](../../troubleshooting/tpm-licensing-faq.mdx). @@ -For internal boot questions, see the [Internal Boot FAQ](./internal-boot-faq.mdx). +Pour les questions sur le démarrage interne, consultez la [FAQ sur le démarrage interne](./internal-boot-faq.mdx).Also applies to: 110-110
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` at line 83, The French page still contains English helper copy in the onboarding FAQ callouts: replace the English sentence "If you have questions about device counts or mirrored boot, see the [Internal Boot FAQ](./internal-boot-faq.mdx). For TPM-based licensing questions, see the [TPM Licensing FAQ](../../troubleshooting/tpm-licensing-faq.mdx)." with a proper French translation, preserving the link targets and markdown link text (e.g., translate the visible text but keep ./internal-boot-faq.mdx and ../../troubleshooting/tpm-licensing-faq.mdx unchanged); ensure the translated wording appears in the same MDX file and update any identical occurrences referenced in the comment (the other instance at lines 110-110) so both callouts are translated consistently.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx-112-128 (1)
112-128:⚠️ Potential issue | 🟡 MinorGive the license flow its own section title.
This block is about obtaining a license key, not BIOS settings. Keeping it under
## Recomendaciones para el BIOSleaves the page with two top-level sections of the same name.Proposed fix
-## Recomendaciones para el BIOS +## Obtén una clave de licencia Inicia sesión en tu cuenta de Unraid.net para obtener una clave de licencia:🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 112 - 128, The license acquisition steps are under the wrong heading "## Recomendaciones para el BIOS"; create a new section header for the license flow (e.g., "## Obtener clave de licencia" or "## Obtener y gestionar la licencia") and move the entire block (the numbered steps plus the two image divs and the final explanatory sentence) out from under "## Recomendaciones para el BIOS" into that new section so the BIOS recommendations remain separate from the license/key instructions.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx-114-130 (1)
114-130:⚠️ Potential issue | 🟡 MinorGive the license flow its own section title.
This block is about obtaining a license key, not BIOS settings. Keeping it under
## BIOS-Empfehlungenleaves the page with two top-level sections of the same name.Proposed fix
-## BIOS-Empfehlungen +## Lizenzschlüssel erhalten Melden Sie sich bei Ihrem Unraid.net-Konto an, um einen Lizenzschlüssel zu erhalten:🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 114 - 130, The license key instructions are currently under the "## BIOS-Empfehlungen" header; create a new top-level section header (e.g., "## Lizenzschlüssel erhalten" or "## Lizenzschlüssel") and move the block that starts with "Melden Sie sich bei Ihrem Unraid.net-Konto..." (including the numbered steps and the two image divs) under that new header so the BIOS recommendations header only contains BIOS-related content and the license flow has its own clear section title.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx-112-128 (1)
112-128:⚠️ Potential issue | 🟡 MinorGive the license flow its own section title.
This block is about signing in for a license key, not BIOS configuration. Leaving it under
## Recommandations pour le BIOScreates two top-level sections with the same title and a misleading TOC entry.Proposed fix
-## Recommandations pour le BIOS +## Obtenir une clé de licence Connectez-vous à votre compte Unraid.net pour obtenir une clé de licence :🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 112 - 128, The license-signin block currently sits under the heading "## Recommandations pour le BIOS" which is misleading and duplicates a top-level section; create a new heading (e.g., "## Obtenir une clé de licence" or "## Connexion et licence") and move the entire block that starts with "Connectez-vous à votre compte Unraid.net pour obtenir une clé de licence :" (including the %%WebGUI|web-gui%% reference and the two image divs ![Commencer] and ![Installer clé d'essai]) under that new heading so the BIOS section only contains BIOS-related content and the TOC shows a separate License/Sign-in entry.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx-154-155 (1)
154-155:⚠️ Potential issue | 🟡 MinorLocalize the advanced BIOS checklist items.
These two new checklist lines are still in English inside an otherwise French section.
Proposed fix
-✅ Enable **%%hardware virtualization|hvm%%** features (e.g., **%%Intel VT-x|intel-vt-x%%** or **%%AMD-V|amd-v%%**) for **%%virtual machines (VMs)|vm%%**.\ -✅ Enable **%%IOMMU|iommu%%** support (Intel VT-d or AMD-Vi) for PCI device assignment to VMs. +✅ Activez les fonctionnalités de **%%virtualisation matérielle|hvm%%** (par ex. **%%Intel VT-x|intel-vt-x%%** ou **%%AMD-V|amd-v%%**) pour les **%%machines virtuelles (VM)|vm%%**.\ +✅ Activez la prise en charge **%%IOMMU|iommu%%** (Intel VT-d ou AMD-Vi) pour l’affectation de périphériques PCI aux VM.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 154 - 155, The two checklist items are left in English—localize them into French while preserving the MDX translation tokens and link keys: replace the line containing "%%hardware virtualization|hvm%%", "%%Intel VT-x|intel-vt-x%%", "%%AMD-V|amd-v%%" and "%%virtual machines (VMs)|vm%%" with a French translation (e.g., "Activez les fonctionnalités de %%hardware virtualization|hvm%% (par ex. %%Intel VT-x|intel-vt-x%% ou %%AMD-V|amd-v%%) pour les %%virtual machines (VMs)|vm%%.") and replace the line containing "%%IOMMU|iommu%%" (Intel VT-d / AMD-Vi) with a French version (e.g., "Activez le support %%IOMMU|iommu%% (Intel VT-d ou AMD-Vi) pour l'affectation PCI aux VM."); keep the exact bracketed translation keys intact and ensure punctuation/line breaks match surrounding checklist formatting.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx-114-114 (1)
114-114:⚠️ Potential issue | 🟡 MinorDuplicate
## BIOS 建议heading creates structure ambiguityThe same H2 appears at Line 114 and Line 138. Please keep one heading and rename the other section to reflect its actual topic (license-key flow vs BIOS checklist).
Also applies to: 138-138
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` at line 114, Two identical H2 headings "## BIOS 建议" appear twice; keep one as the BIOS section and rename the other to match its actual content (license-key flow vs BIOS checklist). Locate both "## BIOS 建议" headings in the document (the duplicates) and rename the one that describes the license key flow to something like "## 许可密钥流程" (or rename the checklist one to "## BIOS 检查清单" if more accurate), then update any internal anchors or cross-references that relied on the old heading to the new heading text.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx-124-124 (1)
124-124:⚠️ Potential issue | 🟡 MinorPrefer “账户” over “帐户” for consistency
Line 124 uses “帐户”; use “账户” to match common Simplified Chinese UI/document wording in this repo.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` at line 124, Replace the inconsistent Simplified Chinese wording "帐户" in the sentence "登录或创建帐户后，将自动安装试用密钥。" with "账户" so the line reads "登录或创建账户后，将自动安装试用密钥。" to match the repo's preferred terminology.
🧹 Nitpick comments (1)
i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx (1)
16-16: Précisez explicitement le périphérique ciblé dans l’étape de sauvegarde.La formulation actuelle peut se lire comme “n’importe quel périphérique”. Clarifier “périphérique de démarrage” évite l’ambiguïté.
✏️ Proposition
-Pour sauvegarder votre périphérique de démarrage, allez sur l'onglet **Principal**, sélectionnez le périphérique et cliquez sur **Sauvegarde du périphérique de démarrage**. +Pour sauvegarder votre périphérique de démarrage, allez sur l'onglet **Principal**, sélectionnez votre **périphérique de démarrage** et cliquez sur **Sauvegarde du périphérique de démarrage**.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx` at line 16, Update the sentence "Pour sauvegarder votre périphérique de démarrage, allez sur l'onglet **Principal**, sélectionnez le périphérique et cliquez sur **Sauvegarde du périphérique de démarrage**." to explicitly state which device to select by clarifying "sélectionnez le périphérique de démarrage (la clé USB/SSD contenant l'OS)" or similar; ensure the phrase "périphérique de démarrage" is unambiguous and replace the original sentence in the document so readers know to pick the boot device specifically.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Line 149: The checklist contains literal "\n" sequences that will render
instead of creating new lines; update the checklist block so each item is on its
own Markdown line (remove the escaped "\n" and place each bullet/✅ entry on its
own line) for the entries containing tokens like "%%AHCI|ahci%%",
"%%HBA-Modus|hba-mode%%" and "%%RAID|raid%%" (also fix the duplicate occurrence
around the second instance mentioned) so the items render as separate lines
rather than showing "\n".
- Around line 164-167: The new :::important block contains an English sentence
that wasn't localized; update that block by translating the English paragraph
("Many motherboards limit boot device selection to 12 hard drives... Configure
the BIOS to treat the flash drive as a removable device whenever possible.")
into German, preserving the existing second German paragraph about disabling INT
13h on HBAs and keeping the :::important admonition markup and paragraph
structure intact (so the warning reads fully in German and matches
tone/verbosity of the existing German text).
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Around line 13-15: Replace the remaining English sentences in the release
notes: the link line starting "See [Unraid OS Prerelease (Bugs &
Feedback)](https://product.unraid.net/b/unraid-os-prelease-bugs-feedback)" and
the warning beginning "ReiserFS is no longer supported in modern Linux kernels;
you must migrate off ReiserFS before upgrading to this release. See [Converting
to a new file system type]…" with German translations; for example use "Siehe
[Unraid OS Prerelease (Bugs &
Feedback)](https://product.unraid.net/b/unraid-os-prelease-bugs-feedback) für
von anderen Testern gemeldete Probleme." and "ReiserFS wird in modernen
Linux-Kerneln nicht mehr unterstützt; Sie müssen vor dem Upgrade auf diese
Version von ReiserFS migrieren. Siehe [Konvertieren zu einem neuen
Dateisystemtyp] für Details." Locate and update the exact strings "See [Unraid
OS Prerelease (Bugs & Feedback)](...)" and "ReiserFS is no longer supported in
modern Linux kernels; you must migrate off ReiserFS before upgrading to this
release. See [Converting to a new file system type](...)" in the file and
replace them with the German text to fully localize the i18n/de page.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Around line 147-152: Remove the literal "\n" sequences and fix the
mixed-language items in this checklist: replace the English lines beginning with
"Enable **%%hardware virtualization|hvm%%**" and "Enable **%%IOMMU|iommu%%**"
with Spanish equivalents and keep the same placeholder tokens (e.g., use
"Habilitar **%%hardware virtualization|hvm%%** ..." and "Habilitar
**%%IOMMU|iommu%%** ..."), and ensure all checklist items use the same checkbox
style (keep the existing ✅ markers and remove any stray backslashes). Apply the
same corrections to the repeated occurrence noted (line 158).
- Around line 162-165: The important-block contains an English warning left
untranslated; replace the English paragraph inside the :::important block with a
Spanish translation and keep the existing Spanish sentence that follows,
ensuring the block remains a single contiguous note. Locate the :::important
block (the text starting "Many motherboards limit boot device selection to 12
hard drives.") and change that English sentence to a natural Spanish equivalent
(e.g., "Muchas placas base limitan la selección de dispositivos de arranque a 12
discos duros. Si su unidad flash USB se reconoce como un disco duro, es posible
que no pueda arrancar desde ella después de instalar 12 discos duros físicos;
configure la BIOS para que trate la unidad flash como un dispositivo extraíble
siempre que sea posible.") and preserve the subsequent Spanish sentence about
disabling INT 13h support.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Line 51: The heading "Intégration" lost the `#onboarding` anchor referenced by
other pages; restore it by adding the onboarding id to that heading (e.g.,
update the heading node "## Intégration" to include the anchor id or add an
explicit anchor tag immediately before it so the URL
deploy-and-configure-unraid-os.mdx#onboarding resolves correctly).
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Around line 13-15: The French release notes still contain untranslated English
sections—translate the remaining English guidance into French, specifically the
paragraphs starting with "See [Unraid OS Prerelease (Bugs & Feedback)]…" and
"ReiserFS is no longer supported…" and any content under the Known issues and
Licensing headings (including the ReiserFS upgrade-blocking instructions);
update the French strings in this document and the corresponding "40-40"
variant, ensure links and anchor targets remain unchanged, and verify the
localized page renders fully in French.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Around line 149-150: The checklist contains literal "\n" sequences embedded in
the prose (e.g., the line with "设置 USB 闪存驱动器为主要启动设备" and the line containing
"%%AHCI|ahci%%", "%%HBA 模式|hba-mode%%", etc.); remove those literal "\n"
characters and replace them with actual Markdown list item line breaks so each
checklist entry is its own line (or properly formatted Markdown list), ensuring
the tokens like %%AHCI|ahci%% and %%hba-mode%% remain intact and the surrounding
punctuation/spacing is preserved.
- Line 12: The document deploy-and-configure-unraid-os.mdx contains large
English-only blocks in the Chinese locale; replace those English passages
(including the sentence referencing "Multi-language support" and the token
%%WebGUI|web-gui%%) with Chinese translations (or wrap them in the proper i18n
translation keys) so the page is fully localized, update any English
links/anchor text to Chinese equivalents, and run the i18n extraction/validation
to ensure no English strings remain in i18n/zh.
---
Outside diff comments:
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx`:
- Around line 153-168: Replace the duplicated Tailscale caution that was
accidentally inserted under the headings "###### Docker-Container" and "######
Virtuelle Maschinen" with the original Docker/VM WiFi-specific guidance: under
"###### Docker-Container" restore the three WiFi caveats (when WiFi is enabled
the system uses ipvlan and macvlan is not supported; disable Host access for
custom networks in Settings → Docker; container network type must not be br0,
bond0 or eth0), and under "###### Virtuelle Maschinen" restore the original VM
WiFi-specific caveat text that was present before the duplication (i.e., the
note referencing WiFi-related network limitations for VMs rather than the
Tailscale settings description). Ensure the Tailscale explanation remains only
in the dedicated Tailscale section and not duplicated here.
---
Minor comments:
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx`:
- Around line 294-296: Remove the duplicated notification-intro paragraph in the
MDX content: locate the repeated German paragraph "Unraid kann Ihnen
Benachrichtigungen über wichtige Systemereignisse, Aktualisierungen und
Warnungen über Ihren Browser, per E-Mail oder über
Drittanbieter-Benachrichtigungsdienste senden. Die Seite für
Benachrichtigungseinstellungen ermöglicht es Ihnen, zu steuern, wie und wann Sie
diese Benachrichtigungen erhalten." and delete the second occurrence so the
section contains the paragraph only once.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Line 85: The page still contains English helper link text "Internal Boot FAQ"
and "TPM Licensing FAQ" — update those callouts to their German translations
(e.g., "Interne Boot-FAQ" and "TPM-Lizenzierungs-FAQ" or your approved localized
strings) in the markdown so the link labels are fully translated while keeping
the existing hrefs (./internal-boot-faq.mdx and
../../troubleshooting/tpm-licensing-faq.mdx); apply the same change to the
duplicate occurrence mentioned at lines 112-112.
- Around line 114-130: The license key instructions are currently under the "##
BIOS-Empfehlungen" header; create a new top-level section header (e.g., "##
Lizenzschlüssel erhalten" or "## Lizenzschlüssel") and move the block that
starts with "Melden Sie sich bei Ihrem Unraid.net-Konto..." (including the
numbered steps and the two image divs) under that new header so the BIOS
recommendations header only contains BIOS-related content and the license flow
has its own clear section title.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Line 83: Replace the English helper copy on the Spanish page by translating
the sentence "If you have questions about device counts or mirrored boot, see
the [Internal Boot FAQ](./internal-boot-faq.mdx). For TPM-based licensing
questions, see the [TPM Licensing
FAQ](../../troubleshooting/tpm-licensing-faq.mdx)." into Spanish, keeping the
same link targets and markdown structure; ensure the translated string replaces
the original in deploy-and-configure-unraid-os.mdx and also update the other
occurrence referenced ("Also applies to: 110-110") so both instances use the
Spanish translation.
- Around line 112-128: The license acquisition steps are under the wrong heading
"## Recomendaciones para el BIOS"; create a new section header for the license
flow (e.g., "## Obtener clave de licencia" or "## Obtener y gestionar la
licencia") and move the entire block (the numbered steps plus the two image divs
and the final explanatory sentence) out from under "## Recomendaciones para el
BIOS" into that new section so the BIOS recommendations remain separate from the
license/key instructions.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Around line 13-15: Replace the two English sentences in the Spanish release
notes with accurate Spanish translations: translate "See [Unraid OS Prerelease
(Bugs &
Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) for
issues reported by other testers." and "ReiserFS is no longer supported in
modern Linux kernels; you must migrate off ReiserFS before upgrading to this
release. See [Converting to a new file system
type](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type)
for details." into Spanish preserving the links and their markdown, and ensure
phrasing matches the surrounding locale tone and terminology in this file
(i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md).
- Line 40: Replace the English sentence "To proactively switch to TPM-based
licensing, see [How can I move from flash-based licensing to TPM-based
licensing](../troubleshooting/tpm-licensing-faq.mdx#tpm)." with its Spanish
translation, keeping the same link target and anchor; e.g., use "Para cambiar
proactivamente a la licencia basada en TPM, consulte [¿Cómo puedo pasar de la
licencia basada en flash a la licencia basada en
TPM?](../troubleshooting/tpm-licensing-faq.mdx#tpm)." This updates the text in
the string on the line containing that English sentence.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx`:
- Line 18: The French sentence starting "Vous utiliserez l’onglet **Principal**
dans le Unraid %%WebGUI|web-gui%% ..." is awkward; reword it for natural French
and smooth flow (e.g. use "Dans la WebGUI d'Unraid, onglet **Principal**, vous
pouvez..." or similar) and ensure consistent spacing/typography around "Unraid"
and the %%shortcodes%%. Also change the text at the later occurrence after a
colon to start with a lowercase letter (make the first character after ":"
lowercase) to improve flow. Update the lines containing the sentence beginning
with "Vous utiliserez l’onglet **Principal**..." and the corresponding line
after the colon so both read naturally and consistently.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Line 83: The French page still contains English helper copy in the onboarding
FAQ callouts: replace the English sentence "If you have questions about device
counts or mirrored boot, see the [Internal Boot FAQ](./internal-boot-faq.mdx).
For TPM-based licensing questions, see the [TPM Licensing
FAQ](../../troubleshooting/tpm-licensing-faq.mdx)." with a proper French
translation, preserving the link targets and markdown link text (e.g., translate
the visible text but keep ./internal-boot-faq.mdx and
../../troubleshooting/tpm-licensing-faq.mdx unchanged); ensure the translated
wording appears in the same MDX file and update any identical occurrences
referenced in the comment (the other instance at lines 110-110) so both callouts
are translated consistently.
- Around line 112-128: The license-signin block currently sits under the heading
"## Recommandations pour le BIOS" which is misleading and duplicates a top-level
section; create a new heading (e.g., "## Obtenir une clé de licence" or "##
Connexion et licence") and move the entire block that starts with
"Connectez-vous à votre compte Unraid.net pour obtenir une clé de licence :"
(including the %%WebGUI|web-gui%% reference and the two image divs ![Commencer]
and ![Installer clé d'essai]) under that new heading so the BIOS section only
contains BIOS-related content and the TOC shows a separate License/Sign-in
entry.
- Around line 154-155: The two checklist items are left in English—localize them
into French while preserving the MDX translation tokens and link keys: replace
the line containing "%%hardware virtualization|hvm%%", "%%Intel
VT-x|intel-vt-x%%", "%%AMD-V|amd-v%%" and "%%virtual machines (VMs)|vm%%" with a
French translation (e.g., "Activez les fonctionnalités de %%hardware
virtualization|hvm%% (par ex. %%Intel VT-x|intel-vt-x%% ou %%AMD-V|amd-v%%) pour
les %%virtual machines (VMs)|vm%%.") and replace the line containing
"%%IOMMU|iommu%%" (Intel VT-d / AMD-Vi) with a French version (e.g., "Activez le
support %%IOMMU|iommu%% (Intel VT-d ou AMD-Vi) pour l'affectation PCI aux VM.");
keep the exact bracketed translation keys intact and ensure punctuation/line
breaks match surrounding checklist formatting.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx`:
- Line 18: Replace the newly added English strings with their Simplified Chinese
equivalents: change the UI label "Main" back to "主页面" wherever it appears (e.g.,
the phrase "You’ll use the **Main** tab..."), and localize the other English
additions including the "%%WebGUI|web-gui%%" and "%%array|array%%" annotated
tokens so the sentence reads naturally in Chinese and matches the Simplified
Chinese UI; ensure both additions (the one containing "Main"/"主页面" and the other
added at the same commit) are translated consistently with the rest of the
document.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Line 114: Two identical H2 headings "## BIOS 建议" appear twice; keep one as the
BIOS section and rename the other to match its actual content (license-key flow
vs BIOS checklist). Locate both "## BIOS 建议" headings in the document (the
duplicates) and rename the one that describes the license key flow to something
like "## 许可密钥流程" (or rename the checklist one to "## BIOS 检查清单" if more
accurate), then update any internal anchors or cross-references that relied on
the old heading to the new heading text.
- Line 124: Replace the inconsistent Simplified Chinese wording "帐户" in the
sentence "登录或创建帐户后，将自动安装试用密钥。" with "账户" so the line reads "登录或创建账户后，将自动安装试用密钥。"
to match the repo's preferred terminology.
---
Duplicate comments:
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx`:
- Line 74: Replace the two leftover English paragraphs (the sentence containing
"You can configure various access settings..." with MDX tokens %%SSH|ssh%%,
%%SSL|ssl%%/%%TLS|tls%%, %%WebGUI|web-gui%% and the link to [Securing your
connection](../../system-administration/secure-your-server/securing-your-connection.mdx)
at lines 74 and 226) with their German translations while preserving all MDX
tokens and the exact link target; ensure tokens remain unchanged (e.g.,
%%SSH|ssh%%, %%SSL|ssl%%, %%TLS|tls%%, %%WebGUI|web-gui%%) and the relative link
path stays identical.
- Around line 170-186: The headings "### Virtuelle Maschinen" and "###
Bestätigungen" are mismatched with their paragraph content and duplicated
screenshot; move the Power Mode paragraph (currently under "### Virtuelle
Maschinen" and referencing Power Mode) into a correctly named "###
Leistungsmodus" (or rename the heading at that block) and replace the VM
networking reference (%%VM|vm%% link) with the appropriate topic for Power Mode;
then move the user-share paragraph (the text about %%User shares|user-share%%
and disk inclusion/exclusion) under "### Bestätigungen" and ensure its
screenshot points to the correct image (replace the duplicated
/img/settings-powermode.png with the user-share screenshot path). Ensure the
headings "### Virtuelle Maschinen" contains VM-specific content and links (e.g.,
the %%VM|vm%% networking link) and that image files correspond to each section.
- Around line 188-222: The content blocks are misaligned with their headings:
move the console-related paragraph and the /img/settings-console.png block out
of "### Bestätigungen {`#ups-settings`}" into a clearly labeled console/UPS
settings section (or rename the heading to "Konsoleneinstellungen") and update
the anchor; move the Network Services/NFS paragraph and the
/img/settings-nfs.png into a "Network Services" or "NFS" section (replace the
incorrect "## Benachrichtigungseinstellungen" heading), and ensure the NFS text
references the correct tunable; place the SMB screenshot (/img/settings-smb.png)
and the SMB-specific copy under an SMB/SMB-Einstellungen heading (not under "###
Benutzerprogramme"); keep the plugins description (Community Applications,
appdata backups, etc.) under "### Benutzerprogramme" only, remove duplicated or
unrelated text, and ensure each image matches its section.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx`:
- Around line 98-99: There is an orphaned closing admonition marker (":::")
after the already-closed ":::info" block; open the file and remove the
standalone "::: " marker (the extra closing directive that follows the ":::info"
/ "::: " pair) so the admonition structure is balanced—search for the ":::info"
block and delete the subsequent lone ":::".
---
Nitpick comments:
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx`:
- Line 16: Update the sentence "Pour sauvegarder votre périphérique de
démarrage, allez sur l'onglet **Principal**, sélectionnez le périphérique et
cliquez sur **Sauvegarde du périphérique de démarrage**." to explicitly state
which device to select by clarifying "sélectionnez le périphérique de démarrage
(la clé USB/SSD contenant l'OS)" or similar; ensure the phrase "périphérique de
démarrage" is unambiguous and replace the original sentence in the document so
readers know to pick the boot device specifically.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 643f0bdf-586a-4542-bfbb-7b47b3ea2b21
📒 Files selected for processing (23)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
✅ Files skipped from review due to trivial changes (6)
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
- i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
- i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
🚧 Files skipped from review as they are similar to previous changes (2)
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx
| ### Grundlegende Einstellungen | ||
|
|
||
| ### Grundlegende Einstellungen | ||
| ✅ Stellen Sie das USB-Flash-Laufwerk als primäres Boot-Gerät ein.\n✅ Konfigurieren Sie den Speichercontroller im **%%AHCI|ahci%%**-Modus mit SATA-Verbindungen.\n✅ Stellen Sie den Controller auf **%%HBA-Modus|hba-mode%%** (nicht **%%RAID|raid%%**).\n✅ Deaktivieren Sie **Secure Boot**, da dies von Unraid OS nicht unterstützt wird. |
Contributor
There was a problem hiding this comment.
Fix the escaped newlines in the BIOS checklist.
The literal \n sequences will render on the page instead of breaking this checklist into separate lines.
Proposed fix
-✅ Stellen Sie das USB-Flash-Laufwerk als primäres Boot-Gerät ein.\n✅ Konfigurieren Sie den Speichercontroller im **%%AHCI|ahci%%**-Modus mit SATA-Verbindungen.\n✅ Stellen Sie den Controller auf **%%HBA-Modus|hba-mode%%** (nicht **%%RAID|raid%%**).\n✅ Deaktivieren Sie **Secure Boot**, da dies von Unraid OS nicht unterstützt wird.
+✅ Stellen Sie das USB-Flash-Laufwerk als primäres Boot-Gerät ein.\
+✅ Konfigurieren Sie den Speichercontroller im **%%AHCI|ahci%%**-Modus mit SATA-Verbindungen.\
+✅ Stellen Sie den Controller auf **%%HBA-Modus|hba-mode%%** (nicht **%%RAID|raid%%**).\
+✅ Deaktivieren Sie **Secure Boot**, da dies von Unraid OS nicht unterstützt wird.
@@
-✅ Passen Sie die Boot-Reihenfolge an: **Forced-FDD**, **USB-HDD**, **USB-ZIP**.\n✅ Deaktivieren Sie die USB 2.0/3.0-Unterstützung.\n✅ Schalten Sie alle Schnelles-Start-Funktionen um.\n✅ Schalten Sie die USB-Tastatur-Unterstützung um.
+✅ Passen Sie die Boot-Reihenfolge an: **Forced-FDD**, **USB-HDD**, **USB-ZIP**.\
+✅ Deaktivieren Sie die USB-2.0/3.0-Unterstützung.\
+✅ Schalten Sie alle Schnellstart-Funktionen um.\
+✅ Schalten Sie die USB-Tastatur-Unterstützung um.Also applies to: 160-160
🧰 Tools
🪛 LanguageTool
[grammar] ~149-~149: Hier könnte ein Fehler sein.
Context: ...sh-Laufwerk als primäres Boot-Gerät ein.\n✅ Konfigurieren Sie den Speichercontrolle...
(QB_NEW_DE)
[grammar] ~149-~149: Hier könnte ein Fehler sein.
Context: ...CI|ahci%%**-Modus mit SATA-Verbindungen.\n✅ Stellen Sie den Controller auf **%%HBA-...
(QB_NEW_DE)
[grammar] ~149-~149: Hier könnte ein Fehler sein.
Context: ...|hba-mode%%** (nicht %%RAID|raid%%).\n✅ Deaktivieren Sie Secure Boot, da di...
(QB_NEW_DE)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
at line 149, The checklist contains literal "\n" sequences that will render
instead of creating new lines; update the checklist block so each item is on its
own Markdown line (remove the escaped "\n" and place each bullet/✅ entry on its
own line) for the entries containing tokens like "%%AHCI|ahci%%",
"%%HBA-Modus|hba-mode%%" and "%%RAID|raid%%" (also fix the duplicate occurrence
around the second instance mentioned) so the items render as separate lines
rather than showing "\n".
Comment on lines
+164
to
+167
| :::important | ||
| Many motherboards limit boot device selection to 12 hard drives. If your USB flash drive is recognized as a hard drive, you may not be able to boot from it after installing 12 physical hard drives. Configure the BIOS to treat the flash drive as a removable device whenever possible. | ||
|
|
||
| :::important | ||
| Viele Mainboards beschränken die Auswahl der Boot-Geräte auf 12 Festplatten. Wenn Ihr USB-Flashlaufwerk als Festplatte erkannt wird, können Sie eventuell nicht davon starten, nachdem Sie 12 physische Festplatten installiert haben. Konfigurieren Sie das BIOS, um das Flashlaufwerk, soweit möglich, als Wechseldatenträger zu behandeln. | ||
| Wenn Sie einen zusätzlichen HBA verwenden, können Sie möglicherweise die INT 13h-Unterstützung deaktivieren, um zu verhindern, dass dessen angeschlossene Laufwerke in der Liste der bootfähigen Geräte erscheinen, was hilft, innerhalb der Grenze von 12 Laufwerken zu bleiben. |
Contributor
There was a problem hiding this comment.
Translate the BIOS warning block.
This new :::important note starts in English, so a high-importance troubleshooting warning is only partially localized.
Proposed fix
:::important
-Many motherboards limit boot device selection to 12 hard drives. If your USB flash drive is recognized as a hard drive, you may not be able to boot from it after installing 12 physical hard drives. Configure the BIOS to treat the flash drive as a removable device whenever possible.
+Viele Motherboards begrenzen die Auswahl des Boot-Geräts auf 12 Festplatten. Wenn Ihr USB-Flash-Laufwerk als Festplatte erkannt wird, können Sie nach dem Einbau von 12 physischen Festplatten möglicherweise nicht mehr davon booten. Konfigurieren Sie das BIOS nach Möglichkeit so, dass das Flash-Laufwerk als Wechseldatenträger behandelt wird.
-Wenn Sie einen zusätzlichen HBA verwenden, können Sie möglicherweise die INT 13h-Unterstützung deaktivieren, um zu verhindern, dass dessen angeschlossene Laufwerke in der Liste der bootfähigen Geräte erscheinen, was hilft, innerhalb der Grenze von 12 Laufwerken zu bleiben.
+Wenn Sie einen zusätzlichen HBA verwenden, können Sie die INT 13h-Unterstützung eventuell deaktivieren, damit dessen angeschlossene Laufwerke nicht in der Liste der bootfähigen Geräte erscheinen und Sie innerhalb der Grenze von 12 Laufwerken bleiben.
:::🧰 Tools
🪛 LanguageTool
[style] ~167-~167: Diese Formulierung ist möglicherweise redundant. Die Wörter „können“ und „möglicherweise“ drücken dasselbe aus.
Context: ... zusätzlichen HBA verwenden, können Sie möglicherweise die INT 13h-Unterstützung deaktivieren,...
(VERDOPPELUNG)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
around lines 164 - 167, The new :::important block contains an English sentence
that wasn't localized; update that block by translating the English paragraph
("Many motherboards limit boot device selection to 12 hard drives... Configure
the BIOS to treat the flash drive as a removable device whenever possible.")
into German, preserving the existing second German paragraph about disabling INT
13h on HBAs and keeping the :::important admonition markup and paragraph
structure intact (so the warning reads fully in German and matches
tone/verbosity of the existing German text).
Comment on lines
+13
to
+15
| See [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) for issues reported by other testers. | ||
|
|
||
| ReiserFS is no longer supported in modern Linux kernels; you must migrate off ReiserFS before upgrading to this release. See [Converting to a new file system type](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) for details. |
Contributor
There was a problem hiding this comment.
Untranslated English content in German release notes
Line 13, Line 15, and Line 40 are still English. Please translate these to German to keep the i18n/de page fully localized.
Also applies to: 40-40
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`
around lines 13 - 15, Replace the remaining English sentences in the release
notes: the link line starting "See [Unraid OS Prerelease (Bugs &
Feedback)](https://product.unraid.net/b/unraid-os-prelease-bugs-feedback)" and
the warning beginning "ReiserFS is no longer supported in modern Linux kernels;
you must migrate off ReiserFS before upgrading to this release. See [Converting
to a new file system type]…" with German translations; for example use "Siehe
[Unraid OS Prerelease (Bugs &
Feedback)](https://product.unraid.net/b/unraid-os-prelease-bugs-feedback) für
von anderen Testern gemeldete Probleme." and "ReiserFS wird in modernen
Linux-Kerneln nicht mehr unterstützt; Sie müssen vor dem Upgrade auf diese
Version von ReiserFS migrieren. Siehe [Konvertieren zu einem neuen
Dateisystemtyp] für Details." Locate and update the exact strings "See [Unraid
OS Prerelease (Bugs & Feedback)](...)" and "ReiserFS is no longer supported in
modern Linux kernels; you must migrate off ReiserFS before upgrading to this
release. See [Converting to a new file system type](...)" in the file and
replace them with the German text to fully localize the i18n/de page.
Comment on lines
+147
to
+152
| ✅ Establecer el dispositivo de arranque primario en la unidad flash USB.\n✅ Configurar el controlador de almacenamiento al modo **%%AHCI|ahci%%** con conexiones SATA.\n✅ Configurar el controlador en modo **%%HBA|hba-mode%%** (no **%%RAID|raid%%**).\n✅ Desactivar **Arranque Seguro** ya que no es compatible con Unraid OS. | ||
|
|
||
| ✅ Establecer el dispositivo de arranque primario en la unidad flash USB.\n✅ Configurar el controlador de almacenamiento al modo **%%AHCI|ahci%%** con conexiones SATA.\n✅ Configurar el controlador en modo **%%HBA|hba-mode%%** (no **%%RAID|raid%%**).\n✅ Desactivar **Arranque Seguro** ya que no es compatible con Unraid OS. | ||
| ### Configuraciones Avanzadas | ||
|
|
||
| ### Configuraciones Avanzadas | ||
| ✅ Enable **%%hardware virtualization|hvm%%** features (e.g., **%%Intel VT-x|intel-vt-x%%** or **%%AMD-V|amd-v%%**) for **%%virtual machines (VMs)|vm%%**.\ | ||
| ✅ Enable **%%IOMMU|iommu%%** support (Intel VT-d or AMD-Vi) for PCI device assignment to VMs. |
Contributor
There was a problem hiding this comment.
Fix the checklist formatting and leftover English in this block.
The literal \n sequences will render verbatim, and the advanced BIOS items are still English.
Proposed fix
-✅ Establecer el dispositivo de arranque primario en la unidad flash USB.\n✅ Configurar el controlador de almacenamiento al modo **%%AHCI|ahci%%** con conexiones SATA.\n✅ Configurar el controlador en modo **%%HBA|hba-mode%%** (no **%%RAID|raid%%**).\n✅ Desactivar **Arranque Seguro** ya que no es compatible con Unraid OS.
+✅ Establece la unidad flash USB como dispositivo de arranque principal.\
+✅ Configura el controlador de almacenamiento en modo **%%AHCI|ahci%%** con conexiones SATA.\
+✅ Configura el controlador en modo **%%HBA|hba-mode%%** (no **%%RAID|raid%%**).\
+✅ Desactiva **Arranque Seguro**, ya que no es compatible con Unraid OS.
@@
-✅ Enable **%%hardware virtualization|hvm%%** features (e.g., **%%Intel VT-x|intel-vt-x%%** or **%%AMD-V|amd-v%%**) for **%%virtual machines (VMs)|vm%%**.\
-✅ Enable **%%IOMMU|iommu%%** support (Intel VT-d or AMD-Vi) for PCI device assignment to VMs.
+✅ Habilita las funciones de **%%virtualización de hardware|hvm%%** (por ejemplo, **%%Intel VT-x|intel-vt-x%%** o **%%AMD-V|amd-v%%**) para las **%%máquinas virtuales (VM)|vm%%**.\
+✅ Habilita la compatibilidad con **%%IOMMU|iommu%%** (Intel VT-d o AMD-Vi) para asignar dispositivos PCI a las VM.
@@
-✅ Ajustar el orden de arranque a: **Forced-FDD**, **USB-HDD**, **USB-ZIP**.\n✅ Deshabilitar el soporte USB 2.0/3.0.\n✅ Alternar cualquier característica de Arranque Rápido.\n✅ Alternar el soporte para teclado USB.
+✅ Ajusta el orden de arranque a: **Forced-FDD**, **USB-HDD**, **USB-ZIP**.\
+✅ Deshabilita el soporte USB 2.0/3.0.\
+✅ Alterna cualquier función de Arranque Rápido.\
+✅ Alterna la compatibilidad con teclado USB.Also applies to: 158-158
🧰 Tools
🪛 LanguageTool
[grammar] ~147-~147: Aquí puede haber un error.
Context: ...rranque primario en la unidad flash USB.\n✅ Configurar el controlador de almacenami...
(QB_NEW_ES)
[grammar] ~147-~147: Aquí puede haber un error.
Context: ...o %%AHCI|ahci%% con conexiones SATA.\n✅ Configurar el controlador en modo **%%H...
(QB_NEW_ES)
[grammar] ~147-~147: Aquí puede haber un error.
Context: ...HBA|hba-mode%%** (no %%RAID|raid%%).\n✅ Desactivar Arranque Seguro ya que n...
(QB_NEW_ES)
[grammar] ~147-~147: Agrega un signo de puntuación.
Context: ...id%%**).\n✅ Desactivar Arranque Seguro ya que no es compatible con Unraid OS. ...
(QB_NEW_ES_OTHER_ERROR_IDS_MISSING_PUNCTUATION)
[grammar] ~149-~149: Corrige la mayúscula.
Context: ...ble con Unraid OS. ### Configuraciones Avanzadas ✅ Enable **%%hardware virtualization|hvm...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
around lines 147 - 152, Remove the literal "\n" sequences and fix the
mixed-language items in this checklist: replace the English lines beginning with
"Enable **%%hardware virtualization|hvm%%**" and "Enable **%%IOMMU|iommu%%**"
with Spanish equivalents and keep the same placeholder tokens (e.g., use
"Habilitar **%%hardware virtualization|hvm%%** ..." and "Habilitar
**%%IOMMU|iommu%%** ..."), and ensure all checklist items use the same checkbox
style (keep the existing ✅ markers and remove any stray backslashes). Apply the
same corrections to the repeated occurrence noted (line 158).
Comment on lines
+162
to
+165
| :::important | ||
| Many motherboards limit boot device selection to 12 hard drives. If your USB flash drive is recognized as a hard drive, you may not be able to boot from it after installing 12 physical hard drives. Configure the BIOS to treat the flash drive as a removable device whenever possible. | ||
|
|
||
| :::important | ||
| Muchas placas base limitan la selección de dispositivos de arranque a 12 discos duros. Si tu unidad flash USB se reconoce como disco duro, es posible que no puedas arrancar desde ella después de instalar 12 discos duros físicos. Configura la BIOS para tratar la unidad flash como un dispositivo extraíble siempre que sea posible. | ||
| Si utiliza un HBA adicional, es posible desactivar el soporte de INT 13h para evitar que sus unidades conectadas aparezcan en la lista de dispositivos de arranque; esto le ayudará a mantenerse dentro del límite de 12 discos. |
Contributor
There was a problem hiding this comment.
Translate the BIOS warning block.
This new :::important note starts in English, so a high-importance troubleshooting warning is only partially localized.
Proposed fix
:::important
-Many motherboards limit boot device selection to 12 hard drives. If your USB flash drive is recognized as a hard drive, you may not be able to boot from it after installing 12 physical hard drives. Configure the BIOS to treat the flash drive as a removable device whenever possible.
+Muchas placas base limitan la selección del dispositivo de arranque a 12 discos duros. Si tu unidad flash USB se reconoce como un disco duro, es posible que no puedas arrancar desde ella después de instalar 12 discos físicos. Configura el BIOS para tratar la unidad flash como un dispositivo extraíble siempre que sea posible.
-Si utiliza un HBA adicional, es posible desactivar el soporte de INT 13h para evitar que sus unidades conectadas aparezcan en la lista de dispositivos de arranque; esto le ayudará a mantenerse dentro del límite de 12 discos.
+Si usas un HBA adicional, quizá puedas desactivar el soporte de INT 13h para evitar que las unidades conectadas aparezcan en la lista de dispositivos de arranque; esto te ayudará a mantenerte dentro del límite de 12 discos.
:::🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
around lines 162 - 165, The important-block contains an English warning left
untranslated; replace the English paragraph inside the :::important block with a
Spanish translation and keep the existing Spanish sentence that follows,
ensuring the block remains a single contiguous note. Locate the :::important
block (the text starting "Many motherboards limit boot device selection to 12
hard drives.") and change that English sentence to a natural Spanish equivalent
(e.g., "Muchas placas base limitan la selección de dispositivos de arranque a 12
discos duros. Si su unidad flash USB se reconoce como un disco duro, es posible
que no pueda arrancar desde ella después de instalar 12 discos duros físicos;
configure la BIOS para que trate la unidad flash como un dispositivo extraíble
siempre que sea posible.") and preserve the subsequent Spanish sentence about
disabling INT 13h support.
|
|
||
| ::: | ||
|
|
||
| ## Intégration |
Contributor
There was a problem hiding this comment.
Restore the #onboarding anchor on this heading.
The new French release-notes page links here via deploy-and-configure-unraid-os.mdx#onboarding, but this heading no longer exposes that id.
Proposed fix
-## Intégration
+## Intégration {`#onboarding`}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ## Intégration | |
| ## Intégration {`#onboarding`} |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
at line 51, The heading "Intégration" lost the `#onboarding` anchor referenced by
other pages; restore it by adding the onboarding id to that heading (e.g.,
update the heading node "## Intégration" to include the anchor id or add an
explicit anchor tag immediately before it so the URL
deploy-and-configure-unraid-os.mdx#onboarding resolves correctly).
Comment on lines
+13
to
+15
| See [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) for issues reported by other testers. | ||
|
|
||
| ReiserFS is no longer supported in modern Linux kernels; you must migrate off ReiserFS before upgrading to this release. See [Converting to a new file system type](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) for details. |
Contributor
There was a problem hiding this comment.
Translate the remaining English release-note guidance.
The French page still switches back to English in the known-issues and licensing sections, including upgrade-blocking instructions about ReiserFS.
Proposed fix
-See [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) for issues reported by other testers.
+Consultez [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) pour les problèmes signalés par d’autres testeurs.
-ReiserFS is no longer supported in modern Linux kernels; you must migrate off ReiserFS before upgrading to this release. See [Converting to a new file system type](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) for details.
+ReiserFS n’est plus pris en charge par les noyaux Linux modernes ; vous devez migrer depuis ReiserFS avant de passer à cette version. Consultez [la section sur la conversion vers un nouveau type de système de fichiers](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) pour plus de détails.
@@
-To proactively switch to TPM-based licensing, see [How can I move from flash-based licensing to TPM-based licensing](../troubleshooting/tpm-licensing-faq.mdx#tpm).
+Pour passer de manière proactive à une licence basée sur le TPM, consultez [Comment passer d’une licence basée sur le flash à une licence basée sur le TPM](../troubleshooting/tpm-licensing-faq.mdx#tpm).Also applies to: 40-40
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`
around lines 13 - 15, The French release notes still contain untranslated
English sections—translate the remaining English guidance into French,
specifically the paragraphs starting with "See [Unraid OS Prerelease (Bugs &
Feedback)]…" and "ReiserFS is no longer supported…" and any content under the
Known issues and Licensing headings (including the ReiserFS upgrade-blocking
instructions); update the French strings in this document and the corresponding
"40-40" variant, ensure links and anchor targets remain unchanged, and verify
the localized page renders fully in French.
| :::info\[Localize] | ||
|
|
||
| 用户在配置语言设置后可能更易于遵循本指南。查看[多语言支持](../../using-unraid-to/customize-your-experience/multi-language-support.mdx)，以便在您偏爱的语言中让%%WebGUI|web-gui%%更易访问。 | ||
| It may be easier for users to follow this guide after configuring their language settings. Check out [Multi-language support](../../using-unraid-to/customize-your-experience/multi-language-support.mdx) to make the %%WebGUI|web-gui%% more accessible in your preferred language. |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Localization regression: Chinese page now contains large English-only blocks
Lines 12, 36, 51–113, 116–117, 134–135, and 165–167 are English in a i18n/zh document. This breaks locale consistency and Chinese-reader flow.
Also applies to: 36-36, 51-113, 116-117, 134-135, 165-167
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
at line 12, The document deploy-and-configure-unraid-os.mdx contains large
English-only blocks in the Chinese locale; replace those English passages
(including the sentence referencing "Multi-language support" and the token
%%WebGUI|web-gui%%) with Chinese translations (or wrap them in the proper i18n
translation keys) so the page is fully localized, update any English
links/anchor text to Chinese equivalents, and run the i18n extraction/validation
to ensure no English strings remain in i18n/zh.
Comment on lines
+149
to
150
| ✅ 设置 USB 闪存驱动器为主要启动设备。\n✅ 配置存储控制器为通过 SATA 连接的 **%%AHCI|ahci%%** 模式。\n✅ 将控制器设置为 **%%HBA 模式|hba-mode%%** （不是 **%%RAID|raid%%**）。\n✅ 禁用 **安全启动**，因为 Unraid OS 不支持此功能。 | ||
|
|
Contributor
There was a problem hiding this comment.
Literal \n escape sequences are embedded in checklist content
Line 149 and Line 160 include \n inside prose, which will render as raw text instead of intended line breaks/list items in Markdown.
Proposed fix
-✅ 设置 USB 闪存驱动器为主要启动设备。\n✅ 配置存储控制器为通过 SATA 连接的 **%%AHCI|ahci%%** 模式。\n✅ 将控制器设置为 **%%HBA 模式|hba-mode%%** （不是 **%%RAID|raid%%**）。\n✅ 禁用 **安全启动**，因为 Unraid OS 不支持此功能。
+✅ 设置 USB 闪存驱动器为主要启动设备。
+✅ 配置存储控制器为通过 SATA 连接的 **%%AHCI|ahci%%** 模式。
+✅ 将控制器设置为 **%%HBA 模式|hba-mode%%** （不是 **%%RAID|raid%%**）。
+✅ 禁用 **安全启动**，因为 Unraid OS 不支持此功能。
...
-✅ 调整启动顺序为：**Forced-FDD**、**USB-HDD**、**USB-ZIP**。\n✅ 禁用 USB 2.0/3.0 支持。\n✅ 切换任何快速启动功能。\n✅ 切换 USB 键盘支持。
+✅ 调整启动顺序为：**Forced-FDD**、**USB-HDD**、**USB-ZIP**。
+✅ 禁用 USB 2.0/3.0 支持。
+✅ 切换任何快速启动功能。
+✅ 切换 USB 键盘支持。Also applies to: 160-160
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
around lines 149 - 150, The checklist contains literal "\n" sequences embedded
in the prose (e.g., the line with "设置 USB 闪存驱动器为主要启动设备" and the line containing
"%%AHCI|ahci%%", "%%HBA 模式|hba-mode%%", etc.); remove those literal "\n"
characters and replace them with actual Markdown list item line breaks so each
checklist entry is its own line (or properly formatted Markdown list), ensuring
the tokens like %%AHCI|ahci%% and %%hba-mode%% remain intact and the surrounding
punctuation/spacing is preserved.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 12
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (3)
i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (1)
112-134:⚠️ Potential issue | 🔴 CriticalDuplicate heading and mismatched content.
This section is titled "Recommandations pour le BIOS" but describes how to obtain a license key by signing into Unraid.net. The same heading appears again at line 136 for the actual BIOS recommendations. This appears to be a copy/merge error.
Proposed fix
-## Recommandations pour le BIOS - -Connectez-vous à votre compte Unraid.net pour obtenir une clé de licence : +## Obtenir une clé de licence + +Connectez-vous à votre compte Unraid.net pour obtenir une clé de licence :🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 112 - 134, The "Recommandations pour le BIOS" heading is duplicated and currently contains unrelated license-key instructions (the %%WebGUI|web-gui%% steps and images Upc_get_started.png / Upc_install_trial_key.png); move the license key sign-in steps and images into the appropriate license/registration section (or change the heading to match the content), and restore the BIOS section so it only contains BIOS-specific recommendations; ensure the duplicate "Recommandations pour le BIOS" heading is removed or merged so the BIOS guidance appears once and the license steps appear under a correct "Licence / Enregistrement" heading.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (1)
8-8:⚠️ Potential issue | 🟡 MinorTranslate the introductory paragraph to Spanish.
This paragraph remains in English within the Spanish localization file.
Suggested translation
-After booting Unraid OS for the first time, you'll use the %%WebGUI|web-gui%% to complete your system configuration. This interface lets you manage your server, set up storage, configure user shares, and control features like %%hardware virtualization|hvm%% and Docker containers. +Después de iniciar Unraid OS por primera vez, usarás el %%WebGUI|web-gui%% para completar la configuración de tu sistema. Esta interfaz te permite administrar tu servidor, configurar el almacenamiento, configurar recursos compartidos de usuario y controlar funciones como la %%virtualización de hardware|hvm%% y los contenedores Docker.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` at line 8, Replace the English introductory paragraph with a Spanish translation, preserving the localization tokens exactly (%%WebGUI|web-gui%% and %%hardware virtualization|hvm%%) and the word "Docker"; only change the surrounding English text to Spanish so it reads naturally (e.g., "Después de iniciar Unraid OS por primera vez, use la %%WebGUI|web-gui%% para completar la configuración del sistema. Esta interfaz le permite administrar su servidor, configurar el almacenamiento, crear y gestionar recursos compartidos de usuario y controlar funciones como la %%hardware virtualization|hvm%% y los contenedores Docker."). Ensure accents and punctuation are correct and no other lines are modified.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (1)
114-138:⚠️ Potential issue | 🟠 MajorGive the new licensing flow its own heading.
Line 114 and Line 138 both render as
## BIOS-Empfehlungen, but the first section is now about signing in to Unraid.net and installing a trial key. That leaves the page outline and TOC with two BIOS sections, while the first one is not about BIOS at all.✏️ Suggested fix
-## BIOS-Empfehlungen +## Lizenzschlüssel erhalten🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 114 - 138, The first "## BIOS-Empfehlungen" heading is incorrect for the block that describes signing into Unraid.net and installing a trial key; rename that first heading to something like "## Lizenzierung" or "## Lizenzschlüssel" (and update any adjacent references such as the important note that links to Tools → Registration) so the page no longer has two identical "## BIOS-Empfehlungen" headings and the TOC reflects the licensing flow correctly.
♻️ Duplicate comments (10)
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (4)
51-113:⚠️ Potential issue | 🟠 MajorOnboarding 章节应提供中文内容而不是英文原文。
Line 51-113 当前为英文流程说明，属于明显的本地化回退。
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 51 - 113, 将文件中标题为 "Onboarding" 的段落（当前英文第51-113行）翻译为中文并替换原文；保留所有 MDX 结构、重定向注释标记(:::note[Unraid 7.3 and later]:::)、步骤编号、链接如 ./internal-boot-faq.mdx 与 ../../troubleshooting/tpm-licensing-faq.mdx、以及图片节点（例如 /img/onboarding_step1.png … onboarding_step6.png）不变；保持术语一致（例如 “Flash Boot” -> “闪存启动”，“internal boot” -> “内部启动”，“Get Started” -> “开始” 等），并确保按钮/菜单项和 FAQ 链接文本也翻译为中文但不改动链接目标或文件名（例如 Settings → Onboarding Wizard 翻译为 设置 → 引导向导）。
116-117:⚠️ Potential issue | 🟠 Major许可证与 BIOS 提示块存在英文残留，需统一中文。
这些行在
i18n/zh页面中仍是英文，会影响中文读者连续阅读。Also applies to: 134-135, 165-167
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 116 - 117, The English fragments "Log in to your Unraid.net account to obtain a license key:" (and the similar English lines around the same sections) remain in the Chinese locale file and should be replaced with proper Chinese to maintain consistency; locate these strings in i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (the occurrences you noted around the three blocks) and replace them with an appropriate Chinese translation (e.g., "登录您的 Unraid.net 帐户以获取授权密钥：" or the preferred project phrasing), ensuring the phrasing matches surrounding Chinese content and updates all duplicates.
149-150:⚠️ Potential issue | 🟠 Major清单中包含字面量
\n，会被渲染为原始字符。请把
\n改成真实换行/独立列表项，避免页面显示异常。Suggested fix
-✅ 设置 USB 闪存驱动器为主要启动设备。\n✅ 配置存储控制器为通过 SATA 连接的 **%%AHCI|ahci%%** 模式。\n✅ 将控制器设置为 **%%HBA 模式|hba-mode%%** （不是 **%%RAID|raid%%**）。\n✅ 禁用 **安全启动**，因为 Unraid OS 不支持此功能。 +✅ 设置 USB 闪存驱动器为主要启动设备。 +✅ 配置存储控制器为通过 SATA 连接的 **%%AHCI|ahci%%** 模式。 +✅ 将控制器设置为 **%%HBA 模式|hba-mode%%** （不是 **%%RAID|raid%%**）。 +✅ 禁用 **安全启动**，因为 Unraid OS 不支持此功能。 ... -✅ 调整启动顺序为：**Forced-FDD**、**USB-HDD**、**USB-ZIP**。\n✅ 禁用 USB 2.0/3.0 支持。\n✅ 切换任何快速启动功能。\n✅ 切换 USB 键盘支持。 +✅ 调整启动顺序为：**Forced-FDD**、**USB-HDD**、**USB-ZIP**。 +✅ 禁用 USB 2.0/3.0 支持。 +✅ 切换任何快速启动功能。 +✅ 切换 USB 键盘支持。Also applies to: 160-160
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 149 - 150, The checklist contains literal "\n" characters inside the string "✅ 设置 USB 闪存驱动器为主要启动设备.\n✅ 配置存储控制器为通过 SATA 连接的 **%%AHCI|ahci%%** 模式.\n✅ 将控制器设置为 **%%HBA 模式|hba-mode%%** （不是 **%%RAID|raid%%**）.\n✅ 禁用 **安全启动**，因为 Unraid OS 不支持此功能。" — remove the literal "\n" sequences and split this into real separate lines/list items (each starting with "✅") so each checkbox becomes its own markdown line; make the same change for the other occurrence referenced (the one around the content at 160) to avoid raw "\n" rendering.
12-12:⚠️ Potential issue | 🟠 Major将 zh 文档中的英文提示恢复为中文本地化文本。
Line 12 在中文页面中使用了整段英文说明，打断本地化一致性。
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` at line 12, 当前中文页面包含整段英文说明，需要恢复为中文本地化文本：将那句“Check out [Multi-language support](../../using-unraid-to/customize-your-experience/multi-language-support.mdx) to make the %%WebGUI|web-gui%% more accessible in your preferred language.”替换为其中文翻译（例如：“可前往[多语言支持](../../using-unraid-to/customize-your-experience/multi-language-support.mdx) 将 %%WebGUI|web-gui%% 设置为首选语言以提升可访问性。”），保留原有链接目标和占位符 %%WebGUI|web-gui%% 不变，确保文件 i18n/zh/... 的内容与周围中文段落一致。i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md (1)
13-18:⚠️ Potential issue | 🟠 MajorUntranslated English remains in the French release notes (still unresolved).
Line 13, Lines 15-16, Line 18, and Line 43 are still in English. This is a localization break in a French doc page and includes upgrade-critical guidance.
Proposed fix
-See [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) for issues reported by other testers. +Consultez [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) pour les problèmes signalés par d’autres testeurs. -- Critical: In 7.3.0-beta.1, non-encrypted XFS pools can fail to mount, causing all drives in the pool to appear unmountable. See [7.3.0 beta1 - (non-encrypted) xfs pool all drives are un-mountable](https://product.unraid.net/p/7-3-0-beta1-non-encrypted-xfs-pool-all-drives-are-un-mountanble). -- Important: If you are running 7.3.0-beta.1 and format an XFS volume on a 4Kn disk (a disk that reports 4096-byte sectors), that newly formatted volume will not mount after the fix for the issue above is applied. +- Critique : Dans 7.3.0-beta.1, les pools XFS non chiffrés peuvent ne pas se monter, ce qui peut faire apparaître tous les disques du pool comme non montables. Voir [7.3.0 beta1 - (non-encrypted) xfs pool all drives are un-mountable](https://product.unraid.net/p/7-3-0-beta1-non-encrypted-xfs-pool-all-drives-are-un-mountanble). +- Important : Si vous utilisez 7.3.0-beta.1 et formatez un volume XFS sur un disque 4Kn (un disque qui signale des secteurs de 4096 octets), ce volume nouvellement formaté ne se montera pas après l’application du correctif du problème ci-dessus. -ReiserFS is no longer supported in modern Linux kernels; you must migrate off ReiserFS before upgrading to this release. See [Converting to a new file system type](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) for details. +ReiserFS n’est plus pris en charge par les noyaux Linux modernes ; vous devez migrer depuis ReiserFS avant de passer à cette version. Consultez [Converting to a new file system type](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) pour plus de détails. -To proactively switch to TPM-based licensing, see [How can I move from flash-based licensing to TPM-based licensing](../troubleshooting/tpm-licensing-faq.mdx#tpm). +Pour passer de manière proactive à une licence basée sur le TPM, consultez [How can I move from flash-based licensing to TPM-based licensing](../troubleshooting/tpm-licensing-faq.mdx#tpm).Also applies to: 43-43
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md` around lines 13 - 18, Translate the remaining English strings in the French release notes to French: replace "See [Unraid OS Prerelease (Bugs & Feedback)](...)" with its French equivalent, localize the two bullet headers and bodies starting with "Critical: In 7.3.0-beta.1, non-encrypted XFS pools..." and "Important: If you are running 7.3.0-beta.1..." into French, and translate the ReiserFS sentence ("ReiserFS is no longer supported...") and the linked anchor text; keep links unchanged but ensure their surrounding text is fully translated (these occur around the phrases shown in the diff and again at the location referenced as line 43). Ensure tone and technical terms match existing French docs and run a quick spell/grammar check after translating.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (2)
168-172:⚠️ Potential issue | 🟠 MajorTranslate the
:::importantwarning block to French.The warning text at lines 169-171 is still in English. The first paragraph about motherboard boot device limits needs translation.
Proposed fix
:::important -Many motherboards limit boot device selection to 12 hard drives. If your USB flash drive is recognized as a hard drive, you may not be able to boot from it after installing 12 physical hard drives. Configure the BIOS to treat the flash drive as a removable device whenever possible. +De nombreuses cartes mères limitent la sélection des périphériques de démarrage à 12 disques durs. Si votre clé USB est reconnue comme un disque dur, vous risquez de ne plus pouvoir démarrer dessus après l'installation de 12 disques physiques. Configurez le BIOS pour traiter la clé USB comme un périphérique amovible lorsque cela est possible. Si vous utilisez une carte HBA supplémentaire, vous pourrez peut-être désactiver la prise en charge INT 13h pour empêcher que ses lecteurs connectés n'apparaissent dans la liste des périphériques de démarrage, aidant ainsi à rester dans la limite des 12 lecteurs. :::,
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 168 - 172, The warning block marked by :::important contains the first paragraph still in English (the motherboard boot device limit sentence); replace that English sentence with a proper French translation while leaving the second paragraph (about disabling INT 13h on an HBA) as-is, ensuring grammatical consistency and punctuation within the same :::important block in deploy-and-configure-unraid-os.mdx.
51-51:⚠️ Potential issue | 🟠 MajorRestore the
#onboardinganchor on this heading.The heading still lacks the
#onboardinganchor that other pages link to.Proposed fix
-## Intégration +## Intégration {`#onboarding`},
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` at line 51, The heading "## Intégration" is missing the `#onboarding` anchor; locate the heading line with the exact text "## Intégration" in deploy-and-configure-unraid-os.mdx and restore the anchor by adding the anchor token directly to the heading (e.g., append {`#onboarding`}) so other pages linking to `#onboarding` resolve correctly.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (2)
149-149:⚠️ Potential issue | 🟠 MajorRemove the literal
\nescapes from the checklist.MDX will render these as text, not as line breaks, so the BIOS checklist shows raw
\ncharacters instead of separate entries.🛠️ Suggested fix
-✅ Stellen Sie das USB-Flash-Laufwerk als primäres Boot-Gerät ein.\n✅ Konfigurieren Sie den Speichercontroller im **%%AHCI|ahci%%**-Modus mit SATA-Verbindungen.\n✅ Stellen Sie den Controller auf **%%HBA-Modus|hba-mode%%** (nicht **%%RAID|raid%%**).\n✅ Deaktivieren Sie **Secure Boot**, da dies von Unraid OS nicht unterstützt wird. +✅ Stellen Sie das USB-Flash-Laufwerk als primäres Boot-Gerät ein.\ +✅ Konfigurieren Sie den Speichercontroller im **%%AHCI|ahci%%**-Modus mit SATA-Verbindungen.\ +✅ Stellen Sie den Controller auf **%%HBA-Modus|hba-mode%%** (nicht **%%RAID|raid%%**).\ +✅ Deaktivieren Sie **Secure Boot**, da dies von Unraid OS nicht unterstützt wird. -✅ Passen Sie die Boot-Reihenfolge an: **Forced-FDD**, **USB-HDD**, **USB-ZIP**.\n✅ Deaktivieren Sie die USB 2.0/3.0-Unterstützung.\n✅ Schalten Sie alle Schnelles-Start-Funktionen um.\n✅ Schalten Sie die USB-Tastatur-Unterstützung um. +✅ Passen Sie die Boot-Reihenfolge an: **Forced-FDD**, **USB-HDD**, **USB-ZIP**.\ +✅ Deaktivieren Sie die USB 2.0/3.0-Unterstützung.\ +✅ Schalten Sie alle Schnelles-Start-Funktionen um.\ +✅ Schalten Sie die USB-Tastatur-Unterstützung um.Also applies to: 160-160
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` at line 149, The checklist contains literal "\n" escape sequences inside the MDX string (e.g., the line starting "✅ Stellen Sie das USB-Flash-Laufwerk..." and the repeated occurrence later) which render as text; remove the "\n" escapes and split the entries into actual separate MDX lines or a proper Markdown checklist (each item on its own line beginning with "✅" or "- [ ]"/"- [x]") so each BIOS step is rendered as a distinct checklist entry.
164-167:⚠️ Potential issue | 🟠 MajorTranslate this
:::importantwarning completely.Line 165 is still English, so a high-importance troubleshooting note is only partially localized.
🌐 Suggested wording
:::important -Many motherboards limit boot device selection to 12 hard drives. If your USB flash drive is recognized as a hard drive, you may not be able to boot from it after installing 12 physical hard drives. Configure the BIOS to treat the flash drive as a removable device whenever possible. +Viele Motherboards begrenzen die Auswahl des Boot-Geräts auf 12 Festplatten. Wenn Ihr USB-Flash-Laufwerk als Festplatte erkannt wird, können Sie nach dem Einbau von 12 physischen Festplatten möglicherweise nicht mehr davon booten. Konfigurieren Sie das BIOS nach Möglichkeit so, dass das Flash-Laufwerk als Wechseldatenträger behandelt wird. -Wenn Sie einen zusätzlichen HBA verwenden, können Sie möglicherweise die INT 13h-Unterstützung deaktivieren, um zu verhindern, dass dessen angeschlossene Laufwerke in der Liste der bootfähigen Geräte erscheinen, was hilft, innerhalb der Grenze von 12 Laufwerken zu bleiben. +Wenn Sie einen zusätzlichen HBA verwenden, können Sie die INT 13h-Unterstützung eventuell deaktivieren, damit dessen angeschlossene Laufwerke nicht in der Liste der bootfähigen Geräte erscheinen und Sie innerhalb der Grenze von 12 Laufwerken bleiben. :::🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 164 - 167, The important warning block labeled ":::important" contains an untranslated English sentence; replace the remaining English sentence ("Many motherboards limit boot device selection to 12 hard drives...") with an accurate German translation so the entire warning is fully localized, keeping the existing German sentence about INT 13h and ensuring terminology (BIOS, USB-Stick, HBA, INT 13h) remains consistent with the rest of the document.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md (1)
13-18:⚠️ Potential issue | 🟠 MajorTranslate the remaining English copy on this German page.
These paragraphs are still English, so the new release notes are only partially localized in the most reader-visible sections.
🌐 Suggested wording
-See [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) for issues reported by other testers. +Siehe [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) für von anderen Testern gemeldete Probleme. -- Critical: In 7.3.0-beta.1, non-encrypted XFS pools can fail to mount, causing all drives in the pool to appear unmountable. See [7.3.0 beta1 - (non-encrypted) xfs pool all drives are un-mountable](https://product.unraid.net/p/7-3-0-beta1-non-encrypted-xfs-pool-all-drives-are-un-mountanble). -- Important: If you are running 7.3.0-beta.1 and format an XFS volume on a 4Kn disk (a disk that reports 4096-byte sectors), that newly formatted volume will not mount after the fix for the issue above is applied. +- Kritisch: In 7.3.0-beta.1 können nicht verschlüsselte XFS-Pools nicht eingebunden werden, wodurch alle Laufwerke im Pool als nicht einbindbar erscheinen. Siehe [7.3.0 beta1 - (non-encrypted) xfs pool all drives are un-mountable](https://product.unraid.net/p/7-3-0-beta1-non-encrypted-xfs-pool-all-drives-are-un-mountanble). +- Wichtig: Wenn Sie 7.3.0-beta.1 verwenden und ein XFS-Volume auf einer 4Kn-Festplatte formatieren (eine Festplatte, die 4096-Byte-Sektoren meldet), wird dieses neu formatierte Volume nicht eingebunden, nachdem der Fix für das obige Problem angewendet wurde. -ReiserFS is no longer supported in modern Linux kernels; you must migrate off ReiserFS before upgrading to this release. See [Converting to a new file system type](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) for details. +ReiserFS wird in modernen Linux-Kerneln nicht mehr unterstützt; Sie müssen vor dem Upgrade auf diese Version von ReiserFS auf ein anderes Dateisystem migrieren. Details finden Sie unter [Konvertieren zu einem neuen Dateisystemtyp](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type). -To proactively switch to TPM-based licensing, see [How can I move from flash-based licensing to TPM-based licensing](../troubleshooting/tpm-licensing-faq.mdx#tpm). +Wenn Sie proaktiv auf TPM-basierte Lizenzierung umstellen möchten, lesen Sie die [FAQ zur TPM-basierten Lizenzierung](../troubleshooting/tpm-licensing-faq.mdx#tpm).Also applies to: 43-43
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md` around lines 13 - 18, Several paragraphs in the release notes remain in English — locate the block beginning with "See [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) for issues reported by other testers." (including the two bullet points about XFS and the ReiserFS sentence) and replace those English sentences with fluent German translations while preserving the links, bullet formatting, and the reference to the "Converting to a new file system type" link; ensure the translated text conveys the same warnings (Critical/Important) and the ReiserFS deprecation notice.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Line 85: Translate the two remaining English helper sentences into German:
replace the sentence beginning "If you have questions about device counts or
mirrored boot, see the [Internal Boot FAQ](./internal-boot-faq.mdx)..." and the
sentence beginning "For TPM-based licensing questions, see the [TPM Licensing
FAQ](../../troubleshooting/tpm-licensing-faq.mdx)..." with idiomatic German
equivalents, keeping the exact markdown link labels and targets, preserving
punctuation and relative paths, and ensure the same wording/links are used where
the second English occurrence appears so the onboarding flow is fully localized.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Line 110: Replace the English sentence "For internal boot questions, see the
[Internal Boot FAQ](./internal-boot-faq.mdx)." with its Spanish translation and
keep the same link target; update the link text to "Preguntas frecuentes sobre
el arranque interno" so the final line reads: "Para preguntas sobre el arranque
interno, consulte las [Preguntas frecuentes sobre el arranque
interno](./internal-boot-faq.mdx)."
- Line 83: Replace the English guidance sentence "If you have questions about
device counts or mirrored boot, see the [Internal Boot
FAQ](./internal-boot-faq.mdx), which also includes video walkthroughs. For
TPM-based licensing questions, see the [TPM Licensing
FAQ](../../troubleshooting/tpm-licensing-faq.mdx)." with its Spanish
translation; update the text in deploy-and-configure-unraid-os.mdx so it reads:
"Si tiene preguntas sobre el número de dispositivos o el arranque en espejo,
consulte las [Preguntas frecuentes sobre arranque
interno](./internal-boot-faq.mdx), que también incluye guías en vídeo. Para
preguntas sobre licencias basadas en TPM, consulte las [Preguntas frecuentes
sobre licencias TPM](../../troubleshooting/tpm-licensing-faq.mdx)." Ensure the
markdown links remain unchanged.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx`:
- Around line 7-60: The Spanish localization file contains English content;
translate all visible strings into Spanish (title "Internal Boot FAQ", intro
paragraph, video labels "New server setup"/"Existing server conversion", iframe
titles, all FAQ headings and answers) or explicitly mark the file as a
placeholder if translation is pending; update the header and each anchored
question (e.g., headings/IDs internal-boot-bios-order,
internal-boot-secure-boot, internal-boot-drive-count, internal-boot-mirror,
internal-boot-flash-license) and their answers to Spanish, ensuring any inline
tags like %%array|array%% and %%ZFS|zfs%% remain unchanged and links keep
relative paths.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Line 43: Replace the English sentence "To proactively switch to TPM-based
licensing, see [How can I move from flash-based licensing to TPM-based
licensing](../troubleshooting/tpm-licensing-faq.mdx#tpm)." with its Spanish
translation: "Para pasar proactivamente a la licencia basada en TPM, consulte
[¿Cómo puedo pasar de la licencia basada en flash a la licencia basada en
TPM?](../troubleshooting/tpm-licensing-faq.mdx#tpm)." Keep the link target
unchanged and preserve surrounding punctuation and markdown formatting.
- Around line 13-18: The Spanish release notes still contain English text in the
"Known issues" block — translate the listed lines into Spanish: the link text
"Unraid OS Prerelease (Bugs & Feedback)", the two bullet points starting with
"Critical: In 7.3.0-beta.1, non-encrypted XFS pools..." and "Important: If you
are running 7.3.0-beta.1..." and the ReiserFS sentence "ReiserFS is no longer
supported..." — replace each English sentence with an accurate Spanish
translation while preserving the existing links and reference targets (keep the
bracketed URLs and Markdown link syntax intact) and ensure terminology like
"XFS", "4Kn", "ReiserFS" and version "7.3.0-beta.1" remain unchanged.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Line 110: Replace the English sentence 'For internal boot questions, see the
[Internal Boot FAQ](./internal-boot-faq.mdx).' with its French translation,
preserving the markdown link target; e.g. use "Pour les questions liées au
démarrage interne, consultez la [FAQ sur le démarrage
interne](./internal-boot-faq.mdx)."
- Line 83: Replace the English sentence "If you have questions about device
counts or mirrored boot, see the [Internal Boot FAQ](./internal-boot-faq.mdx),
which also includes video walkthroughs. For TPM-based licensing questions, see
the [TPM Licensing FAQ](../../troubleshooting/tpm-licensing-faq.mdx)." with a
French localization, keeping the same Markdown link targets; use: "Si vous avez
des questions sur le nombre d'appareils ou le démarrage en miroir, consultez la
[FAQ sur le démarrage interne](./internal-boot-faq.mdx), qui comprend également
des tutoriels vidéo. Pour les questions de licence liées au TPM, consultez la
[FAQ sur la licence TPM](../../troubleshooting/tpm-licensing-faq.mdx)."
- Around line 154-155: The two lines under Advanced Settings are still in
English; translate them to French preserving the i18n replacement tokens and
link keys (e.g., %%hardware virtualization|hvm%%, %%Intel VT-x|intel-vt-x%%,
%%AMD-V|amd-v%%, %%virtual machines (VMs)|vm%%, %%IOMMU|iommu%%) and the
checkmark formatting; update the text so it reads in French while keeping the
exact token syntax and punctuation intact (for example, replace "Enable" with
"Activez" and "support" with "prise en charge") so the translation integrates
correctly in the French document.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Line 47: The bullet label currently duplicates the word "Amélioration"
("Amélioration : Amélioration de la gestion des états de fichier de clé
manquant"); update that line to remove the duplicated leading word so it reads
smoothly (for example "Amélioration : Gestion des états de fichier de clé
manquant" or simply "Amélioration de la gestion des états de fichier de clé
manquant") by editing the exact string "Amélioration : Amélioration de la
gestion des états de fichier de clé manquant".
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Line 33: The sentence "我们推荐使用密码管理器来安全存储。" is duplicated (appears at both the
current line 33 and line 39); remove one occurrence to avoid redundant content —
keep the instance that best fits surrounding context (either the earlier
explanatory paragraph or the later summary) and ensure any adjacent spacing/line
breaks are preserved so formatting and flow for the
"deploy-and-configure-unraid-os.mdx" content remain correct.
- Line 114: There are two identical section headings "## BIOS 建议" that create
structural ambiguity; locate both occurrences of the heading text "## BIOS 建议"
in deploy-and-configure-unraid-os.mdx, keep one as the BIOS section and rename
the other to a more specific subsection title (suggestion: "## 许可证获取" or "##
获取许可证") so it accurately reflects its content and removes the duplicate heading;
update any cross-references or table-of-contents anchor text if present to match
the new heading.
---
Outside diff comments:
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Around line 114-138: The first "## BIOS-Empfehlungen" heading is incorrect for
the block that describes signing into Unraid.net and installing a trial key;
rename that first heading to something like "## Lizenzierung" or "##
Lizenzschlüssel" (and update any adjacent references such as the important note
that links to Tools → Registration) so the page no longer has two identical "##
BIOS-Empfehlungen" headings and the TOC reflects the licensing flow correctly.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Line 8: Replace the English introductory paragraph with a Spanish translation,
preserving the localization tokens exactly (%%WebGUI|web-gui%% and %%hardware
virtualization|hvm%%) and the word "Docker"; only change the surrounding English
text to Spanish so it reads naturally (e.g., "Después de iniciar Unraid OS por
primera vez, use la %%WebGUI|web-gui%% para completar la configuración del
sistema. Esta interfaz le permite administrar su servidor, configurar el
almacenamiento, crear y gestionar recursos compartidos de usuario y controlar
funciones como la %%hardware virtualization|hvm%% y los contenedores Docker.").
Ensure accents and punctuation are correct and no other lines are modified.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Around line 112-134: The "Recommandations pour le BIOS" heading is duplicated
and currently contains unrelated license-key instructions (the
%%WebGUI|web-gui%% steps and images Upc_get_started.png /
Upc_install_trial_key.png); move the license key sign-in steps and images into
the appropriate license/registration section (or change the heading to match the
content), and restore the BIOS section so it only contains BIOS-specific
recommendations; ensure the duplicate "Recommandations pour le BIOS" heading is
removed or merged so the BIOS guidance appears once and the license steps appear
under a correct "Licence / Enregistrement" heading.
---
Duplicate comments:
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Line 149: The checklist contains literal "\n" escape sequences inside the MDX
string (e.g., the line starting "✅ Stellen Sie das USB-Flash-Laufwerk..." and
the repeated occurrence later) which render as text; remove the "\n" escapes and
split the entries into actual separate MDX lines or a proper Markdown checklist
(each item on its own line beginning with "✅" or "- [ ]"/"- [x]") so each BIOS
step is rendered as a distinct checklist entry.
- Around line 164-167: The important warning block labeled ":::important"
contains an untranslated English sentence; replace the remaining English
sentence ("Many motherboards limit boot device selection to 12 hard drives...")
with an accurate German translation so the entire warning is fully localized,
keeping the existing German sentence about INT 13h and ensuring terminology
(BIOS, USB-Stick, HBA, INT 13h) remains consistent with the rest of the
document.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Around line 13-18: Several paragraphs in the release notes remain in English —
locate the block beginning with "See [Unraid OS Prerelease (Bugs &
Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) for
issues reported by other testers." (including the two bullet points about XFS
and the ReiserFS sentence) and replace those English sentences with fluent
German translations while preserving the links, bullet formatting, and the
reference to the "Converting to a new file system type" link; ensure the
translated text conveys the same warnings (Critical/Important) and the ReiserFS
deprecation notice.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Around line 168-172: The warning block marked by :::important contains the
first paragraph still in English (the motherboard boot device limit sentence);
replace that English sentence with a proper French translation while leaving the
second paragraph (about disabling INT 13h on an HBA) as-is, ensuring grammatical
consistency and punctuation within the same :::important block in
deploy-and-configure-unraid-os.mdx.
- Line 51: The heading "## Intégration" is missing the `#onboarding` anchor;
locate the heading line with the exact text "## Intégration" in
deploy-and-configure-unraid-os.mdx and restore the anchor by adding the anchor
token directly to the heading (e.g., append {`#onboarding`}) so other pages
linking to `#onboarding` resolve correctly.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Around line 13-18: Translate the remaining English strings in the French
release notes to French: replace "See [Unraid OS Prerelease (Bugs &
Feedback)](...)" with its French equivalent, localize the two bullet headers and
bodies starting with "Critical: In 7.3.0-beta.1, non-encrypted XFS pools..." and
"Important: If you are running 7.3.0-beta.1..." into French, and translate the
ReiserFS sentence ("ReiserFS is no longer supported...") and the linked anchor
text; keep links unchanged but ensure their surrounding text is fully translated
(these occur around the phrases shown in the diff and again at the location
referenced as line 43). Ensure tone and technical terms match existing French
docs and run a quick spell/grammar check after translating.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Around line 51-113: 将文件中标题为 "Onboarding" 的段落（当前英文第51-113行）翻译为中文并替换原文；保留所有 MDX
结构、重定向注释标记(:::note[Unraid 7.3 and later]:::)、步骤编号、链接如 ./internal-boot-faq.mdx 与
../../troubleshooting/tpm-licensing-faq.mdx、以及图片节点（例如 /img/onboarding_step1.png
… onboarding_step6.png）不变；保持术语一致（例如 “Flash Boot” -> “闪存启动”，“internal boot” ->
“内部启动”，“Get Started” -> “开始” 等），并确保按钮/菜单项和 FAQ 链接文本也翻译为中文但不改动链接目标或文件名（例如
Settings → Onboarding Wizard 翻译为 设置 → 引导向导）。
- Around line 116-117: The English fragments "Log in to your Unraid.net account
to obtain a license key:" (and the similar English lines around the same
sections) remain in the Chinese locale file and should be replaced with proper
Chinese to maintain consistency; locate these strings in
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
(the occurrences you noted around the three blocks) and replace them with an
appropriate Chinese translation (e.g., "登录您的 Unraid.net 帐户以获取授权密钥：" or the
preferred project phrasing), ensuring the phrasing matches surrounding Chinese
content and updates all duplicates.
- Around line 149-150: The checklist contains literal "\n" characters inside the
string "✅ 设置 USB 闪存驱动器为主要启动设备.\n✅ 配置存储控制器为通过 SATA 连接的 **%%AHCI|ahci%%** 模式.\n✅
将控制器设置为 **%%HBA 模式|hba-mode%%** （不是 **%%RAID|raid%%**）.\n✅ 禁用 **安全启动**，因为 Unraid
OS 不支持此功能。" — remove the literal "\n" sequences and split this into real
separate lines/list items (each starting with "✅") so each checkbox becomes its
own markdown line; make the same change for the other occurrence referenced (the
one around the content at 160) to avoid raw "\n" rendering.
- Line 12: 当前中文页面包含整段英文说明，需要恢复为中文本地化文本：将那句“Check out [Multi-language
support](../../using-unraid-to/customize-your-experience/multi-language-support.mdx)
to make the %%WebGUI|web-gui%% more accessible in your preferred
language.”替换为其中文翻译（例如：“可前往[多语言支持](../../using-unraid-to/customize-your-experience/multi-language-support.mdx)
将 %%WebGUI|web-gui%% 设置为首选语言以提升可访问性。”），保留原有链接目标和占位符 %%WebGUI|web-gui%% 不变，确保文件
i18n/zh/... 的内容与周围中文段落一致。
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 97e24957-a8b5-4de4-9b68-105e79d3de24
📒 Files selected for processing (11)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
✅ Files skipped from review due to trivial changes (1)
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
🚧 Files skipped from review as they are similar to previous changes (2)
- i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
| Geräte aus und legen Sie den für die Boot-Partition reservierten Speicherplatz fest. Klicken Sie dann auf | ||
| **Next**. | ||
|
|
||
| If you have questions about device counts or mirrored boot, see the [Internal Boot FAQ](./internal-boot-faq.mdx), which also includes video walkthroughs. For TPM-based licensing questions, see the [TPM Licensing FAQ](../../troubleshooting/tpm-licensing-faq.mdx). |
Contributor
There was a problem hiding this comment.
Translate the remaining onboarding helper text.
Line 85 and Line 112 are still English, so this new German onboarding flow ends up partially localized.
🌐 Suggested wording
- If you have questions about device counts or mirrored boot, see the [Internal Boot FAQ](./internal-boot-faq.mdx), which also includes video walkthroughs. For TPM-based licensing questions, see the [TPM Licensing FAQ](../../troubleshooting/tpm-licensing-faq.mdx).
+ Wenn Sie Fragen zur Anzahl der Geräte oder zum gespiegelten Boot haben, lesen Sie die [FAQ zum internen Boot](./internal-boot-faq.mdx), die auch Video-Anleitungen enthält. Für Fragen zur TPM-basierten Lizenzierung lesen Sie die [FAQ zur TPM-basierten Lizenzierung](../../troubleshooting/tpm-licensing-faq.mdx).
-For internal boot questions, see the [Internal Boot FAQ](./internal-boot-faq.mdx).
+Für Fragen zum internen Boot lesen Sie die [FAQ zum internen Boot](./internal-boot-faq.mdx).Also applies to: 112-112
🧰 Tools
🪛 LanguageTool
[grammar] ~85-~85: Korrigiere die Fehler
Context: ...so includes video walkthroughs. For TPM-based licensing questions, see the [TPM Licen...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~85-~85: Korrigiere die Fehler
Context: ...ludes video walkthroughs. For TPM-based licensing questions, see the [TPM Licensing FAQ](../../trou...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~85-~85: Korrigiere die Fehler
Context: ...ghs. For TPM-based licensing questions, see the [TPM Licensing FAQ](../../troublesh...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~85-~85: Korrigiere die Fehler
Context: ... For TPM-based licensing questions, see the [TPM Licensing FAQ](../../troubleshooti...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~85-~85: Wähle ein passenderes Wort
Context: ...-based licensing questions, see the [TPM Licensing FAQ](../../troubleshooting/tpm-licensing...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_NOUN)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
at line 85, Translate the two remaining English helper sentences into German:
replace the sentence beginning "If you have questions about device counts or
mirrored boot, see the [Internal Boot FAQ](./internal-boot-faq.mdx)..." and the
sentence beginning "For TPM-based licensing questions, see the [TPM Licensing
FAQ](../../troubleshooting/tpm-licensing-faq.mdx)..." with idiomatic German
equivalents, keeping the exact markdown link labels and targets, preserving
punctuation and relative paths, and ensure the same wording/links are used where
the second English occurrence appears so the onboarding flow is fully localized.
|
|
||
| - Para el **arranque interno**, elige el modo de arranque único o en espejo, selecciona el/los dispositivo(s) y establece el espacio reservado para la partición de arranque. Luego haz clic en **Next**. | ||
|
|
||
| If you have questions about device counts or mirrored boot, see the [Internal Boot FAQ](./internal-boot-faq.mdx), which also includes video walkthroughs. For TPM-based licensing questions, see the [TPM Licensing FAQ](../../troubleshooting/tpm-licensing-faq.mdx). |
Contributor
There was a problem hiding this comment.
Translate this sentence to Spanish.
This guidance sentence is in English while the surrounding content is in Spanish.
Suggested translation
- If you have questions about device counts or mirrored boot, see the [Internal Boot FAQ](./internal-boot-faq.mdx), which also includes video walkthroughs. For TPM-based licensing questions, see the [TPM Licensing FAQ](../../troubleshooting/tpm-licensing-faq.mdx).
+ Si tienes preguntas sobre el conteo de dispositivos o el arranque en espejo, consulta las [Preguntas frecuentes sobre el arranque interno](./internal-boot-faq.mdx), que también incluye tutoriales en video. Para preguntas sobre licencias basadas en TPM, consulta las [Preguntas frecuentes sobre licencias TPM](../../troubleshooting/tpm-licensing-faq.mdx).📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| If you have questions about device counts or mirrored boot, see the [Internal Boot FAQ](./internal-boot-faq.mdx), which also includes video walkthroughs. For TPM-based licensing questions, see the [TPM Licensing FAQ](../../troubleshooting/tpm-licensing-faq.mdx). | |
| Si tienes preguntas sobre el conteo de dispositivos o el arranque en espejo, consulta las [Preguntas frecuentes sobre el arranque interno](./internal-boot-faq.mdx), que también incluye tutoriales en video. Para preguntas sobre licencias basadas en TPM, consulta las [Preguntas frecuentes sobre licencias TPM](../../troubleshooting/tpm-licensing-faq.mdx). |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
at line 83, Replace the English guidance sentence "If you have questions about
device counts or mirrored boot, see the [Internal Boot
FAQ](./internal-boot-faq.mdx), which also includes video walkthroughs. For
TPM-based licensing questions, see the [TPM Licensing
FAQ](../../troubleshooting/tpm-licensing-faq.mdx)." with its Spanish
translation; update the text in deploy-and-configure-unraid-os.mdx so it reads:
"Si tiene preguntas sobre el número de dispositivos o el arranque en espejo,
consulte las [Preguntas frecuentes sobre arranque
interno](./internal-boot-faq.mdx), que también incluye guías en vídeo. Para
preguntas sobre licencias basadas en TPM, consulte las [Preguntas frecuentes
sobre licencias TPM](../../troubleshooting/tpm-licensing-faq.mdx)." Ensure the
markdown links remain unchanged.
|  | ||
| </div> | ||
|
|
||
| For internal boot questions, see the [Internal Boot FAQ](./internal-boot-faq.mdx). |
Contributor
There was a problem hiding this comment.
Translate this sentence to Spanish.
-For internal boot questions, see the [Internal Boot FAQ](./internal-boot-faq.mdx).
+Para preguntas sobre el arranque interno, consulta las [Preguntas frecuentes sobre el arranque interno](./internal-boot-faq.mdx).📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| For internal boot questions, see the [Internal Boot FAQ](./internal-boot-faq.mdx). | |
| Para preguntas sobre el arranque interno, consulta las [Preguntas frecuentes sobre el arranque interno](./internal-boot-faq.mdx). |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
at line 110, Replace the English sentence "For internal boot questions, see the
[Internal Boot FAQ](./internal-boot-faq.mdx)." with its Spanish translation and
keep the same link target; update the link text to "Preguntas frecuentes sobre
el arranque interno" so the final line reads: "Para preguntas sobre el arranque
interno, consulte las [Preguntas frecuentes sobre el arranque
interno](./internal-boot-faq.mdx)."
Comment on lines
+7
to
+60
| # Internal Boot FAQ | ||
|
|
||
| This page contains frequently asked questions about internal boot in Unraid OS. For general licensing questions, see the [Licensing FAQ](../../troubleshooting/licensing-faq.mdx). For TPM-based licensing questions, see the [TPM Licensing FAQ](../../troubleshooting/tpm-licensing-faq.mdx). | ||
|
|
||
| --- | ||
|
|
||
| ## Video walkthroughs | ||
|
|
||
| If you'd rather watch a step-by-step walkthrough, these videos cover both common internal boot paths: | ||
|
|
||
| - [Set up a new server with internal boot](https://www.youtube.com/watch?v=NMHaMaa8iV0) | ||
| - [Convert an existing server to internal boot](https://www.youtube.com/watch?v=sruWM1PqjVo) | ||
|
|
||
| <div style={{ marginBottom: "1.5rem" }}> | ||
| <p><strong>New server setup</strong></p> | ||
| <div style={{ position: "relative", paddingBottom: "56.25%", height: 0, overflow: "hidden", borderRadius: "12px" }}> | ||
| <iframe src="https://www.youtube.com/embed/NMHaMaa8iV0" title="Unraid 7.3 Beta: Set Up a New Server with Internal Boot" style={{ position: "absolute", top: 0, left: 0, width: "100%", height: "100%", border: 0 }} allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerPolicy="strict-origin-when-cross-origin" credentialless="" allowFullScreen /> | ||
| </div> | ||
| </div> | ||
|
|
||
| <div> | ||
| <p><strong>Existing server conversion</strong></p> | ||
| <div style={{ position: "relative", paddingBottom: "56.25%", height: 0, overflow: "hidden", borderRadius: "12px" }}> | ||
| <iframe src="https://www.youtube.com/embed/sruWM1PqjVo" title="Unraid 7.3 Beta: Convert Your Server to Internal Boot" style={{ position: "absolute", top: 0, left: 0, width: "100%", height: "100%", border: 0 }} allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerPolicy="strict-origin-when-cross-origin" credentialless="" allowFullScreen /> | ||
| </div> | ||
| </div> | ||
|
|
||
| ### I switched from flash boot to internal boot, but the system still boots from flash. What should I do? {#internal-boot-bios-order} | ||
|
|
||
| Unraid attempts to update the UEFI boot order automatically. If that does not take effect, manually move your internal boot device(s) to the top of your BIOS/UEFI boot order, save changes, and reboot. | ||
|
|
||
| ### What should I do if I see "prohibited by secure boot policy" after enabling internal boot? {#internal-boot-secure-boot} | ||
|
|
||
| Disable **Secure Boot** in your BIOS/UEFI settings, then reboot. | ||
|
|
||
| ### Does an internal boot SSD or NVMe device count toward my attached storage device limit? {#internal-boot-drive-count} | ||
|
|
||
| Yes. Internal boot SSD/NVMe devices count toward your attached device limit. | ||
|
|
||
| Unraid does not currently exclude internal boot drives from the attached device count. If you use mirrored internal boot, both boot devices count. | ||
|
|
||
| Specifically, attached storage devices include all devices present before %%array|array%% start, except one eMMC device and one USB device. See [License Management](../../troubleshooting/licensing-faq.mdx#license-management). | ||
|
|
||
| ### Can I configure internal boot with two SSDs in a mirrored setup for redundancy? {#internal-boot-mirror} | ||
|
|
||
| Yes. Mirrored internal boot is supported by default. | ||
|
|
||
| Internal boot uses %%ZFS|zfs%%, and a mirrored setup uses a %%ZFS mirror|zfs%% for redundancy. If one boot drive fails, Unraid continues running in a degraded state. Replace the failed device through the normal Unraid drive assignment flow to restore the mirror. | ||
|
|
||
| ### Can I enable internal boot and still license from flash? {#internal-boot-flash-license} | ||
|
|
||
| Yes. The licensing method is independent of the boot method. | ||
|
|
||
| For TPM-based licensing details, see the [TPM Licensing FAQ](../../troubleshooting/tpm-licensing-faq.mdx). |
Contributor
There was a problem hiding this comment.
Spanish localization file contains entirely English content.
This file is located in the Spanish localization directory (i18n/es/) but all content is in English. The title, introduction, video descriptions, and all FAQ entries need to be translated to Spanish to match the expected localization.
For example:
- Line 7: "Internal Boot FAQ" → "Preguntas frecuentes sobre el arranque interno"
- Line 9: The intro paragraph is entirely in English
- Lines 34-60: All FAQ questions and answers are in English
If this is intentional as a placeholder pending translation, consider adding a note or marking it as such.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx`
around lines 7 - 60, The Spanish localization file contains English content;
translate all visible strings into Spanish (title "Internal Boot FAQ", intro
paragraph, video labels "New server setup"/"Existing server conversion", iframe
titles, all FAQ headings and answers) or explicitly mark the file as a
placeholder if translation is pending; update the header and each anchored
question (e.g., headings/IDs internal-boot-bios-order,
internal-boot-secure-boot, internal-boot-drive-count, internal-boot-mirror,
internal-boot-flash-license) and their answers to Spanish, ensuring any inline
tags like %%array|array%% and %%ZFS|zfs%% remain unchanged and links keep
relative paths.
Comment on lines
+13
to
+18
| See [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) for issues reported by other testers. | ||
|
|
||
| - Critical: In 7.3.0-beta.1, non-encrypted XFS pools can fail to mount, causing all drives in the pool to appear unmountable. See [7.3.0 beta1 - (non-encrypted) xfs pool all drives are un-mountable](https://product.unraid.net/p/7-3-0-beta1-non-encrypted-xfs-pool-all-drives-are-un-mountanble). | ||
| - Important: If you are running 7.3.0-beta.1 and format an XFS volume on a 4Kn disk (a disk that reports 4096-byte sectors), that newly formatted volume will not mount after the fix for the issue above is applied. | ||
|
|
||
| ReiserFS is no longer supported in modern Linux kernels; you must migrate off ReiserFS before upgrading to this release. See [Converting to a new file system type](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) for details. |
Contributor
There was a problem hiding this comment.
Translate the known issues content to Spanish.
These lines contain English content in the Spanish release notes:
Suggested translation
-See [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) for issues reported by other testers.
+Consulta [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) para ver problemas reportados por otros probadores.
-- Critical: In 7.3.0-beta.1, non-encrypted XFS pools can fail to mount, causing all drives in the pool to appear unmountable. See [7.3.0 beta1 - (non-encrypted) xfs pool all drives are un-mountable](https://product.unraid.net/p/7-3-0-beta1-non-encrypted-xfs-pool-all-drives-are-un-mountanble).
-- Important: If you are running 7.3.0-beta.1 and format an XFS volume on a 4Kn disk (a disk that reports 4096-byte sectors), that newly formatted volume will not mount after the fix for the issue above is applied.
+- Crítico: En 7.3.0-beta.1, los pools XFS no cifrados pueden fallar al montar, causando que todas las unidades del pool aparezcan como no montables. Consulta [7.3.0 beta1 - (non-encrypted) xfs pool all drives are un-mountable](https://product.unraid.net/p/7-3-0-beta1-non-encrypted-xfs-pool-all-drives-are-un-mountanble).
+- Importante: Si estás ejecutando 7.3.0-beta.1 y formateas un volumen XFS en un disco 4Kn (un disco que reporta sectores de 4096 bytes), ese volumen recién formateado no se montará después de aplicar la corrección del problema anterior.
-ReiserFS is no longer supported in modern Linux kernels; you must migrate off ReiserFS before upgrading to this release. See [Converting to a new file system type](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) for details.
+ReiserFS ya no es compatible con los kernels Linux modernos; debes migrar desde ReiserFS antes de actualizar a esta versión. Consulta [Convertir a un nuevo tipo de sistema de archivos](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) para más detalles.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| See [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) for issues reported by other testers. | |
| - Critical: In 7.3.0-beta.1, non-encrypted XFS pools can fail to mount, causing all drives in the pool to appear unmountable. See [7.3.0 beta1 - (non-encrypted) xfs pool all drives are un-mountable](https://product.unraid.net/p/7-3-0-beta1-non-encrypted-xfs-pool-all-drives-are-un-mountanble). | |
| - Important: If you are running 7.3.0-beta.1 and format an XFS volume on a 4Kn disk (a disk that reports 4096-byte sectors), that newly formatted volume will not mount after the fix for the issue above is applied. | |
| ReiserFS is no longer supported in modern Linux kernels; you must migrate off ReiserFS before upgrading to this release. See [Converting to a new file system type](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) for details. | |
| Consulta [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) para ver problemas reportados por otros probadores. | |
| - Crítico: En 7.3.0-beta.1, los pools XFS no cifrados pueden fallar al montar, causando que todas las unidades del pool aparezcan como no montables. Consulta [7.3.0 beta1 - (non-encrypted) xfs pool all drives are un-mountable](https://product.unraid.net/p/7-3-0-beta1-non-encrypted-xfs-pool-all-drives-are-un-mountanble). | |
| - Importante: Si estás ejecutando 7.3.0-beta.1 y formateas un volumen XFS en un disco 4Kn (un disco que reporta sectores de 4096 bytes), ese volumen recién formateado no se montará después de aplicar la corrección del problema anterior. | |
| ReiserFS ya no es compatible con los kernels Linux modernos; debes migrar desde ReiserFS antes de actualizar a esta versión. Consulta [Convertir a un nuevo tipo de sistema de archivos](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) para más detalles. |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`
around lines 13 - 18, The Spanish release notes still contain English text in
the "Known issues" block — translate the listed lines into Spanish: the link
text "Unraid OS Prerelease (Bugs & Feedback)", the two bullet points starting
with "Critical: In 7.3.0-beta.1, non-encrypted XFS pools..." and "Important: If
you are running 7.3.0-beta.1..." and the ReiserFS sentence "ReiserFS is no
longer supported..." — replace each English sentence with an accurate Spanish
translation while preserving the existing links and reference targets (keep the
bracketed URLs and Markdown link syntax intact) and ensure terminology like
"XFS", "4Kn", "ReiserFS" and version "7.3.0-beta.1" remain unchanged.
|  | ||
| </div> | ||
|
|
||
| For internal boot questions, see the [Internal Boot FAQ](./internal-boot-faq.mdx). |
Contributor
There was a problem hiding this comment.
Translate this sentence to French.
Proposed fix
-For internal boot questions, see the [Internal Boot FAQ](./internal-boot-faq.mdx).
+Pour les questions relatives au démarrage interne, consultez la [FAQ sur le démarrage interne](./internal-boot-faq.mdx).📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| For internal boot questions, see the [Internal Boot FAQ](./internal-boot-faq.mdx). | |
| Pour les questions relatives au démarrage interne, consultez la [FAQ sur le démarrage interne](./internal-boot-faq.mdx). |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
at line 110, Replace the English sentence 'For internal boot questions, see the
[Internal Boot FAQ](./internal-boot-faq.mdx).' with its French translation,
preserving the markdown link target; e.g. use "Pour les questions liées au
démarrage interne, consultez la [FAQ sur le démarrage
interne](./internal-boot-faq.mdx)."
Comment on lines
+154
to
+155
| ✅ Enable **%%hardware virtualization|hvm%%** features (e.g., **%%Intel VT-x|intel-vt-x%%** or **%%AMD-V|amd-v%%**) for **%%virtual machines (VMs)|vm%%**.\ | ||
| ✅ Enable **%%IOMMU|iommu%%** support (Intel VT-d or AMD-Vi) for PCI device assignment to VMs. |
Contributor
There was a problem hiding this comment.
Translate these lines to French.
These Advanced Settings instructions are in English within a French document.
Proposed fix
-✅ Enable **%%hardware virtualization|hvm%%** features (e.g., **%%Intel VT-x|intel-vt-x%%** or **%%AMD-V|amd-v%%**) for **%%virtual machines (VMs)|vm%%**.\
-✅ Enable **%%IOMMU|iommu%%** support (Intel VT-d or AMD-Vi) for PCI device assignment to VMs.
+✅ Activez les fonctionnalités de **%%virtualisation matérielle|hvm%%** (par ex., **%%Intel VT-x|intel-vt-x%%** ou **%%AMD-V|amd-v%%**) pour les **%%machines virtuelles (VMs)|vm%%**.\
+✅ Activez la prise en charge de l'**%%IOMMU|iommu%%** (Intel VT-d ou AMD-Vi) pour l'assignation de périphériques PCI aux VMs.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
around lines 154 - 155, The two lines under Advanced Settings are still in
English; translate them to French preserving the i18n replacement tokens and
link keys (e.g., %%hardware virtualization|hvm%%, %%Intel VT-x|intel-vt-x%%,
%%AMD-V|amd-v%%, %%virtual machines (VMs)|vm%%, %%IOMMU|iommu%%) and the
checkmark formatting; update the text so it reads in French while keeping the
exact token syntax and punctuation intact (for example, replace "Enable" with
"Activez" and "support" with "prise en charge") so the translation integrates
correctly in the French document.
|
|
||
| #### Autres licences | ||
|
|
||
| - Amélioration : Amélioration de la gestion des états de fichier de clé manquant |
Contributor
There was a problem hiding this comment.
Avoid duplicated wording in the bullet label.
Line 47 repeats “Amélioration” twice, which reads awkwardly in FR docs.
Proposed fix
-- Amélioration : Amélioration de la gestion des états de fichier de clé manquant
+- Amélioration : Gestion améliorée des états de fichier de clé manquante🧰 Tools
🪛 LanguageTool
[grammar] ~47-~47: Il y a peut-être une erreur ici
Context: ...-faq.mdx#tpm). #### Autres licences - Amélioration : Amélioration de la gestion des états ...
(QB_NEW_FR)
[grammar] ~47-~47: « amélioration » semble plus probable dans ce contexte
Context: .... #### Autres licences - Amélioration : Amélioration de la gestion des états de fichier de c...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~47-~47: Le mot « manquante » est plus probable.
Context: ... la gestion des états de fichier de clé manquant ### Stockage - Nouveau : Afficher les fichi...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_CONFUSION_MANQUANT_MANQUANTE)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`
at line 47, The bullet label currently duplicates the word "Amélioration"
("Amélioration : Amélioration de la gestion des états de fichier de clé
manquant"); update that line to remove the duplicated leading word so it reads
smoothly (for example "Amélioration : Gestion des états de fichier de clé
manquant" or simply "Amélioration de la gestion des états de fichier de clé
manquant") by editing the exact string "Amélioration : Amélioration de la
gestion des états de fichier de clé manquant".
|
|
||
| 首次访问 %%WebGUI|web-gui%% 时，系统会提示您为 %%root 用户|root-user%% 创建强密码。 | ||
|
|
||
| 我们推荐使用密码管理器来安全存储。 |
Contributor
There was a problem hiding this comment.
“我们推荐使用密码管理器来安全存储。”内容重复。
Line 33 与 Line 39 语义重复，建议保留一处以减少噪音。
Also applies to: 39-39
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
at line 33, The sentence "我们推荐使用密码管理器来安全存储。" is duplicated (appears at both the
current line 33 and line 39); remove one occurrence to avoid redundant content —
keep the instance that best fits surrounding context (either the earlier
explanatory paragraph or the later summary) and ensure any adjacent spacing/line
breaks are preserved so formatting and flow for the
"deploy-and-configure-unraid-os.mdx" content remain correct.
|
|
||
| For internal boot questions, see the [Internal Boot FAQ](./internal-boot-faq.mdx). | ||
|
|
||
| ## BIOS 建议 |
Contributor
There was a problem hiding this comment.
重复的 ## BIOS 建议 标题会造成文档结构歧义。
建议保留一个 BIOS 标题，另一个改为更准确的小节名（例如“许可证获取”）。
Also applies to: 138-138
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
at line 114, There are two identical section headings "## BIOS 建议" that create
structural ambiguity; locate both occurrences of the heading text "## BIOS 建议"
in deploy-and-configure-unraid-os.mdx, keep one as the BIOS section and rename
the other to a more specific subsection title (suggestion: "## 许可证获取" or "##
获取许可证") so it accurately reflects its content and removes the duplicate heading;
update any cross-references or table-of-contents anchor text if present to match
the new heading.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit