Conversation
📝 WalkthroughWalkthroughLarge-scale localization and content restructuring across German and Spanish MDX docs and English source: many new/renamed pages, rewritten guidance (API, CLI, OIDC, storage, VMs, troubleshooting), presentation/formatting fixes, and i18n category/footer additions. No code or public API signatures changed. Changes
Sequence Diagram(s)(omitted) Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 125
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (48)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/managing-and-customizing-containers.mdx (4)
93-107: Restructure: Remove duplicate content in start sequence testing section.Lines 93–97 introduce a tip box about testing start sequences, but the same content is repeated immediately at lines 99–101 as a section header, followed by steps. This creates redundancy.
Remove the tip box (lines 93–97) and keep the organized heading + steps format (lines 99–106) for clarity.
:::tip - -Während Unraid keine spezielle "Test-Startsequenz"-Funktion besitzt, können Sie Ihre Startreihenfolge simulieren und überprüfen: - ::: ### Testen Ihrer Startsequenz
108-120: Consolidate context menu explanation; remove duplication.Lines 108–112 introduce the context menu with instructions to access it. However, line 110–120 repeats the exact same introduction and adds the table. Consolidate by removing the standalone important box (lines 108–112) and keep only the integrated explanation before the table (line 120).
:::important - -Um auf das Kontextmenü des Containers zuzugreifen, wechseln Sie zur **Docker**- oder **Dashboard**-Registerkarte und klicken auf das Container-Icon, das Sie verwalten möchten. Dieses Menü bietet einfachen Zugriff auf häufige Aktionen: - ::: ---
140-156: Reorganize: Health indicators and volume mappings content is interleaved incorrectly.The section structure is disjointed:
- Line 116 header: "## Gesundheitsindikator" (Health indicator)
- Lines 140–142: Subsection header "### Volume-Mappings innerhalb eines Containers" (belongs in a different section)
- Lines 144–147: Health indicator definitions (green/yellow/white icons) — these should be under the health indicator heading, not after a volume mapping header
- Line 156: Another "## Volume-Mappings..." header repeats the section name
The health indicator content (lines 144–147) should follow directly after line 120 (the context menu table). Reorganize so:
- Health indicator heading → health indicator table → health indicator icons
- Separate "## Volume-Mappings..." section with its own content
Additionally, remove the duplicate section header at line 156.
160-180: Move User Scripts automation content to correct section.Line 160 introduces User Scripts plugin scheduling in the middle of volume mapping examples. This content belongs in the "## Planung von Start und Stopp" section (line 190+), not here. Lines 160–174 are out of order relative to the volume mapping configuration examples (lines 166–180).
Reorganize: keep volume mapping examples (lines 162–180) under the volume mappings section, and move the User Scripts paragraph and subsequent instructions to the scheduling section that begins at line 190.
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (3)
51-75: Remove duplicate heading.The heading "## BIOS 建议" appears at both line 51 and line 75, creating structural confusion. Lines 53-74 appear to be misplaced content that should either be reorganized or consolidated. This duplicate heading breaks the document hierarchy.
Apply this diff to remove the duplicate heading at line 75:
-## BIOS 建议 -
90-91: Translate English content to Chinese.Lines 90-91 contain untranslated English text within a Chinese documentation file. Translate these lines to maintain consistency and accessibility for Chinese-speaking users.
Current English text:
- Line 90: "Enable %%hardware virtualization|hvm%% features (e.g., %%Intel VT-x|intel-vt-x%% or %%AMD-V|amd-v%%) for %%virtual machines (VMs)|vm%%."
- Line 91: "Enable %%IOMMU|iommu%% support (Intel VT-d or AMD-Vi) for PCI device assignment to VMs."
Apply this diff to provide Chinese translations:
- ✅ 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. + ✅ 启用 **%%硬件虚拟化|hvm%%** 功能（例如，**%%Intel VT-x|intel-vt-x%%** 或 **%%AMD-V|amd-v%%**）用于 **%%虚拟机|vm%%**。\ + ✅ 启用 **%%IOMMU|iommu%%** 支持（Intel VT-d 或 AMD-Vi）以实现虚拟机的 PCI 设备分配。
101-104: Fix markdown syntax for important block.Line 101 uses
:::重要(Chinese characters), but the correct markdown syntax requires:::important(lowercase English). This will cause the block to not render as an important callout.Apply this diff to fix the markdown syntax:
- :::重要 + :::importanti18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx (1)
18-18: Translate untranslated UI label to maintain consistency with Unraid interface terminology.Line 18 uses the untranslated English term "Main 标签" in a Chinese document. According to UI translation standards used in Unraid documentation, this should be translated as "主页面 标签" to align with the actual Unraid interface terminology and maintain consistency with the target audience.
Apply this diff to fix the terminology:
-您将使用 Unraid %%WebGUI|web-gui%% 中的 **Main** 标签来分配和查看设备，包括 %%array|array%% 和池分配，以及任何未分配的设备和您的启动设备（即 **USB 闪存设备**）。 +您将使用 Unraid %%WebGUI|web-gui%% 中的 **主页面** 标签来分配和查看设备，包括 %%array|array%% 和池分配，以及任何未分配的设备和您的启动设备（即 **USB 闪存设备**）。Based on learnings from PR 281.
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx (1)
22-24: Translate the "Main" tab reference to Chinese.Line 22 contains English text "The Main screen" in a Chinese localization file. Per the UI consistency learning (PR 281), the "Main" tab/button should be translated as "主页面" in Chinese to match the actual Unraid interface users see.
Apply this diff to translate the section:
-The **Main** screen enables efficient management of your Unraid storage and disk operations. You can configure your %%array|array%%, %%cache pools|cache-pool%%, and flash devices, as well as manage USB storage and unassigned devices, including remote shares. It displays key information about each storage device, such as health, capacity, and file systems. +**主页面**屏幕使您能够高效管理您的 Unraid 存储和磁盘操作。您可以配置您的%%array|阵列%%、%%cache pools|缓存池%%和闪存设备，以及管理 USB 存储和未分配设备，包括远程共享。它显示每个存储设备的关键信息，如健康状态、容量和文件系统。 - + -At the bottom, the Array Operation section provides maintenance options to keep your %%array|array%% running smoothly. +在底部，阵列操作部分提供维护选项以保持您的%%array|阵列%%平稳运行。[based on learnings]
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx (1)
160-160: Standardize "Main" tab terminology.The documentation uses two different terms for the main tab: "Hauptreiter" (line 160) and "Haupt-Registerkarte" (line 167). For consistency, use the same term throughout. Based on the earlier usage, "Hauptreiter" should be preferred.
- 4. Weisen Sie die richtigen Laufwerke als %%parity|parity%% und den Rest als Datenlaufwerke auf der **Haupt**-Registerkarte zu. + 4. Weisen Sie die richtigen Laufwerke als %%parity|parity%% und den Rest als Datenlaufwerke auf der ***Hauptreiter*** zu.Also applies to: 167-167
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx (1)
99-130: Remove duplicate section 3; keep the expanded version only.Lines 99–108 and 111–130 both define "3. Erstellen und starten Sie die VM" with nearly identical opening content. The first block (lines 99–108) is truncated with only 4 steps, while the second block (lines 111–130) is complete with 8 steps and includes crucial guidance on display settings, SMB configuration, and UPS passthrough. Remove the incomplete block (lines 99–108) entirely and keep the expanded version.
-<details> - <summary><strong>3. Erstellen und starten Sie die VM</strong> - Zum Ein-/Ausklappen klicken</summary> - - Sobald die %%VM|vm%% läuft, richten Sie es wie einen physischen Unraid-Server ein: - - 1. Greifen Sie auf das %%WebGUI|web-gui%% der %%VM|vm%% zu unter `http://[VM-IP]`. - 2. Gehen Sie zu ***Einstellungen → Identifikation***: - 3. Klicken Sie auf der **VMs**-Registerkarte auf das Unraid %%VM|vm%%-Symbol und wählen **Start mit Konsole (%%VNC|vnc-session%%)**. - 4. Gehen Sie zu ***Einstellungen → %%SMB|samba%% Einstellungen → Arbeitsgruppeneinstellungen*** und stellen **Lokaler Master** auf *Nein*, um Konflikte zu vermeiden. -</details> - <details> <summary><strong>3. Erstellen und starten Sie die VM</strong> - Zum Ein-/Ausklappen klicken</summary>i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/docker-troubleshooting.mdx (1)
14-15: Remove duplicate paragraph.Lines 14–15 repeat the exact content from lines 10–11 (already in the info block). This redundant paragraph should be removed.
::: -Docker erleichtert es, eine Vielzahl von Anwendungen auf Ihrem Unraid-Server auszuführen, aber es können Probleme auftreten, wie z.B. Container, die nicht starten, beschädigte Docker-Abbilddateien oder Netzwerkprobleme. Diese Seite befasst sich mit einigen häufigen Problemen im Zusammenhang mit Docker auf Unraid und bietet bewährte Verfahren zu deren effektiven Lösung. - ---i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx (1)
395-431: Duplicate section heading: "## Fehlerbehebung" appears twice.The section "## Fehlerbehebung" (Troubleshooting) appears at line 395 and again at line 431. Additionally, lines 405–427 contain content about unassigned devices, which doesn't logically belong in a troubleshooting section. This suggests structural duplication or misalignment during restructuring.
Review the intended structure and either:
- Consolidate duplicated sections, or
- Reorganize content so that unassigned device guidance is placed appropriately (e.g., as a separate section or moved before troubleshooting).
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/monitor-performance/smart-reports-and-disk-health.mdx (1)
22-26: Remove duplicate introductory line.The text "Einige %%SMART|smart%% Attribute, die Unraid standardmäßig überwacht, umfassen:" appears twice in sequence—once at line 22 and again at line 26 immediately before the attributes table. This duplication disrupts the flow. Line 22 should be removed since line 24 serves as a transitional sentence, and line 26 correctly precedes the table.
Apply this diff to remove the duplicate:
## Wie Unraid SMART nutzt -Einige %%SMART|smart%% Attribute, die Unraid standardmäßig überwacht, umfassen: - Für eine genauere Betrachtung der Daten eines Laufwerks von %%SMART|smart%%, klicken Sie auf dessen Namen im **Main**-Tab der Unraid %%WebGUI|web-gui%%. Einige %%SMART|smart%% Attribute, die Unraid standardmäßig überwacht, umfassen:i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md (1)
153-165: Remove duplicate Docker manager configuration section.Lines 153–157 and 161–165 contain identical content about Docker manager shares. This duplicate section must be removed to avoid confusion.
Apply this diff to remove the duplicate:
-Der Unraid OS Docker-Manager ist standardmäßig so konfiguriert, dass er diese vorhandenen Freigaben verwendet: - -- system - wird verwendet, um Docker-Image-Schichten in einem Loopback-Image zu speichern, das in system/docker gespeichert ist. -- appdata - wird von Docker-Anwendungen verwendet, um Anwendungsdaten zu speichern. -- vielleicht hatten wir keinen Platz mehr - ### Vorhandene Freigaben verwalten Der Unraid OS Docker-Manager ist standardmäßig so konfiguriert, dass er diese vorhandenen Freigaben verwendet:i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx (1)
9-9: Translate untranslated English sentence to German.This German localization file contains untranslated English text that should be translated to maintain consistency and readability for German-speaking users.
Apply this diff to translate the sentence:
-Use the %%parity|parity%%-preserve method to remove a data disk while keeping your %%parity|parity%% valid safely. This is especially useful to avoid a full %%parity|parity%% sync after removal. Please ensure that the disk you're removing is healthy. +Verwenden Sie die %%parity|parity%%-Erhaltungsmethode, um eine Datenfestplatte zu entfernen und gleichzeitig Ihre %%parity|parity%% sicher gültig zu halten. Dies ist besonders nützlich, um eine vollständige %%parity|parity%% Synchronisierung nach der Entfernung zu vermeiden. Stellen Sie bitte sicher, dass die Festplatte, die Sie entfernen, intakt ist.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx (2)
95-114: Remove duplicate detail blocks — these sections are already defined above.Lines 95–102 duplicate lines 72–84, and lines 104–114 duplicate lines 86–93. These create redundant phase descriptions with confusing duplicate numbering.
Delete the duplicate blocks:
-<details> - <summary><strong>6. WebGUI</strong> - Zum Erweitern/Kollabieren klicken</summary> - - Die webbasiertem Verwaltungsoberfläche wird verfügbar und ermöglicht die Fernadministration und -konfiguration Ihres Servers. - - - Die %%WebGUI|web-gui%% startet an diesem Punkt. - - Die Datei `config/go` auf dem Flash-Gerät kann Benutzerbefehle vor oder nach dem Start der %%WebGUI|web-gui%% ausführen. -</details> - -<details> - <summary><strong>7. Array</strong> - Zum Erweitern/Kollabieren klicken</summary> - - Speichergeräte werden eingehängt und verfügbar gemacht, was den Bootvorgang abschließt. Hier werden Ihre Daten zugänglich. - - - Wenn Autostart aktiviert ist, beginnt das %%array|array%% hier; andernfalls ist ein manueller Start erforderlich. - - Laufwerke werden als `/dev/diskX` und `/mnt/cache` (falls vorhanden) eingehängt. - - Freigaben werden im Netzwerk als `/mnt/user/sharename` verfügbar. - - Docker-Container starten in der auf der Docker-Seite angegebenen Reihenfolge mit anpassbaren Verzögerungen. - - Automatisch startende virtuelle Maschinen (%%VMs|vm%%) werden ebenfalls gestartet. -</details>
151-151: Translate English text to German — incomplete localization.The following sentences are in English but surrounded by German text and should be translated:
- Line 151: "Unraid identifies data drives..."
- Line 164: "If the %%parity|parity%% is valid..."
- Line 168: "If you have multiple %%parity drives|parity-drives%%..." (warning block)
- Line 188: "Confirm that the number of unmountable drives..."
These appear to be translation oversights in a Crowdin update. Provide German translations for these segments to complete the localization.
Also applies to: 164-164, 168-168, 188-188
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx (1)
133-157: Remove duplicated content and fix section organization.The "Hochleistungsmodus aktivieren" section (starting line 133) contains a duplicate paragraph about Windows Search indexing that was already covered in the prior section (lines 107–120). Additionally, the "Automatische Festplattendefragmentierung deaktivieren" subsection is repeated (compare lines 121–131 with lines 145–156). Remove the duplications to avoid confusion.
-#### Hochleistungsmodus aktivieren - -Windows Search indexing continuously scans your %%virtual machine|vm%%'s storage to catalog files for faster search results. However, on a %%virtual machine|vm%%, this can cause unnecessary disk I/O, slow down performance, and increase wear on your physical storage, especially SSDs in your [%%cache pool|cache-pool%%](../manage-storage/cache-pools.mdx). - -<details> - <summary><strong>Wie man die Windows-Indizierung deaktiviert</strong> – Klicken zum Ein-/Ausklappen</summary> - - 1. Drücken Sie **Windows + R**, um den Ausführen-Dialog zu öffnen, geben Sie `services.msc` ein und drücken Sie Enter. - 2. Im Dienstefenster scrollen Sie nach unten und klicken mit der rechten Maustaste auf **Windows Search**, dann wählen Sie **Beenden**. - 3. Doppelklicken Sie auf **Windows Search**, ändern Sie den **Starttyp** auf **Deaktiviert** und klicken Sie auf **OK**. -</details> - -#### Automatische Festplattendefragmentierung deaktivieren - -Windows ist so konzipiert, dass physische Festplatten regelmäßig automatisch defragmentiert werden. Auf einer %%VM|vm%% - insbesondere bei Verwendung von SSD-Speicher oder dünnprovisionierten %%vDisks|vdisk%% - ist eine automatische Defragmentierung unnötig und kann zudem die Festplattenlebensdauer verringern und die Leistung beeinträchtigen. - -<details> - <summary><strong>Wie man die automatische Festplattendefragmentierung deaktiviert</strong> – Klicken zum Ein-/Ausklappen</summary> - - 1. Öffnen Sie den **Datei-Explorer**, klicken Sie mit der rechten Maustaste auf das C:-Laufwerk und wählen Sie **Eigenschaften**. - 2. Gehen Sie auf die Registerkarte **Tools** und klicken Sie auf **Optimieren**. - 3. Klicken Sie auf **Einstellungen ändern**. - 4. Deaktivieren Sie **Planmäßig ausführen** und klicken Sie auf **OK**. -</details>i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx (1)
122-126: Remove duplicate NFS heading; restructure section hierarchy for network services.Lines 122-126 contain a confirmed structural error: a level-2 heading "## NFS" at line 122 is immediately followed by descriptive text about network services (line 124-125), then a level-3 heading "### NFS" at line 126.
The descriptive text about network services protocols, FTP, logging, and VPN applies broadly to multiple subsections (SMB, FTP, Logging Server, Tailscale, VPN Manager at lines 134-174), not just NFS.
Fix: Either (1) create a parent "## 网络服务" heading at line 122 and demote the current "### NFS" to "## NFS" as the first subsection, or (2) remove line 122 and move the descriptive text above "## NFS" at line 126 if it should introduce that section specifically.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx (1)
122-132: Remove redundant heading and translate English content to German.Lines 122 and 126 contain duplicate "NFS (Network File System)" headings (h2 and h3). Additionally, line 124 contains untranslated English text describing network services in a German-localized file. Remove the h2 heading and English paragraph, and translate the content to German if retention is necessary.
-## NFS (Network File System) - -**Network Services** let you configure network communication protocols on your Unraid server, which are essential for user and disk shares. You can also enable an %%FTP|ftp%% server, a logging server, and set up a %%VPN|vpn-tunnel%% for secure remote access. - ### NFS (Network File System)i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.0.md (1)
70-72: Remove redundant line 70; line 72 is the corrected version.Lines 70 and 72 are redundant paragraphs with nearly identical German text (differing only in "Anwendungsfällen" vs "Anwendungsbeispielen"). Line 72 provides the correct
.mdxfile reference pointing to the existing file. Remove line 70 to eliminate the duplicate.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx (1)
34-34: Translate remaining English sentences to German.Verification confirms multiple untranslated English sections in this German-language documentation. The following lines contain English text that should be translated to German:
- Line 34: "For instance, if you use an %%FTP|ftp%% client..."
- Line 54: "By tweaking these options, you can manage..."
- Lines 80-84: Windows SMB access block ("Modern versions of Windows...")
- Line 114: "Use %%SSH|ssh%% keys or VPN; never forward Telnet"
All surrounding content is correctly in German, confirming these are incomplete translations that degrade the localization quality.
docs/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (1)
141-141: Update Spanish and French localized documentation with new/img/image paths.Verification confirmed that localized versions have been partially updated: German (de) and Chinese (zh) now use the correct
/img/zfspaths. However, Spanish (es) and French (fr) localized files still reference the old./assets/zfspaths:
./i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx(lines 40, 56, 69, 80, 86, 93, 103, 107, 135, 141)./i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx(lines 40, 56, 69, 80, 86, 93, 103, 107, 137, 143)These files must be updated to use
/img/paths to maintain consistency across all localizations.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx (4)
367-395: Duplicate ethtool and tab component sections.Line 367 starts with
## ethtoolwhich duplicates the ethtool section heading, followed immediately by the Tabs component (lines 371-383). Then line 387 starts## tailwhich immediately duplicates earliertailcontent.This structure is incoherent. The tabs component appears to be orphaned without proper context.
106-174: Fix content/header misalignment in command documentation sections.The review comment is accurate. Verification confirms two major structural issues:
### pssection (line 110) containstopcommand documentation (line 118), notps. All descriptions (lines 121-123) describetopbehavior (CPU/memory realtime display, pressqto quit, arrow keys/kto kill).
### Speicher-Utilitiessection (line 148) header describes disk space and partition utilities (line 150), but content containsps auxprocess commands (lines 158-173) with memory/CPU sorting—contradicting the stated purpose.These represent genuine content misplacements requiring restructuring to align section headers with their actual command documentation.
256-364: Fix severe content-header misalignment in networking sections.The structural issues are confirmed: section headers do not match their content. Specifically:
### ping(line 261) containssscommands instead of ping commands### ethtool(line 287) containsipcommands instead of ethtool commands- Duplicate
### pingsection (line 311) with incorrect summary label "Ss-Optionen anzeigen"### tail(line 327) with label "IP-Optionen anzeigen" but containsethtoolcommandsEach section's commands must be reorganized to match their respective headers and summaries.
40-102: File contains duplicate section headers with mismatched command content; review's specific claims about DiskSpeed duplication are incorrect.The review correctly identified structural duplicates but cited the wrong specific content. Verification reveals:
- Lines 262 & 315: Both labeled
### \ping`but line 262 containsss -tuln(socket statistics command, incorrect for ping section). Line 315 contains the correctping -c 4 google.com` command.- Lines 331 & 391: Both labeled
### \tail`but line 331 containsethtool -i eth0(network driver info, incorrect for tail section). Line 391 contains correcttail -f /var/log/syslog` command.- Lines 196 & 224: Both labeled
### \blockdev -getsz`but line 196 containsfdisk -l /dev/sdX(partition layout, incorrect). Line 224 contains correctblockdev --getsz /dev/sdX` command.Correction to review's claims: Line 40 contains a
smartctlcommand (not DiskSpeed), and lines 99-101 show the only single DiskSpeed mention—no duplication exists at the locations cited. The actual duplicates are the three section header pairs above, each with the first instance having an incorrect/mismatched bash command.These duplicate headers with wrong associated commands suggest substantial content reorganization errors requiring immediate correction.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx (1)
113-152: Remove duplicate maintenance expectations introductory paragraph.Lines 115-116 and 128-130 contain identical text about developers maintaining applications. This duplication appears to be a structural artifact from reorganizing the section.
Apply this diff to remove the duplicated introductory paragraph at line 128:
### Wartungserwartungen Entwickler, die Anwendungen in Community Applications veröffentlichen, werden erwartet, dass sie ihre Projekte pflegen, um die Kompatibilität und Zuverlässigkeit für die Unraid-Community sicherzustellen. Dieser Abschnitt umreißt die laufenden Verantwortlichkeiten, die zur Aufrechterhaltung der Qualität der verfügbaren Anwendungen beitragen. Einmal veröffentlicht, werden Entwickler erwartet: - -Entwickler, die Anwendungen in Community Applications veröffentlichen, werden erwartet, dass sie ihre Projekte pflegen, um die Kompatibilität und Zuverlässigkeit für die Unraid-Community sicherzustellen. Dieser Abschnitt umreißt die laufenden Verantwortlichkeiten, die zur Aufrechterhaltung der Qualität der verfügbaren Anwendungen beitragen. - -Einmal veröffentlicht, werden Entwickler erwartet: - Anwendungen regelmäßig zu aktualisieren, um die Kompatibilität mit neuen Unraid-Releases zu gewährleisten.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (1)
51-106: Unpaired brackets in MDX block labels; duplicate BIOS section.Multiple issues here:
Line 51 & 75: The "BIOS-Empfehlungen" section header and full content appears twice in the document, creating a duplicate section.
Unpaired brackets in block labels (lines ~109, ~190, ~307, ~319 per static analysis):
- These use the pattern
:::info[Historical [Kontext]instead of:::info[Historical Context]- The nested brackets are invalid MDX syntax
Remove the duplicate section and fix the bracket syntax throughout.
- ## BIOS-Empfehlungen (first occurrence around line 51) - [full content...] - - ## BIOS-Empfehlungen (second occurrence around line 75) - [duplicate content...]Keep only one BIOS-Empfehlungen section. For bracket syntax, use:
- :::important[How [um die Unterstützung zu überprüfen] + :::important[Überprüfung der Unterstützung]i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx (1)
153-169: Unpaired brackets in block labels and inconsistent terminology.Multiple MDX blocks use invalid bracket syntax with nested brackets:
- Line ~153:
:::important[Choosing Ihr Migrationsansatz]- Line ~190:
:::note[Before [Sysprep ausführen](unpaired bracket)- Line ~307:
:::info[Historical [Kontext](unpaired bracket)- Line ~319:
:::info[Why [Migrieren?](unpaired bracket)The nested bracket pattern
[Label [content]is invalid. Use proper MDX syntax:- :::note[Before [Sysprep ausführen] + :::note[Sysprep-Vorbereitung]Also, German terminology should be consistent throughout. Lines using English fragments like "Start" should use German equivalents where appropriate ("Starten").
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx (1)
109-116: Unpaired brackets in MDX block label.The block uses nested brackets with an unclosed bracket:
- :::important[How [um die Unterstützung zu überprüfen] + :::important[Überprüfung der Unterstützung]i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx (1)
41-84: Duplicate section on user templates.Lines 41 and 68 introduce the same concept ("Unraid 7.1+ führt Benutzer-%%VM|vm%%-Vorlagen ein..."), and lines 70-84 repeat guidance on creating and using templates that appears earlier. Consolidate this section to eliminate redundancy.
- Unraid 7.1+ führt Benutzer-%%VM|vm%%-Vorlagen ein, die das Speichern und Wiederverwenden Ihrer benutzerdefinierten %%VM|vm%%-Konfigurationen erleichtern. Benutzer-Vorlagen vereinfachen die %%VM|vm%%-Bereitstellung und sorgen für Konsistenz in den Setups. - - 1. Klicken Sie auf **VM hinzufügen** auf der Seite **Virtuelle Maschinen**. - ... - - Um eine Benutzervorlage zu verwenden: - - - Auf der **VMs**-Seite klicken Sie auf **VM hinzufügen** und wählen Ihre Vorlage im Abschnitt **Benutzer-Vorlagen** aus. - - Unraid 7.x führt eine Reihe leistungsstarker Erweiterungen... - - - Bewegen Sie den Mauszeiger über eine Benutzervorlage... + [Keep only one comprehensive section with all necessary steps]i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx (3)
231-231: Untranslated English content on line 231.Line 231 contains English text that should be translated to German:
Write down or take a screenshot of the serial numbers for these unmountable drives - these are your %%parity|parity%% drives.This breaks German localization.
235-235: Untranslated English content on line 235.Line 235 contains English text that should be translated to German:
Return to the **Main** tab and correctly assign the %%parity|parity%% drives using the serial numbers you noted.This breaks German localization.
53-108: Fix structural corruption, broken cross-reference, and complete translation before merge.The file contains multiple critical issues:
Broken cross-reference (line 131): Link
#after-the-test-and-repair(English) cannot resolve to heading "Nach dem Test und der Reparatur" (line 145), which generates German slug#nach-dem-test-und-der-reparatur. Update the link to match the German heading slug.Duplicate sections:
- Lines 86 & 112: "Checken und Reparieren von Laufwerken im WebGUI" appears twice (subsection then main section)
- Lines 173 & 223: "Verlorene Array-Konfiguration" entire section duplicated with identical content
- Lines 240 & 285: "Übersetzen der ddrescue-Ausgabe" duplicated
Untranslated English passages must be translated:
- Line 84: "For non-%%array|array%% drives (like %%cache|cache%%-only devices), use the direct partition path, e.g.,
/dev/sdj1."- Lines 175, 225: Duplicate paragraph "Losing your %%array|array%% configuration can be stressful..." (appears twice, both untranslated)
- Line 270: "If you want to clone directly to an %%array|array%% disk while maintaining %%parity|parity%%, use the
md#device and start the %%array|array%% in Maintenance Mode:"Remove all duplicate sections, fix the anchor reference, and translate all English passages to complete the Crowdin sync.
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx (1)
70-115: Consolidate duplicate UPnP section headers.Lines 70 and 90 both contain the header "Verwendung von UPnP (Universal Plug and Play)". This appears to be unintended duplication. Consider consolidating the workflow steps (Lines 74-86) and configuration steps (Lines 94-114) under a single, well-organized UPnP section with clear subsection structure.
i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx (1)
70-114: Consolidate duplicate UPnP section headers.Lines 70 and 90 both contain the header "使用 UPnP（通用即插即用）". This appears to be unintended duplication mirroring the German version. Consider consolidating the workflow steps (Lines 74-86) and configuration steps (Lines 94-114) under a single, well-organized UPnP section.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (1)
227-257: Remove duplicate section.The section titled "Mindestfreier Speicherplatz für einen Cache-Pool" (lines 227–257) is identical to the section at lines 197–224. This creates redundant content that will confuse readers.
Apply this diff to remove the duplicate:
-## Mindestfreier Speicherplatz für einen Cache-Pool - -Setting a minimum free space for your %%cache pool|cache-pool%% can provide better control over file placement, especially when dealing with large files like high-resolution videos. This setting helps Unraid know when to stop writing to the pool and start writing directly to the larger storage %%array|array%%, avoiding interruptions or data corruption. - -:::tip\[Example] - -Wenn Sie häufig Dateien um die 10 GB herunterladen, legen Sie den Mindestfreien Speicherplatz auf mindestens 10 GB fest, idealerweise 20 GB, um Anpassungen zu ermöglichen. - -::: - -Sie können den Minimumfreier Speicherplatz aufrufen, indem Sie auf den Poolnamen in der Registerkarte **Main** klicken und zu den **Individuellen Pooleinstellungen** gehen. - -<h4>Wie es funktioniert</h4> - -- Wenn Sie eine Datei in ein Freigabe laden, das einen Pool umfasst, respektiert Unraid die erste angezeigte Einstellung (entweder den Mindestfreien Speicherplatz der Freigabe oder den des Pools, je nachdem, welcher zuerst erreicht wird). -- Die Mindestfreier Speicherplatz-Einstellung sagt Unraid, dass der %%cache pool|cache-pool%% nicht mehr verwendet werden soll, wenn der freie Speicherplatz unter diese Menge fällt. -- If your share uses a %%cache pool|cache-pool%% as **Primary storage**, files go to the pool until it reaches the minimum free space, then they are sent directly to the %%array|array%%. -- If set to use a %%cache pool|cache-pool%% exclusively (no **Secondary storage**), this setting is not applied. -- If set to use only the %%array|array%% as **Primary storage**, files go straight to the %%array|array%%. - -:::tip[Use Fallbeispiel] - -Die Medienshare hat eine Freigrenze von 20 GB, was für die Dateien in diesem Share passend ist. Wenn Sie jedoch den Pool auch für eine VM verwenden und für den Fall, dass die VDisk wächst, ein Polster lassen möchten, könnten Sie die Pool-Grenze auf 50 GB setzen. So wird jeder Übertrag an das Medienshare nach dem Pool bei weniger als 50 GB freiem Platz direkt an das Array geleitet. - -::: - -:::tip[Best Praxis] - -Setzen Sie den Mindestfreiraum auf mindestens die Größe der größten Datei, die Sie erwarten, vorzugsweise das Doppelte dieser Größe. Wenn Ihre größte Datei beispielsweise 30 GB groß ist, setzen Sie das Minimum auf 60 GB. - -::: - -:::cautioni18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/shares-primary-storage-612.mdx (1)
15-25: Duplicate section header creates confusion.Lines 15 and 21 both have the identical header "Sekundärspeicher-Dropdown:" but appear to describe different scenarios (primary storage as pool vs. array). This duplicate header suggests incomplete restructuring or copy-paste error.
Consider adding context headers to distinguish the scenarios:
-**Sekundärspeicher-Dropdown:** +**Sekundärspeicher-Dropdown (wenn Primärspeicher ein Pool ist):** - **None:** Kein Sekundärspeicher ist für die Freigabe festgelegt (optional). - Wenn der Primärspeicher ein %%pool|cache-pool%% ist, stehen **None**, **Array** und **Ein anderer Pool** zur Verfügung. - Sie können jeden benannten %%pool|cache-pool%% oder das %%array|array%% wählen. -**Sekundärspeicher-Dropdown:** +**Sekundärspeicher-Dropdown (wenn Primärspeicher das Array ist):** - **None:** Kein Sekundärspeicher ist für die Freigabe festgelegt (optional). - Wenn der Primärspeicher ein %%pool|cache-pool%% ist, stehen **None**, **Array** und **Ein anderer Pool** zur Verfügung. - If the primary storage is the **Array**, **None** and any eligible %%pools|cache-pool%% are available.This would clarify the conditional nature of these dropdown options.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx (1)
40-58: Critical: Duplicate troubleshooting section for parity errors.Lines 40–50 and lines 51–57 contain duplicated content describing "What to do if you encounter parity errors." The first version mixes English bullets with German context; the second version repeats the guidance as a numbered German list. This appears to be an incomplete refactoring or merge artifact.
Remove the duplicate section to avoid confusing readers:
-<h4>What to do if you encounter %%parity|parity%% errors</h4> - -%%Parity|parity%% errors happen when the %%parity|parity%% information your system calculates doesn't match what's stored on your %%parity drives|parity-drives%%. This mismatch can arise from several issues, including: - -- **Untersuchen Sie das Problem:** Beginnen Sie mit dem Überprüfen der %%SMART-Berichte|SMART-Reports%%, die detaillierte Informationen über den Gesundheitszustand Ihrer Festplatten bieten. Achten Sie auf Hinweise auf Festplatten- oder Verbindungsprobleme. -- **Hilfe in unseren Foren suchen:** Wenn Sie das Problem nicht selbst lösen können, ziehen Sie in Betracht, Rat in den Unraid-Foren einzuholen. Die Community kann wertvolle Einblicke und Vorschläge basierend auf ihren Erfahrungen bieten. -- **Führen Sie eine weitere Prüfung durch:** Nachdem Sie Hardwareprobleme behoben haben, ist es eine gute Idee, eine weitere %%parity check|parity-check%% durchzuführen, um sicherzustellen, dass alles wieder in Ordnung ist. -- Unsaubere Shutdowns oder unerwartete Systemabstürze - -When %%parity|parity%% errors occur, either the %%parity drives|parity-drives%% or the data disks could be out of sync. Ideally, a %%parity check|parity-check%% should report zero errors so everything functions correctly. - <h4>What to do if you encounter %%parity|parity%% errors</h4> Wenn Ihr %%parity check|parity-check%% Fehler aufdeckt:The second version (numbered list) should be the single source of truth for this section.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx (1)
58-121: Remove duplicate troubleshooting entries.The troubleshooting section contains duplicate entries that should be consolidated:
- Duplicate 1: Lines 68-76 ("VMs zeigen 'Kann Schnittstellen-MTU nicht abrufen'...") is repeated at lines 99-109
- Duplicate 2: Lines 79-87 ("VNC-Zugriff auf VMs funktioniert nicht...") is repeated at lines 111-115
- Duplicate 3: Lines 89-97 ("VM wird nicht booten (EFI-Shell erscheint)...") is repeated at lines 117-121
Consolidate these into single entries to improve documentation quality and reduce maintenance burden.
Apply this diff to remove the duplicate entries:
<details> - <summary><strong>VMs zeigen "Kann Schnittstellen-MTU nicht abrufen" oder Netzwerkfehler</strong> - Klicken zum Expandieren/Reduzieren</summary> - - Wenn Sie %%OVMF|ovmf%%-basierte %%VMs|vm%% in älteren Unraid-Versionen erstellt haben, könnten Sie auf eine EFI-Shell stoßen. Sie können die %%VM|vm%% starten, indem Sie die folgenden Befehle eingeben: - - 1. Geben Sie `fs0:` ein. - 2. Geben Sie dann `cd efi/boot` ein. - 3. Schließlich geben Sie `bootx64.efi` ein. - - Wenn `fs0:` nicht funktioniert, können Sie stattdessen `fs1:` versuchen. Wenn weiterhin Probleme auftreten, besuchen Sie bitte das [Unraid-Forum](https://forums.unraid.net/) für Unterstützung. -</details> - -<details> - <summary><strong>VNC-Zugriff auf VMs funktioniert nicht oder ist langsam</strong> - Klicken zum Expandieren/Reduzieren</summary> - - Um dieses Problem zu lösen, bearbeiten Sie die %%VM|vm%% im %%WebGUI|web-gui%% und klicken Sie auf **Anwenden**, ohne Änderungen vorzunehmen. Diese Aktion aktualisiert den Maschinentyp auf die neueste unterstützte Version. -</details> - -<details> - <summary><strong>VM wird nicht booten (EFI-Shell erscheint)</strong> - Klicken zum Expandieren/Reduzieren</summary> - - Wenn Sie %%OVMF|ovmf%%-basierte %%VMs|vm%% in älteren Unraid-Versionen erstellt haben, könnten Sie auf eine EFI-Shell stoßen. Sie können die %%VM|vm%% starten, indem Sie die folgenden Befehle eingeben: -</details>i18n/zh/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx (1)
34-41: Structure hierarchy violation confirmed: Remove or rename the level 3 header at line 34 "### 安全与认证".The file contains conflicting header hierarchy. Line 34 has a level 3 header (
### 安全与认证) as a subsection under "## 核心基础设施", while line 41 introduces the same heading name as a level 2 main section (## 安全与认证). This creates confusion in document navigation and violates standard markdown structure conventions.Recommended fixes:
- Rename line 34's header to better describe that subsection (e.g.,
### 安全与认证功能or remove it entirely if the table belongs directly under "核心基础设施")- Or reorganize content so the subsection and main section don't share identical names across different hierarchy levels
i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx (1)
104-108: Duplicate section headers: "Plugin-System" appears twice in close proximity.Lines 104–108 contain a brief "Plugin-System" section with two bullet points, immediately followed by a full section of the same name (Lines 109–117) with planned features table. This is redundant.
Consolidate by removing the first stub section (Lines 104–108):
| **Array-/Cache-Share-Statusüberwachung** | v4.0.0 | -### Plugin-System - -- **Speicherfreigabeerstellung & -einstellungen** - Erweiterte Freigabenkonfigurationsoptionen -- **Speicherfreigabeverwaltungsschnittstelle** - Einheitliches Freigabeverwaltungs-Dashboard - ## Plugin-SystemAlso applies to: 109-117
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx (1)
145-174: Critical: Duplicate section "VPN-Tunneling-Zugriff für das System konfigurieren".Lines 145–157 and lines 158–174 both present "VPN-Tunneling-Zugriff für das System konfigurieren" with overlapping but slightly different instructions:
- First version (lines 149–155): References DNS leak testing via dnsleaktest.com.
- Second version (lines 162–165): References IP verification via whatismyipaddress.com.
These sections should be consolidated into a single, cohesive workflow. Verify which verification method is correct for system-wide VPN tunneling configuration, then remove the duplicate section.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx (1)
92-130: Critical: Duplicate section "HTTPS mit Myunraid.net-Zertifikat und ohne Fallback-URL".Lines 92–129 and lines 131–159 present nearly identical sections with the same heading: "HTTPS mit Myunraid.net-Zertifikat und ohne Fallback-URL."
Both sections describe similar Myunraid.net SSL configuration workflows:
- First version (lines 92–129): Includes a detailed explanation and multiple URL examples with note about fallback access.
- Second version (lines 131–159): Includes step-by-step instructions and recovery steps for DNS failure scenarios.
These sections should be consolidated into one comprehensive guide, or clarified if they represent different SSL modes. The current duplication creates confusion about the intended configuration path.
Also applies to: 131-159
i18n/zh/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx (2)
9-25: CRITICAL: Mixed language and incomplete translation throughout file.Line 9 contains "What 什么是OIDC？" (awkward English/Chinese mix), and lines 15-50 have extensive untranslated English content. The file requires complete translation review. Navigation instructions at lines 22-24 also mix languages ("Navigate to" in English, then Chinese).
198-300: CRITICAL: Severe content duplication and structural corruption.Multiple sections are duplicated verbatim (e.g., "### Required Redirect URI" at line 198 and again around line 252, "Troubleshooting" content repeated), and the document flow is broken. Entire provider sections (Microsoft/Azure, Keycloak, Authelia) appear multiple times with mangled formatting. Lines 243-295 contain orphaned headings and duplicate subsections that corrupt the document structure.
This file requires a complete reconstruction from the source English version (
docs/API/oidc-provider-setup.mdx). Do not merge in its current state.
|
|
||
| 4. Klicken Sie auf **"Code einlösen"**, um den Aktivierungsprozess abzuschließen. Nach erfolgreichem Abschluss wird Ihre Lizenz auf dem Server installiert. | ||
|
|
||
| :::note[Server Kontext erforderlich |
There was a problem hiding this comment.
Fix malformed note block syntax.
Line 58 has an unpaired bracket—the note block is missing its closing bracket. Update the syntax:
- :::note[Server Kontext erforderlich
+ :::note[Server Kontext erforderlich]📝 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.
| :::note[Server Kontext erforderlich | |
| :::note[Server Kontext erforderlich] |
🧰 Tools
🪛 LanguageTool
[typographical] ~58-~58: Zeichen ohne sein Gegenstück: ‚]‘ scheint zu fehlen
Context: ...enz auf dem Server installiert. :::note[Server Kontext erforderlich Wenn Sie da...
(UNPAIRED_BRACKETS)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx
around line 58, the note block header is malformed (missing a closing bracket).
Fix by adding the missing closing bracket after the note title and ensure the
note container is properly terminated with a matching closing ::: so the MDX
admonition block is well-formed.
| 1. Gehen Sie zu Ihrem Unraid-Server | ||
| 2. Öffnen Sie das Dropdown-Menü oben rechts und klicken Sie auf "Unraid.net-Konto verwalten" oder alle sichtbaren Lizenzschlüssel-bezogenen Aktionstasten. |
There was a problem hiding this comment.
Fix German quotation marks and punctuation in list items.
The static analysis tool flagged punctuation issues with quotation marks in the numbered list. German convention uses „" (curved guillemets) rather than "" (straight quotes). Update lines 16-17 to use proper German quotation formatting:
- 2. Öffnen Sie das Dropdown-Menü oben rechts und klicken Sie auf "Unraid.net-Konto verwalten" oder alle sichtbaren Lizenzschlüssel-bezogenen Aktionstasten.
+ 2. Öffnen Sie das Dropdown-Menü oben rechts und klicken Sie auf „Unraid.net-Konto verwalten" oder alle sichtbaren Lizenzschlüssel-bezogenen Aktionstasten.📝 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.
| 1. Gehen Sie zu Ihrem Unraid-Server | |
| 2. Öffnen Sie das Dropdown-Menü oben rechts und klicken Sie auf "Unraid.net-Konto verwalten" oder alle sichtbaren Lizenzschlüssel-bezogenen Aktionstasten. | |
| 1. Gehen Sie zu Ihrem Unraid-Server | |
| 2. Öffnen Sie das Dropdown-Menü oben rechts und klicken Sie auf „Unraid.net-Konto verwalten" oder alle sichtbaren Lizenzschlüssel-bezogenen Aktionstasten. |
🧰 Tools
🪛 LanguageTool
[grammar] ~16-~16: Passe das Symbol an
Context: ...rs: 1. Gehen Sie zu Ihrem Unraid-Server 2. Öffnen Sie das Dropdown-Menü oben rechts...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~17-~17: Ersetze das Satzzeichen
Context: ...wn-Menü oben rechts und klicken Sie auf "Unraid.net-Konto verwalten" oder alle sichtbar...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~17-~17: Ersetze das Satzzeichen
Context: ...s und klicken Sie auf "Unraid.net-Konto verwalten" oder alle sichtbaren Lizenzschlüssel-be...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdx
around lines 16–17, replace the English straight quotes with German opening and
closing quotes („…“) for the menu label, ensure each numbered list item ends
with a period, and normalize the adjective to lowercase and without an
unnecessary hyphen: change "Unraid.net-Konto verwalten" to „Unraid.net-Konto
verwalten“, add a trailing period to item 1, and change
"Lizenzschlüssel-bezogenen" to "lizenzschlüsselbezogenen" in item 2.
| ### Benachrichtigungseinstellungen | ||
|
|
||
| You can configure browser and email notifications on this page, subscribing to different types and setting custom alerts for %%SMART|smart%% attribute values. | ||
| 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. | ||
|
|
||
| Hier werden Drittanbieter-Plugins angezeigt, die die Funktionalität von Unraid erweitern und Ihnen mehr Kontrolle über Ihren Server geben. Zum Beispiel ist das [Community-Applikationen Plugin](../../using-unraid-to/run-docker-containers/community-applications.mdx) enthalten. Andere Plugins bieten Funktionen zur Systemüberwachung, -wartung, Speicherverwaltung und `appdata`-Backups. | ||
|
|
There was a problem hiding this comment.
Duplicate content block.
Lines 214–215 repeat text identical to lines 374–375 ("Hier werden Drittanbieter-Plugins angezeigt..."). Remove the duplicate to avoid redundancy and improve clarity.
- Hier werden Drittanbieter-Plugins angezeigt, die die Funktionalität von Unraid erweitern und Ihnen mehr Kontrolle über Ihren Server geben. Zum Beispiel ist das [Community-Applikationen Plugin](../../using-unraid-to/run-docker-containers/community-applications.mdx) enthalten. Andere Plugins bieten Funktionen zur Systemüberwachung, -wartung, Speicherverwaltung und `appdata`-Backups.
-
<div style={{ margin: 'auto', maxWidth: '400px'}}>
</div>🧰 Tools
🪛 LanguageTool
[grammar] ~214-~214: Entferne ein Leerzeichen
Context: ...eispiel ist das [Community-Applikationen Plugin](../../using-unraid-to/run-docker...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
around lines 210 to 215: there is a duplicate sentence block ("Hier werden
Drittanbieter-Plugins angezeigt...") appearing at lines 214–215 that repeats the
same text later at lines 374–375; remove the duplicate lines 214–215 (and any
stray blank line if needed) so the content appears only once, preserving the
original link and formatting in the remaining occurrence.
| ### Exklusive Freigaben | ||
|
|
||
| Wir haben eine neue Einstellung hinzugefügt: "Einstellungen/Globale Freigabeeinstellungen/Exklusive Freigaben erlauben" \[Ja/Nein] Standard: Nein. Wenn auf Ja gesetzt und wenn der primäre Speicher für eine Freigabe ein Pool ist und der sekundäre Speicher auf "None" gesetzt ist, wird ein Symlink unter /mnt/user/*share* erstellt, der direkt auf das Pool-Freigabeverzeichnis verweist. (Es wird zusätzlich überprüft, dass die Freigabe auch nicht auf anderen Volumes vorhanden ist.) | ||
| Wir haben eine neue Einstellung hinzugefügt: "Einstellungen/Globale Freigabeeinstellungen/Exklusive Freigaben erlauben" \[Ja/Nein] Standard: Nein. Wenn auf Ja gesetzt und wenn der primäre Speicher für eine Freigabe ein Pool ist und der sekundäre Speicher auf "None" gesetzt ist, wird ein Symlink unter /mnt/user/_share_ erstellt, der direkt auf das Pool-Freigabeverzeichnis verweist. (Es wird zusätzlich überprüft, dass die Freigabe auch nicht auf anderen Volumes vorhanden ist.) |
There was a problem hiding this comment.
Fix missing comma in German sentence structure.
The static analysis tool flagged a missing comma per German grammar rules. The sentence should have a comma after "Wenn auf Ja gesetzt" to properly separate this introductory clause from the main clause.
Apply this diff to fix the grammar:
-Wir haben eine neue Einstellung hinzugefügt: "Einstellungen/Globale Freigabeeinstellungen/Exklusive Freigaben erlauben" \[Ja/Nein] Standard: Nein. Wenn auf Ja gesetzt und wenn der primäre Speicher für eine Freigabe ein Pool ist und der sekundäre Speicher auf "None" gesetzt ist, wird ein Symlink unter /mnt/user/_share_ erstellt, der direkt auf das Pool-Freigabeverzeichnis verweist. (Es wird zusätzlich überprüft, dass die Freigabe auch nicht auf anderen Volumes vorhanden ist.)
+Wir haben eine neue Einstellung hinzugefügt: "Einstellungen/Globale Freigabeeinstellungen/Exklusive Freigaben erlauben" \[Ja/Nein] Standard: Nein. Wenn auf Ja gesetzt, und wenn der primäre Speicher für eine Freigabe ein Pool ist und der sekundäre Speicher auf "None" gesetzt ist, wird ein Symlink unter /mnt/user/_share_ erstellt, der direkt auf das Pool-Freigabeverzeichnis verweist. (Es wird zusätzlich überprüft, dass die Freigabe auch nicht auf anderen Volumes vorhanden ist.)📝 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.
| Wir haben eine neue Einstellung hinzugefügt: "Einstellungen/Globale Freigabeeinstellungen/Exklusive Freigaben erlauben" \[Ja/Nein] Standard: Nein. Wenn auf Ja gesetzt und wenn der primäre Speicher für eine Freigabe ein Pool ist und der sekundäre Speicher auf "None" gesetzt ist, wird ein Symlink unter /mnt/user/_share_ erstellt, der direkt auf das Pool-Freigabeverzeichnis verweist. (Es wird zusätzlich überprüft, dass die Freigabe auch nicht auf anderen Volumes vorhanden ist.) | |
| Wir haben eine neue Einstellung hinzugefügt: "Einstellungen/Globale Freigabeeinstellungen/Exklusive Freigaben erlauben" \[Ja/Nein] Standard: Nein. Wenn auf Ja gesetzt, und wenn der primäre Speicher für eine Freigabe ein Pool ist und der sekundäre Speicher auf "None" gesetzt ist, wird ein Symlink unter /mnt/user/_share_ erstellt, der direkt auf das Pool-Freigabeverzeichnis verweist. (Es wird zusätzlich überprüft, dass die Freigabe auch nicht auf anderen Volumes vorhanden ist.) |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~174-~174: Fehlendes Komma: Teilsätze, Einschübe, Aufzählungen und direkte Rede müssen durch ein Komma vom Rest des Satzes getrennt werden.
Context: ... und wenn der primäre Speicher für eine Freigabe ein Pool ist und der sekundäre Speicher...
(AI_DE_KOMMA_MISSING_COMMA)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.md
around line 174, there is a missing comma after the introductory clause "Wenn
auf Ja gesetzt"; insert a comma immediately after "Wenn auf Ja gesetzt" so the
clause reads "Wenn auf Ja gesetzt, und wenn der primäre..." (or restructure to
"Wenn auf Ja gesetzt, und wenn der primäre Speicher..." as appropriate) to
comply with German punctuation rules.
| ### Unterstützung für overlay2 Speicher-Treiber hinzufügen | ||
|
|
||
| Um "Docker-Fork-Bombs" zu verhindern, haben wir eine neue Einstellung eingeführt, ***Einstellungen → Docker → Docker PID Limit***, die die maximale Anzahl an Prozess-IDs angibt, die ein Container aktiv haben kann (Standardwert: 2048). | ||
| Verwenden Sie auf einem ZFS-Volume **Docker data-root=directory**, empfehlen wir, zu _**Einstellungen → Docker**_ zu navigieren und den **Docker-Speicher-Treiber** auf **overlay2** umzuschalten, dann den Verzeichnisinhalt zu löschen und Docker die Image-Ebenen neu herunterladen zu lassen. | ||
| Die veraltete **native** Einstellung verursacht erhebliche Stabilitätsprobleme auf ZFS-Volumes. | ||
|
|
||
| Wenn Sie einen Container haben, der mehr PIDs benötigt, können Sie entweder diese Einstellung erhöhen oder für einen spezifischen Container durch Hinzufügen von `--pids-limit 3000` zur Docker-Vorlage *Extra-Parameter* Einstellung übersteuern. | ||
| Wenn die Beibehaltung der Möglichkeit zum Downgrade auf frühere Versionen wichtig ist, dann wechseln Sie stattdessen zu **Docker data-root=xfs vDisk**. | ||
|
|
||
| ### Unterstützung für overlay2 Speicher-Treiber hinzufügen | ||
| ### Andere Änderungen | ||
|
|
||
| Verwenden Sie auf einem ZFS-Volume **Docker data-root=directory**, empfehlen wir, zu ***Einstellungen → Docker*** zu navigieren und den **Docker-Speicher-Treiber** auf **overlay2** umzuschalten, dann den Verzeichnisinhalt zu löschen und Docker die Image-Ebenen neu herunterladen zu lassen. | ||
| Verwenden Sie auf einem ZFS-Volume **Docker data-root=directory**, empfehlen wir, zu _**Einstellungen → Docker**_ zu navigieren und den **Docker-Speicher-Treiber** auf **overlay2** umzuschalten, dann den Verzeichnisinhalt zu löschen und Docker die Image-Ebenen neu herunterladen zu lassen. | ||
| Die veraltete **native** Einstellung verursacht erhebliche Stabilitätsprobleme auf ZFS-Volumes. | ||
|
|
||
| Wenn die Beibehaltung der Möglichkeit zum Downgrade auf frühere Versionen wichtig ist, dann wechseln Sie stattdessen zu **Docker data-root=xfs vDisk**. | ||
|
|
There was a problem hiding this comment.
Remove duplicate overlay2 storage driver guidance.
Lines 272–277 and 279–285 contain nearly identical content about overlay2 storage driver recommendations. Remove the duplication.
Apply this diff to consolidate and remove the duplicate:
### Unterstützung für overlay2 Speicher-Treiber hinzufügen
Verwenden Sie auf einem ZFS-Volume **Docker data-root=directory**, empfehlen wir, zu _**Einstellungen → Docker**_ zu navigieren und den **Docker-Speicher-Treiber** auf **overlay2** umzuschalten, dann den Verzeichnisinhalt zu löschen und Docker die Image-Ebenen neu herunterladen zu lassen.
Die veraltete **native** Einstellung verursacht erhebliche Stabilitätsprobleme auf ZFS-Volumes.
Wenn die Beibehaltung der Möglichkeit zum Downgrade auf frühere Versionen wichtig ist, dann wechseln Sie stattdessen zu **Docker data-root=xfs vDisk**.
-
-### Andere Änderungen
-
-Verwenden Sie auf einem ZFS-Volume **Docker data-root=directory**, empfehlen wir, zu _**Einstellungen → Docker**_ zu navigieren und den **Docker-Speicher-Treiber** auf **overlay2** umzuschalten, dann den Verzeichnisinhalt zu löschen und Docker die Image-Ebenen neu herunterladen zu lassen.
-Die veraltete **native** Einstellung verursacht erhebliche Stabilitätsprobleme auf ZFS-Volumes.
-
-Wenn die Beibehaltung der Möglichkeit zum Downgrade auf frühere Versionen wichtig ist, dann wechseln Sie stattdessen zu **Docker data-root=xfs vDisk**.
-### Verhinderung von Docker-Fork-Bombs
+### Weitere Docker-VerbesserungenCommittable suggestion skipped: line range outside the PR's diff.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~272-~272: Uneinheitliche Verwendung von Bindestrichen. Der Text enthält sowohl ‚Speicher-Treiber‘ als auch ‚Speichertreiber‘.
Context: ... Docker ### Unterstützung für overlay2 Speicher-Treiber hinzufügen Verwenden Sie auf einem ZFS...
(DE_COMPOUND_COHERENCY)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md
around lines 272 to 285 there is a duplicated paragraph explaining the overlay2
storage-driver guidance; remove the second occurrence (lines 279–285) so the
guidance appears only once under the appropriate heading, ensure surrounding
headings and spacing remain correct and no extra blank lines are left after
deletion.
| ## How do I manage my Unraid server in the account app? | ||
|
|
||
| To manage your Unraid server: | ||
|
|
||
| 1. Go to your Unraid server | ||
| 2. Open the dropdown menu in the top-right and click "Manage Unraid.net Account" or any visible license key related action buttons. |
There was a problem hiding this comment.
Translate the entire section heading and instructions to Chinese.
Lines 12-17 are in English but this is a Chinese localization file. The heading and step-by-step instructions must be translated to Chinese to maintain consistency with the rest of the document (lines 19-30 which are properly localized).
Apply this diff to complete the Chinese translation:
- ## How do I manage my Unraid server in the account app?
-
- To manage your Unraid server:
-
- 1. Go to your Unraid server
- 2. Open the dropdown menu in the top-right and click "Manage Unraid.net Account" or any visible license key related action buttons.
+ ## 我如何在账户应用中管理我的 Unraid 服务器?
+
+ 要管理您的 Unraid 服务器:
+
+ 1. 前往您的 Unraid 服务器
+ 2. 打开右上角的下拉菜单，点击"管理 Unraid.net 账户"或任何可见的许可证密钥相关操作按钮。Alternatively, reference the German version (i18n/de/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdx) for consistency if a professional translation is available.
📝 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.
| ## How do I manage my Unraid server in the account app? | |
| To manage your Unraid server: | |
| 1. Go to your Unraid server | |
| 2. Open the dropdown menu in the top-right and click "Manage Unraid.net Account" or any visible license key related action buttons. | |
| ## 我如何在账户应用中管理我的 Unraid 服务器? | |
| 要管理您的 Unraid 服务器: | |
| 1. 前往您的 Unraid 服务器 | |
| 2. 打开右上角的下拉菜单，点击"管理 Unraid.net 账户"或任何可见的许可证密钥相关操作按钮。 |
🤖 Prompt for AI Agents
In
i18n/zh/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdx
around lines 12 to 17, the section heading and the three-step instructions are
still in English; replace them with a Chinese translation that matches the style
of the surrounding localized content (lines 19–30). Change the heading "How do I
manage my Unraid server in the account app?" to an appropriate Chinese heading
and translate the list items: "To manage your Unraid server:", "1. Go to your
Unraid server", and "2. Open the dropdown menu in the top-right and click
"Manage Unraid.net Account" or any visible license key related action buttons."
into fluent Chinese, preserving meaning and UI text in quotes; follow wording
and tone consistent with i18n/zh and, if needed, reference the German file for
phrasing guidance.
| This option will **only** appear in the Navigation Bar if your Unraid server meets the %%hardware virtualization|hvm%% requirements. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Translate the untranslated VM note content to Chinese.
The note block for VMs (lines 77-79) is entirely in English within a Chinese localization file. This section must be translated to maintain consistency with the rest of the document.
Apply this diff to translate the section:
-This option will **only** appear in the Navigation Bar if your Unraid server meets the %%hardware virtualization|hvm%% requirements.
+此选项只有在您的 Unraid 服务器满足%%hardware virtualization|硬件虚拟化%%要求时才会在导航栏中出现。📝 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.
| This option will **only** appear in the Navigation Bar if your Unraid server meets the %%hardware virtualization|hvm%% requirements. | |
| ::: | |
| 此选项只有在您的 Unraid 服务器满足%%hardware virtualization|硬件虚拟化%%要求时才会在导航栏中出现。 | |
| ::: |
🤖 Prompt for AI Agents
In
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx
around lines 77 to 79, the VM note is still in English; translate the note into
Chinese while preserving the Markdown formatting and the inline placeholder
%%hardware virtualization|hvm%% and the surrounding ::: block and bold markup.
Replace the English sentence "This option will **only** appear in the Navigation
Bar if your Unraid server meets the %%hardware virtualization|hvm%%
requirements." with an equivalent Chinese sentence that keeps the bold emphasis
on "only" and leaves the placeholder unchanged.
|
|
||
| 您可以在**主界面**选项卡的同一**阵列操作**部分中使用相应按钮停止阵列、关闭或重启。 | ||
|
|
There was a problem hiding this comment.
Ensure consistent UI terminology translation in info block.
Line 95 uses "主界面选项卡" (Main interface tab), which translates the UI label differently from line 18. For consistency, this should use "主页面选项卡" (Main page tab) to match the standard Unraid UI terminology.
Apply this diff to fix the terminology:
-您可以在**主界面**选项卡的同一**阵列操作**部分中使用相应按钮停止阵列、关闭或重启。
+您可以在**主页面**选项卡的同一**阵列操作**部分中使用相应按钮停止阵列、关闭或重启。Based on learnings from PR 281.
📝 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.
| 您可以在**主界面**选项卡的同一**阵列操作**部分中使用相应按钮停止阵列、关闭或重启。 | |
| 您可以在**主页面**选项卡的同一**阵列操作**部分中使用相应按钮停止阵列、关闭或重启。 |
🤖 Prompt for AI Agents
In
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
around lines 94 to 96, the UI label translation uses "主界面" but should match the
standard term used elsewhere ("主页面"); update the string "**主界面**选项卡" to
"**主页面**选项卡" in that sentence so terminology is consistent with line 18 and
other docs.
| 您可以在此页面配置浏览器和电子邮件通知，订阅不同类型并为 %%SMART|smart%% 属性值设定自定义警报。 | ||
| Unraid 可以通过您的浏览器、电子邮件或第三方通知服务，向您发送关于重要系统事件、更新和警报的通知。通知设置页面可让您控制如何以及何时接收这些通知。 | ||
|
|
||
| 此处显示第三方插件，增强了 Unraid 的功能，并为您提供更多服务器控制。例如，[社区应用程序插件](../../using-unraid-to/run-docker-containers/community-applications.mdx) 已包含其中。其他插件提供了系统监控、维护、存储管理和 `appdata` 备份等功能。 |
There was a problem hiding this comment.
Remove misplaced third-party plugin reference from notification settings.
Line 214 contains "此处显示第三方插件..." which appears to be copied from the "用户实用工具" section (line 375). This content is contextually incorrect within the notification settings and should be removed. The same content correctly appears later in the "用户实用工具" section.
Apply this diff:
-此处显示第三方插件，增强了 Unraid 的功能，并为您提供更多服务器控制。例如，[社区应用程序插件](../../using-unraid-to/run-docker-containers/community-applications.mdx) 已包含其中。其他插件提供了系统监控、维护、存储管理和 `appdata` 备份等功能。
<div style={{ margin: 'auto', maxWidth: '400px'}}>📝 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.
| 此处显示第三方插件，增强了 Unraid 的功能，并为您提供更多服务器控制。例如，[社区应用程序插件](../../using-unraid-to/run-docker-containers/community-applications.mdx) 已包含其中。其他插件提供了系统监控、维护、存储管理和 `appdata` 备份等功能。 |
🤖 Prompt for AI Agents
In
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
around line 214, remove the misplaced sentence "此处显示第三方插件，增强了 Unraid
的功能，并为您提供更多服务器控制。例如，[社区应用程序插件](../../using-unraid-to/run-docker-containers/community-applications.mdx)
已包含其中。其他插件提供了系统监控、维护、存储管理和 `appdata` 备份等功能。" so the notification settings
section contains only relevant notification content; do not modify or relocate
this text because it already correctly appears in the "用户实用工具" section later.
| 首次访问 %%WebGUI|web-gui%% 时，系统会提示您为 %%root 用户|root-user%% 创建强密码。 | ||
|
|
||
| 请确保您的密码： | ||
| 我们推荐使用密码管理器来安全存储。 |
There was a problem hiding this comment.
Remove duplicate password manager recommendation.
The recommendation to use a password manager appears twice: at line 33 and again at line 39. Consolidate this into a single occurrence to avoid redundancy.
Apply this diff to remove the duplicate:
我们推荐使用密码管理器来安全存储。
- 唯一
- 至少 8 个字符。 （不过，最佳实践推荐使用 12+ 个字符来确保密码的最大安全性！）
- 字母、数字和特殊字符的组合
-
-我们推荐使用密码管理器来安全存储。Also applies to: 39-39
🤖 Prompt for AI Agents
In
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
around lines 33 and 39, the sentence "我们推荐使用密码管理器来安全存储。" is duplicated; remove
one of the two occurrences so the recommendation appears only once, keeping the
preferred placement (either line 33 or line 39) and deleting the other line to
consolidate the text.
There was a problem hiding this comment.
Actionable comments posted: 123
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (41)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/monitor-performance/smart-reports-and-disk-health.mdx (1)
20-27: Remove duplicate content and clarify the section structure.Lines 22 and 26 contain identical text: "Einige %%SMART|smart%% Attribute, die Unraid standardmäßig überwacht, umfassen:". Line 24 discusses clicking on drive names in the Web GUI, but then the same introduction repeats. This structure is confusing and suggests a copy-paste error or misalignment during the restructuring.
Clarify the flow: either remove the first introduction at line 22 and keep line 26 before the table, or move line 24's content elsewhere if it's meant to be contextual information.
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx (1)
22-24: Translate the Main tab section to Chinese.Lines 22–24 contain the entire "Main" tab description in English within a Chinese localization file. Additionally, per the UI learnings, "Main" should be translated as "主页面" to align with the actual Unraid interface terminology.
Apply this diff to translate the section:
-The **Main** screen enables efficient management of your Unraid storage and disk operations. You can configure your %%array|array%%, %%cache pools|cache-pool%%, and flash devices, as well as manage USB storage and unassigned devices, including remote shares. It displays key information about each storage device, such as health, capacity, and file systems. - -At the bottom, the Array Operation section provides maintenance options to keep your %%array|array%% running smoothly. +**主页面**屏幕能够高效地管理您的 Unraid 存储和磁盘操作。您可以配置您的%%array|阵列%%、%%cache pools|缓存池%%和闪存设备，以及管理 USB 存储和未分配设备，包括远程共享。它显示有关每个存储设备的关键信息，如健康状态、容量和文件系统。 + +在底部，阵列操作部分提供维护选项以保持您的%%array|阵列%%运行顺利。i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (3)
51-75: Remove duplicate "## BIOS 建议" header.The section header appears at both line 51 and line 75, creating structural confusion. The first section (lines 51–73) covers license key installation via WebGUI Quick Start, while the second (lines 75–105) contains actual BIOS configuration guidance. These should have distinct headers or be reorganized for clarity.
Suggested fix: Rename the first section to reflect license management (e.g., "## 安装试用密钥" or "## 许可证设置") and keep the second as "## BIOS 建议":
-## BIOS 建议 +## 安装试用密钥 在部署 Unraid OS 之前，务必验证系统的 BIOS 和存储控制器设置。下面是一个检查清单，帮助确保兼容性、稳定性，并获取关键功能。
88-91: Translate untranslated English text in advanced BIOS settings.Lines 90–91 contain English instructions for hardware virtualization and IOMMU support, breaking consistency with the surrounding Chinese documentation. These should be translated to Chinese.
Apply this diff to add Chinese translations:
### 高级设置 - ✅ 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. + ✅ 启用**%%硬件虚拟化|hvm%%%%**功能（例如**%%Intel VT-x|intel-vt-x%%%%**或**%%AMD-V|amd-v%%%%**）用于**%%虚拟机 (VMs)|vm%%%%**。\ + ✅ 启用**%%IOMMU|iommu%%%%**支持（Intel VT-d 或 AMD-Vi）用于虚拟机的 PCI 设备分配。
101-104: Correct markdown callout syntax.Line 101 uses
:::重要but should follow the standard callout format:::importantused consistently throughout the document. Mixing English and Chinese callout tags creates inconsistency.Apply this diff to fix the markdown syntax:
- :::重要 + :::important 许多主板将可启动设备限制为 12 个硬盘。如果您的 USB 闪存驱动器被识别为硬盘，则在安装 12 个物理硬盘后，您可能无法从中启动。在可能的情况下，将 BIOS 配置为将闪存驱动器视为可移动设备。 如果使用附加的 HBA，则您可以禁用 INT 13h 支持，以防止其连接的驱动器出现在可启动设备列表中，从而帮助保持在 12 驱动器限制范围内。\n :::i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (2)
33-39: Remove duplicate password manager recommendation.Lines 33 and 39 contain identical text: "Wir empfehlen die Verwendung eines Passwort-Managers zur sicheren Speicherung." This appears to be a copy-paste error; the recommendation should appear only once. Remove line 39 to avoid redundancy.
- Einzigartig - Mindestens 8 Zeichen lang. (Obwohl die beste Praxis 12+ für die sichersten Passwörter empfiehlt!) - Eine Mischung aus Buchstaben, Zahlen und Sonderzeichen - -Wir empfehlen die Verwendung eines Passwort-Managers zur sicheren Speicherung.
51-75: Resolve duplicate section headers breaking document structure.The document contains two identical level-2 headers "## BIOS-Empfehlungen" (lines 51 and 75). This violates Markdown document hierarchy and will cause issues with:
- Table of contents generation in Docusaurus
- Document navigation and cross-references
- Reader orientation
Additionally, the first section (lines 51–73) contains license registration and trial-key installation steps, which contradicts its "BIOS-Empfehlungen" header. The second section (lines 75–105) contains the actual BIOS settings guidance.
Action required: Either rename the first section header (line 51) to reflect its license-management content (e.g., "Lizenzschlüssel registrieren"), or consolidate/reorganize these sections into separate, properly named headers.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx (1)
122-126: Section header restructuring creates ambiguous scope.Line 122 renames the section from "Netzwerkdienste" to "NFS (Network File System)", but lines 124–125 retain generic "Network Services" introductory text in English. This mismatch suggests the section now covers only NFS, yet the intro describes broader network protocols (FTP, Syslog, Tailscale, VPN).
Clarify the section intent: either localize the intro text to reflect NFS-specific scope, or rename the header back to reflect network services broadly.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (2)
197-263: Remove duplicate section: "Mindestfreier Speicherplatz für einen Cache-Pool" appears twice.The section titled "Mindestfreier Speicherplatz für einen Cache-Pool" appears at line 197 and again at line 227 with nearly identical or very similar content. Consolidate into a single section, and delete the duplicate at lines 227–263 (or vice versa, whichever is the canonical version).
19-36: Consolidate mixed English/German content throughout info block.Lines 19–36 mix German headers ("%%Cache-Pools|cache-pool%% bieten mehrere Vorteile...") with English bullet items (e.g., "Faster write speeds:", "Data protection..."). Translate all English content to German for a cohesive German translation.
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx (1)
15-31: Malformed important block with duplicated content outside.Lines 15–19 define an
:::importantblock that appears incomplete or incorrectly closed. The content "Fernzugriff über Unraid Connect bietet:" and its following bullets (lines 21–25) duplicate the intended block content, suggesting the block structure was not properly refactored.The important block should contain the feature bullets. Apply this diff to consolidate:
-:::important[Security erinnerung] - -Fernzugriff über Unraid Connect bietet: - -::: - -Fernzugriff über Unraid Connect bietet: - -- **Bequemlichkeit** - Greifen Sie schnell auf die Verwaltungsoberfläche Ihres Servers von überall zu, mit einer sicheren, cloudverwalteten Verbindung. -- **Sicherheit** - Dynamische Zugriffsmodi begrenzen die Exposition, indem der Zugang zum Internet nur dann erlaubt ist, wenn es nötig ist, was die Risiken durch automatisierte Angriffe reduziert. -- **Einfachheit** - Keine Notwendigkeit für manuelle Portweiterleitungen oder VPN-Client-Einrichtung für grundlegende Verwaltungsaufgaben. +:::important[Security reminder] + +Fernzugriff über Unraid Connect bietet: + +- **Bequemlichkeit** - Greifen Sie schnell auf die Verwaltungsoberfläche Ihres Servers von überall zu, mit einer sicheren, cloudverwalteten Verbindung. +- **Sicherheit** - Dynamische Zugriffsmodi begrenzen die Exposition, indem der Zugang zum Internet nur dann erlaubt ist, wenn es nötig ist, was die Risiken durch automatisierte Angriffe reduziert. +- **Einfachheit** - Keine Notwendigkeit für manuelle Portweiterleitungen oder VPN-Client-Einrichtung für grundlegende Verwaltungsaufgaben. + +:::i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx (1)
122-126: Fix section header and introductory text to match: Line 122 header "NFS (网络文件系统)" conflicts with line 124's "网络服务" (Network Services). Additionally, line 126 repeats the same header name, creating redundancy. Clarify the structure by either renaming line 122 back to "## 网络服务" or updating line 124's bold text to align with the NFS emphasis to maintain consistency with the subsection.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md (2)
212-224: Remove duplicate "Ändern des Dateisystemtyps eines Pools" section.Lines 212–217 and lines 219–224 contain identical content and headings. The section should appear only once.
Apply this diff to remove the duplicate:
Für alle Einzel-Slot-Pools kann der Dateisystemtyp geändert werden, wenn das Array gestoppt ist. Für btrfs/zfs-Multiple-Slot-Pools kann der Dateisystemtyp nicht geändert werden. Um die Geräte wiederzuverwenden, müssen Sie die Schaltfläche Pool löschen klicken. -Ändern des Dateisystemtyps eines Pools: - -Für alle Einzel-Slot-Pools kann der Dateisystemtyp geändert werden, wenn das Array gestoppt ist. - -Für btrfs/zfs-Multiple-Slot-Pools kann der Dateisystemtyp nicht geändert werden. Um die Geräte wiederzuverwenden, -müssen Sie die Schaltfläche Pool löschen klicken. ### Verbesserungen
153-165: Remove incomplete placeholder text and consolidate duplicate Docker-Manager descriptions.Line 157 contains incomplete placeholder text ("vielleicht hatten wir keinen Platz mehr" — "maybe we had no more space") that should not appear in release notes. Additionally, lines 153–157 describe Docker-Manager shares, and this description is repeated identically in lines 160–165 under the "Vorhandene Freigaben verwalten" section, creating redundancy.
Action required:
- Remove line 157 entirely.
- Consolidate or remove one of the two Docker-Manager descriptions to eliminate redundancy.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx (2)
99-102: ---Remove DiskSpeed installation instructions from the "Top-Nutzung anzeigen" section.
Lines 99–102 contain DiskSpeed (a disk speed testing app) inside a collapsible labeled "Show Top Usage," which is semantically incorrect. The
topcommand is a real-time process monitor; DiskSpeed installation does not belong in this section. Either remove this content entirely (since it's an application, not a CLI tool), or move it to a dedicated subsection under Systemüberwachung for disk monitoring utilities.
240-287: Restructure duplicated network diagnostics section — confirmed critical structural issues.The file contains severe structural problems that extend beyond the initially reviewed section:
Lines 240–287 (Network Diagnostics)
- Line 244: Details box labeled "Ss-Optionen" incorrectly contains
blkidcommand- Lines 261–287:
### pingsubsection containsss -tulnandss -tupexamples (socket commands, not ping tests)- Lines 288–295:
### ethtoolsubsection containsip addr showandip route showcommands (IP config commands, not ethtool)- Lines 296–303: Duplicate
### pingheader immediately follows- Lines 304–308:
### tailsubsection appears within network diagnostics sectionDuplicate headers throughout file
## ethtoolappears both as subsection (line ~288) and again as top-level header (line ~331)## tailappears both as subsection (line ~304) and as top-level header (line ~367)### tailappears as duplicate subsection (line ~378)The entire network diagnostics section requires reorganization to place commands under correct headers, remove duplicates, and correct misplaced content in details boxes.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx (2)
72-114: Remove duplicate<details>blocks in boot sequence section.The sections for "6. WebGUI" and "7. Array" are duplicated (lines 72–84 and 95–102 for WebGUI; lines 86–93 and 104–114 for Array). The second instances are truncated or incomplete. This appears to be a merge conflict or restructuring error. Retain only the more complete versions and remove the duplicates.
Consolidate by removing lines 95–114 and keeping the more comprehensive first versions (lines 72–93):
</details> -<details> - <summary><strong>6. WebGUI</strong> - Zum Erweitern/Kollabieren klicken</summary> - - Die webbasiertem Verwaltungsoberfläche wird verfügbar und ermöglicht die Fernadministration und -konfiguration Ihres Servers. - - - Die %%WebGUI|web-gui%% startet an diesem Punkt. - - Die Datei `config/go` auf dem Flash-Gerät kann Benutzerbefehle vor oder nach dem Start der %%WebGUI|web-gui%% ausführen. -</details> - -<details> - <summary><strong>7. Array</strong> - Zum Erweitern/Kollabieren klicken</summary> - - Speichergeräte werden eingehängt und verfügbar gemacht, was den Bootvorgang abschließt. Hier werden Ihre Daten zugänglich. - - - Wenn Autostart aktiviert ist, beginnt das %%array|array%% hier; andernfalls ist ein manueller Start erforderlich. - - Laufwerke werden als `/dev/diskX` und `/mnt/cache` (falls vorhanden) eingehängt. - - Freigaben werden im Netzwerk als `/mnt/user/sharename` verfügbar. - - Docker-Container starten in der auf der Docker-Seite angegebenen Reihenfolge mit anpassbaren Verzögerungen. - - Automatisch startende virtuelle Maschinen (%%VMs|vm%%) werden ebenfalls gestartet. -</details> An diesem Punkt ist der Unraid-Server voll funktionsfähig.
149-151: Translate untranslated English sections in recovery procedure.Lines 151, 164, and surrounding recovery procedure text contain English content that should be translated to German for consistency with the rest of the file.
Line 151: "Unraid identifies data drives by detecting existing valid file systems..." needs German translation.
Line 164+: "If the %%parity|parity%% is valid..." and the warning block "If you have multiple %%parity drives|parity-drives%%..." also require translation.
These appear to be incomplete translation work in the recovery section (approximately lines 149–174).
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/shares-primary-storage-612.mdx (1)
15-25: Remove duplicated "Sekundärspeicher-Dropdown" section.Lines 15–19 and 21–25 both define a "Sekundärspeicher-Dropdown:" section with nearly identical content. This is a clear duplication that should be removed. Retain only one version of this section and verify the content is accurate.
- **Sekundärspeicher-Dropdown:** - - - **None:** Kein Sekundärspeicher ist für die Freigabe festgelegt (optional). - - Wenn der Primärspeicher ein %%pool|cache-pool%% ist, stehen **None**, **Array** und **Ein anderer Pool** zur Verfügung. - - Sie können jeden benannten %%pool|cache-pool%% oder das %%array|array%% wählen. - - **Sekundärspeicher-Dropdown:** - - - **None:** Kein Sekundärspeicher ist für die Freigabe festgelegt (optional). - - Wenn der Primärspeicher ein %%pool|cache-pool%% ist, stehen **None**, **Array** und **Ein anderer Pool** zur Verfügung. - - If the primary storage is the **Array**, **None** and any eligible %%pools|cache-pool%% are available. + **Sekundärspeicher-Dropdown:** + + - **None:** Kein Sekundärspeicher ist für die Freigabe festgelegt (optional). + - Wenn der Primärspeicher ein %%pool|cache-pool%% ist, stehen **None**, **Array** und **Ein anderer Pool** zur Verfügung. + - Sie können jeden benannten %%pool|cache-pool%% oder das %%array|array%% wählen. + - If the primary storage is the **Array**, **None** and any eligible %%pools|cache-pool%% are available.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx (1)
47-56: Mixed English/German content; incomplete translation confirmed.The file contains extensive English text in a German localization. Lines 47–56 contain entirely English paragraphs ("When your system shuts down gracefully...", "By default, diagnostics are automatically anonymized..."), followed by German section headers ("Ermittlung der Lesegeschwindigkeit von Festplatten"), followed by more English content ("You can use built-in Linux tools..."). This mixed-language pattern continues throughout the document.
The corresponding English source file does not exist, indicating this is not intentional shared content. The entire German localization file requires translation to ensure consistency for German-speaking users.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx (1)
1-50: Remove "extensive" and "throughout" - restrict claim to identified untranslated paragraphs.This German localization file contains untranslated English content in specific sections, particularly at lines 11, 30, and 39. Lines 11 and 39 contain full English paragraphs ("An unclean shutdown happens..." and "Properly configuring shutdown timeouts..."), while line 30 contains an untranslated English bullet point. These sections should be translated to complete the German localization.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx (3)
53-88: Duplicate section heading and incomplete English text requires fixing before merge.Line 53 introduces the section "Gerätenamensgebung: Pfade und Symbole", and then line 86 introduces an identical heading "Checken und Reparieren von Laufwerken im WebGUI". However, a second "Checken und Reparieren von Laufwerken im WebGUI" heading appears at line 112. Additionally, line 84 contains an entirely untranslated English sentence ("For non-%%array|array%% drives...") that breaks the German flow. Line 88 also repeats the heading with a slightly different encoding (
|vs|) which is unnecessary.
- Remove the duplicate/misplaced heading at line 86.
- Translate or remove the English sentence at line 84.
- Remove the redundant heading at line 88 (or consolidate the two identical headings into one).
- Verify the structure matches the English version to ensure consistency.
173-220: Mixed English and German content; incomplete translations.This section contains multiple untranslated English passages that disrupt the German localization:
- Line 175–176: "Losing your %%array|array%% configuration..." (English)
- Line 231: "Write down or take a screenshot..." (English)
- Line 235: "Return to the Main tab..." (English)
These sentences should be translated to German to complete the localization. Additionally, LanguageTool flags at line 246 suggest a punctuation issue (em dash vs period).
Translate the untranslated English sentences to German, or confirm these are intentional references. Also apply the punctuation fix suggested by LanguageTool at line 246.
240-313: Inconsistent compound word hyphenation; mixed English content; LanguageTool grammar flags.Static analysis indicates inconsistent use of hyphens: "Dateisystem-Reparaturtools" (line 76) vs. "Dateisystem-Reparatur-Tools" (referenced in hints). Additionally:
Line 244: "Best Methoden" should be "Beste Methoden" (LanguageTool grammar flag).
Lines 250–252: Repeated sentence about ddrescue and Nerd Tools plugin (appears at line 189 as well).
Line 270: Untranslated English sentence: "If you want to clone directly..." (should be German).
Multiple ellipsis formatting inconsistencies flagged by LanguageTool.
Standardize hyphenation of compound words (choose either "Dateisystem-Reparaturtools" or "Dateisystem-Reparatur-Tools" and apply consistently).
Fix "Best Methoden" → "Beste Methoden".
Remove or consolidate the duplicate ddrescue/Nerd Tools explanation (lines 189 vs. 250).
Translate or remove the untranslated English sentence at line 270.
Address ellipsis formatting per LanguageTool suggestions.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (1)
33-37: Verified: German localization file contains extensive untranslated English sections.The flagged sections are confirmed to contain untranslated English content mixed throughout the file:
- Lines 33–37, 108, 127: English paragraphs and guidance interspersed after German headers/bullets
- Lines 131–137: English feature description mixed within German bullet list
- Lines 224, 239, 321: Critical issue—identical English paragraph appears three times without translation, appearing to be duplicated content in a section titled "Kompression und RAM" (German header)
This is a clear localization gap rather than intentional English preservation. The file mixes German structure (section headers, some bullet points) with untranslated English content, and the repetition of identical paragraphs suggests incomplete translation work.
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (1)
138-165: Clarify or consolidate duplicate "Lizenzverwaltung" sections.The document has two sections named "Lizenzverwaltung" (License Management):
- Line 138 starts "## Anpassung" (Customization)
- Line 148 begins "## Lizenzverwaltung" with tabs for customization actions (banner, dashboard, themes)
- Line 168 repeats "## Lizenzverwaltung" with license key management content (lines 170–179)
This creates ambiguity. The first "Lizenzverwaltung" (line 148) actually contains customization features, while the second (line 168) covers license key operations. Consider restructuring:
- Rename line 138 section to "## Anpassung und Lizenzverwaltung" or split into two clear sections, or
- Move the tabs (lines 152–164) into the "## Anpassung" section and keep "## Lizenzverwaltung" (line 168) focused solely on key management.
- ## Anpassung + ## Anpassung und Benutzeroberfläche Mit Deep Linking in Unraid Connect können Sie... - ## Lizenzverwaltung + [Move tabs and customization content here] Die Verwaltung Ihrer Lizenzen in Unraid Connect ist einfach...i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx (1)
70-114: Remove duplicate section header and consolidate UPnP instructions.The section header "## 使用 UPnP（通用即插即用）" appears twice (line 70 and line 90), with two different sets of instructions. This is confusing for readers. Lines 70–87 contain a 6-step flow, while lines 90–114 contain a reworked 4-step flow with a troubleshooting caution block. It appears the second instance (lines 90–114) is the intended replacement, but the old section was not fully removed.
Consolidate into a single section by removing the duplicate header and the first set of instructions (lines 70–87), keeping only the second section (lines 90–114) which contains the expanded configuration guidance and troubleshooting notes.
-## 使用 UPnP（通用即插即用） - -UPnP 自动化了端口转发，简化了远程访问而无需手动路由器配置。 - -1. 在***设置 → 管理访问 → Unraid API***中，选择远程访问下拉菜单中的动态选项： - - **动态 - UPnP：** 使用%%UPnP|upnp%%自动打开和关闭随机端口（需要在路由器上启用%%UPnP|upnp%%）。 - - \*\*动态 - 手动端口转发：\*\*需要您手动在路由器上转发选定的端口。 - -2. 导航到 [Unraid Connect](https://connect.myunraid.net/)，并进入管理或服务器详细页面。 - -3. 如果您的服务器当前无法从您的位置访问，则**动态远程访问**卡片将显示一个按钮。 - -4. 点击按钮以启用 WAN 访问。如果使用 %%UPnP|upnp%%，将创建一个新端口转发租约（通常为 30 分钟）并在活动期间自动续订。 - -5. 该卡将显示当前状态和 UPnP 状态。 - -6. 在 10 分钟不活动后 - 或者如果您点击 **禁用远程访问** - 将自动撤销互联网访问。%%UPnP|upnp%% 租约也会被移除。 - ---- - ## 使用 UPnP（通用即插即用）i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (1)
92-104: Remove duplicate section header "备份加密".The section header "## 备份加密" appears at line 92, followed by a subsection "### 备份加密" at line 101 within the "## 隐私与安全" section. This creates confusing header hierarchy. The content at lines 92–98 appears to belong under the "## 隐私与安全" umbrella, so consolidate by removing the redundant top-level header at line 92.
-## 备份加密 - -当前，Flash 备份存储在云中且未加密。作为预防措施，备份中从不包括敏感数据，包括所有用户和 root 密码以及所有 %%WireGuard|wireguard%% 密钥。 - -1. 在 ***设置 → 管理访问 → Unraid API*** 中，点击 **停用** 闪存备份。 -2. 在确认对话框中，如果您希望立即删除备份，请勾选 **也删除云备份**。否则，备份将在空闲一段时间后自动删除。 - ## 隐私与安全i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (2)
138-164: Correct section header: "自定义" not "许可证管理".Line 138 shows a section header "## 自定义" (Customization), but line 148 incorrectly changes it to "## 许可证管理" (License Management). However, the content in lines 152–164 (the Tabs component with banner, dashboard rearrangement, and theme customization) is clearly customization content, not license management.
The actual license management content appears later at lines 168–175 under a second "## 许可证管理" header.
Restore the correct header for lines 138–164 and remove the duplicate "许可证管理" at line 148:
-## 许可证管理 - -在 Unraid Connect 中管理您的许可证很简单。在 **我的密钥** 部分，您可以： +## 自定义 + +在 Unraid Connect 中自定义您的体验很简单：
200-230: Consolidate redundant "卸载插件" section.The section header "## 卸载插件" appears at line 217, but the content describing uninstall consequences already appears at lines 208–214 under the "当您点击服务器上的详情时" context (line 200). Lines 217–230 repeat this same information under a separate header. Consolidate to remove duplication.
Move the uninstall guidance into a single, clearly labeled section and remove the duplicate:
当您退出登录时： --- -## 退出登录 - -您可以随时从 ***设置 → 管理访问 → Unraid Connect → 账户状态*** 点击 **退出登录** 按钮来注销 Unraid Connect。 - -卸载 Unraid Connect 插件时： - -- 所有闪存备份文件将被停用并从本地闪存驱动器中删除。 -- 云备份标记为从 Unraid 服务器中移除；它们将保留 30 天，之后将永久清除。如需立即删除，请在卸载前[禁用闪存备份](./automated-flash-backup.mdx)。 -- 远程访问将被禁用。确保从路由器中移除任何相关的端口转发规则。 -- 您的服务器将从 Unraid.net 注销。 - ---- - ## 卸载插件 卸载 Unraid Connect 插件时：i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx (1)
40-51: CRITICAL: Remove duplicate header.Line 40 and line 51 contain identical headers "What to do if you encounter %%parity|parity%% errors". This is a duplicate that should be removed. The section structure appears to be corrupted with the header appearing twice.
Remove the first occurrence (line 40) and keep only the properly structured section starting at line 51.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx (1)
99-130: Remove the first redundant detail block (lines 99–108).The file contains two identical section headers ("3. Erstellen und starten Sie die VM"). The first block (lines 99–108) is an incomplete predecessor; the second block (lines 110–130) contains all its content plus comprehensive additions (display settings, UPS configuration, Community Applications, and OS updates). Delete lines 99–108 to eliminate redundancy and preserve the complete, current workflow.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx (1)
145-174: Remove duplicate "VPN-Tunneling-Zugriff für das System konfigurieren" section.Lines 145–157 and 158–174 contain two conflicting versions of the same configuration section. The first directs users to install Firefox and accept defaults; the second provides different steps. Merge these into a single, cohesive guide or clarify which is the authoritative workflow.
Review the two sections and consolidate:
- Lines 145–157: Install Firefox, configure via VPN-Manager, enable tunnel, verify at dnsleaktest.com
- Lines 158–174: Install Firefox, accept defaults, visit whatismyipaddress.com, enable tunnel, note DNS/update requirements
Suggested action: Keep the second version (lines 158–174) as it includes critical DNS and update notes in the :::note block, and remove the first version (lines 145–157).
i18n/zh/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx (1)
238-242: Fragmented testing/troubleshooting flow.Lines 238–242 describe testing steps, but the subsequent sections (lines 244+) introduce troubleshooting under a different heading structure. The flow from "✅ Testing Your Configuration" to troubleshooting lacks clear transitions and includes duplicate/reordered steps. Restructure to create a cohesive testing → troubleshooting → debugging progression.
Reorganize the section order: consolidate all testing steps, followed by common issues, then advanced debugging. Remove duplicate content identified in the "Debug-Modus" duplication issue above.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx (1)
193-224: Remove duplicated Userspace Networking content from "Serve vs. Trichter" section.The identical explanation appears at both lines 146–149 and lines 197–200. The content under ":::info[Serve vs. Trichter]" incorrectly describes Userspace Networking behavior instead of Serve/Funnel behavior. Either remove this redundant block and keep only the "## Userspace-Netzwerk" section, or replace the "Serve vs. Trichter" section with appropriate content explaining Serve (reverse proxy) vs. Funnel (public internet) functionality.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx (2)
92-129: Remove duplicate section with identical heading.Lines 92–129 and 131–159 both contain the heading "HTTPS mit Myunraid.net-Zertifikat und ohne Fallback-URL" with nearly overlapping content. The second occurrence appears to be a copy-paste error or merge artifact. Consolidate these sections into a single, unified treatment or clarify the intent if they are meant to differ.
Also applies to: 131-159
14-180: Remove or translate English content in German localization.This German localization file contains multiple blocks of untranslated English text that break the German-language experience:
- Line 97: "This method provides the highest level of %%SSL|ssl%%..."
- Lines 177–180: "Custom certificates allow you to secure your Unraid..."
- Line 190: Info block header mixing "When" (English) + "Bei der Verwendung..." (German)
- Lines 256–257, 287–296: Multiple English paragraphs ("You should disable...") interspersed with German instructions
Either translate these sections fully to German or remove them if they duplicate information already provided in German above. A mixed-language document diminishes the localization quality.
Also applies to: 256-287
i18n/de/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx (4)
372-425: Remove duplicate provider sections for Authentik and Okta.The Authentik configuration appears twice (lines 372–384 and 400–412) and Okta appears twice (lines 386–398 and 414–425). Delete the duplicate sections to prevent user confusion and maintain clean documentation structure.
Apply this diff to remove duplicates:
Berechtigungsrichtlinien können in der Schnittstelle mit E-Mail-Domains oder erweiterten Ansprüchen konfiguriert werden. -### Authentik - -Erstellen Sie einen neuen OAuth2/OpenID-Anbieter in Authentik und erstellen Sie eine Anwendung, die mit dem Anbieter verknüpft ist. - -**Konfiguration:** - -- **Issuer URL**: `https://login.microsoftonline.com/YOUR_TENANT_ID/v2.0` -- **Client-ID**: Aus der Authentik-Anbieter-Konfiguration -- **Client-Secret**: Aus der Authentik-Anbieter-Konfiguration -- **Erforderliche Scopes**: `openid`, `profile`, `email` -- **Redirect-URI**: `http://YOUR_UNRAID_IP/graphql/api/auth/oidc/callback` - -Berechtigungsrichtlinien können in der Schnittstelle konfiguriert werden. - -### Okta - -Erstellen Sie eine neue OIDC-Webanwendung in der Okta-Admin-Konsole und weisen Sie entsprechende Benutzer oder Gruppen zu. - -**Konfiguration:** - -- **Issuer URL**: `https://YOUR_DOMAIN.okta.com` -- **Client-ID**: Aus der Okta-Anwendungskonfiguration -- **Client-Secret**: Aus der Okta-Anwendungskonfiguration -- **Erforderliche Scopes**: `openid`, `profile`, `email` -- **Redirect-URI**: `http://YOUR_UNRAID_IP/graphql/api/auth/oidc/callback` - -Berechtigungsrichtlinien können in der Schnittstelle konfiguriert werden.
216-243: Remove duplicate "✅ Konfiguration testen" section.The testing section is duplicated across lines 216–225 and 233–243 with nearly identical content (image, security notes, and test steps). Retain the more complete version and delete the redundant copy to eliminate confusion.
76-82: Fix duplicate heading "### Beispiele für den einfachen Modus".Line 76 introduces a new section with
## Beispiele für den einfachen Modus, immediately followed by an identical### Beispiele für den einfachen Modusheading at line 81–82. Remove the duplicate heading level to create a clean hierarchy.
46-56: Remove duplicate "Wann sollte der einfache Modus verwendet werden:" subsection.Lines 46–50 and 52–56 both introduce "Wann sollte der einfache Modus verwendet werden:" with similar bullet content. Consolidate into a single subsection or restructure to avoid repetition.
| | | **Empfohlen für die meisten** | | | ||
|
|
||
| ## Einrichten des dynamischen Fernzugriffs | ||
| ## Verwendung von UPnP (Universal Plug and Play) |
There was a problem hiding this comment.
Duplicate section header: "## Verwendung von UPnP" appears twice.
Line 70 and line 90 both define the same section header ## Verwendung von UPnP (Universal Plug and Play). This breaks documentation structure and will cause table-of-contents conflicts.
The second header (line 90) should be renamed or removed. Based on the content that follows (troubleshooting note, then UPnP configuration steps), consider renaming line 90 to:
-## Verwendung von UPnP (Universal Plug and Play)
+## UPnP konfigurierenOr, if the content at lines 90–114 is meant to be a subsection of the first UPnP section, restructure it as:
-## Verwendung von UPnP (Universal Plug and Play)
+### UPnP-KonfigurationsschritteAlso applies to: 90-90
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx
around lines 70 and 90, there is a duplicate section header "## Verwendung von
UPnP (Universal Plug and Play)"; remove the duplicate by either renaming the
header on line 90 to a distinct subsection title (for example "### Probleme mit
UPnP (Fehlerbehebung)" or "### UPnP: Fehlerbehebung und Hinweise") or convert
the line-90 header to a third-level header (prepend one additional #) so the
troubleshooting steps become a subsection of the main UPnP section, ensuring
only one top-level "## Verwendung von UPnP" remains and updating adjacent
anchors/links if present.
| ## Verwendung von UPnP (Universal Plug and Play) | ||
|
|
||
| %%UPnP|upnp%% automatisiert die Portweiterleitung und vereinfacht den Fernzugriff, ohne dass eine manuelle Routerkonfiguration erforderlich ist. | ||
| Wenn sich die Einstellung beim Neuladen von %%UPnP|upnp%% auf manuelle Portweiterleitung ändert, kann es sein, dass Unraid nicht mit Ihrem Router kommunizieren kann. Überprüfen Sie, ob %%UPnP|upnp%% aktiviert ist, und erwägen Sie, die Firmware Ihres Routers zu aktualisieren. |
There was a problem hiding this comment.
Identical troubleshooting caution duplicated verbatim.
Lines 92 and 112 contain the exact same troubleshooting text about UPnP/manual port forwarding. This appears to be a copy-paste artifact introduced during restructuring.
Remove the duplicate at line 112, keeping the one in the caution block (lines 110–114):
Wenn die manuelle Portweiterleitung zu konfigurieren:
1. **Wählen Sie einen WAN-Port:** Wählen Sie eine zufällige Portnummer über 1000 (zum Beispiel 13856 oder 48653), anstelle des Standards 443.
2. **Einstellungen in Unraid anwenden:** Klicken Sie auf **Anwenden**, um den gewählten Port zu speichern.
3. **Konfigurieren Sie Ihren Router:** Richten Sie eine Portweiterleitungsregel auf Ihrem Router ein, die den von Ihnen gewählten WAN-Port auf den HTTPS-Port Ihres Servers leitet. Die Unraid-Schnittstelle stellt die richtigen Ports und die IP-Adresse bereit.
Einige Router erfordern möglicherweise, dass der WAN-Port und der HTTPS-Port übereinstimmen. Verwenden Sie in diesem Fall dieselbe hohe Zufallszahl für beide.
4. **Überprüfen Sie die Portweiterleitung (nur immer eingeschaltet):** Drücken Sie die Schaltfläche **Prüfen**. Wenn alles korrekt ist, sehen Sie „Ihr Unraid-Server ist vom Internet aus erreichbar."
Bei dynamischer Weiterleitung klicken Sie auf **Dynamischen Fernzugriff aktivieren** in [Unraid Connect](https://connect.myunraid.net/), um den Zugriff zu aktivieren.
5. **Zugriff auf Ihren Server:** Melden Sie sich bei [Unraid Connect](https://connect.myunraid.net/) an und klicken Sie auf den **Verwalten**-Link, um sich remote mit Ihrem Server zu verbinden.
---
## Sicherer lokaler Zugriff aktivieren
Sicherer lokaler Zugriff stellt sicher, dass alle Verbindungen zu Ihrem Unraid-%%WebGUI|web-gui%%, sogar innerhalb Ihres Heim- oder Büronetzwerks, mit HTTPS verschlüsselt werden, um alle sensiblen Informationen, wie Anmeldedaten und Konfigurationsdaten, zu schützen.
Zu den Vorteilen des sicheren lokalen Zugriffs gehören:
- **Verschlüsselung** - Alle zwischen Ihrem Browser und dem Server ausgetauschten Daten sind geschützt.
- **Konsistenz** - Verwenden Sie dieselbe sichere URL für sowohl lokalen als auch Fernzugriff.
- **Einhaltung** - Befolgt die Sicherheitsbestenpraktiken zum Schutz administrativer Schnittstellen.
Um sicheren lokalen Zugriff zu aktivieren:
1. Gehen Sie zu ***Einstellungen → Verwaltungszugriff***.
2. Überprüfen Sie im Bereich **CA-signiertes Zertifikat** auf Warnungen zu DNS-Rebinding.
- Wenn keine Warnungen angezeigt werden, setzen Sie **SSL/TLS verwenden** auf **Strikt**.
- Wenn Warnungen vorhanden sind, lesen Sie [DNS-Rebinding-Schutz](../unraid-os/system-administration/secure-your-server/securing-your-connection.mdx#dns-rebinding-protection).
:::important
-Mit %%SSL|ssl%%/%%TLS|tls%% auf Strict gesetzt, müssen Client-Geräte den DNS-Namen Ihres Servers auflösen. Wenn Ihre Internetverbindung ausfällt, kann der Zugriff auf das %%WebGUI|web-gui%% verloren gehen. In [Zugriff auf Ihren Server, wenn DNS ausgefallen ist](../unraid-os/system-administration/secure-your-server/securing-your-connection.mdx#accessing-your-server-when-dns-is-down) finden Sie Wiederherstellungsschritte.
+Mit %%SSL|ssl%%/%%TLS|tls%% auf Strict gesetzt, müssen Client-Geräte den DNS-Namen Ihres Servers auflösen. Wenn Ihre Internetverbindung ausfällt, kann der Zugriff auf das %%WebGUI|web-gui%% verloren gehen. In [Zugriff auf Ihren Server, wenn DNS ausgefallen ist](../unraid-os/system-administration/secure-your-server/securing-your-connection.mdx#accessing-your-server-when-dns-is-down) finden Sie Wiederherstellungsschritte.
:::Also applies to: 112-112
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx
around lines 92 to 112: there is an identical troubleshooting sentence about
UPnP/manual port forwarding duplicated at line 112; remove the duplicate
sentence at line 112 so only the caution block (lines 110–114) remains, keeping
surrounding punctuation and spacing intact.
|
|
||
| :::important | ||
|
|
||
| Mit %%SSL|ssl%%/%%TLS|tls%% auf Strict gesetzt, müssen Client-Geräte den DNS-Namen Ihres Servers auflösen. Wenn Ihre Internetverbindung ausfällt, kann der Zugriff auf das %%WebGUI|web-gui%% verloren gehen. In [Zugriff auf Ihren Server, wenn DNS ausgefallen ist](../unraid-os/system-administration/secure-your-server/securing-your-connection.mdx#accessing-your-server-when-dns-is-down) finden Sie Wiederherstellungsschritte. |
There was a problem hiding this comment.
Fix line-ending formatting issue flagged by static analysis.
Line 159 has ::: (block closure) on the same line as the period, when it should be on its own line. This breaks the Markdown block structure.
-Mit %%SSL|ssl%%/%%TLS|tls%% auf Strict gesetzt, müssen Client-Geräte den DNS-Namen Ihres Servers auflösen. Wenn Ihre Internetverbindung ausfällt, kann der Zugriff auf das %%WebGUI|web-gui%% verloren gehen. In [Zugriff auf Ihren Server, wenn DNS ausgefallen ist](../unraid-os/system-administration/secure-your-server/securing-your-connection.mdx#accessing-your-server-when-dns-is-down) finden Sie Wiederherstellungsschritte. :::
+Mit %%SSL|ssl%%/%%TLS|tls%% auf Strict gesetzt, müssen Client-Geräte den DNS-Namen Ihres Servers auflösen. Wenn Ihre Internetverbindung ausfällt, kann der Zugriff auf das %%WebGUI|web-gui%% verloren gehen. In [Zugriff auf Ihren Server, wenn DNS ausgefallen ist](../unraid-os/system-administration/secure-your-server/securing-your-connection.mdx#accessing-your-server-when-dns-is-down) finden Sie Wiederherstellungsschritte.
:::Committable suggestion skipped: line range outside the PR's diff.
🧰 Tools
🪛 LanguageTool
[grammar] ~159-~159: Passe das Symbol an
Context: ...our-server-when-dns-is-down) finden Sie Wiederherstellungsschritte. :::
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx
around line 159, the closing Markdown block marker ":::" is on the same line as
the preceding sentence period which breaks block structure; move the ":::”
marker to its own line immediately after the sentence (i.e., end the sentence
with a period, insert a newline, then place ":::” on the next line), and ensure
the file uses proper LF line endings with no trailing spaces.
|
|
||
| Unter Windows können Laufwerke, die größer als 32 GB sind, nicht als FAT32 mit den eingebauten Formatierungstools formatiert werden (sie verwenden standardmäßig exFAT). Für Laufwerke, die größer als 32 GB sind, müssen Sie ein Drittanbieter-Tool wie [Rufus](https://rufus.ie/en/) verwenden, um als FAT32 zu formatieren. | ||
|
|
There was a problem hiding this comment.
Fix German grammar in the FAT32 formatting instruction.
Line 45 has an incomplete German construction. "Verwenden, um als FAT32 zu formatieren" is missing a direct object and is grammatically awkward. The clause needs restructuring to clearly reference what is being formatted.
Consider revising to one of these options:
-Für Laufwerke, die größer als 32 GB sind, müssen Sie ein Drittanbieter-Tool wie [Rufus](https://rufus.ie/en/) verwenden, um als FAT32 zu formatieren.
+Für Laufwerke, die größer als 32 GB sind, müssen Sie ein Drittanbieter-Tool wie [Rufus](https://rufus.ie/en/) verwenden, um sie als FAT32 zu formatieren.Or alternatively:
-Für Laufwerke, die größer als 32 GB sind, müssen Sie ein Drittanbieter-Tool wie [Rufus](https://rufus.ie/en/) verwenden, um als FAT32 zu formatieren.
+Für Laufwerke, die größer als 32 GB sind, müssen Sie ein Drittanbieter-Tool wie [Rufus](https://rufus.ie/en/) verwenden, um diese in FAT32 zu formatieren.📝 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.
| Unter Windows können Laufwerke, die größer als 32 GB sind, nicht als FAT32 mit den eingebauten Formatierungstools formatiert werden (sie verwenden standardmäßig exFAT). Für Laufwerke, die größer als 32 GB sind, müssen Sie ein Drittanbieter-Tool wie [Rufus](https://rufus.ie/en/) verwenden, um als FAT32 zu formatieren. | |
| Unter Windows können Laufwerke, die größer als 32 GB sind, nicht als FAT32 mit den eingebauten Formatierungstools formatiert werden (sie verwenden standardmäßig exFAT). Für Laufwerke, die größer als 32 GB sind, müssen Sie ein Drittanbieter-Tool wie [Rufus](https://rufus.ie/en/) verwenden, um sie als FAT32 zu formatieren. |
🧰 Tools
🪛 LanguageTool
[grammar] ~45-~45: Hier könnte ein Fehler sein.
Context: ...Rufus](https://rufus.ie/en/) verwenden, um als FAT32 zu formatieren. ::: ### Her...
(QB_NEW_DE)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx
around lines 44–46 the German clause "Verwenden, um als FAT32 zu formatieren" is
incomplete and awkward; replace this fragment with a clear construction that
includes the direct object, e.g. "müssen Sie ein Drittanbieter-Tool wie Rufus
verwenden, um das Laufwerk als FAT32 zu formatieren" (ensure proper punctuation
and capitalization).
| - **Webbrowser:** Besuchen Sie auf einem anderen Gerät in Ihrem lokalen Netzwerk `http://tower.local`. Wenn Sie einen anderen Hostnamen festgelegt haben, verwenden Sie diesen anstelle von `tower` (z.B. für den Hostnamen `unraidserver` würden Sie `http://unraidserver.local` besuchen). %%mDNS|mdns%% kümmert sich um die Auflösung dieser `.local`-Adressen. | ||
|
|
||
| :::important | ||
|
|
||
| Der Unraid-Server ist über Ihr LAN zugänglich, sobald er vollständig gestartet ist. Sie können die IP-Adresse in der DHCP-Clientliste Ihres Routers finden oder ein Netzwerk-Scan-Tool verwenden. |
There was a problem hiding this comment.
Clarify hyphenation for compound term across descriptive text.
The static analysis tool flags inconsistent treatment of 'Unraid-Server' (line 25, with hyphen) versus 'unraidserver' (line 21, without hyphen). While the example on line 21 is a literal hostname/code snippet (which may reasonably omit the hyphen), the descriptive text on line 25 should consistently treat the compound noun. Verify that the hyphenation aligns with German style guidelines for the documentation, and apply consistent treatment in both locations if they both refer to the system as a compound noun rather than a technical hostname.
🧰 Tools
🪛 LanguageTool
[grammar] ~21-~21: Passe das Symbol an
Context: ...e anfängliches Passwort. - Webbrowser: Besuchen Sie auf einem anderen Gerät in...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[uncategorized] ~25-~25: Uneinheitliche Verwendung von Bindestrichen. Der Text enthält sowohl ‚Unraid-Server‘ als auch ‚unraidserver‘.
Context: ...r .local-Adressen. :::important Der Unraid-Server ist über Ihr LAN zugänglich, sobald er ...
(DE_COMPOUND_COHERENCY)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
around lines 21–25, make hyphenation consistent by treating the descriptive
compound noun as "Unraid-Server" (hyphenated, capitalized) in the prose on line
25, while leaving the literal hostname/code example on line 21 as "unraidserver"
(no hyphen) since hostnames must not contain hyphens here; update the
descriptive sentence to use "Unraid-Server" so the documentation follows German
style and resolves the static analysis flag.
| Sie können dies mit einem Befehl tun: | ||
|
|
||
| Sie können dies mit einem Befehl tun: |
There was a problem hiding this comment.
Remove duplicate line.
The line "Sie können dies mit einem Befehl tun:" appears twice consecutively. Remove one instance.
-Sie können dies mit einem Befehl tun:
-
-Sie können dies mit einem Befehl tun:
+Sie können dies mit einem Befehl tun:📝 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.
| Sie können dies mit einem Befehl tun: | |
| Sie können dies mit einem Befehl tun: | |
| Sie können dies mit einem Befehl tun: |
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-command-line.mdx
around lines 34 to 36: the sentence "Sie können dies mit einem Befehl tun:" is
duplicated on consecutive lines; remove one of the duplicate lines so the
sentence appears only once, preserving surrounding punctuation and spacing.
|
|
||
| - Sie können mit der GUI nur ein Laufwerk gleichzeitig entfernen. | ||
| - Stellen Sie sicher, dass Ihr Pool ein redundantes %%RAID|raid%%-Profil verwendet (wie %%RAID 1|raid1%% für sowohl Daten als auch Metadaten). | ||
| - To check your pool's %%RAID|raid%% level, navigate to the Main tab and click on the pool. Scroll down to the Balance Status section (for %%BTRFS|btrfs%%) or ZFS pool status (for %%ZFS|zfs%%). |
There was a problem hiding this comment.
🧩 Analysis chain
Translate English text to German in this localization file.
Line 5 contains untranslated English instructions in a German-localized file, breaking the user experience for German speakers. The entire sentence must be translated to German, consistent with the localization approach used in lines 12–15 (e.g., "Hauptmenü" for "Main tab").
Suggested German translation structure:
- "Main tab" → "Registerkarte Hauptmenü" (matching lines 12–15)
- "navigate to the Main tab and click on the pool" → "navigieren Sie zur Registerkarte Hauptmenü und klicken Sie auf den Pool"
- "Scroll down to the Balance Status section" → "Scrollen Sie nach unten zum Bereich Balance-Status"
Apply this diff to fully translate line 5 to German:
- To check your pool's %%RAID|raid%% level, navigate to the Main tab and click on the pool. Scroll down to the Balance Status section (for %%BTRFS|btrfs%%) or ZFS pool status (for %%ZFS|zfs%%).
+ Um die %%RAID|raid%%-Ebene Ihres Pools zu überprüfen, navigieren Sie zur Registerkarte **Hauptmenü** und klicken Sie auf den Pool. Scrollen Sie nach unten zum **Balance-Status** (für %%BTRFS|btrfs%%) oder zum ZFS-Pool-Status (für %%ZFS|zfs%%).🏁 Script executed:
#!/bin/bash
# Verify the German localization file and check line 5 and surrounding context
FILE_PATH="i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-gui.mdx"
echo "=== Checking file existence and content ==="
if [ -f "$FILE_PATH" ]; then
echo "File exists. Displaying first 25 lines:"
head -25 "$FILE_PATH" | cat -n
else
echo "File not found at: $FILE_PATH"
echo "Searching for similar files..."
find . -name "remove-disk-gui.mdx" -type f 2>/dev/null | head -10
fiLength of output: 1604
🏁 Script executed:
#!/bin/bash
# Search for German localization files in the expected directory
echo "=== Checking directory structure ==="
find i18n/de -type d -name "*manage-storage*" 2>/dev/null
find i18n/de -type f -name "*.mdx" | grep -i "disk\|storage" | head -20Length of output: 2592
Translate English text to German on line 5.
Line 5 contains untranslated English in this German localization file, breaking usability for German speakers. The sentence must be translated to German, consistent with the localization approach used throughout the document (lines 12–15 use "Registerkarte Hauptmenü" for "Main tab").
Suggested translation:
- To check your pool's %%RAID|raid%% level, navigate to the Main tab and click on the pool. Scroll down to the Balance Status section (for %%BTRFS|btrfs%%) or ZFS pool status (for %%ZFS|zfs%%).
+ Um die %%RAID|raid%%-Ebene Ihres Pools zu überprüfen, navigieren Sie zur Registerkarte **Hauptmenü** und klicken Sie auf den Pool. Scrollen Sie nach unten zum **Balance-Status** (für %%BTRFS|btrfs%%) oder zum ZFS-Pool-Status (für %%ZFS|zfs%%).📝 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.
| - To check your pool's %%RAID|raid%% level, navigate to the Main tab and click on the pool. Scroll down to the Balance Status section (for %%BTRFS|btrfs%%) or ZFS pool status (for %%ZFS|zfs%%). | |
| - Um die %%RAID|raid%%-Ebene Ihres Pools zu überprüfen, navigieren Sie zur Registerkarte **Hauptmenü** und klicken Sie auf den Pool. Scrollen Sie nach unten zum **Balance-Status** (für %%BTRFS|btrfs%%) oder zum ZFS-Pool-Status (für %%ZFS|zfs%%). |
🧰 Tools
🪛 LanguageTool
[grammar] ~5-~5: Hier könnte ein Fehler sein.
Context: ...en als auch Metadaten). - To check your pool's %%RAID|raid%% level, navigate to the Ma...
(QB_NEW_DE)
[misspelling] ~5-~5: Hier liegt möglicherweise ein Tippfehler vor.
Context: ...'s %%RAID|raid%% level, navigate to the Main tab and click on the pool. Scroll down to t...
(DE_MULTITOKEN_SPELLING_TWO)
[grammar] ~5-~5: Korrigiere das Wort
Context: ...oll down to the Balance Status section (for %%BTRFS|btrfs%%) or ZFS pool status (fo...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_SPELLING)
[grammar] ~5-~5: Korrigiere das Wort
Context: ...ce Status section (for %%BTRFS|btrfs%%) or ZFS pool status (for %%ZFS|zfs%%). ::...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_SPELLING)
[grammar] ~5-~5: Passe die Groß- und Kleinschreibung an
Context: ...us section (for %%BTRFS|btrfs%%) or ZFS pool status (for %%ZFS|zfs%%). ::: ::: U...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_LOWERCASE)
[grammar] ~5-~5: Passe die Groß- und Kleinschreibung an
Context: ...ction (for %%BTRFS|btrfs%%) or ZFS pool status (for %%ZFS|zfs%%). ::: ::: Um eine ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_LOWERCASE)
[grammar] ~5-~5: Korrigiere das Wort
Context: ...or %%BTRFS|btrfs%%) or ZFS pool status (for %%ZFS|zfs%%). ::: ::: Um eine Festp...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_SPELLING)
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-gui.mdx
lines 5-5: replace the untranslated English sentence with a German translation
consistent with the document's style (use "Registerkarte **Hauptmenü**" for
"Main tab"); for example, change the line to: Um den RAID-Level Ihres Pools zu
prüfen, gehen Sie zur Registerkarte **Hauptmenü** und klicken Sie auf den Pool.
Scrollen Sie nach unten zum Abschnitt "Balance-Status" (für Btrfs) oder
"ZFS-Pool-Status" (für ZFS).
| - **Bezahlte Lizenz:** Diese gehört für immer Ihnen! Es gibt jedoch Einschränkungen hinsichtlich der Anzahl der Geräte, die je nach gewähltem Plan (**Starter**, **Unleashed** oder **Lifetime**) variieren. Nach der Aktivierung müssen Sie keine Internetverbindung mehr herstellen. | ||
| ::: | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Remove stray admonition marker.
Line 18 contains a standalone ::: with no associated admonition type or context. This appears to be a formatting artifact and should be removed to maintain valid Docusaurus markdown syntax.
- :::📝 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.
| ::: | |
| # (Lines 1-17 remain unchanged, line 18 is removed) | |
| # Line 19 onwards continue with the tip block |
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-license-issues.mdx
around line 18 there is a stray standalone ":::". Remove that line so there is
no orphaned admonition marker; ensure no adjacent admonition block is
intended—if there was, replace with a properly formatted admonition opening like
":::note" or the full admonition block, otherwise delete the standalone ":::".
| ::: | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Invalid admonition syntax on line 24.
Line 24 contains a bare ::: without an admonition type, which is invalid Docusaurus/MDX syntax and will likely cause rendering errors. In Docusaurus, admonitions must follow the pattern :::type to open and ::: to close. A bare ::: cannot open an admonition.
Based on the structure, line 24 appears to be extraneous and should likely be removed.
Apply this diff to remove the invalid admonition marker:
:::
-:::
:::tip🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdx
around lines 22 to 24, there is an invalid bare ":::” on line 24 that does not
specify an admonition type and should be removed; edit the file to delete the
extraneous ":::” (or replace it with a properly typed opening admonition like
":::note" if an admonition was intended) so that all admonition markers are
correctly paired and valid.
|
|
||
| - **[仪表板视图](./tour-the-web-gui.mdx#1-dashboard)** - 仪表板提供系统的详细实时概览，显示磁盘健康状况、温度、资源利用率和应用状态的指示。 | ||
| - **[Array Operation](./tour-the-web-gui.mdx#2-main)** - Manage your %%array|array%% effortlessly. You can assign devices for use in either the %%array|array%% or %%cache|cache%%, spin individual disks up and down, start and stop the %%array|array%%, and even perform on-the-fly %%parity checks|parity-check%%, all from a single page. | ||
| - **[数组操作](./tour-the-web-gui.mdx#2-main)** - 无需费力就可管理您的 %%array|数组%%。 您可以为设备分配在 %%array|阵列%% 或 %%cache|缓存%% 中使用，单独启动和停止磁盘，启动和停止 %%array|阵列%% ，甚至可以在一个页面上执行即时 %%parity checks|校验检查%%。 |
There was a problem hiding this comment.
🧩 Analysis chain
Verify anchor consistency with translated tour-the-web-gui.mdx file.
Line 13 references ./tour-the-web-gui.mdx#2-main, using the English "main" in the anchor. However, per the learning notes, the UI terminology in the Chinese Unraid interface translates "Main" as "主页面" (Main Page). If the referenced file has been translated and its heading now uses "主页面", the anchor #2-main may no longer match and could produce a broken link.
Please verify that the heading in the referenced tour-the-web-gui.mdx file remains unchanged or that the anchor reference is updated to match the Chinese translation. You can confirm this by:
🏁 Script executed:
#!/bin/bash
# Check the heading structure in the referenced Chinese file to ensure anchor consistency
rg -A 2 -B 2 '##.*[Mm]ain|##.*主页面' 'i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx'Length of output: 0
🏁 Script executed:
#!/bin/bash
# Check if the referenced file exists and examine its structure
echo "=== Checking if tour-the-web-gui.mdx exists ==="
if [ -f 'i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx' ]; then
echo "File exists. Listing first 100 lines to check structure:"
head -100 'i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx'
else
echo "File does not exist at expected path"
fi
echo -e "\n=== Checking for similar files ==="
fd 'tour-the-web-gui' --type fLength of output: 3508
🏁 Script executed:
#!/bin/bash
# Check what the actual anchor reference should be by examining the file content more broadly
echo "=== Checking for section numberings and headings in the Chinese file ==="
rg -n '^#+' 'i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx' | head -20Length of output: 284
🏁 Script executed:
#!/bin/bash
# Check if there's an English version to compare anchor patterns
echo "=== Checking English version for comparison ==="
if [ -f 'docs/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx' ]; then
echo "English file exists. Checking its headings:"
rg -n '^#+' 'docs/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx' | head -20
else
echo "English version not found"
fiLength of output: 382
Fix broken anchor reference on line 13 - Chinese heading requires updated anchor ID.
The heading in tour-the-web-gui.mdx has been translated from "### 2. Main" to "### 2. 主页", but the anchor reference remains #2-main (English). Since the relative link resolves to the Chinese version of the file, the anchor will not match the translated heading and will produce a broken link.
The anchor should be updated to reference the Chinese heading ID (typically generated as #2-主页 by Docusaurus) or verified against the actual anchor ID generated from the translated heading.
| #### General timeouts | ||
|
|
||
| Configure the general shutdown timeout in **_Settings → Disk Settings → Shutdown time-out_**. | ||
| Configure the general shutdown timeout in ***Settings → Disk Settings → Shutdown time-out***. |
There was a problem hiding this comment.
🧩 Analysis chain
Verify the hyphenation of "Shutdown time-out" in UI settings.
Line 274 refers to ***Settings → Disk Settings → Shutdown time-out*** (hyphenated), but the table at line 170 labels this same setting as "General shutdown timeout" (non-hyphenated). Confirm which format matches the actual Unraid UI to ensure consistency and user navigation accuracy.
Also applies to: 170-170
🏁 Script executed:
#!/bin/bash
# Description: Verify the exact label of this setting in documentation or UI references
# Search for references to this setting throughout the docs
rg -i "shutdown.time.?out" docs/ --type mdx
# Check if other documentation pages reference this setting
rg -i "disk settings" docs/ --type mdx -C 2Length of output: 55
🏁 Script executed:
#!/bin/bash
# Search for variations of shutdown timeout terminology in docs
echo "=== Searching for 'time-out' (hyphenated) ==="
rg -i "time-out" docs/ -C 2
echo ""
echo "=== Searching for 'timeout' (non-hyphenated) ==="
rg -i "timeout" docs/ -C 2
echo ""
echo "=== Searching for 'Disk Settings' context ==="
rg -i "disk settings" docs/ -C 3Length of output: 42112
Align table label terminology with actual UI setting name.
Line 170's table labels this setting as "General shutdown timeout" (non-hyphenated), but the navigation path shown in the same table and at line 274 directs users to ***Settings → Disk Settings → Shutdown time-out*** (hyphenated). To maintain consistency and avoid user confusion, the table label should mirror the actual UI terminology—either update it to "General shutdown time-out" or verify and clarify which form is the authoritative UI label.
🤖 Prompt for AI Agents
In docs/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx around
lines 170 and 274, the table label "General shutdown timeout" (line 170) does
not match the UI navigation text "Shutdown time-out" (line 274); update the
table label to exactly "General shutdown time-out" to match the UI (or, if the
authoritative UI uses the non-hyphenated form, change the navigation/path text
to "Shutdown timeout" instead) and ensure both the table label and the nav path
use the identical wording.
|
|
||
| 1. Schließen Sie Ihren Webbrowser. Dies setzt Ihre Sitzung zurück. | ||
| 2. Melden Sie sich von Ihrem Konto ab. | ||
| 3. Klicken Sie auf "Server entfernen" auf der Serververwaltungs-Karte. |
There was a problem hiding this comment.
Fix German quotation marks in list item 3.
Line 30 uses straight quotes instead of curved German quotation marks:
- 3. Klicken Sie auf "Server entfernen" auf der Serververwaltungs-Karte.
+ 3. Klicken Sie auf „Server entfernen" auf der Serververwaltungs-Karte.📝 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.
| 3. Klicken Sie auf "Server entfernen" auf der Serververwaltungs-Karte. | |
| 3. Klicken Sie auf „Server entfernen" auf der Serververwaltungs-Karte. |
🧰 Tools
🪛 LanguageTool
[grammar] ~30-~30: Ersetze das Satzzeichen
Context: ... von Ihrem Konto ab. 3. Klicken Sie auf "Server entfernen" auf der Serververwaltungs-Ka...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~30-~30: Ersetze das Satzzeichen
Context: ...em Konto ab. 3. Klicken Sie auf "Server entfernen" auf der Serververwaltungs-Karte.
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdx
around line 30, the list item uses straight ASCII quotes ("Server entfernen")
instead of German typographic quotation marks; replace the straight quotes with
German opening and closing quotation marks („Server entfernen“) so the sentence
reads: 3. Klicken Sie auf „Server entfernen“ auf der Serververwaltungs-Karte.
| 3. Warten Sie auf die Aktivierung und den Abschluss des ersten Backups. Der Status zeigt **Aktiviert: Auf dem neuesten Stand**, wenn es fertig ist. | ||
|
|
||
| Nach der Aktivierung werden alle Konfigurationsänderungen innerhalb von 1–2 Minuten automatisch in die Cloud gesichert. | ||
| Das Flash-Backup wurde entwickelt, um essentielle Konfigurationsdateien zu speichern und keine vollständige Kopie Ihres Flash-Laufwerks. Es sichert keine temporären Dateien (wie Protokolle) oder Anwendungs-Binaries. Plugin-Konfigurationen sind enthalten, aber Anwendungsdateien müssen beim Start neu heruntergeladen werden. Einzelne Dateien bis zu 10 MB werden gesichert; wenn das Gesamtbackup 100 MB überschreitet, wird es gelöscht und neu erstellt. |
There was a problem hiding this comment.
Remove duplicate content about Flash-Backup scope.
Lines 62 and 70 contain identical paragraphs describing what Flash-Backup stores and its limitations. This appears to be an accidental duplication from copy/paste. Remove one instance:
Das Flash-Backup wurde entwickelt, um essentielle Konfigurationsdateien zu speichern und keine vollständige Kopie Ihres Flash-Laufwerks. Es sichert keine temporären Dateien (wie Protokolle) oder Anwendungs-Binaries. Plugin-Konfigurationen sind enthalten, aber Anwendungsdateien müssen beim Start neu heruntergeladen werden. Einzelne Dateien bis zu 10 MB werden gesichert; wenn das Gesamtbackup 100 MB überschreitet, wird es gelöscht und neu erstellt.
- :::important
-
- So stellen Sie Ihre Konfiguration wieder her:
-
- :::
-
- Das Flash-Backup wurde entwickelt, um essentielle Konfigurationsdateien zu speichern und keine vollständige Kopie Ihres Flash-Laufwerks. Es sichert keine temporären Dateien (wie Protokolle) oder Anwendungs-Binaries. Plugin-Konfigurationen sind enthalten, aber Anwendungsdateien müssen beim Start neu heruntergeladen werden. Einzelne Dateien bis zu 10 MB werden gesichert; wenn das Gesamtbackup 100 MB überschreitet, wird es gelöscht und neu erstellt.Also applies to: 70-70
🧰 Tools
🪛 LanguageTool
[style] ~62-~62: Möchten Sie die modernere Schreibweise „essenzielle“ verwenden?
Context: ... Das Flash-Backup wurde entwickelt, um essentielle Konfigurationsdateien zu speichern und ...
(Z_ANSTATT_T)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
around lines 62 and 70, there is an accidental duplicated paragraph that
describes the Flash-Backup scope; remove one of the two identical paragraphs
(either the one at line 62 or the one at line 70) so the content appears only
once, and ensure surrounding whitespace and paragraph breaks remain correct
after deletion.
| - Sollte der Internetzugang nach dem Start nicht sofort verfügbar sein, installieren Sie Plugins über ***Apps → Frühere Apps*** neu, sobald die Konnektivität wiederhergestellt ist. Konfigurationsdateien werden einsatzbereit sein. | ||
|
|
||
| ## Flash-Backup deaktivieren | ||
| ## Backups-Verschlüsselung |
There was a problem hiding this comment.
Remove duplicate "Backups-Verschlüsselung" section.
Lines 92–104 and lines 101–104 both define a "Backups-Verschlüsselung" section with nearly identical content about encryption and sensitive data exclusions. This duplication creates redundancy and confusion. Consolidate into a single section:
## Backups-Verschlüsselung
Derzeit werden Flash-Backups ohne Verschlüsselung in der Cloud gespeichert. Vorsichtshalber werden sensible Daten - einschließlich aller Benutzer- und Root-Passwörter sowie alle %%WireGuard|wireguard%%-Schlüssel - nie im Backup enthalten.
1. Klicken Sie in **Einstellungen → Management-Zugriff → Unraid API** auf **Deaktivieren** für Flash-Backup.
2. Aktivieren Sie im Bestätigungsdialog **Auch Cloud-Backup löschen**, wenn Sie Ihr Backup sofort entfernen möchten. Andernfalls werden Backups nach einer gewissen Inaktivität automatisch gelöscht.
- ## Datenschutz und Sicherheit
-
- ### Backups-Verschlüsselung
-
- Derzeit werden Flash-Backups ohne Verschlüsselung in der Cloud gespeichert. Vorsichtshalber werden sensible Daten - einschließlich aller Benutzer- und Root-Passwörter sowie alle %%WireGuard|wireguard%%-Schlüssel - nie im Backup enthalten.Also applies to: 101-101
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
around lines 92 and 101–104 there is a duplicate "Backups-Verschlüsselung"
section; remove the redundant copy so only one "Backups-Verschlüsselung" header
and its content remain, merging any minor differences if present (preserve the
most complete wording and the note about excluding sensitive data) and ensure
surrounding numbering/anchors and whitespace are correct after deletion.
|
|
||
| <div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}> | ||
|  | ||
|  |
There was a problem hiding this comment.
🧩 Analysis chain
Image path updates are consistent across the file.
All image references have been updated from ./assets/zfsX.png to /img/zfsX.png, which is consistent with asset serving infrastructure. Note that line 88 and 113 still reference ./assets/zfs9.png (and possibly others)—verify if these are intentionally excluded or need updating.
Run a search to identify any remaining ./assets/ paths that should have been updated:
Also applies to: 62-62, 75-75, 88-88, 94-94, 101-101, 113-113, 117-117, 147-147, 153-153, 166-166, 234-234, 251-251, 289-289, 300-300
🏁 Script executed:
#!/bin/bash
# Verify all image paths are updated to /img/ pattern
rg -n '\./assets/zfs' i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdxLength of output: 56
Update image paths at lines 88 and 113 for consistency.
Verification confirms that image paths have been partially updated. Lines 88 and 113 still use the old ./assets/zfs8.png and ./assets/zfs9.png patterns, while all other image references in the file have been converted to /img/zfsX.png. These two lines should be updated to match the rest of the file:
- Line 88: Change
./assets/zfs8.png→/img/zfs8.png - Line 113: Change
./assets/zfs9.png→/img/zfs9.png
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
around lines 88 and 113, two image references still use the old relative paths;
update line 88 from ./assets/zfs8.png to /img/zfs8.png and update line 113 from
./assets/zfs9.png to /img/zfs9.png so they match the rest of the file's
/img/zfsX.png pattern.
| Flash 备份旨在存储必要的配置文件，而不是闪存盘的完整副本。它不会备份临时文件（例如日志）或应用程序二进制文件。插件配置包括在内，但应用程序文件将在启动时需要重新下载。单个文件支持最多 10 MB 的备份；如果总备份超过 100 MB，就会被删除和重新创建。 | ||
|
|
||
| :::important | ||
| 备份不包括 config/shadow 和 config/smbpasswd 文件。用户帐户会被保留，但密码不会。在恢复后，您需要重置所有用户密码，包括 root 密码。%%WireGuard|wireguard%% 密钥也未包括在内。 | ||
|
|
||
| 要恢复您的配置： | ||
|
|
||
| ::: | ||
|
|
||
| Flash 备份旨在存储必要的配置文件，而不是闪存盘的完整副本。它不会备份临时文件（例如日志）或应用程序二进制文件。插件配置包括在内，但应用程序文件将在启动时需要重新下载。单个文件支持最多 10 MB 的备份；如果总备份超过 100 MB，就会被删除和重新创建。 |
There was a problem hiding this comment.
Remove duplicate content about flash backup scope.
Lines 62 and 70 both contain identical text: "Flash 备份旨在存储必要的配置文件，而不是闪存盘的完整副本..." This appears to be accidental duplication from content restructuring. Remove one instance to eliminate redundancy.
Flash 备份旨在存储必要的配置文件，而不是闪存盘的完整副本。它不会备份临时文件（例如日志）或应用程序二进制文件。插件配置包括在内，但应用程序文件将在启动时需要重新下载。单个文件支持最多 10 MB 的备份；如果总备份超过 100 MB，就会被删除和重新创建。
-:::important
-
-要恢复您的配置：
-
-:::
-
-Flash 备份旨在存储必要的配置文件，而不是闪存盘的完整副本。它不会备份临时文件（例如日志）或应用程序二进制文件。插件配置包括在内，但应用程序文件将在启动时需要重新下载。单个文件支持最多 10 MB 的备份；如果总备份超过 100 MB，就会被删除和重新创建。
-
## 恢复闪存备份Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In
i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
around lines 62 to 70 there is a duplicated paragraph block describing the scope
of flash backups; remove the redundant copy so only a single instance of that
explanatory paragraph remains, making sure to preserve surrounding markup (the
:::important block and spacing) and not to alter the remaining paragraph's
content or ordering.
| :::important | ||
| 备份不包括 config/shadow 和 config/smbpasswd 文件。用户帐户会被保留，但密码不会。在恢复后，您需要重置所有用户密码，包括 root 密码。%%WireGuard|wireguard%% 密钥也未包括在内。 | ||
|
|
||
| 要恢复您的配置： | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Complete or remove the orphaned important block.
Lines 64–68 contain an incomplete :::important block with only the header "要恢复您的配置：" (To recover your configuration:) followed by ::: closing tag, but no content. This block appears incomplete. Either populate it with recovery guidance or remove it if the recovery section (starting at line 72) is the intended main recovery flow.
If this block is meant to supplement the detailed recovery section below, consider adding a brief cross-reference instead:
:::important
-
-要恢复您的配置：
-
+要恢复您的配置，请参阅下面的恢复闪存备份部分。
:::📝 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.
| :::important | |
| 备份不包括 config/shadow 和 config/smbpasswd 文件。用户帐户会被保留，但密码不会。在恢复后，您需要重置所有用户密码，包括 root 密码。%%WireGuard|wireguard%% 密钥也未包括在内。 | |
| 要恢复您的配置： | |
| ::: | |
| :::important | |
| 要恢复您的配置，请参阅下面的恢复闪存备份部分。 | |
| ::: |
🤖 Prompt for AI Agents
In
i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
around lines 64 to 68, there is an incomplete ":::important" admonition that
contains only the header "要恢复您的配置：" and an immediate closing ":::" with no
content; either remove this empty important block or populate it with a short
recovery note or cross-reference to the main recovery section (e.g., a one-line
pointer like "请参阅下面的恢复步骤。") so the admonition is complete and meaningful.
| 3. **条带** 只适用于非关键性、临时数据 - 如果任何磁盘故障，您将失去所有数据。 | ||
| ::: |
There was a problem hiding this comment.
Malformed admonition block placement in numbered list.
Lines 143–144 appear to embed an admonition block (closing :::) within a numbered list item. This is syntactically invalid Markdown/MDX. Admonition blocks should be placed outside of lists, or the list structure should be adjusted. The intent seems to be emphasizing item 3, but the current nesting will break parsing.
Restructure this section. If the intent is to have a warning after item 2, move the admonition outside the list:
2. 停止%%array|array%%。
-3. **条带** 只适用于非关键性、临时数据 - 如果任何磁盘故障，您将失去所有数据。
- :::
-4. 选择您要添加的磁盘。
+
+:::caution
+**条带** 只适用于非关键性、临时数据 - 如果任何磁盘故障，您将失去所有数据。
+:::
+
+3. 选择您要添加的磁盘。Alternatively, if item 3 should remain a list item, remove the closing ::: and restructure as plain text.
Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
around lines 143–144, there is a malformed admonition closing token (`:::`)
inside a numbered list item which breaks MDX parsing; fix by removing the
admonition tokens from inside the list and either (A) close the list before the
admonition and place a properly formatted admonition block after the list, or
(B) if the content should remain as item 3, remove the `:::` tokens and convert
the admonition content into normal/italicized list text so the list remains
valid.
| :::tip[Optimizing 硬盘数量 | ||
|
|
||
| 这提供了两个主要优点： | ||
|
|
||
| **优化配置示例：** | ||
|
|
||
| - **RAIDZ1**: 3、5 或 9 个硬盘（数据盘 = 2、4 或 8） | ||
| - **RAIDZ2**: 4、6 或 10 个硬盘（数据盘 = 2、4 或 8） | ||
| - **RAIDZ3**: 5、9 或 17 个硬盘（数据盘 = 2、6 或 14） | ||
|
|
||
| 请注意，这些优化是可选的 - 上述建议适用于大多数使用情况。 | ||
|
|
||
| ::: |
There was a problem hiding this comment.
MDX syntax error: Incomplete admonition title bracket (second occurrence).
Line 178 has the same issue: :::tip[Optimizing 硬盘数量 is missing the closing bracket ]. This will cause MDX parsing failures.
Apply this diff to fix the syntax:
-:::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.
| :::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
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
lines 178-190: the admonition opener `:::tip[Optimizing 硬盘数量` is missing the
closing bracket, causing MDX parse errors; fix by adding the closing `]` to the
title (so the line reads `:::tip[Optimizing 硬盘数量]`) and ensure the admonition is
closed with `:::` after the block.
| :::note | ||
| Linking your license key to your account is a one-time process. Once linked, you can manage your license from either the WebGUI or your online account portal. | ||
|
|
||
| 将您的许可证密钥链接到您的帐户是一次性过程。链接后，您可以从 %%WebGUI|web-gui%% 或您的在线帐户门户管理您的许可证。 |
There was a problem hiding this comment.
Standardize Chinese terminology: "帐户" vs "账户".
Static analysis flagged inconsistency in Chinese terminology at lines 81 and 90. Line 81 uses "帐户" while line 90 uses "账户". Both mean "account," but inconsistent usage within the same document should be standardized. Please choose one form and apply it consistently throughout the file.
Recommended fix: Use "账户" (the more modern/common form) consistently in all locations.
Also applies to: 90-90
🧰 Tools
🪛 LanguageTool
[uncategorized] ~81-~81: 您的意思是“"账"户”？
Context: ... - 您的许可证将自动链接 :::note 将您的许可证密钥链接到您的帐户是一次性过程。链接后，您可以从 %%WebGUI|web-gui%% 或您的在...
(ZHANG7_ZHANG8)
[uncategorized] ~81-~81: 您的意思是“"账"户”？
Context: ...是一次性过程。链接后，您可以从 %%WebGUI|web-gui%% 或您的在线帐户门户管理您的许可证。 ::: :::important 如果您在链接许可...
(ZHANG7_ZHANG8)
🤖 Prompt for AI Agents
In
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx
around lines 81 and 90, the document uses mixed Chinese terms "帐户" and "账户" for
"account"; update all instances to use the recommended, consistent form "账户"
(replace "帐户" with "账户" at line 81 and any other occurrences including line 90)
so the terminology is uniform throughout the file.
There was a problem hiding this comment.
Actionable comments posted: 74
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (35)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx (1)
9-9: Translate untranslated English sentence to German.Line 9 contains untranslated English text that should be translated to maintain consistency for German-speaking users.
Apply this diff to translate the sentence:
-Use the %%parity|parity%%-preserve method to remove a data disk while keeping your %%parity|parity%% valid safely. This is especially useful to avoid a full %%parity|parity%% sync after removal. Please ensure that the disk you're removing is healthy. +Verwenden Sie die %%parity|parity%%-Erhaltungsmethode, um eine Festplatte zu entfernen und gleichzeitig Ihre %%parity|parity%% gültig zu halten. Dies ist besonders nützlich, um eine vollständige %%parity|parity%%-Synchronisierung nach der Entfernung zu vermeiden. Stellen Sie sicher, dass die Festplatte, die Sie entfernen, fehlerfrei ist.i18n/de/docusaurus-plugin-content-docs/current/API/api-key-app-developer-authorization-flow.mdx (1)
52-81: Section heading "Verfügbare Ressourcen" mismatch: contains JavaScript implementation example, not resource listing.Line 52 introduces "## Verfügbare Ressourcen:" (Available Resources), but the content below is a JavaScript code example demonstrating the OAuth flow implementation. This semantic mismatch is confusing—the section heading doesn't reflect the actual content.
The available resources are already described at line 48 within the "Bereichsformat" section. Consider renaming this section to something more accurate like "## Beispielintegration" (Example Integration) or "## JavaScript Beispiel" (JavaScript Example) to align the heading with its content. Section headings should concisely reflect the content of each section.
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx (1)
22-24: Translate the Main section content to Chinese.The section heading is in Chinese, but the entire description (lines 22–24) remains in English. This is inconsistent with the rest of the localized document. The surrounding sections (Dashboard, Shares, Users) are translated to Chinese.
Apply this diff to translate the section:
-The **Main** screen enables efficient management of your Unraid storage and disk operations. You can configure your %%array|array%%, %%cache pools|cache-pool%%, and flash devices, as well as manage USB storage and unassigned devices, including remote shares. It displays key information about each storage device, such as health, capacity, and file systems. - -At the bottom, the Array Operation section provides maintenance options to keep your %%array|array%% running smoothly. +**主页面**屏幕能够高效管理您的 Unraid 存储和磁盘操作。您可以配置您的%%array|阵列%%、%%cache pools|缓存池%%和闪存设备，以及管理 USB 存储和未分配的设备，包括远程共享。它显示每个存储设备的关键信息，如健康状态、容量和文件系统。 + +在底部，阵列操作部分提供维护选项以保持您的%%array|阵列%%运行平稳。Note: Per previous learnings (PR 281), the "Main" UI element is translated as "主页面" in the actual Unraid interface.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx (1)
62-121: Multiple duplicate troubleshooting detail blocks detected.The troubleshooting section contains exact duplicates:
- Lines 68–77 ("VMs zeigen 'Kann Schnittstellen-MTU nicht abrufen'...") is repeated at lines 99–109
- Lines 79–87 ("VNC-Zugriff auf VMs funktioniert nicht...") is repeated at lines 111–115
- Lines 89–97 ("VM wird nicht booten (EFI-Shell erscheint)") is partially repeated at lines 117–121 (with incomplete content)
Remove the duplicate blocks (lines 99–121) or verify this is intentional restructuring from the Crowdin update.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/managing-and-customizing-containers.mdx (3)
110-120: Remove duplicate context menu instructions.Lines 110–111 and 118–120 contain identical text about accessing the container context menu. This duplication should be removed to improve document clarity.
Remove the duplicate at lines 118–120 since it immediately repeats the instruction provided at lines 110–111.
- -Sobald Sie Ihren Docker-Container erstellt und gestartet haben, ist die Verwaltung über die %%WebGUI|web-gui%% einfach. Dieser Leitfaden erläutert die Verwendung des Kontextmenüs, das Verständnis von Container-Gesundheitsindikatoren und den Zugriff auf Volumen-Zuordnungen innerhalb Ihres Containers. - -Um auf das Kontextmenü des Containers zuzugreifen, wechseln Sie zur **Docker**- oder **Dashboard**-Registerkarte und klicken auf das Container-Icon, das Sie verwalten möchten. Dieses Menü bietet einfachen Zugriff auf häufige Aktionen:
116-158: Restructure health indicators and volume mappings sections to eliminate duplication and confusion.The document structure between lines 116–158 is problematic:
- Line 116 introduces "Gesundheitsindikator" (Health Indicators) as a main section (
##).- Lines 118–139 provide introduction, image, and table for health indicators.
- Line 140 then introduces "Volume-Mappings innerhalb eines Containers" as a subsection (
###), but health indicator descriptions (lines 144–147, the 🟢🟡⚪ icons) are embedded within it.- Line 156 repeats "## Volume-Mappings innerhalb eines Containers" as a main section (
##), duplicating the earlier subsection.- Lines 158–159 duplicate lines 142–143.
This interwoven structure breaks document hierarchy and creates confusion about whether health indicators are part of volume mappings or standalone.
Reorganize the sections to:
- Complete the "Gesundheitsindikator" section with its health indicator table (lines 126–139).
- Move health indicator descriptions (🟢🟡⚪) from line 144–147 to the appropriate location within the health indicators section.
- Remove the duplicate "### Volume-Mappings" at line 140 and its duplicate content (lines 142–143, 156–159).
- Keep only one "## Volume-Mappings innerhalb eines Containers" section with its content at the appropriate hierarchy level.
93-101: Remove incomplete tip block and duplicated content.Lines 93–97 contain a
:::tipblock that introduces content duplicated at lines 99–101. The tip wrapper appears incomplete and serves no additional value since the same guidance is provided in the standard paragraph that follows.Remove the incomplete
:::tipblock (lines 93–97) and keep only the standard paragraph (lines 99–101):-:::tip - -Während Unraid keine spezielle "Test-Startsequenz"-Funktion besitzt, können Sie Ihre Startreihenfolge simulieren und überprüfen: - -::: - ### Testen Ihrer Startsequenzi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md (1)
37-37: Fix "Fritzbox" to use official "FRITZ!Box" capitalization.The text references "(Fritzbox)" in the FritzBox router context. The official product stylization is "FRITZ!Box". Please update to match the official capitalization across this and other release notes.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md (1)
212-224: Remove duplicated "Ändern des Dateisystemtyps eines Pools" section.Lines 212–217 and 219–224 contain identical content. This appears to be a copy-paste error during restructuring. Remove the duplicate at lines 219–224.
Apply this diff:
Für all Einzel-Slot-Pools kann der Dateisystemtyp geändert werden, wenn das Array gestoppt ist. Für btrfs/zfs-Multiple-Slot-Pools kann der Dateisystemtyp nicht geändert werden. Um die Geräte wiederzuverwenden, müssen Sie die Schaltfläche Pool löschen klicken. - -Ändern des Dateisystemtyps eines Pools: - -Für alle Einzel-Slot-Pools kann der Dateisystemtyp geändert werden, wenn das Array gestoppt ist. - -Für btrfs/zfs-Multiple-Slot-Pools kann der Dateisystemtyp nicht geändert werden. Um die Geräte wiederzuverwenden, -müssen Sie die Schaltfläche Pool löschen klicken. - ### Verbesserungeni18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx (3)
72-93: Remove duplicate boot phase sections.Lines 95–114 duplicate the "6. WebGUI" and "7. Array" sections from lines 72–93. This appears to be a merge or copy-paste error. Delete the duplicate content block at lines 95–114.
-<details> - <summary><strong>6. WebGUI</strong> - Zum Erweitern/Kollabieren klicken</summary> - - Die webbasiertem Verwaltungsoberfläche wird verfügbar und ermöglicht die Fernadministration und -konfiguration Ihres Servers. - - - Die %%WebGUI|web-gui%% startet an diesem Punkt. - - Die Datei `config/go` auf dem Flash-Gerät kann Benutzerbefehle vor oder nach dem Start der %%WebGUI|web-gui%% ausführen. -</details> - -<details> - <summary><strong>7. Array</strong> - Zum Erweitern/Kollabieren klicken</summary> - - Speichergeräte werden eingehängt und verfügbar gemacht, was den Bootvorgang abschließt. Hier werden Ihre Daten zugänglich. - - - Wenn Autostart aktiviert ist, beginnt das %%array|array%% hier; andernfalls ist ein manueller Start erforderlich. - - Laufwerke werden als `/dev/diskX` und `/mnt/cache` (falls vorhanden) eingehängt. - - Freigaben werden im Netzwerk als `/mnt/user/sharename` verfügbar. - - Docker-Container starten in der auf der Docker-Seite angegebenen Reihenfolge mit anpassbaren Verzögerungen. - - Automatisch startende virtuelle Maschinen (%%VMs|vm%%) werden ebenfalls gestartet. -</details>Also applies to: 95-114
188-188: Translate embedded English sentence to German.Line 188 contains an English sentence in a numbered list that should be translated to German.
Current English text:
3. Confirm that the number of unmountable drives matches your %%parity|parity%% count.Suggested German translation:
3. Bestätigen Sie, dass die Anzahl der nicht einzuhängenden Laufwerke Ihrer %%parity|parity%%-Anzahl entspricht.
151-151: Translate untranslated English paragraph to German.Line 151 contains an entire paragraph in English within the German translation file. This paragraph is also left untranslated in Spanish and French versions, while the Chinese translation demonstrates it should be properly translated rather than kept in English.
English text requiring German translation:
Unraid identifies data drives by detecting existing valid file systems. %%Parity drives|parity-drives%%, which lack a file system, appear unmountable. This characteristic allows you to distinguish %%parity drives|parity-drives%% from data drives after booting with a new flash device.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (2)
33-39: Consolidate duplicate password-manager recommendation text.The recommendation "Wir empfehlen die Verwendung eines Passwort-Managers zur sicheren Speicherung." appears on both line 33 and line 39, creating redundancy. Consider repositioning this text to appear once—either as a standalone note before or after the bullet list of password requirements, not both.
51-73: Rename section heading to reflect license/account setup content.This section (lines 51–73) covers Lizenzschlüssel (license key) management and account registration, but the heading reads "## BIOS-Empfehlungen," which does not match the content. The actual BIOS checklist begins again at line 75 with the same heading. Consider renaming this first section to something like "## Lizenzschlüssel verwalten" or "## Konto und Lizenzschlüssel" to clarify the distinction.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx (1)
63-75: Remove duplicate text from the Berechtigungen section.The sentence "Dieser Ansatz hält Ihr System sicher, während fortgeschrittene Benutzer ihre Skripte ausführen können" appears identically at line 63 and line 75, creating redundancy and confusion about the organizational structure.
Apply this diff to remove the duplicate:
Dieser Ansatz hält Ihr System sicher, während fortgeschrittene Benutzer ihre Skripte ausführen können. Wenn Sie benutzerdefinierte Skripte oder Programme auf dem USB-Stick gespeichert haben, gehen Sie wie folgt vor: ... 2. **Skripte mit einem Interpreter ausführen:** - Schließen Sie das Skript mit dem Interpreter ein (z.B. `bash /boot/config/scripts/myscript.sh`). -Dieser Ansatz hält Ihr System sicher, während fortgeschrittene Benutzer ihre Skripte ausführen können.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx (1)
145-174: Remove or consolidate duplicate section: "VPN-Tunneling-Zugriff für das System konfigurieren" appears twice.Lines 145–157 and lines 158–174 contain nearly identical sections with the same title. This appears to be a duplication error from the Crowdin import or merge process. Please consolidate these sections into a single, authoritative version.
Additionally, verify the content between the two sections:
- Lines 149–150: First version references Firefox and Community Applications
- Lines 162–163: Second version also references Firefox and Community Applications with similar steps
Determine which version is current and remove the redundant copy.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx (1)
163-226: Remove duplicate WireGuard trademark notices.The WireGuard trademark notice appears three times:
- Line 163:
\* *„%%WireGuard|wireguard%%" und das „%%WireGuard|wireguard%%"-Logo sind eingetragene Warenzeichen von Jason A. Donenfeld.*- Line 195:
\* *„%%WireGuard|wireguard%%" und das „%%WireGuard|wireguard%%"-Logo sind eingetragene Warenzeichen von Jason A. Donenfeld.*- Line 226:
\* *"%%WireGuard|wireguard%%" und das "%%WireGuard|wireguard%%" Logo sind eingetragene Marken von Jason A. Donenfeld.*These should appear only once, at the end of the document. Additionally, there are slight variations in wording ("Warenzeichen" vs. "Marken") and quotation marks (German „" vs. straight quotes "") that should be standardized.
Consolidate to a single trademark notice at the end of the file with consistent wording and quotation marks.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx (1)
154-189: Resolve duplicate section heading: "Konfigurationen, die vermieden werden sollten".This heading appears twice:
- Line 154: Introduces DNS/testing configurations
- Line 189: Introduces a NAT configuration table
These are two distinct sections with different content. The first should be renamed to reflect its focus on DNS configuration and testing, and the second should be renamed to reflect its focus on NAT configuration options. For example:
- Line 154 section: "DNS-Konfiguration und Fehlersuche" or "DNS-Konfigurationen"
- Line 189 section: Could remain as is, or be renamed "NAT-Konfigurationsszenarien" for clarity
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx (1)
92-159: Remove or consolidate duplicate section: "HTTPS mit Myunraid.net-Zertifikat und ohne Fallback-URL".This section heading and content appear twice:
- Lines 92–130: First occurrence with expandable details block
- Lines 131–159: Second occurrence with nearly identical content
The two sections are functionally identical and should be consolidated into a single section. Compare the content carefully and keep only one version, removing the redundant copy.
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (2)
138-180: 🔴 Critical: Consolidate duplicate "Lizenzverwaltung" sections and reorganize subsections.The file contains two separate "## Lizenzverwaltung" headers (lines 148 and 168) with overlapping content. Additionally, the section at lines 148–164 incorrectly embeds customization options (change banner, rearrange dashboard, switch themes) which belong under "## Anpassung" (lines 138–146).
Restructure as follows:
- Anpassung (lines 138–146 + tabs from lines 152–164): Consolidate the Deep Linking intro with the customization tabs.
- Lizenzverwaltung (keep lines 168–179 only): Focus on license management operations (key reassignment, upgrades, downloads, status checking).
- Remove the duplicate tabs from the first Lizenzverwaltung block.
Apply this diff:
## Anpassung Mit Deep Linking in Unraid Connect können Sie direkt zu bestimmten Abschnitten Ihres Unraid %%WebGUI|web-gui%% springen, indem Sie einfach auf einen der umkreisten Link-Buttons (unten) in der Connect-Oberfläche klicken, um direkt zur relevanten Verwaltungsseite Ihres Servers zu gelangen. <div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}>  </div> -::: +Mit Unraid Connect können Sie auch: + +<Tabs> + <TabItem value="Banner" label="Bannerbild ändern" default> + <ConnectChangeBanner /> + </TabItem> + + <TabItem value="ordnen" label="Kacheln im Dashboard umarrangieren"> + <ConnectRearrangeDashboard /> + </TabItem> + + <TabItem value="Thema" label="Themen wechseln"> + <ConnectSwitchThemes /> + </TabItem> +</Tabs> --- ## Lizenzverwaltung - Die Verwaltung Ihrer Lizenzen in Unraid Connect ist einfach. Unter dem Abschnitt **Meine Schlüssel** können Sie: - - <Tabs> - <TabItem value="Banner" label="Bannerbild ändern" default> - <ConnectChangeBanner /> - </TabItem> - - <TabItem value="ordnen" label="Kacheln im Dashboard umarrangieren"> - <ConnectRearrangeDashboard /> - </TabItem> - - <TabItem value="Thema" label="Themen wechseln"> - <ConnectSwitchThemes /> - </TabItem> - </Tabs> - - --- - - ## Lizenzverwaltung Die Verwaltung Ihrer Lizenzen in Unraid Connect ist einfach. Unter dem Abschnitt **Meine Schlüssel** können Sie:
208-230: 🟠 Major: Remove duplicate consequence bullets in deinstallation section.Lines 208–213 and lines 219–224 contain nearly identical bullet lists describing the consequences of plugin deinstallation. Remove the first instance (lines 208–213).
Apply this diff:
## Abmeldung Sie können sich jederzeit von Unraid Connect abmelden über ***Einstellungen → Verwaltungszugriff → Unraid Connect → Kontostatus***, indem Sie auf die **Abmelden**-Schaltfläche klicken. - Wenn Sie das Unraid Connect Plugin deinstallieren: - - - Alle Flash-Backup-Dateien werden deaktiviert und von Ihrem lokalen Flash-Laufwerk gelöscht. - - Cloud-Backups sind zur Entfernung von Unraid-Servern markiert; sie werden für 30 Tage aufbewahrt, danach werden sie dauerhaft gelöscht. Für eine sofortige Löschung, [deaktivieren Sie Flash-Backup](./automated-flash-backup.mdx), bevor Sie es deinstallieren. - - Der Fernzugriff wird deaktiviert. Stellen Sie sicher, dass Sie alle zugehörigen Portweiterleitungsregeln von Ihrem Router entfernen. - - Ihr Server wird von Unraid.net abgemeldet. - - --- - ## Deinstallation des Pluginsi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx (1)
59-59: 🟡 Minor: Standardize German compound word formation.Lines 59 and 90 use inconsistent hyphenation for the German compound word referring to license key files:
- Line 59:
Lizenzschlüsseldateien(no hyphen, correct modern German)- Line 90:
Lizenzschlüssel-Datei(with hyphen, older style)Standardize to the modern German convention without hyphens:
Lizenzschlüsseldatei.Apply this diff:
-Sie die richtige Lizenzschlüssel-Datei verwenden +Sie die richtige Lizenzschlüsseldatei verwendenAlso applies to: 90-90
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx (1)
18-18: Use standard UI terminology "主页面" instead of English "Main".Line 18 uses English "Main 标签" but should use the standard Unraid UI term "主页面 标签" (Main page tab) for consistency with Chinese localization and other documentation.
-您将使用 Unraid %%WebGUI|web-gui%% 中的 **Main** 标签来分配和查看设备，包括 %%array|array%% 和池分配，以及任何未分配的设备和您的启动设备（即 **USB 闪存设备**）。 +您将使用 Unraid %%WebGUI|web-gui%% 中的 **主页面** 标签来分配和查看设备，包括 %%array|array%% 和池分配，以及任何未分配的设备和您的启动设备（即 **USB 闪存设备**）。Based on learnings from PR 281.
i18n/zh/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx (1)
267-300: Duplicated content sections may indicate incomplete refactoring.Lines 267-270 (调试模式/Debugging Mode section header and opening) appear duplicated at lines 272-280 with the full debugging instructions. Similarly, multiple provider configuration sections show repeated "配置：" headers (e.g., lines 373-375, 387-389, 401-403).
Please verify these are intentional duplicates or if the content consolidation was incomplete. If these are unintentional, consider consolidating to a single clear section.
i18n/de/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx (1)
372-425: Critical: Remove duplicate provider configuration sections.The OIDC provider setup sections contain duplicated instructions:
- Authentik appears twice: lines 372–384 and again at lines 400–412
- Okta appears twice: lines 386–398 and again at lines 414–424
Remove the duplicate sections (lines 400–424) to eliminate redundancy and clarify the provider setup flow. Consolidate to a single, complete instance of each provider's configuration.
Apply this diff to remove the duplicates:
Berechtigungsrichtlinien können in der Schnittstelle konfiguriert werden. -### Authentik - -Erstellen Sie einen neuen OAuth2/OpenID-Anbieter in Authentik und erstellen Sie eine Anwendung, die mit dem Anbieter verknüpft ist. - -**Konfiguration:** - -- **Issuer URL**: `https://authentik.example.com/application/o/<application_slug>/` -- **Client-ID**: Aus der Authentik-Anbieter-Konfiguration -- **Client-Secret**: Aus der Authentik-Anbieter-Konfiguration -- **Erforderliche Scopes**: `openid`, `profile`, `email` -- **Redirect-URI**: `http://YOUR_UNRAID_IP/graphql/api/auth/oidc/callback` - -Berechtigungsrichtlinien können in der Schnittstelle konfiguriert werden. - -### Okta - -Erstellen Sie eine neue OIDC-Webanwendung in der Okta-Admin-Konsole und weisen Sie entsprechende Benutzer oder Gruppen zu. - -**Konfiguration:** - -- **Issuer URL**: `https://YOUR_DOMAIN.okta.com` -- **Client-ID**: Aus der Okta-Anwendungskonfiguration -- **Client-Secret**: Aus der Okta-Anwendungskonfiguration -- **Erforderliche Scopes**: `openid`, `profile`, `email` -- **Redirect-URI**: `http://YOUR_UNRAID_IP/graphql/api/auth/oidc/callback` - -Berechtigungsrichtlinien können in der Schnittstelle konfiguriert werden.i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (1)
148-176: Remove duplicate "许可证管理" section heading.The section "许可证管理" appears twice (at line 148 with tabs for customization content, and again at line 168 with license management bullet points). This creates confusion about which section provides which information.
Either:
- Rename the first section (line 148) to reflect it contains customization/personalization options, or
- Merge the two sections if they're meant to be combined
The current structure suggests two separate features but the heading collision obscures their purpose.
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx (1)
52-91: Standardize Chinese terminology: Replace all instances of "帐户" with "账户".The file inconsistently mixes "帐户" (traditional form) and "账户" (modern form) for "account." Verification confirms 6 instances of the wrong form that must be corrected:
- Line 52: Section heading
- Line 54: Description text
- Line 58: Bullet point
- Line 68: Instruction text
- Line 76: Instruction text
- Line 81: Two instances in note section
Replace all "帐户" with "账户" throughout this file to match the preferred modern form used elsewhere in the document (lines 60, 70, 89, 91).
i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx (2)
76-76: Fix escaped asterisks in bullet text.Line 76 contains improperly escaped asterisks (
\*\*) mixed with unescaped ones (**). Remove the backslashes to use standard Markdown bold syntax.Apply this diff:
- \*\*动态 - 手动端口转发：\*\*需要您手动在路由器上转发选定的端口。 + **动态 - 手动端口转发：**需要您手动在路由器上转发选定的端口。
110-114: Translate troubleshooting admonition title fully to Chinese.Line 110 contains the admonition title "Troubleshooting", which is entirely in English for a Chinese-language document. Translate this to Chinese for consistency.
Apply this diff:
- :::caution\[Troubleshooting] + :::caution\[故障排除]i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx (1)
1-50: File contains mixed English and German content.This German-localized file has inconsistent language: the opening description (line 11) and sections of the "Implementierungsdetails" block (lines 26, 27, etc.) are in English, while the newly added note block (lines 45-49) is in German. For a localized documentation file, all content should be consistently in German. Either translate all English sections to German or consolidate language usage.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx (2)
236-247: Remove duplicate "Schritt 4" header.Both line 236 and line 247 are labeled "Schritt 4: Bearbeiten Sie das XML für Ihre virtuelle Maschine". This header appears twice consecutively with different content, which is confusing. Either rename one to "Schritt 5" or consolidate the sections.
1-452: Significant mixed English/German content throughout file.The file contains English instruction steps interspersed with German text. Examples: Line 56 contains "Store %%VM|vm%% images on a %%cache pool|cache-pool%% instead of an %%array|array%% for the [best performance]" within a German-localized document. For consistency, all instructions should be in German.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx (1)
52-57: Fix German translation: heading should address anonymization and content must be translated to German.The review comment is verified as accurate. In the English source (
./docs/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx), line 53 has a section titled### Anonymization of diagnostic datawith German-localized content translated accordingly. However, the German translation file has:
- Line 52: Heading
### Ermittlung der Lesegeschwindigkeit von Festplatten(about drive read speed—incorrect topic)- Lines 54–56: Untranslated English paragraphs about anonymization and Mover logging
The heading should translate the English title about anonymization, and the content must be translated to German. Lines 54–56 currently violate the principle of localized documentation by remaining in English within the
i18n/de/directory. The subsequent h2 heading at line 59 (also about read speed) is a separate, correctly-placed section that happens to use the same topic title.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx (1)
40-51: Remove duplicate heading and consolidate error-handling steps.Lines 40 and 51 contain the same heading "What to do if you encounter %%parity|parity%% errors". Lines 44–47 present this content as bullet points, then lines 55–57 repeat it as a numbered list. This duplication creates confusion about the intended structure.
Consolidate into a single, clear procedural section with one list format (either bullets or numbered steps, not both).
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/shares-primary-storage-612.mdx (1)
15-25: Remove duplicate secondary storage dropdown section.Lines 15–19 and lines 21–25 contain duplicate "Sekundärspeicher-Dropdown:" headers and nearly identical bullet lists. Remove the second instance (lines 21–25) to eliminate this duplication.
-**Sekundärspeicher-Dropdown:** - -- **None:** Kein Sekundärspeicher ist für die Freigabe festgelegt (optional). -- Wenn der Primärspeicher ein %%pool|cache-pool%% ist, stehen **None**, **Array** und **Ein anderer Pool** zur Verfügung. -- If the primary storage is the **Array**, **None** and any eligible %%pools|cache-pool%% are available.
|
|
||
| <div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}> | ||
|  | ||
|  |
There was a problem hiding this comment.
🧩 Analysis chain
Critical: Image paths fail MDX compilation — images not found at /img/ location.
The pipeline failure indicates the images referenced at /img/zfs1.png through /img/zfs16.png do not exist. The change from relative paths (./assets/zfsX.png) to absolute paths (/img/zfsX.png) appears to be incorrect or incomplete.
Please verify:
- Do the image files exist in the repository at
/img/zfs1.pngthrough/img/zfs16.png? - Should these paths remain relative to the file (e.g.,
../../assets/zfs1.pngor similar)? - Or do they need to be stored in a different location to match the absolute path pattern?
Run this script to locate the ZFS images in the repository:
Also applies to: 62-62, 75-75, 88-88, 94-94, 101-101, 113-113, 117-117, 166-166, 206-206, 234-234, 251-251, 289-289, 300-300
🏁 Script executed:
#!/bin/bash
# Description: Search for ZFS image files in the repository
fd -e png -e jpg -e jpeg | grep -i zfsLength of output: 8482
Fix broken image paths — images not found at /img/ location.
The image files (zfs1.png through zfs16.png) exist in the repository at docs/unraid-os/advanced-configurations/optimize-storage/assets/ but are referenced as /img/zfsX.png, causing the pipeline compilation failure. Hard-coded absolute paths will not be detected at compilation time and will result in a 404 error.
Since the MDX file uses Markdown syntax for images, Docusaurus converts Markdown image references to require() calls, which means relative paths must be used. Revert all 16 image path references from /img/zfsX.png to ./assets/zfsX.png.
Affected lines: 42, 62, 75, 88, 94, 101, 113, 117, 166, 206, 234, 251, 289, 300
🧰 Tools
🪛 GitHub Actions: PR Preview
[error] 42-42: MDX compilation failed: Markdown image with URL '/img/zfs1.png' couldn't be resolved to an existing local image file.
🤖 Prompt for AI Agents
In docs/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
around lines 42, 62, 75, 88, 94, 101, 113, 117, 166, 206, 234, 251, 289, and
300, image references use absolute paths like /img/zfsX.png which fail at build
time; replace each absolute reference with the correct relative path
./assets/zfsX.png so Markdown/Docusaurus resolves them via require(), updating
all 16 occurrences to ./assets/zfs1.png through ./assets/zfs16.png respectively.
|
|
||
| - The disk was disabled due to external factors (like cables or power issues). | ||
| - You've checked the disk's health using [%%SMART reports|smart-report%%](../../../system-administration/monitor-performance/smart-reports-and-disk-health.mdx). | ||
| - You've checked the disk's health using [%%SMART reports|smart-report%%](../../system-administration/monitor-performance/smart-reports-and-disk-health.mdx). |
There was a problem hiding this comment.
🧩 Analysis chain
Critical: Broken internal links blocking merge.
The pipeline reports that internal links on lines 169, 179, 180, and 187 cannot be resolved. All four links follow the pattern ../../system-administration/ or ../../troubleshooting/ and fail to resolve.
- Line 169:
../../system-administration/monitor-performance/smart-reports-and-disk-health.mdx - Line 179 & 187:
../../system-administration/advanced-tools/command-line-interface.mdx#smartctl - Line 180:
../../troubleshooting/common-issues/data-recovery.mdx#running-the-repair
Verify these paths exist in the repository and that anchor references (e.g., #smartctl, #running-the-repair) are defined in their target files. Until links are corrected, the build will not pass.
Also applies to: 179-179, 180-180, 187-187
🏁 Script executed:
#!/bin/bash
# Description: Verify that link targets exist in the documentation tree
# Find files matching the link targets
fd -e mdx "smart-reports-and-disk-health" || echo "NOT FOUND: smart-reports-and-disk-health.mdx"
fd -e mdx "command-line-interface" || echo "NOT FOUND: command-line-interface.mdx"
fd -e mdx "data-recovery" || echo "NOT FOUND: data-recovery.mdx"
# Check for anchor definitions in target files (if found)
echo "---"
echo "Checking for #smartctl anchor in command-line-interface.mdx:"
fd -e mdx "command-line-interface" --exec grep -l "smartctl" {} \;
echo "Checking for #running-the-repair anchor in data-recovery.mdx:"
fd -e mdx "data-recovery" --exec grep -l "running-the-repair\|Running the repair" {} \;Length of output: 2368
---
🏁 Script executed:
```shell
#!/bin/bash
# Verify relative paths and anchor definitions
# 1. Check source file and exact link formats
echo "=== SOURCE FILE LINK FORMATS ==="
grep -n "../../system-administration\|../../troubleshooting" docs/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx | head -10
# 2. Verify correct relative path depth
# Source: docs/unraid-os/using-unraid-to/manage-storage/array/
# Target: docs/unraid-os/system-administration/
echo ""
echo "=== PATH DEPTH ANALYSIS ==="
echo "Source depth: docs/unraid-os/using-unraid-to/manage-storage/array/ = 4 levels in docs/"
echo "Target depth: docs/unraid-os/system-administration/ = 2 levels in docs/"
echo "Need to go UP: array → manage-storage → using-unraid-to → unraid-os (3 levels, so ../../../)"
# 3. Check for #running-the-repair with broader pattern
echo ""
echo "=== CHECKING FOR REPAIR ANCHOR (broader patterns) ==="
grep -n "repair\|#running-the-repair" docs/unraid-os/troubleshooting/common-issues/data-recovery.mdx | head -20
# 4. Check heading format in data-recovery.mdx to understand anchor generation
echo ""
echo "=== HEADING FORMATS IN data-recovery.mdx ==="
grep -n "^##\|^###\|^####" docs/unraid-os/troubleshooting/common-issues/data-recovery.mdx | head -15
Length of output: 3965
🏁 Script executed:
# No cloning needed - focusing on existing repository filesLength of output: 59
Critical: Incorrect relative path depth on lines 169, 179, 180, and 187.
All four links use ../../ when they should use ../../../. The source file is at docs/unraid-os/using-unraid-to/manage-storage/array/, so reaching system-administration/ or troubleshooting/ at the unraid-os/ level requires going up 3 directory levels, not 2.
Correct the paths:
- Line 169:
../../system-administration/→../../../system-administration/ - Line 179 & 187:
../../system-administration/→../../../system-administration/ - Line 180:
../../troubleshooting/→../../../troubleshooting/
The target files exist and anchors are properly defined (#smartctl and #running-the-repair from heading "### Running the Repair" on line 133 of data-recovery.mdx). The build failures are due solely to incorrect relative path depth.
🧰 Tools
🪛 GitHub Actions: PR Preview
[warning] 169-169: Markdown link with URL '../../system-administration/monitor-performance/smart-reports-and-disk-health.mdx' in source file could not be resolved.
[warning] 169-169: Markdown link with URL '../../system-administration/monitor-performance/smart-reports-and-disk-health.mdx' in source file could not be resolved.
🤖 Prompt for AI Agents
In
docs/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx
around lines 169, 179, 180, and 187 the relative links use ../../ but the source
file is three levels deep, so update the paths to go up three levels (../../../)
instead of two; specifically change line 169 ../../system-administration/ →
../../../system-administration/, lines 179 and 187 ../../system-administration/
→ ../../../system-administration/, and line 180 ../../troubleshooting/ →
../../../troubleshooting/ so the links correctly resolve to the target files and
anchors.
|
|
||
| :::tip[What's Neu] | ||
|
|
||
| Ab Unraid OS v7.2 ist die API direkt in das Betriebssystem integriert - keine Plugin-Installation erforderlich! |
There was a problem hiding this comment.
Fix em-dash punctuation in the "What's New" tip.
Line 17 uses a hyphen-minus (-) where an em-dash (–) is preferred in German technical writing. The sentence currently reads "…keine Plugin-Installation erforderlich!" but should use proper punctuation before "keine."
Apply this diff:
- Ab Unraid OS v7.2 ist die API direkt in das Betriebssystem integriert - keine Plugin-Installation erforderlich!
+ Ab Unraid OS v7.2 ist die API direkt in das Betriebssystem integriert – keine Plugin-Installation erforderlich!📝 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.
| Ab Unraid OS v7.2 ist die API direkt in das Betriebssystem integriert - keine Plugin-Installation erforderlich! | |
| Ab Unraid OS v7.2 ist die API direkt in das Betriebssystem integriert – keine Plugin-Installation erforderlich! |
🧰 Tools
🪛 LanguageTool
[grammar] ~17-~17: Ersetze das Satzzeichen
Context: ...st die API direkt in das Betriebssystem integriert - keine Plugin-Installation erforderlich!...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_DASH_–)
🤖 Prompt for AI Agents
In i18n/de/docusaurus-plugin-content-docs/current/API/index.mdx around line 17,
the sentence uses a hyphen-minus before "keine Plugin-Installation
erforderlich!" — replace the ASCII hyphen-minus with a proper em-dash (or German
Gedankenstrich, e.g., "–" or "—" as per project convention) so the line reads:
"Ab Unraid OS v7.2 ist die API direkt in das Betriebssystem integriert – keine
Plugin-Installation erforderlich!" and ensure spacing around the dash matches
the repo's German punctuation style.
| Für eine vollständige Liste aller Veröffentlichungen, Änderungsprotokolle und Download-Links besuchen Sie die [Unraid API GitHub Releases](https://github.com/unraid/api/releases) Seite. | ||
|
|
There was a problem hiding this comment.
Remove unnecessary whitespace before "Seite."
Line 134 contains an extra space before "Seite." which creates unnecessary whitespace in the rendered output.
Apply this diff:
- Für eine vollständige Liste aller Veröffentlichungen, Änderungsprotokolle und Download-Links besuchen Sie die [Unraid API GitHub Releases](https://github.com/unraid/api/releases) Seite.
+ Für eine vollständige Liste aller Veröffentlichungen, Änderungsprotokolle und Download-Links besuchen Sie die [Unraid API GitHub Releases](https://github.com/unraid/api/releases) Seite.📝 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.
| Für eine vollständige Liste aller Veröffentlichungen, Änderungsprotokolle und Download-Links besuchen Sie die [Unraid API GitHub Releases](https://github.com/unraid/api/releases) Seite. | |
| Für eine vollständige Liste aller Veröffentlichungen, Änderungsprotokolle und Download-Links besuchen Sie die [Unraid API GitHub Releases](https://github.com/unraid/api/releases) Seite. |
🧰 Tools
🪛 LanguageTool
[grammar] ~134-~134: Entferne ein Leerzeichen
Context: ...(https://github.com/unraid/api/releases) Seite. ::: ### Unraid v7.2-beta.1 High...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
🤖 Prompt for AI Agents
In i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx
around lines 134-135, there is an extra space before "Seite." in the sentence
ending with the GitHub Releases link; edit that line to remove the unnecessary
whitespace so there is exactly one space between the closing parenthesis and
"Seite." (i.e., collapse any double space to a single space).
| :::warning[Legacy Unterstützung] | ||
|
|
||
| Versionen vor Unraid 7.2 erfordern die Installation der API über das Unraid Connect-Plugin. Einige Funktionen sind in älteren Versionen möglicherweise nicht verfügbar. | ||
|
|
||
| ::: | ||
|
|
||
| :::tip[Pre-release Versionen] | ||
|
|
||
| Sie können das Unraid Connect-Plugin immer installieren, um Vorabversionen der API zu erhalten und neuen Funktionen frühzeitig Zugang zu verschaffen, bevor sie in den Unraid OS-Veröffentlichungen enthalten sind. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Remove trailing whitespace after admonition markers.
Lines 171, 177, and 179 have unnecessary spaces after the admonition closing markers (:::), which can create unwanted whitespace in the rendered output. Remove these trailing spaces for consistent formatting.
Apply this diff:
- :::warning[Legacy Unterstützung]
+ :::warning[Legacy Unterstützung]
Versionen vor Unraid 7.2 erfordern die Installation der API über das Unraid Connect-Plugin. Einige Funktionen sind in älteren Versionen möglicherweise nicht verfügbar.
-:::
+:::
-:::tip[Pre-release Versionen]
+:::tip[Pre-release Versionen]
Sie können das Unraid Connect-Plugin immer installieren, um Vorabversionen der API zu erhalten und neuen Funktionen frühzeitig Zugang zu verschaffen, bevor sie in den Unraid OS-Veröffentlichungen enthalten sind.
-:::
+:::🧰 Tools
🪛 LanguageTool
[grammar] ~173-~173: Entferne ein Leerzeichen
Context: ...die Installation der API über das Unraid Connect-Plugin. Einige Funktionen sind i...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~177-~177: Entferne ein Leerzeichen
Context: ...icht verfügbar. ::: :::tip[Pre-release Versionen] Sie können das Unraid Connec...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~179-~179: Entferne ein Leerzeichen
Context: ...elease Versionen] Sie können das Unraid Connect-Plugin immer installieren, um Vo...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~179-~179: Entferne ein Leerzeichen
Context: ... zu verschaffen, bevor sie in den Unraid OS-Veröffentlichungen enthalten sind. :...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx around
lines 171 to 181: some admonition closing markers (":::") have trailing spaces
on lines 171, 177, and 179; remove the trailing whitespace directly after those
":::” markers so each admonition closing marker is exactly ":::” with no extra
spaces to ensure consistent rendering.
| :::important | ||
| Ändern Sie nur den Host-Portwert. Ändern Sie den Container-Port nur, wenn Sie wissen, dass die Anwendung ihn unterstützt. | ||
|
|
||
| Die meisten Vorlagen bieten sinnvolle Standardwerte, aber Sie können Port-Zuordnungen hinzufügen oder anpassen. | ||
|
|
||
| ::: | ||
|
|
||
| Die meisten Vorlagen bieten sinnvolle Standardwerte, aber Sie können Port-Zuordnungen hinzufügen oder anpassen. |
There was a problem hiding this comment.
Remove duplicate content outside admonition block.
Line 13 is a verbatim duplication of the content inside the admonition block (line 9). This creates redundancy. Either remove line 13 or clarify why the same information needs to appear both inside and outside the admonition.
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/port-mappings.mdx
around lines 7 to 13, there is a duplicated sentence: the same text appears
inside the :::important admonition and again immediately after (line 13). Remove
the duplicate line 13 (or alternatively remove the admonition wrapper and keep
the standalone sentence) so the message appears only once; ensure surrounding
spacing and Markdown admonition syntax remain valid after removal.
|
|
||
| - Pfade sind case-sensitiv. | ||
| - Containerpfade sollten mit einem `/` beginnen. | ||
| - Wenn ein nicht zugewiesenes Gerät als Host-Pfad verwendet wird, setzen Sie den Zugriffsmodus auf eine "Slave"-Option, um eine ordnungsgemäße Erkennung sicherzustellen. |
There was a problem hiding this comment.
Use German quotation marks for consistency.
The quote marks around "Slave" should use German quotes („Slave") instead of ASCII quotes, to align with German typography conventions used elsewhere in this file.
🧰 Tools
🪛 LanguageTool
[grammar] ~17-~17: Ersetze das Satzzeichen
Context: ..., setzen Sie den Zugriffsmodus auf eine "Slave"-Option, um eine ordnungsgemäße Erkennun...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTESLAVEQUOTEDASHOPTION_„SLAVEL_DOUBLE_QUOTDASHOPTION)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/volume-mappings.mdx
around line 17, the string "Slave" uses ASCII quotes; replace them with German
typographic quotes so it reads „Slave“ to match the German typography used
elsewhere in the file.
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.md
Outdated
Show resolved
Hide resolved
| @@ -12,7 +12,9 @@ import ManageApiKeysCli from './partials/manage-api-keys-cli.mdx'; | |||
| # 使用 Unraid API | |||
|
|
|||
| :::tip[Quick 开始] | |||
There was a problem hiding this comment.
Translate admonition titles fully to Chinese.
Multiple admonition titles mix English keywords with Chinese translations, breaking immersion in a Chinese-language document. Translate these titles entirely to Chinese for consistency.
Apply these diffs:
- :::tip[Quick 开始]
+ :::tip[快速开始]- :::info[Preferred 方法]
+ :::info[推荐方法]- :::warning[Required 大多数操作需要]
+ :::warning[大多数操作需要]- :::tip[Pro 提示]
+ :::tip[专业提示]- :::caution[Rate 限制]
+ :::caution[速率限制]- :::info[Learn 更多]
+ :::info[了解更多]Also applies to: 26-26, 56-56, 208-208, 220-220, 244-244
🤖 Prompt for AI Agents
In i18n/zh/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx
around line 14 (and also update lines 26, 56, 208, 220, 244), several admonition
titles use mixed English and Chinese (e.g., "Quick 开始"); replace each mixed
title with a fully Chinese equivalent (e.g., "快速开始") ensuring all admonition
markers (:::{tip}, :::note, :::warning, etc.) display a fully translated Chinese
title; scan the file for other admonition headings and make consistent
replacements so all admonition titles are purely Chinese and match the document
tone.
| :::important[Security 提醒] | ||
| 在启用远程访问之前，请确保您的 root 密码是强且唯一的。如有需要，请在 **用户** 页面上进行更新。此外，保持您的 Unraid 操作系统更新至最新版本，以防范安全漏洞。[了解更多关于更新 Unraid 的信息](../unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx)。 | ||
|
|
||
| 通过 Unraid Connect 提供的远程访问： | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Translate security admonition title fully to Chinese.
Line 15 contains the admonition title "Security 提醒", which mixes English with Chinese. Translate this fully to Chinese for consistency with the rest of the document.
Apply this diff:
- :::important[Security 提醒]
+ :::important[安全提醒]📝 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.
| :::important[Security 提醒] | |
| 在启用远程访问之前，请确保您的 root 密码是强且唯一的。如有需要，请在 **用户** 页面上进行更新。此外，保持您的 Unraid 操作系统更新至最新版本，以防范安全漏洞。[了解更多关于更新 Unraid 的信息](../unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx)。 | |
| 通过 Unraid Connect 提供的远程访问： | |
| ::: | |
| :::important[安全提醒] | |
| 通过 Unraid Connect 提供的远程访问： | |
| ::: |
🤖 Prompt for AI Agents
In
i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx
around lines 15 to 19, the admonition title "Security 提醒" mixes English and
Chinese; replace it with a fully Chinese title such as "安全 提醒" or better "安全提醒"
so the admonition title is entirely in Chinese and consistent with the rest of
the document.
| :::important | ||
| Hängen Sie die einzelne Diagnosedatei im ZIP-Format an, wenn Sie Beiträge in Foren posten. Vermeiden Sie das Hochladen der extrahierten Dateien einzeln. | ||
|
|
||
| When your system shuts down gracefully, the session log is saved automatically to the flash drive. You can access it after rebooting by going to ***Tools → Syslog → syslog-previous***. This log is also included in diagnostics on the next boot. However, if the system crashes, the system log will be lost. In these cases, enabling %%syslog|syslog%% mirroring to the flash or using a remote %%syslog server|syslog-server%% is recommended to preserve logs for troubleshooting. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
English text in German document — critical localization issue.
Lines 48–49 contain English text that should be translated to German for consistency with the rest of this localized file. The :::important admonition wraps content about graceful shutdown logs, but it appears to be a copy-paste error or incomplete translation.
Provide the German translation for this section.
🧰 Tools
🪛 LanguageTool
[grammar] ~48-~48: Hier könnte ein Fehler sein.
Context: ...he flash drive. You can access it after rebooting by going to ***Tools → Syslog → syslog-...
(QB_NEW_DE)
[grammar] ~48-~48: Korrigiere die Fehler
Context: ...rive. You can access it after rebooting by going to ***Tools → Syslog → syslog-pre...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~48-~48: Korrigiere die Fehler
Context: ...e. You can access it after rebooting by going to **Tools → Syslog → syslog-previous...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~48-~48: Korrigiere die Fehler
Context: ... can access it after rebooting by going to Tools → Syslog → syslog-previous....
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~48-~48: Hier könnte ein Fehler sein.
Context: ...o Tools → Syslog → syslog-previous. This log is also included in diagnostic...
(QB_NEW_DE)
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
lines 46–50: Replace the English text inside the :::important block with a
German translation; use the following text verbatim: "Wenn Ihr System
ordnungsgemäß herunterfährt, wird das Sitzungsprotokoll automatisch auf dem
Flash‑Laufwerk gespeichert. Nach dem Neustart können Sie es unter Tools → Syslog
→ syslog-previous aufrufen. Dieses Log wird außerdem bei der nächsten
Boot‑Diagnose mit aufgenommen. Bei einem Systemabsturz geht das Systemprotokoll
jedoch verloren. In solchen Fällen wird empfohlen, die
%%syslog|syslog%%‑Spiegelung auf den Flash zu aktivieren oder einen entfernten
%%syslog server|syslog-server%% zu verwenden, um die Protokolle für die
Fehlersuche zu erhalten."
| :::note | ||
|
|
||
| Make sure to replace `/dev/sdX` with a valid physical device. Avoid logical Unraid devices, such as `/dev/md1`, which include %%parity|parity%% processes that may distort the raw performance readings. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
English text in note block — localization error.
Line 102 contains English text: "Make sure to replace /dev/sdX with a valid physical device..." This should be translated to German to match the document's localization.
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
around lines 100 to 104 contains English text inside a note block; replace that
English sentence with a German translation while preserving code fragments and
placeholders exactly (/dev/sdX, /dev/md1, %%parity|parity%%) and keeping the
note block formatting intact—for example, change the sentence to a concise
German equivalent that warns to use a valid physical device and avoid logical
Unraid devices that include parity processes which may distort raw performance
readings.
| :::note | ||
|
|
||
| This script only performs read-only operations and won't modify any data on your drives. However, it's best to schedule the test during idle periods, as it may affect disk I/O and interfere with %%array|array%% performance. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
English text in persistent log notes — localization error.
Line 134 contains English text: "This script only performs read-only operations..." This section should be translated to German to maintain consistency with the German localization.
🧰 Tools
🪛 LanguageTool
[grammar] ~134-~134: Hier könnte ein Fehler sein.
Context: ... only performs read-only operations and won't modify any data on your drives. However...
(QB_NEW_DE)
[grammar] ~134-~134: Hier könnte ein Fehler sein.
Context: ...odify any data on your drives. However, it's best to schedule the test during idle p...
(QB_NEW_DE)
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
around lines 132 to 136: the persistent note block contains English text ("This
script only performs read-only operations...") that should be translated to
German; replace the English sentence with an accurate German translation
preserving placeholders like %%array|array%% and the note formatting, ensuring
phrasing is natural and keeps the caution about scheduling during idle periods
(e.g., "Dieses Skript führt nur Leseoperationen aus und verändert keine Daten
auf Ihren Laufwerken. Es ist jedoch am besten, den Test in Ruhezeiten zu planen,
da er die Festplatten-E/A beeinträchtigen und die Leistung von %%array|array%%
stören kann.").
| ### Welche Controller werden für Unraid empfohlen? | ||
|
|
||
| Unraid funktioniert am besten mit nicht-%%RAID|raid%% Host-Bus-Adaptern (HBAs). Es ist am besten, Hardware-%%RAID|raid%%-Controller zu vermeiden, da diese die Informationen zur Laufwerksgesundheit verschleiern und die Wartung erschweren können. | ||
| Unraid funktioniert am besten mit nicht-%%RAID|raid%% Host-Bus-Adaptern (HBAs). Es ist am besten, Hardware-%%RAID|raid%%-Controller zu vermeiden, da diese die Informationen zur Laufwerksgesundheit verschleiern und die Wartung erschweren können. |
There was a problem hiding this comment.
Address LanguageTool-flagged grammar and consistency issues.
Static analysis has flagged several grammar and style corrections needed for proper German:
- Line 35: Remove extra space before "Host-Bus-Adaptern"
- Line 37: Adjust article form "Empfohlene" → "Empfohlenen" (dative case)
- Line 79: Adjust article form "Allgemeines" → "Allgemeinen" (dative case)
- Line 91: Replace hyphen with em-dash (–) for consistency
These are essential corrections for grammatically correct German. Apply the following:
- Unraid funktioniert am besten mit nicht-%%RAID|raid%% Host-Bus-Adaptern (HBAs).
+ Unraid funktioniert am besten mit nicht-%%RAID|raid%%Host-Bus-Adaptern (HBAs).
- Sie können den [Empfohlene Controller-Thread]...
+ Sie können den [Empfohlenen Controller-Thread]...
- posten Sie im [Allgemeines Support-Forum]...
+ posten Sie im [Allgemeinen Support-Forum]...
- Wenn Sie verschlüsselte Laufwerke verwenden und das Verschlüsselungspasswort vergessen, ist eine Datenwiederherstellung nicht möglich - es gibt keinen Hintereingang.
+ Wenn Sie verschlüsselte Laufwerke verwenden und das Verschlüsselungspasswort vergessen, ist eine Datenwiederherstellung nicht möglich – es gibt keinen Hintereingang.Also applies to: 37-37, 79-79, 91-91
🧰 Tools
🪛 LanguageTool
[grammar] ~35-~35: Entferne ein Leerzeichen
Context: ...oniert am besten mit nicht-%%RAID|raid%% Host-Bus-Adaptern (HBAs). Es ist am best...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
lines 35, 37, 79, 91: remove the stray extra space before "Host-Bus-Adaptern" on
line 35; change the article/adjective "Empfohlene" to the dative form
"Empfohlenen" on line 37; change "Allgemeines" to the dative form "Allgemeinen"
on line 79; and replace the hyphen at line 91 with an em-dash (–) for
consistency; update the text in place so spelling/case and punctuation match
correct German grammar.
|
|
||
| Unraid allows for the expansion of storage across multiple controllers. You can add a compatible HBA (as mentioned above). Ensure the controller operates in standard HBA (non-%%RAID|raid%%) mode and supports %%AHCI|ahci%%/SATA. Avoid using %%RAID|raid%%-only cards, as Unraid requires direct disk access for %%parity|parity%% and monitoring. | ||
| </details> | ||
| Unraid allows for the expansion of storage across multiple controllers. You can add a compatible HBA (as mentioned above). Ensure the controller operates in standard HBA (non-%%RAID|raid%%) mode and supports %%AHCI|ahci%%/SATA. Avoid using %%RAID|raid%%-only cards, as Unraid requires direct disk access for %%parity|parity%% and monitoring. |
There was a problem hiding this comment.
Localize English content sections to German.
Multiple sections contain English text mixed with German in a localized German FAQ file. This breaks consistency and defeats the purpose of localization. Sections affected:
- Lines 45: "Unraid allows for the expansion..."
- Lines 53–55: "Unraid utilizes %%SMART|smart%% data..."
- Line 59: "If you're uncertain about a drive's health, you can share..."
All English content in this German localization file should be translated to German to maintain consistency and user experience.
Also applies to: 53-55, 59-59
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
around lines 45, 53–55 and 59, several English sentences are present in the
German localization; replace those English fragments with accurate German
translations while preserving any inline placeholders/variables (e.g.,
%%RAID|raid%%, %%AHCI|ahci%%, %%parity|parity%%, %%SMART|smart%%) and existing
MDX formatting; ensure the German reads naturally and matches surrounding tone
(for line 45 translate the HBA/RAID explanation into German, for lines 53–55
translate the SMART monitoring explanation, and for line 59 translate the
guidance about sharing drive health), keep punctuation and capitalization
consistent with German grammar.
| 3. **Führen Sie eine weitere Prüfung durch:** Nachdem Sie Hardwareprobleme behoben haben, ist es eine gute Idee, eine weitere %%parity check|parity-check%% durchzuführen, um sicherzustellen, dass alles wieder in Ordnung ist. | ||
|
|
||
| :::info\[Rebuild Zeit | ||
| :::info[Rebuild Zeit |
There was a problem hiding this comment.
Fix malformed info block header: missing closing bracket.
Line 59 has :::info[Rebuild Zeit with no closing bracket. Change to :::info[Rebuild Zeit] to close the header properly.
-:::info[Rebuild Zeit
+:::info[Rebuild Zeit]📝 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.
| :::info[Rebuild Zeit | |
| :::info[Rebuild Zeit] |
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
around line 59, the info block header is malformed: it currently reads
":::info[Rebuild Zeit" without a closing bracket; fix it by adding the missing
closing bracket so the header becomes ":::info[Rebuild Zeit]".
| 1. Gehen Sie zu **Einstellungen** und schalten Sie Docker und den %%VM|vm%% Manager aus. Dies verhindert, dass Dateien geöffnet bleiben, sodass der %%Mover|mover%% alles reibungslos übertragen kann. | ||
| 2. In the **Shares** tab, for each share you want to move (like `appdata` or `system`), set **Primary storage** to the source %%cache pool|cache-pool%% and **Secondary storage** to the %%array|array%%. Set **Mover action** to **cache → array**. | ||
| 3. Go to the **Main** tab and click **Move Now** to transfer files from the %%cache pool|cache-pool%% to the %%array|array%%. | ||
| 4. Nachdem der %%Mover|mover%% fertig ist, überprüfen Sie, ob die Dateien verschoben wurden, indem Sie im **Haupt**-Tab neben dem Cache-Eintrag auf das Ordnersymbol klicken. | ||
| 5. Once all files are on the %%array|array%%, you can safely turn Docker and %%VM|vm%% services back on. |
There was a problem hiding this comment.
🧩 Analysis chain
Translate English procedural steps to German for consistency.
Lines 10–11 and 13 contain English instructions ("In the Shares tab...", "Go to the Main tab...", "Once all files...") within a German documentation file. For a German locale (i18n/de/), these should be translated to maintain consistent language throughout.
Provide German translations for the English steps, for example:
- Line 10: Translate "In the Shares tab..." to German
- Line 11: Translate "Go to the Main tab..." to German
- Line 13: Translate "Once all files..." to German
---
🏁 Script executed:
```shell
#!/bin/bash
# Find and examine the target file
find . -name "move-pool-to-array.mdx" -o -name "move-pool-to-array*" | head -20
Length of output: 567
🏁 Script executed:
#!/bin/bash
# List all files in the i18n/de directory structure to understand localization
find i18n/de -type f -name "*.mdx" | head -10Length of output: 781
🏁 Script executed:
#!/bin/bash
# Check the actual content of the target file
cat "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-pool-to-array.mdx" 2>/dev/null || echo "File not found"Length of output: 1127
🏁 Script executed:
#!/bin/bash
# Search for similar mixed-language patterns in other German locale files
rg -n "In the|Go to|Once all" i18n/de --type mdx -C2 | head -50Length of output: 27
🏁 Script executed:
#!/bin/bash
# Check if there's an English version of this same file for comparison
find . -path "*/current/unraid-os/using-unraid-to/manage-storage/partials/move-pool-to-array.mdx" | grep -v i18nLength of output: 0
---
🏁 Script executed:
```shell
#!/bin/bash
# Examine the English source file for comparison
cat "./docs/unraid-os/using-unraid-to/manage-storage/partials/move-pool-to-array.mdx"
Length of output: 1024
🏁 Script executed:
#!/bin/bash
# Check a few other German locale files for translation completeness patterns
for file in $(find i18n/de -type f -name "*.mdx" | head -5); do
echo "=== $file ==="
head -20 "$file" | tail -10
doneLength of output: 1843
🏁 Script executed:
#!/bin/bash
# Search for English words commonly found in UI instructions within German files
rg "In the|Go to|Once all|click|tab" i18n/de --type txt --type md -C1 | head -30Length of output: 3375
🏁 Script executed:
#!/bin/bash
# Check git log for this specific file to understand translation status
git log --oneline "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-pool-to-array.mdx" 2>/dev/null | head -5Length of output: 132
Translate English procedural steps 2, 3, and 5 to German to complete localization.
The German locale file contains partially translated content. While steps 1 and 4 are in German, steps 2, 3, and 5 remain in English. This creates an inconsistent user experience in the German documentation. Other German locale files in the repository are fully translated, indicating this is an incomplete translation.
Translate the following to German:
- Step 2: "In the Shares tab, for each share you want to move (like
appdataorsystem), set Primary storage to the source %%cache pool|cache-pool%% and Secondary storage to the %%array|array%%. Set Mover action to cache → array." - Step 3: "Go to the Main tab and click Move Now to transfer files from the %%cache pool|cache-pool%% to the %%array|array%%."
- Step 5: "Once all files are on the %%array|array%%, you can safely turn Docker and %%VM|vm%% services back on."
🧰 Tools
🪛 LanguageTool
[grammar] ~9-~9: Ergänze ein Satzzeichen
Context: ...nd schalten Sie Docker und den %%VM|vm%% Manager aus. Dies verhindert, dass Datei...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_VMPIPEVMPERCENTPERCENTDASHMANAGER)
[grammar] ~10-~10: Passe das Symbol an
Context: ...os übertragen kann. 2. In the Shares tab, for each share you want to move (like ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~10-~10: Korrigiere die Fehler
Context: ...rtragen kann. 2. In the Shares tab, for each share you want to move (like `appd...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~10-~10: Korrigiere die Fehler
Context: ...gen kann. 2. In the Shares tab, for each share you want to move (like appdata ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~10-~10: Korrigiere die Fehler
Context: ...ann. 2. In the Shares tab, for each share you want to move (like appdata or `sy...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~10-~10: Korrigiere die Fehler
Context: .... In the Shares tab, for each share you want to move (like appdata or `system...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~10-~10: Korrigiere die Fehler
Context: ... the Shares tab, for each share you want to move (like appdata or system), s...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~10-~10: Korrigiere die Fehler
Context: ...Shares tab, for each share you want to move (like appdata or system), set ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~10-~10: Korrigiere die Fehler
Context: ...hares** tab, for each share you want to move (like appdata or system), set **Pri...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~10-~10: Korrigiere das Wort
Context: ...* tab, for each share you want to move (like appdata or system), set **Primary s...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_SPELLING)
[grammar] ~10-~10: Korrigiere das Wort
Context: ... share you want to move (like appdata or system), set Primary storage to t...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_SPELLING)
[grammar] ~10-~10: Passe das Symbol an
Context: ...t to move (like appdata or system), set Primary storage to the source %%cac...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~10-~10: Passe das Symbol an
Context: ...orsystem`), set Primary storage to the source %%cache pool|cache-pool%% an...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~10-~10: Passe das Symbol an
Context: ...r system), set Primary storage to the source %%cache pool|cache-pool%% and **...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~10-~10: Passe das Symbol an
Context: ...ystem`), set Primary storage to the source %%cache pool|cache-pool%% and **Secondar...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~10-~10: Korrigiere das Wort
Context: ...to the source %%cache pool|cache-pool%% and Secondary storage to the %%array|ar...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_SPELLING)
[style] ~10-~10: Stilistisch kann es schöner sein, Doppelungen ganzer Phrasen in einem Satz zu vermeiden.
Context: ...cache pool|cache-pool%% and Secondary storage to the %%array|array%%. Set Mover action t...
(DOPPELUNGEN_PHRASEN)
[grammar] ~10-~10: Wähle ein passenderes Wort
Context: ...ndary storage** to the %%array|array%%. Set Mover action to cache → array. ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_NOUN)
[grammar] ~10-~10: Passe das Symbol an
Context: ...e %%array|array%%. Set Mover action to cache → array. 3. Go to the *Main...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-pool-to-array.mdx
around lines 9 to 13 the procedural steps 2, 3 and 5 are still in English;
replace them with German translations: Step 2 -> "Wechseln Sie zur Registerkarte
**Shares** und setzen Sie für jedes zu verschiebende Share (z. B. `appdata` oder
`system`) **Primary storage** auf den Quell‑%%cache pool|cache-pool%% und
**Secondary storage** auf das %%array|array%%. Stellen Sie **Mover action** auf
**cache → array**.", Step 3 -> "Gehen Sie zur Registerkarte **Main** und klicken
Sie auf **Move Now**, um Dateien vom %%cache pool|cache-pool%% in das
%%array|array%% zu verschieben.", Step 5 -> "Sobald alle Dateien auf dem
%%array|array%% sind, können Sie Docker‑ und %%VM|vm%%‑Dienste wieder sicher
einschalten."
|
|
||
| 2. **Dateien löschen:** | ||
| Führen Sie diesen Befehl aus und ersetzen Sie `[share_name]` durch den Namen Ihres Freigabeordners: | ||
| ::::Hinweis[Alternative Methoden] |
There was a problem hiding this comment.
🧩 Analysis chain
Mixed language markers in documentation.
Line 141 contains "::::Hinweis[Alternative Methoden]" with mixed German and English structure. Should this be "::::Hinweis[Alternative Methoden]" consistently, or should it follow the English pattern used elsewhere in the documentation?
I'll verify the review comment by examining the file and understanding the documentation patterns in the codebase.
I'll examine the file content and check for similar patterns in the codebase to verify the reviewer's concern.
🏁 Script executed:
#!/bin/bash
# Check the actual file content around line 141
echo "=== File content around line 141 ==="
sed -n '135,147p' 'i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx'
echo -e "\n=== Search for similar ::::Hinweis patterns ==="
rg '::::Hinweis' i18n/de/
echo -e "\n=== Search for English equivalents (::::Note or ::::Caution) ==="
rg '::::(Note|Caution|Warning|Info|Tip)' i18n/ --type=mdx | head -20
echo -e "\n=== Check if there are English versions of this file ==="
find . -name 'shares.mdx' -type fLength of output: 1727
🏁 Script executed:
#!/bin/bash
# Check the actual file content around line 141
echo "=== File content around line 141 ==="
sed -n '135,147p' 'i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx'
echo -e "\n=== Search for similar ::::Hinweis patterns in German docs ==="
rg '::::Hinweis' i18n/de/ -n
echo -e "\n=== Search for English callout patterns ==="
rg '::::(Note|Caution|Warning|Info|Tip)' docs/ --type=mdx -n | head -15
echo -e "\n=== Check English version of shares.mdx if exists ==="
find . -path '*/docs/*' -name 'shares.mdx' -type fLength of output: 1318
I need to check the English version and search for callout patterns more broadly.
🏁 Script executed:
#!/bin/bash
# Check English version around the same section
echo "=== English version around equivalent section ==="
grep -n "Alternative Methods\|Empty the Share" docs/unraid-os/using-unraid-to/manage-storage/shares.mdx -A 20 -B 5 | head -50
echo -e "\n=== Search for all callout patterns (:::: or :::) ==="
rg '::+[A-Za-z]+' docs/ -n | grep -E ':::+' | head -20
echo -e "\n=== Search for callouts in German docs ==="
rg '::+[A-Za-z]+' i18n/de/ -n | grep -E ':::+' | head -20
echo -e "\n=== Search for note/hint patterns in other locales ==="
rg ':::+(Note|Hinweis|Nota|Remarque|备注)' i18n/ -n | head -15
echo -e "\n=== Check for Docusaurus configuration ==="
find . -name 'docusaurus.config.*' -o -name 'sidebars.*' | head -5Length of output: 4866
🏁 Script executed:
#!/bin/bash
# Check English version around the same section
echo "=== English version for comparison ==="
sed -n '135,160p' docs/unraid-os/using-unraid-to/manage-storage/shares.mdx
echo -e "\n=== Search for all ::: and :::: callout patterns in English docs ==="
rg '::+[A-Za-z]+\[' docs/ -n | head -20
echo -e "\n=== Search for note/hint patterns across all locales ==="
rg '::+(note|Note|Hinweis|Nota|Remarque|提示)\[' -i | head -20
echo -e "\n=== Check Docusaurus admonition/callout syntax in any markdown files ==="
rg ':::+(note|caution|tip|info|warning|danger)\[' docs/ -n | head -15Length of output: 6933
Use standard Docusaurus admonition type instead of custom German keyword.
The line uses ::::Hinweis[Alternative Methoden], but Hinweis is not a recognized Docusaurus admonition type. Other German documentation files consistently use standard English admonition types (note, tip, caution, info, important) while keeping the content in German. Change to ::::note[Alternative Methoden] to match the English equivalent and align with the rest of the codebase.
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
around line 141, the admonition uses a nonstandard German keyword "Hinweis"
which Docusaurus doesn't recognize; replace the custom admonition header with
the standard Docusaurus type by changing `::::Hinweis[Alternative Methoden]` to
`::::note[Alternative Methoden]` so the admonition renders correctly and matches
other German docs.
| Diese Ressourcen verbinden Sie mit Community-Foren und Entwicklerdiskussionen, wo Sie Hilfe finden, Probleme beheben und auf dem Laufenden bleiben können. | ||
|
|
||
| - **Apps-Tab**: Klicken Sie auf den **Apps**-Tab und filtern Sie nach **Installierte Apps**. Suchen Sie dort die App und wählen Sie **Support**. | ||
|
|
||
| - **Dashboard- oder Docker-Tabs**: Gehen Sie zu den **Dashboard**- oder **Docker**-Tabs, klicken Sie auf das Symbol des Containers, den Sie verwenden, und wählen Sie **Support**. | ||
|
|
||
| - **Plugins-Tab**: Im **Plugins**-Tab hat jedes Plugin in seiner Zusammenfassung einen **Support-Thread**-Link für einen schnellen Zugriff. | ||
|
|
||
| :::tip[Support preferences] | ||
| Bei der Nutzung der Support-Optionen suchen Sie nach diesen Dropdown-Optionen: | ||
| :::tip[Support Präferenzen] | ||
|
|
||
| Das **Action Center** befindet sich im **Apps**-Tab in der %%WebGUI|web-gui%% und dient als zentrales Hub für die Verwaltung des Anwendungsstatus. Es bietet Informationen über: | ||
|
|
||
| - **Updates verfügbar**: Anwendungen, die neuere Versionen zur Installation bereit haben | ||
| - **Veraltete Anwendungen**: Anwendungen, die nicht mehr gepflegt oder empfohlen werden | ||
|
|
||
| - **Discord**: Wenn verfügbar, ist Discord in der Regel der bevorzugte Support-Kanal der Betreuer gegenüber dem Forum. | ||
| - **Projekt**: Fragen zur Anwendung selbst werden am besten über die offiziellen Kanäle des Projekts beantwortet. | ||
| ::: | ||
|
|
||
| Diese Ressourcen verbinden Sie mit Community-Foren und Entwicklerdiskussionen, wo Sie Hilfe finden, Probleme beheben und auf dem Laufenden bleiben können. |
There was a problem hiding this comment.
Remove duplicate content about connecting to community resources.
Lines 79 and 96 contain identical text: "Diese Ressourcen verbinden Sie mit Community-Foren und Entwicklerdiskussionen, wo Sie Hilfe finden, Probleme beheben und auf dem Laufenden bleiben können." This creates confusing redundancy. Keep one instance and remove the other.
Apply this diff to remove the duplicate on line 96:
:::
-Diese Ressourcen verbinden Sie mit Community-Foren und Entwicklerdiskussionen, wo Sie Hilfe finden, Probleme beheben und auf dem Laufenden bleiben können.
-
---Committable suggestion skipped: line range outside the PR's diff.
🧰 Tools
🪛 LanguageTool
[grammar] ~81-~81: Entferne ein Wort
Context: ...dem Laufenden bleiben können. - Apps-Tab: Klicken Sie auf den Apps-Tab und fi...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_NOUN)
[grammar] ~81-~81: Passe die Groß- und Kleinschreibung an
Context: ...den Apps-Tab und filtern Sie nach Installierte Apps. Suchen Sie dort die App und wäh...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~83-~83: Entferne ein Wort
Context: ...Support*. - Dashboard- oder Docker-Tabs: Gehen Sie zu den Dashboard- oder **...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_NOUN)
[grammar] ~85-~85: Ergänze ein Wort
Context: ...enden, und wählen Sie Support. - Plugins-Tab: Im Plugins-Tab hat jedes Plu...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_NOUN)
[grammar] ~87-~87: Ergänze ein Satzzeichen
Context: ...einen schnellen Zugriff. :::tip[Support Präferenzen] Das Action Center befi...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_SUPPORTDASHPRÄFERENZEN)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx
around lines 79–96 there is a duplicated sentence ("Diese Ressourcen verbinden
Sie mit Community-Foren und Entwicklerdiskussionen, wo Sie Hilfe finden,
Probleme beheben und auf dem Laufenden bleiben können."). Remove the second
occurrence (around line 96) so the paragraph appears only once, and ensure
surrounding spacing/line breaks remain consistent after deletion.
| :::tip[Best Praxis] | ||
|
|
||
| Store application data (settings, libraries, etc.) outside the container, typically in the `appdata` %%user share|user-share%%. This [share management](../../../manage-storage/shares.mdx) approach keeps your data safe during updates or reinstalls. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
English content in German-localized documentation.
The tip block (lines 7-11) contains entirely English text while the rest of the file is in German. This should be translated to German for consistency with the localized documentation.
🧰 Tools
🪛 LanguageTool
[grammar] ~9-~9: Passe das Symbol an
Context: ...pdata` %%user share|user-share%%. This share management ap...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/volume-mappings.mdx
lines 7-11: The tip block is in English; replace it with German to match the
localized file. Change the block to a German translation, for example:
":::tip[Beste Praxis]\n\nSpeichere Anwendungsdaten (Einstellungen, Bibliotheken
usw.) außerhalb des Containers, typischerweise im `appdata` %%user
share|user-share%%. Dieser
[Share‑Verwaltung](../../../manage-storage/shares.mdx)‑Ansatz schützt deine
Daten bei Updates oder Neuinstallationen.\n\n:::" and ensure the markdown/tip
syntax and the share link remain intact.
There was a problem hiding this comment.
Actionable comments posted: 16
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (8)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx (1)
113-131:⚠️ Potential issue | 🟡 MinorDeduplicate the repeated “Wartungserwartungen” intro paragraph.
The paragraph at Line 115 is repeated verbatim at Line 130, which reads as redundant.
✂️ Suggested fix
### Wartungserwartungen - -Entwickler, die Anwendungen in Community Applications veröffentlichen, werden erwartet, dass sie ihre Projekte pflegen, um die Kompatibilität und Zuverlässigkeit für die Unraid-Community sicherzustellen. Dieser Abschnitt umreißt die laufenden Verantwortlichkeiten, die zur Aufrechterhaltung der Qualität der verfügbaren Anwendungen beitragen.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx (3)
242-242:⚠️ Potential issue | 🟡 MinorHeading grammar needs correction.
“Neusformatiert eines Laufwerks” should be “Neuformatieren eines Laufwerks”.✏️ Suggested fix
-## Neusformatiert eines Laufwerks +## Neuformatieren eines Laufwerks
269-318:⚠️ Potential issue | 🟠 MajorCache reformat workflow still contains English sentences.
Several steps are English (e.g., “Sometimes, you'll need…”, “For each share…”, “For a single-drive…”). Translate these to keep the section consistent.
586-627:⚠️ Potential issue | 🟠 MajorRepair instructions still contain English sentences.
Translate the ZFS guidance line and the “Stop and restart…” bullet.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (4)
17-36:⚠️ Potential issue | 🟠 MajorTranslate the introductory overview and benefits list to German.
Line 17 and Lines 21–27 are still English; the info bullets at Lines 31–36 are also English. Please localize these strings while preserving the %%tokens%%.
244-270:⚠️ Potential issue | 🟠 Major‘Mindestfreier Speicherplatz’ section is duplicated and content is mismatched.
Line 244 repeats the heading from Line 274, and Lines 246–265 describe disk replacement and multi‑pool benefits rather than minimum free space. Please move that block to the appropriate section and keep a single minimum‑free‑space section here.
276-292:⚠️ Potential issue | 🟠 MajorTranslate the minimum‑free‑space explanation and bullets.
Line 276 and Lines 290–292 are still English; translate them while preserving the %%tokens%%.
335-343:⚠️ Potential issue | 🟠 MajorTranslate the Linux‑level move explanation in the details block.
Lines 335–336 are English; translate to German while keeping %%tokens%% and paths intact.
🤖 Fix all issues with AI agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx`:
- Line 36: Change the incorrect feminine article in the sentence "Stoppen Sie
die Array." to the correct neuter article: replace "die" with "das" so the
sentence reads "Stoppen Sie das Array."; locate this exact sentence in the file
and update the article.
- Line 176: The admonition title mixes English and German in the admonition
marker ":::warning[Important Überlegungen]"; update that marker to a
single-language title (e.g. replace with ":::warning[Wichtige Überlegungen]" for
German consistency or ":::warning[Important Considerations]" for English) so the
admonition heading matches the document language and formatting.
- Line 246: Replace the typo "Stärken Sie sicher" with the correct phrase
"Stellen Sie sicher" in the sentence currently reading "Wenn Ihr System Hot-Swap
unterstützt, müssen Sie nicht herunterfahren. Stärken Sie sicher, dass das Array
vor Hardware-Änderungen gestoppt wird." so the second sentence becomes "Stellen
Sie sicher, dass das Array vor Hardware-Änderungen gestoppt wird." in the MDX
content for replacing-disks-in-array.mdx.
- Line 165: The admonition title mixes English and German in the admonition
declaration :::important[When um dieses Verfahren zu verwenden]; update the
bracketed title to a fully German phrase such as "Wenn Sie dieses Verfahren
verwenden" (or "Wenn Sie dieses Verfahren anwenden") so the admonition reads
:::important[Wenn Sie dieses Verfahren verwenden]; edit the string inside the
brackets in the admonition declaration to correct the language.
- Line 198: The admonition title mixes English and German (":::info[Rebuild
Zeiterwartungen]"); update it to a fully German title such as ":::info[Erwartete
Rebuild-Zeiten]" (or ":::info[Rebuild-Erwartungen]" / ":::info[Erwartete
Wiederherstellungszeiten]") by replacing the existing admonition header string
so the admonition marker :::info uses a German-only label.
- Line 214: Replace the English admonition title and escaped bracket in the
admonition marker: change ":::important\[Prerequisites]" to use an unescaped
bracket and a German title, e.g. ":::important[Voraussetzungen]"; update the
admonition header in the file so the bracket is `[` not `\[` and the title is
translated to German (Voraussetzungen).
- Line 222: The admonition uses an English title and contains an escaped bracket
token ":::warning\[Warnings]"; replace it with a proper German admonition and
unescaped bracket syntax by changing the token to ":::warning[Warnungen]" so the
admonition renders correctly (locate the string ":::warning\\[Warnings]" in the
file and update it to ":::warning[Warnungen]").
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`:
- Around line 47-53: The heading "Sichern Ihres Cache-Pools auf das Array" does
not match the embedded component <PoolMultiDeviceMode />; update the heading to
reflect the multi-device mode (e.g., "Mehrgerätmodus" or "Mehrgerät‑Modus" /
"Mehrere Geräte") so it semantically matches <PoolMultiDeviceMode /> and keep
the single-device section heading paired with <PoolSingleDeviceMode />; ensure
the heading text you choose is consistent with other headings in this file.
- Around line 108-110: The link to "#converting-a-pool-to-btrfs-or-zfs" is
broken because the German heading "Umwandlung eines Pools in BTRFS oder ZFS"
generates a different slug; fix it by adding an explicit ID to that heading so
it matches the English slug (e.g. change the heading "Umwandlung eines Pools in
BTRFS oder ZFS" to include {`#converting-a-pool-to-btrfs-or-zfs`}); ensure the
explicit ID matches the link used in the note referencing the
converting-a-pool-to-btrfs-or-zfs anchor.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`:
- Around line 461-477: Replace the mixed-language admonition titles with fully
German titles: update the first admonition title "Why Ist Parität nicht genug?"
to "Warum reicht Parität nicht?" and change the second admonition title "Just Um
es noch einmal zu sagen" to "Nur zur Erinnerung"; ensure these changes are
applied to the corresponding markdown/admonition blocks (the :::important[...]
and :::note[...] blocks) so the display text is fully German while leaving the
inner content and inline translation tokens (e.g., %%parity|Parität%%, %%cache
pools|cache-pool%%, %%BTRFS|btrfs%%, %%ZFS|zfs%%) unchanged.
- Around line 333-391: The BTRFS Actions section contains English text that
needs full German translation: translate the intro paragraph starting
"Maintaining your %%BTRFS|btrfs%% pools...", the "Balance" description and its
bullets under "Wann Balance durchgeführt werden sollte" and "Reparatur eines
Dateisystems", the "Scrub" bullets under "Über das WebGUI", "Empfohlener
Zeitplan", "Wie man Scrub durchführt", and the final English sentence linking to
BTRFS docs; keep the existing German headings/notes/tips and tokens (e.g.,
%%BTRFS|btrfs%%, %%WebGUI|web-gui%%, "Gleichgewicht", "Balance", "Scrub")
unchanged while replacing only the English sentences and bullets with accurate
German translations that match the tone and formatting of surrounding content.
- Around line 441-444: Replace the English warning text inside the :::important
block that begins "Do not format an unmountable drive..." with a German
translation, keeping the admonition markup unchanged and preserving the
placeholder token %%parity|parity%% exactly as-is; for example use: "Formatieren
Sie ein nicht einhängbares Laufwerk nicht, wenn Sie nicht bereit sind, alle
darauf befindlichen Daten zu verlieren. Das Formatieren löscht alles und
aktualisiert die %%parity|parity%%-Informationen, wodurch eine Wiederherstellung
unmöglich wird. Versuchen Sie immer zuerst, das Dateisystem zu reparieren."
- Around line 397-399: The introductory paragraph "Unassigned drives are storage
devices connected to your Unraid server..." is still in English; replace it with
a German translation while preserving the special tokens %%array|array%%,
%%cache pool|cache-pool%% and %%virtual machines|vm%% exactly as-is. Update the
text in the same location so it reads in German (e.g., "Nicht zugewiesene
Laufwerke sind Speichermedien...") and ensure the surrounding note block :::note
remains unchanged.
- Around line 150-154: The step "Run %%Mover|mover%% from the **Main** tab. Wait
for it to finish and ensure that the %%cache|cache%% is empty." is still in
English; replace it with a proper German sentence using the same tokens
(%%Mover|mover%% and %%cache|cache%%) and preserving formatting/markup (bold
**Main**) so it reads e.g. "Führen Sie %%Mover|mover%% von der
**Main**-Registerkarte aus. Warten Sie, bis der Vorgang abgeschlossen ist, und
stellen Sie sicher, dass der %%cache|cache%% leer ist." Update the line
containing the %%Mover|mover%% token accordingly.
- Line 191: Replace the English sentence "For more details on advanced
%%BTRFS|btrfs%% features, check out the [official BTRFS
documentation](https://btrfs.readthedocs.io/en/latest/Introduction.html)." with
a German translation while preserving the tokenized filesystem name
%%BTRFS|btrfs%% and the link URL; e.g. use a concise German sentence such as
"Für weitere Details zu erweiterten %%BTRFS|btrfs%%-Funktionen siehe die
[offizielle
BTRFS-Dokumentation](https://btrfs.readthedocs.io/en/latest/Introduction.html)."
Ensure punctuation and link text are localized and the surrounding admonition
remains in German.
- Line 115: The sentence "To set the file system type globally, navigate to
***Settings → Disk Settings*** to set the default file system for new
%%array|array%% drives only. Unraid defaults to %%XFS|xfs%% for %%array|array%%
drives." is still in English; replace it with a proper German translation while
preserving the markdown emphasis and the placeholders/shortcodes
(%%array|array%% and %%XFS|xfs%%) exactly as-is; ensure the translated text
conveys the same meaning (how to set global default in Settings → Disk Settings,
applies only to new array drives, and that Unraid defaults to XFS for array
drives).
...ent-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx
Show resolved
Hide resolved
|
|
||
| Manchmal wird ein Laufwerk nicht aufgrund eines tatsächlichen Defekts deaktiviert, sondern wegen Problemen wie lockeren Kabeln, Stromproblemen oder vorübergehende Störungen. Falls dies der Fall ist, können Sie versuchen, das deaktivierte Laufwerk wieder zu aktivieren, indem Sie es auf sich selbst wiederherstellen, anstatt es zu ersetzen. | ||
|
|
||
| :::important[When um dieses Verfahren zu verwenden] |
There was a problem hiding this comment.
Mixed English/German admonition title.
The admonition title contains mixed languages: "When um dieses Verfahren zu verwenden" should be fully German.
Suggested fix
- :::important[When um dieses Verfahren zu verwenden]
+ :::important[Wann dieses Verfahren zu verwenden ist]🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx`
at line 165, The admonition title mixes English and German in the admonition
declaration :::important[When um dieses Verfahren zu verwenden]; update the
bracketed title to a fully German phrase such as "Wenn Sie dieses Verfahren
verwenden" (or "Wenn Sie dieses Verfahren anwenden") so the admonition reads
:::important[Wenn Sie dieses Verfahren verwenden]; edit the string inside the
brackets in the admonition declaration to correct the language.
|
|
||
| ::: | ||
|
|
||
| :::warning[Important Überlegungen] |
There was a problem hiding this comment.
Mixed English/German admonition title.
Suggested fix
- :::warning[Important Überlegungen]
+ :::warning[Wichtige Überlegungen]📝 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.
| :::warning[Important Überlegungen] | |
| :::warning[Wichtige Überlegungen] |
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx`
at line 176, The admonition title mixes English and German in the admonition
marker ":::warning[Important Überlegungen]"; update that marker to a
single-language title (e.g. replace with ":::warning[Wichtige Überlegungen]" for
German consistency or ":::warning[Important Considerations]" for English) so the
admonition heading matches the document language and formatting.
| 8. Optional wählen Sie den %%Wartungsmodus|maintenance-mode%%, um den Wiederherstellungsprozess zu beschleunigen. | ||
| 9. Klicken Sie auf **Start**, um den Neubau zu beginnen. Unraid nimmt die Inhalte von der emulierten Festplatte und rekonstruiert sie auf dem physischen Laufwerk. | ||
|
|
||
| :::info[Rebuild Zeiterwartungen] |
There was a problem hiding this comment.
Mixed English/German admonition title.
Suggested fix
- :::info[Rebuild Zeiterwartungen]
+ :::info[Zeiterwartungen für den Neuaufbau]🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx`
at line 198, The admonition title mixes English and German (":::info[Rebuild
Zeiterwartungen]"); update it to a fully German title such as ":::info[Erwartete
Rebuild-Zeiten]" (or ":::info[Rebuild-Erwartungen]" / ":::info[Erwartete
Wiederherstellungszeiten]") by replacing the existing admonition header string
so the admonition marker :::info uses a German-only label.
|
|
||
| **Beispielszenario:** Sie haben eine Unraid-Konfiguration mit einer **2TB Paritätsfestplatte** und einer **1TB Datenfestplatte** und möchten die 1TB Festplatte durch eine **4TB Festplatte** ersetzen. Zuerst weisen Sie die neue 4TB Festplatte als Paritätsfestplatte zu, was die 2TB Festplatte ersetzt. Dann verschieben Sie die ursprüngliche 2TB Festplatte in den Datensteckplatz und entfernen die 1TB Festplatte vollständig. Nach diesen Änderungen haben Sie eine 4TB Festplatte als neue Parität, was sicherstellt, dass Sie in Zukunft Datenfestplatten bis zu 4TB hinzufügen können. Die 2TB Festplatte wird nun Ihre vorhandenen Daten enthalten, während die 1TB Festplatte anderweitig verwendet werden kann. Dieser Austausch hält Ihre Daten sicher und Ihr Array geschützt, während er zukünftige Upgrades ermöglicht. | ||
|
|
||
| :::important\[Prerequisites] |
There was a problem hiding this comment.
English admonition title and escaped bracket syntax.
The title "Prerequisites" should be translated to German, and the escaped bracket \[ should be [.
Suggested fix
- :::important\[Prerequisites]
+ :::important[Voraussetzungen]🧰 Tools
🪛 LanguageTool
[grammar] ~214-~214: Ergänze ein Leerzeichen
Context: ...tige Upgrades ermöglicht. :::important[Prerequisites] - Stellen Sie vor dem Start sicher, d...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_ORTHOGRAPHY_SPACE)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx`
at line 214, Replace the English admonition title and escaped bracket in the
admonition marker: change ":::important\[Prerequisites]" to use an unescaped
bracket and a German title, e.g. ":::important[Voraussetzungen]"; update the
admonition header in the file so the bracket is `[` not `\[` and the title is
translated to German (Voraussetzungen).
|
|
||
| - Alle in ReiserFS formatierten Laufwerke müssen so schnell wie möglich auf ein anderes Dateisystem migriert werden, da sie in einer zukünftigen Version von Unraid (voraussichtlich Unraid 7.3) nicht mehr nutzbar sein werden. | ||
| - Alle Laufwerke, die in einer älteren Version von XFS formatiert sind, müssen vor 2030 migriert werden. | ||
| For more details on advanced %%BTRFS|btrfs%% features, check out the [official BTRFS documentation](https://btrfs.readthedocs.io/en/latest/Introduction.html). |
There was a problem hiding this comment.
Translate the BTRFS documentation sentence.
This is still English within a German admonition.
🌐 Suggested translation
-For more details on advanced %%BTRFS|btrfs%% features, check out the [official BTRFS documentation](https://btrfs.readthedocs.io/en/latest/Introduction.html).
+Weitere Details zu erweiterten %%BTRFS|btrfs%%-Funktionen finden Sie in der [offiziellen BTRFS-Dokumentation](https://btrfs.readthedocs.io/en/latest/Introduction.html).📝 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.
| For more details on advanced %%BTRFS|btrfs%% features, check out the [official BTRFS documentation](https://btrfs.readthedocs.io/en/latest/Introduction.html). | |
| Weitere Details zu erweiterten %%BTRFS|btrfs%%-Funktionen finden Sie in der [offiziellen BTRFS-Dokumentation](https://btrfs.readthedocs.io/en/latest/Introduction.html). |
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`
at line 191, Replace the English sentence "For more details on advanced
%%BTRFS|btrfs%% features, check out the [official BTRFS
documentation](https://btrfs.readthedocs.io/en/latest/Introduction.html)." with
a German translation while preserving the tokenized filesystem name
%%BTRFS|btrfs%% and the link URL; e.g. use a concise German sentence such as
"Für weitere Details zu erweiterten %%BTRFS|btrfs%%-Funktionen siehe die
[offizielle
BTRFS-Dokumentation](https://btrfs.readthedocs.io/en/latest/Introduction.html)."
Ensure punctuation and link text are localized and the surrounding admonition
remains in German.
| Maintaining your %%BTRFS|btrfs%% pools in Unraid is essential for keeping them running well and ensuring your data stays safe. Two key tools you’ll want to use regularly are **Balance** and **Scrub**. These operations help solve space allocation problems, optimize your storage use, and protect your data from hidden corruption. | ||
|
|
||
| Schauen wir uns an, was jede Operation macht und wann sie verwendet wird: | ||
| Lassen Sie uns aufschlüsseln, was jede Operation tut und wann sie zu verwenden ist: | ||
|
|
||
| <Tabs> | ||
| <TabItem value="gleichgewicht" label="Gleichgewicht" default> | ||
| <BtrfsBalance /> | ||
| </TabItem> | ||
| ### Gleichgewicht | ||
|
|
||
| <TabItem value="scrub" label="Scrub"> | ||
| <BtrfsScrub /> | ||
| </TabItem> | ||
| </Tabs> | ||
| The **Balance** operation redistributes data and metadata chunks across your %%BTRFS|btrfs%% pool. This process helps free up space, resolves allocation issues, and can fix "no space left on device" errors even when space seems available. | ||
|
|
||
| #### Wann Balance durchgeführt werden sollte | ||
|
|
||
| - Wenn Sie "Kein Speicherplatz mehr auf dem Gerät"-Fehler haben, aber noch freier Speicherplatz vorhanden ist. | ||
| - Nach dem Hinzufügen oder Entfernen von Laufwerken in einem Pool. | ||
| - Um den Platzverbrauch zu optimieren und die Leistung zu verbessern. | ||
|
|
||
| #### Reparatur eines Dateisystems | ||
|
|
||
| 1. Klicken Sie im %%WebGUI|web-gui%% auf den Pool im **Main**-Tab und wählen Sie **Balance**. | ||
| 2. (Optional) Fügen Sie Parameter für den erweiterten Gebrauch hinzu (siehe Unraid-Hilfe für Details). | ||
| 3. Klicken Sie auf **Start**, um zu beginnen. | ||
|
|
||
| :::note\[Timing] | ||
|
|
||
| Reparaturen können je nach Größe oder starkem Schaden des Dateisystems von mehreren Minuten bis zu mehreren Stunden dauern. Der Fortschritt mag langsam erscheinen, aber Sie können die Aktivität überprüfen, indem Sie die Lese-/Schreibstatistiken auf der Hauptseite betrachten. | ||
|
|
||
| ::: | ||
|
|
||
| ### Scrub | ||
|
|
||
| Die **Scrub**-Operation liest alle Daten- und Metadaten, überprüft die Integrität der Prüfsummen und repariert beschädigte Blöcke mithilfe vorhandener redundanter Kopien. Scrubbing hilft, stille Datenbeschädigungen, auch bekannt als "Bit Rot", zu identifizieren und zu beheben, bevor sie zu einem signifikanten Problem werden. | ||
|
|
||
| #### Über das WebGUI | ||
|
|
||
| - **Start the array**: Start the %%array|array%% in the correct mode (refer to the section above). | ||
| - **Wählen Sie die Festplatte aus**: Gehen Sie zum **Main** Tab und klicken Sie auf die Festplatte, die Sie reparieren möchten. | ||
| - **Zugriff auf Reparaturoptionen**: Blättern Sie zu **Dateisystemstatus überprüfen**. | ||
|
|
||
| #### Empfohlener Zeitplan | ||
|
|
||
| - Hoch genutzte Pools: **Einmal pro Woche** | ||
| - Alle anderen Pools: **Einmal pro Monat** | ||
|
|
||
| #### Wie man Scrub durchführt | ||
|
|
||
| 1. Klicken Sie im %%WebGUI|web-gui%% auf den Pool im **Main**-Tab und wählen Sie **Scrub**. | ||
| 2. Klicken Sie auf **Start**, um den Betrieb zu starten. | ||
|
|
||
| :::note\[Timing] | ||
|
|
||
| Wenn Sie die Reparaturausgabe nicht verstehen oder der Prozess fehlschlägt, teilen Sie Ihre Diagnosen und das Reparaturlog im [Unraid Forum](https://forums.unraid.net/) für weitere Unterstützung. | ||
|
|
||
| ::: | ||
|
|
||
| :::tip | ||
|
|
||
| Sowohl **Balance** als auch **Scrub** können bei laufendem System durchgeführt werden, jedoch beachten Sie, dass die Leistung während dieser Operationen beeinträchtigt werden kann. Sie können den Fortschritt im %%WebGUI|web-gui%% überwachen. | ||
|
|
||
| ::: | ||
|
|
||
| For more details on advanced %%BTRFS|btrfs%% features, check out the [official BTRFS documentation](https://btrfs.readthedocs.io/en/latest/Introduction.html). |
There was a problem hiding this comment.
BTRFS Actions section still has English paragraphs and bullets.
Translate the intro, Balance description, Scrub steps, and the closing sentence to German.
🧰 Tools
🪛 LanguageTool
[grammar] ~333-~333: Entferne ein Leerzeichen
Context: ...-- ## BTRFS-Aktionen Maintaining your %%BTRFS|btrfs%% pools in Unraid is essential for keeping them...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~333-~333: Korrigiere die Fehler
Context: ...ng your %%BTRFS|btrfs%% pools in Unraid is essential for keeping them running well...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~333-~333: Korrigiere die Fehler
Context: ...your %%BTRFS|btrfs%% pools in Unraid is essential for keeping them running well and ensur...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~333-~333: Korrigiere die Fehler
Context: ...FS|btrfs%% pools in Unraid is essential for keeping them running well and ensuring ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~333-~333: Korrigiere die Fehler
Context: ...trfs%% pools in Unraid is essential for keeping them running well and ensuring your dat...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~333-~333: Korrigiere die Fehler
Context: ...ools in Unraid is essential for keeping them running well and ensuring your data sta...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~333-~333: Korrigiere die Fehler
Context: ...in Unraid is essential for keeping them running well and ensuring your data stays safe....
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~333-~333: Korrigiere die Fehler
Context: ...d is essential for keeping them running well and ensuring your data stays safe. Two ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~333-~333: Korrigiere die Fehler
Context: ...essential for keeping them running well and ensuring your data stays safe. Two key ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~333-~333: Korrigiere die Fehler
Context: ...ntial for keeping them running well and ensuring your data stays safe. Two key tools you...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~333-~333: Korrigiere die Fehler
Context: ... keeping them running well and ensuring your data stays safe. Two key tools you’ll w...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~333-~333: Korrigiere die Fehler
Context: ...ing them running well and ensuring your data stays safe. Two key tools you’ll want t...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~333-~333: Korrigiere die Fehler
Context: ...hem running well and ensuring your data stays safe. Two key tools you’ll want to use ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~333-~333: Korrigiere die Fehler
Context: ...nning well and ensuring your data stays safe. Two key tools you’ll want to use regul...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~339-~339: Korrigiere die Fehler
Context: ...ree up space, resolves allocation issues, and can fix "no space left on device" e...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~339-~339: Korrigiere die Fehler
Context: ...e up space, resolves allocation issues, and can fix "no space left on device" error...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~339-~339: Korrigiere die Fehler
Context: ... space, resolves allocation issues, and can fix "no space left on device" errors ev...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~339-~339: Hier könnte ein Fehler sein.
Context: ...ce, resolves allocation issues, and can fix "no space left on device" errors even when ...
(QB_NEW_DE)
[grammar] ~339-~339: Korrigiere die Fehler
Context: ...n issues, and can fix "no space left on device" errors even when space seems available....
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~339-~339: Korrigiere die Fehler
Context: ..., and can fix "no space left on device" errors even when space seems available. #### ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~339-~339: Korrigiere die Fehler
Context: ...an fix "no space left on device" errors even when space seems available. #### Wann ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~339-~339: Korrigiere die Fehler
Context: ...x "no space left on device" errors even when space seems available. #### Wann Balan...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~339-~339: Korrigiere die Fehler
Context: ... space left on device" errors even when space seems available. #### Wann Balance dur...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~339-~339: Korrigiere die Fehler
Context: ... left on device" errors even when space seems available. #### Wann Balance durchgefü...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~339-~339: Korrigiere die Fehler
Context: ...on device" errors even when space seems available. #### Wann Balance durchgeführt werden...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~343-~343: Passe das Symbol an
Context: ... durchgeführt werden sollte - Wenn Sie "Kein Speicherplatz mehr auf dem Gerät"-Fehle...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~343-~343: Ersetze das Satzzeichen
Context: ...nn Sie "Kein Speicherplatz mehr auf dem Gerät"-Fehler haben, aber noch freier Speicher...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_GERÄTQUOTEDASHFEHLER_GERÄTL_DOUBLE_QUOTDASHFEHLER)
[grammar] ~361-~361: Entferne ein Satzzeichen
Context: ...Die Scrub-Operation liest alle Daten- und Metadaten, überprüft die Integrität...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_PUNCTUATION_DATENDASH)
[grammar] ~361-~361: Ersetze das Satzzeichen
Context: ...e Datenbeschädigungen, auch bekannt als "Bit Rot", zu identifizieren und zu beheben,...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~361-~361: Ersetze das Satzzeichen
Context: ...enbeschädigungen, auch bekannt als "Bit Rot", zu identifizieren und zu beheben, bevo...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~366-~366: Entferne ein Wort
Context: ...n above). - Wählen Sie die Festplatte aus: Gehen Sie zum Main Tab und klicken ...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_NOUN)
[grammar] ~366-~366: Entferne ein Leerzeichen
Context: ...Festplatte aus**: Gehen Sie zum Main Tab und klicken Sie auf die Festplatte, ...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~367-~367: Entferne ein Wort
Context: ...Sie reparieren möchten. - Zugriff auf Reparaturoptionen: Blättern Sie zu **Dateisystemstatus übe...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_NOUN)
[grammar] ~371-~371: Entferne ein Leerzeichen
Context: ...prüfen**. #### Empfohlener Zeitplan - Hoch genutzte Pools: Einmal pro Woche - Alle ande...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`
around lines 333 - 391, The BTRFS Actions section contains English text that
needs full German translation: translate the intro paragraph starting
"Maintaining your %%BTRFS|btrfs%% pools...", the "Balance" description and its
bullets under "Wann Balance durchgeführt werden sollte" and "Reparatur eines
Dateisystems", the "Scrub" bullets under "Über das WebGUI", "Empfohlener
Zeitplan", "Wie man Scrub durchführt", and the final English sentence linking to
BTRFS docs; keep the existing German headings/notes/tips and tokens (e.g.,
%%BTRFS|btrfs%%, %%WebGUI|web-gui%%, "Gleichgewicht", "Balance", "Scrub")
unchanged while replacing only the English sentences and bullets with accurate
German translations that match the tone and formatting of surrounding content.
| Unassigned drives are storage devices connected to your Unraid server that aren't part of the main %%array|array%% or any %%cache pool|cache-pool%%. You can use these drives to transfer files, create backups, or provide fast storage for %%virtual machines|vm%%. | ||
|
|
||
| :::note |
There was a problem hiding this comment.
Unassigned drives intro paragraph is still English.
Translate this paragraph to German.
🧰 Tools
🪛 LanguageTool
[grammar] ~397-~397: Korrigiere die Fehler
Context: ...s are storage devices connected to your Unraid server that aren't part of the main %%a...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Korrigiere die Fehler
Context: ...torage devices connected to your Unraid server that aren't part of the main %%array|ar...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Korrigiere die Fehler
Context: ...devices connected to your Unraid server that aren't part of the main %%array|array%%...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Korrigiere die Fehler
Context: ...es connected to your Unraid server that aren't part of the main %%array|array%% or any...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Korrigiere die Fehler
Context: ...ected to your Unraid server that aren't part of the main %%array|array%% or any %%ca...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Korrigiere die Fehler
Context: ... to your Unraid server that aren't part of the main %%array|array%% or any %%cache pool|cach...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Korrigiere die Fehler
Context: ...aren't part of the main %%array|array%% or any %%cache pool|cache-pool%%. You can ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Korrigiere die Fehler
Context: ...n't part of the main %%array|array%% or any %%cache pool|cache-pool%%. You can use ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Hier könnte ein Fehler sein.
Context: ...%array|array%% or any %%cache pool|cache-pool%%. You can use these drives to transfer f...
(QB_NEW_DE)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`
around lines 397 - 399, The introductory paragraph "Unassigned drives are
storage devices connected to your Unraid server..." is still in English; replace
it with a German translation while preserving the special tokens
%%array|array%%, %%cache pool|cache-pool%% and %%virtual machines|vm%% exactly
as-is. Update the text in the same location so it reads in German (e.g., "Nicht
zugewiesene Laufwerke sind Speichermedien...") and ensure the surrounding note
block :::note remains unchanged.
| :::important | ||
|
|
||
| Do not format an unmountable drive unless you are okay with losing all the data on it. Formatting will erase everything and update the %%parity|parity%% information, making recovery impossible. Always try to fix the file system first. | ||
|
|
There was a problem hiding this comment.
Translate the “Do not format…” warning.
This warning is still English in the German troubleshooting section.
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`
around lines 441 - 444, Replace the English warning text inside the :::important
block that begins "Do not format an unmountable drive..." with a German
translation, keeping the admonition markup unchanged and preserving the
placeholder token %%parity|parity%% exactly as-is; for example use: "Formatieren
Sie ein nicht einhängbares Laufwerk nicht, wenn Sie nicht bereit sind, alle
darauf befindlichen Daten zu verlieren. Das Formatieren löscht alles und
aktualisiert die %%parity|parity%%-Informationen, wodurch eine Wiederherstellung
unmöglich wird. Versuchen Sie immer zuerst, das Dateisystem zu reparieren."
...saurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 12
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 (8)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx (1)
113-131:⚠️ Potential issue | 🟡 MinorDuplicate section structure: "Wartungserwartungen" appears twice with identical content.
The document has a confusing structure:
- Line 113:
## Wartungserwartungenwith intro paragraph at lines 115-116- Line 128:
### Wartungserwartungen(subsection with same name) with identical paragraph at lines 130-131This creates redundancy and structural confusion. Consider:
- Renaming the subsection at line 128 to something more specific (e.g., "### Laufende Pflichten" or "### Pflege nach Veröffentlichung")
- Removing the duplicate paragraph at lines 130-131
📝 Proposed fix
## Wartungserwartungen Entwickler, die Anwendungen in Community Applications veröffentlichen, werden erwartet, dass sie ihre Projekte pflegen, um die Kompatibilität und Zuverlässigkeit für die Unraid-Community sicherzustellen. Dieser Abschnitt umreißt die laufenden Verantwortlichkeiten, die zur Aufrechterhaltung der Qualität der verfügbaren Anwendungen beitragen. ### Einreichungsvoraussetzungen ... -### Wartungserwartungen - -Entwickler, die Anwendungen in Community Applications veröffentlichen, werden erwartet, dass sie ihre Projekte pflegen, um die Kompatibilität und Zuverlässigkeit für die Unraid-Community sicherzustellen. Dieser Abschnitt umreißt die laufenden Verantwortlichkeiten, die zur Aufrechterhaltung der Qualität der verfügbaren Anwendungen beitragen. +### Laufende Pflichten Einmal veröffentlicht, werden Entwickler erwartet:i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx (1)
395-431:⚠️ Potential issue | 🟠 MajorDuplicate section heading: "## Fehlerbehebung" appears twice.
There are two
## Fehlerbehebung(Troubleshooting) sections—one at line 395 and another at line 431. This creates confusing document structure and navigation issues. The content between lines 397–427 (about unassigned drives and plugins) appears to be misplaced or leftover from a restructuring.Consider consolidating these sections or renaming one to reflect its actual content (e.g., "### Nicht zugewiesene Geräte" for the unassigned devices content).
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (5)
33-33:⚠️ Potential issue | 🟠 MajorUntranslated English text.
This paragraph is in English and should be translated to Spanish for consistency with the rest of the document.
211-211:⚠️ Potential issue | 🟠 MajorUntranslated English text.
This sentence is in English and should be translated to Spanish.
222-241:⚠️ Potential issue | 🟠 MajorMisplaced content in "Compression and RAM" section.
Lines 224 and 239-240 contain content about importing ZFS pools and disk assignment, which belongs in the "Importando grupos ZFS" section (line 263), not in "Compresión y RAM". Additionally, this same paragraph is duplicated at line 321.
The section should focus on compression and RAM/ARC topics. Consider removing lines 224 and 237-241, or moving them to the appropriate import section.
327-327:⚠️ Potential issue | 🟠 MajorUntranslated English text in table.
The "Resultado" column contains English text that should be translated to Spanish.
378-378:⚠️ Potential issue | 🟠 MajorUntranslated English text.
This bullet point contains English text that should be translated to Spanish.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (1)
244-271:⚠️ Potential issue | 🔴 CriticalSection content mismatch - incorrect content under "Mindestfreier Speicherplatz" header.
Lines 244-271 have structural problems:
- The header at line 244 says "Mindestfreier Speicherplatz für einen Cache-Pool" but contains disk replacement text (line 246)
- Steps 258-264 describe data protection and workload isolation, not minimum free space settings
- Line 274 has a duplicate of the same section header
This appears to be content from multiple sections incorrectly merged. The actual minimum free space content begins at line 274.
🐛 Suggested approach
Consider either:
- Rename the header at line 244 to match its actual content (e.g., "Ersetzen einer Festplatte im Pool")
- Or remove lines 244-271 entirely if they duplicate content found elsewhere
🤖 Fix all issues with AI agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`:
- Around line 45-48: Translate the remaining English passages in this German
document: replace the English note block about the hybrid "ZFS-in-array"
approach (the paragraph shown in the diff) with a correct German translation,
and also translate the other English snippets referenced at lines 108–109, 127,
135, 224, 239 and 321; while doing so, detect the repeated "Import" paragraph
present at the locations around lines 224 and 239, translate it once into German
and remove the duplicate to avoid repetition. Ensure translations preserve the
existing inline tokens (%%ZFS|zfs%%, %%array|array%%) and technical wording, and
update both occurrences or remove one so only a single translated import
paragraph remains.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`:
- Around line 280-285: The two duplicated sentences about pool-to-pool transfers
("Unraid erlaubt keinen direkten Dateitransfer zwischen Pools..." and "Wenn
einer der Dateien zu einem Docker-Container und/oder %%VM|vm%% gehört...") are
misplaced under the "Mindestfreier Speicherplatz" section; remove these
sentences from this location so they only remain in the later section that
actually covers moving files between pools (the lines that begin the mover/CLI
discussion). Ensure you delete both occurrences in the current block to avoid
redundancy.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`:
- Around line 418-425: The list items beginning with "Einfaches Mounten und
Unmounten von Laufwerken..." and the subsequent bullets are orphaned after a
closing ":::” block; move those bullets back inside the appropriate note/tip
block (the preceding ":::") or under the correct heading so they are nested
properly, ensure there is a blank line before and after the block delimiter and
that each list item retains the "-" prefix, and remove the stray closing ":::”
only if duplicative so the content is correctly contained and renders as an
intended list.
- Line 443: Translate the three untranslated English sentences into German and
replace the English text in the MDX so the localization is consistent,
preserving all Docusaurus inline tokens (e.g., keep %%parity|parity%%,
%%ZFS|zfs%%, %%scrub|scrub%%, %%array|array%% intact) and formatting
(bold/Normal mode markers). Specifically update the sentence currently at the
text containing "Do not format an unmountable drive..." to a German equivalent,
the line with "For %%ZFS|zfs%%: Use **Normal mode** and run a
%%scrub|scrub%%..." to German while keeping **Normal mode** and the %% tokens,
and the line "Stop and restart the %%array|array%% in **Normal mode**." to
German likewise; ensure punctuation and markdown emphasis are preserved.
- Around line 289-293: Several English sentences in the cache drive reformatting
section remain untranslated; replace the English strings with German
translations while preserving the placeholder tokens (e.g., %%cache|cache%%,
%%array|array%%, %%XFS|xfs%%, EXT4) and formatting (bold/italic). Specifically
translate the sentences starting with "For each share with files in the
%%cache|cache%%, set **Primary storage**...", "For a single-drive
%%cache|cache%%, %%XFS|xfs%% or EXT4 are recommended.", "Note that %%XFS|xfs%%
and EXT4 are only available with one %%cache|cache%% slot.", "Confirm only the
%%cache|cache%% drive is listed as unmountable.", and "For each share you
changed, set **Primary storage**..." to German, keeping the same markup and
tokens so references like %%cache|cache%%, %%array|array%%, %%XFS|xfs%%, and the
bold **Primary storage**/**Secondary storage** remain intact.
- Line 397: Translate the English paragraph that starts "Unassigned drives are
storage devices connected to your Unraid server that aren't part of the main
%%array|array%% or any %%cache pool|cache-pool%%..." into German, preserving the
placeholder tokens exactly (%%array|array%%, %%cache pool|cache-pool%%,
%%virtual machines|vm%%) and the intended meaning about using unassigned drives
for transfers, backups, or fast VM storage; update the paragraph text
accordingly in the same location.
- Line 153: Replace the English sentence "**Run %%Mover|mover%%**: Run
%%Mover|mover%% from the **Main** tab. Wait for it to finish and ensure that the
%%cache|cache%% is empty." with a German translation, preserving the
placeholders and bold formatting (%%Mover|mover%% and %%cache|cache%% and
**Main**); for example: "Führen Sie %%Mover|mover%% aus: Führen Sie
%%Mover|mover%% auf der Registerkarte **Main** aus. Warten Sie, bis der Vorgang
abgeschlossen ist, und stellen Sie sicher, dass der %%cache|cache%% leer ist."
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`:
- Around line 45-49: The note block contains untranslated English lines
describing the hybrid %%ZFS|zfs%%-in-array approach; replace that English text
with a Spanish translation, preserving the special tokens (%%ZFS|zfs%% and
%%array|array%%) and the MDX note block markers (:::note ... :::); update the
two lines so the meaning remains the same but fully in Spanish, ensuring tokens
and punctuation are unchanged.
- Around line 303-309: The support vdev table rows (entries "Vdev especial",
"Vdev de deduplicación", "Vdev de log (SLOG)", "Vdev de cache (L2ARC)") contain
incorrect descriptions copied from the use-cases table; replace each cell in the
"Descripción" column with the correct purpose: for "Vdev especial" say it stores
metadata/small blocks to improve metadata I/O performance, for "Vdev de
deduplicación" say it stores deduplication tables (DEDUP metadata), for "Vdev de
log (SLOG)" say it is a synchronous write intent log to accelerate sync writes,
and for "Vdev de cache (L2ARC)" say it is a read cache for frequently accessed
data; leave the "Detalles / Ejemplos" column adjusted if needed to match these
corrected descriptions.
- Around line 106-110: The tip block starting with ":::tip" that contains the
text "Para añadir un disco %%ZFS|zfs%% al %%array|array%%:" is misplaced and
incomplete within the "Creating a ZFS pool" content; either remove this empty
tip or relocate its full content into the dedicated "Agregar un disco ZFS al
array" section and replace it with a contextual tip relevant to allocation
profile choice. Locate the tip by searching for the literal markup ":::tip" and
the string "Para añadir un disco %%ZFS|zfs%% al %%array|array%%:" and then
either delete the block or move and expand it into the "Agregar un disco ZFS al
array" section (or add the missing explanatory lines) so the tip is complete and
placed with the related content.
- Around line 331-335: Translate the English sentences inside the :::tip block
(the lines containing "Always assign every physical drive from your original
%%ZFS|zfs%% pool, including all support vdevs, when importing into Unraid. This
ensures smooth detection and integration. For new pools created in Unraid,
support vdevs are optional and generally not needed for most users.") into
Spanish, keeping the surrounding :::tip ::: markers and the %%ZFS|zfs%% token
unchanged and preserving punctuation and meaning.
- Around line 41-43: The image reference in the MDX uses an incorrect absolute
path '/img/zfs1.png' causing a broken image; update the src to the relative path
'./assets/zfs1.png' in the MDX where the img is referenced (replace
'/img/zfs1.png' with './assets/zfs1.png') or alternatively move the file into
the static img folder so the existing '/img/zfs1.png' path resolves; adjust only
the img src in the MDX (the surrounding div can remain unchanged).
🟡 Minor comments (13)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx-204-204 (1)
204-204:⚠️ Potential issue | 🟡 MinorEnglischer Satz am Abschnittsende.
Line 204 ist noch Englisch; bitte übersetzen.
💡 Vorschlag
-This procedure works for both data drives and %%parity drives|parity-drives%% that have been disabled. +Dieses Verfahren funktioniert sowohl für Datenlaufwerke als auch für deaktivierte %%parity drives|parity-drives%%.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md-106-106 (1)
106-106:⚠️ Potential issue | 🟡 MinorUse the German compound with hyphens (“Windows‑11‑VM”).
This reads more naturally and matches standard German compound styling.
✍️ Suggested wording
-- Korrektur: Standardwerte für Windows 11 VM ändern. +- Korrektur: Standardwerte für Windows‑11‑VM ändern.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md-81-81 (1)
81-81:⚠️ Potential issue | 🟡 MinorReplace “=” and mixed-language “Array-Disk” for clearer German.
The phrase reads like a key/value and mixes English; rephrase for readability.
✍️ Suggested wording
-- Korrektur: Windows kann keinen neuen Ordner für einen Share mit primärem=ZFS-Pool und sekundärem=EXT4-Array-Disk erstellen. +- Korrektur: Windows kann keinen neuen Ordner für einen Share mit primärem ZFS‑Pool und sekundärem EXT4‑Array‑Laufwerk erstellen.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx-87-93 (1)
87-93:⚠️ Potential issue | 🟡 MinorRedundant tip block duplicates the Action Center section below.
The content in this tip block (lines 89-93) is nearly identical to the "Aktualisierungen von Anwendungen (Aktionscenter)" section at lines 100-109, which provides more complete information. Additionally, the tip title "Support Präferenzen" doesn't accurately describe the Action Center content within.
Consider either:
- Removing this tip block entirely since it duplicates the section below, or
- Keeping only a brief cross-reference like: "Siehe Aktualisierungen von Anwendungen für Details zum Action Center."
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx-472-472 (1)
472-472:⚠️ Potential issue | 🟡 MinorMixed English/German in admonition title: "Just Um".
Line 472 has
:::note[Just Um es noch einmal zu sagen]which mixes English "Just" with German. Use a fully German title.Suggested fix
-:::note[Just Um es noch einmal zu sagen] +:::note[Zur Erinnerung]i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx-87-87 (1)
87-87:⚠️ Potential issue | 🟡 MinorMixed English/German in admonition title.
:::note[Additional Anmerkungen]mixes English "Additional" with German "Anmerkungen". For consistency, use a fully German title such as:::note[Zusätzliche Anmerkungen].Suggested fix
-:::note[Additional Anmerkungen] +:::note[Zusätzliche Anmerkungen]i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx-519-519 (1)
519-519:⚠️ Potential issue | 🟡 Minor"Steps" should be translated to "Schritte".
Line 519 uses the English word "Steps" in
(siehe Steps oben). Use the German equivalent.Suggested fix
-1. Starten Sie das %%array|array%% im richtigen Modus (siehe Steps oben). +1. Starten Sie das %%array|array%% im richtigen Modus (siehe Schritte oben).i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx-461-461 (1)
461-461:⚠️ Potential issue | 🟡 MinorMixed English/German in admonition title: "Why Ist".
Line 461 has
:::important[Why Ist Parität nicht genug?]which awkwardly mixes English "Why" with German. Use a fully German title.Suggested fix
-:::important[Why Ist Parität nicht genug?] +:::important[Warum reicht Parität nicht aus?]i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx-351-354 (1)
351-354:⚠️ Potential issue | 🟡 MinorMixed language admonition label.
The label
Planning adelantemixes English and Spanish. Should bePlanificando con anticipaciónorPlanificando a futuro.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx-129-136 (1)
129-136:⚠️ Potential issue | 🟡 MinorMixed language admonition label.
The label
What esto habilitamixes English and Spanish. Should be fully Spanish, e.g.,Qué habilita estoorLo que esto habilita.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx-191-196 (1)
191-196:⚠️ Potential issue | 🟡 MinorMixed language admonition label.
The label
How elegirmixes English and Spanish. Should beCómo elegir.Also, line 194 has a typo:
escritashould beescritura(noun form).i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx-11-17 (1)
11-17:⚠️ Potential issue | 🟡 MinorMixed language admonition label and duplicate content.
The admonition label
Special graciasmixes English and Spanish. Consider usingAgradecimientos especialesor similar fully Spanish label.The paragraph on lines 13-14 is duplicated verbatim on line 17. Remove one instance to avoid redundancy.
Proposed fix
-:::important[Special gracias] +:::important[Agradecimientos especiales] %%ZFS|zfs%% aporta integridad de datos avanzada, configuraciones de almacenamiento flexibles y alto rendimiento a tu sistema Unraid. Esta guía explica los conceptos básicos de %%ZFS|zfs%% y te guía en la gestión de pools %%ZFS|zfs%% directamente desde el %%WebGUI|web-gui%% de Unraid. Ya sea que estés configurando un nuevo almacenamiento %%ZFS|zfs%% o integrando un pool existente, encontrarás los pasos y contexto que necesitas para comenzar con confianza. ::: - -%%ZFS|zfs%% aporta integridad de datos avanzada, configuraciones de almacenamiento flexibles y alto rendimiento a tu sistema Unraid. Esta guía explica los conceptos básicos de %%ZFS|zfs%% y te guía en la gestión de pools %%ZFS|zfs%% directamente desde el %%WebGUI|web-gui%% de Unraid. Ya sea que estés configurando un nuevo almacenamiento %%ZFS|zfs%% o integrando un pool existente, encontrarás los pasos y contexto que necesitas para comenzar con confianza.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx-11-14 (1)
11-14:⚠️ Potential issue | 🟡 MinorRemove duplicated intro paragraph inside the callout.
The paragraph on Line 13–14 repeats the standalone intro on Line 17, so readers see the same text twice. Keep one copy (either inside the callout or as the main intro).
| :::note | ||
|
|
||
| The hybrid %%ZFS|zfs%%-in-array approach is helpful for specific backup or replication scenarios but is not a replacement for a full %%ZFS|zfs%% pool. %%ZFS|zfs%% disks in the %%array|array%% are managed individually; you do not get the combined performance, redundancy, or self-healing of a true multi-disk %%ZFS|zfs%% pool. For full %%ZFS|zfs%% functionality, always use dedicated %%ZFS|zfs%% pools. | ||
|
|
There was a problem hiding this comment.
Translate remaining English passages in this German doc.
Lines 45–48, 108–109, 127, 135, 224, 239, and 321 are still English, which breaks localization consistency. Please translate them (and consider deduplicating the repeated import paragraph at Line 224 and Line 239 once translated).
Also applies to: 108-109, 127-127, 135-135, 224-224, 239-239, 321-321
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`
around lines 45 - 48, Translate the remaining English passages in this German
document: replace the English note block about the hybrid "ZFS-in-array"
approach (the paragraph shown in the diff) with a correct German translation,
and also translate the other English snippets referenced at lines 108–109, 127,
135, 224, 239 and 321; while doing so, detect the repeated "Import" paragraph
present at the locations around lines 224 and 239, translate it once into German
and remove the duplicate to avoid repetition. Ensure translations preserve the
existing inline tokens (%%ZFS|zfs%%, %%array|array%%) and technical wording, and
update both occurrences or remove one so only a single translated import
paragraph remains.
| Unraid erlaubt keinen direkten Dateitransfer zwischen Pools über das %%WebGUI|web-gui%%, aber Sie können es mit dem %%Mover|mover%%-Werkzeug oder über die Befehlszeile tun. | ||
|
|
||
| ::: | ||
|
|
||
| Sie können den Minimumfreier Speicherplatz aufrufen, indem Sie auf den Poolnamen in der Registerkarte **Main** klicken und zu den **Individuellen Pooleinstellungen** gehen. | ||
| Wenn einer der Dateien zu einem Docker-Container und/oder %%VM|vm%% gehört, müssen die Dienste deaktiviert sein, damit die Dateien erfolgreich verschoben werden können. | ||
|
|
There was a problem hiding this comment.
Duplicate content from later sections.
Lines 280-281 and 284-285 contain text that also appears at lines 385 and 389 respectively:
- "Unraid erlaubt keinen direkten Dateitransfer zwischen Pools..."
- "Wenn einer der Dateien zu einem Docker-Container..."
This content appears to be misplaced here under the "Mindestfreier Speicherplatz" section, as it relates to moving files between pools (covered later in lines 383-391).
🐛 Proposed fix - remove misplaced content
:::tip\[Example]
-Unraid erlaubt keinen direkten Dateitransfer zwischen Pools über das %%WebGUI|web-gui%%, aber Sie können es mit dem %%Mover|mover%%-Werkzeug oder über die Befehlszeile tun.
+Wenn Sie häufig Dateien um die 10 GB herunterladen, legen Sie den Mindestfreien Speicherplatz auf mindestens 10 GB fest, idealerweise 20 GB, um Anpassungen zu ermöglichen.
:::
-Wenn einer der Dateien zu einem Docker-Container und/oder %%VM|vm%% gehört, müssen die Dienste deaktiviert sein, damit die Dateien erfolgreich verschoben werden können.
-
<h4>Wie es funktioniert</h4>📝 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.
| Unraid erlaubt keinen direkten Dateitransfer zwischen Pools über das %%WebGUI|web-gui%%, aber Sie können es mit dem %%Mover|mover%%-Werkzeug oder über die Befehlszeile tun. | |
| ::: | |
| Sie können den Minimumfreier Speicherplatz aufrufen, indem Sie auf den Poolnamen in der Registerkarte **Main** klicken und zu den **Individuellen Pooleinstellungen** gehen. | |
| Wenn einer der Dateien zu einem Docker-Container und/oder %%VM|vm%% gehört, müssen die Dienste deaktiviert sein, damit die Dateien erfolgreich verschoben werden können. | |
| :::tip[Example] | |
| Wenn Sie häufig Dateien um die 10 GB herunterladen, legen Sie den Mindestfreien Speicherplatz auf mindestens 10 GB fest, idealerweise 20 GB, um Anpassungen zu ermöglichen. | |
| ::: | |
| <h4>Wie es funktioniert</h4> |
🧰 Tools
🪛 LanguageTool
[grammar] ~284-~284: Ensure spelling is correct
Context: ...r über die Befehlszeile tun. ::: Wenn einer der Dateien zu einem Docker-Container u...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 280 - 285, The two duplicated sentences about pool-to-pool
transfers ("Unraid erlaubt keinen direkten Dateitransfer zwischen Pools..." and
"Wenn einer der Dateien zu einem Docker-Container und/oder %%VM|vm%% gehört...")
are misplaced under the "Mindestfreier Speicherplatz" section; remove these
sentences from this location so they only remain in the later section that
actually covers moving files between pools (the lines that begin the mover/CLI
discussion). Ensure you delete both occurrences in the current block to avoid
redundancy.
| Um Daten vom Cache zu verschieben: | ||
|
|
||
| 1. Starten Sie das %%array|array%%. | ||
| 2. **Run %%Mover|mover%%**: Run %%Mover|mover%% from the **Main** tab. Wait for it to finish and ensure that the %%cache|cache%% is empty. |
There was a problem hiding this comment.
Untranslated English instruction.
Line 153 contains **Run %%Mover|mover%%**: Run %%Mover|mover%% from the **Main** tab... in English within German documentation. Translate to German.
Suggested fix
-2. **Run %%Mover|mover%%**: Run %%Mover|mover%% from the **Main** tab. Wait for it to finish and ensure that the %%cache|cache%% is empty.
+2. **%%Mover|mover%% ausführen**: Führen Sie %%Mover|mover%% über den **Main**-Tab aus. Warten Sie, bis der Vorgang abgeschlossen ist, und stellen Sie sicher, dass der %%cache|cache%% leer ist.📝 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.
| 2. **Run %%Mover|mover%%**: Run %%Mover|mover%% from the **Main** tab. Wait for it to finish and ensure that the %%cache|cache%% is empty. | |
| 2. **%%Mover|mover%% ausführen**: Führen Sie %%Mover|mover%% über den **Main**-Tab aus. Warten Sie, bis der Vorgang abgeschlossen ist, und stellen Sie sicher, dass der %%cache|cache%% leer ist. |
🧰 Tools
🪛 LanguageTool
[grammar] ~153-~153: Entferne ein Wort
Context: ...arten Sie das %%array|array%%. 2. Run %%Mover|mover%%: Run %%Mover|mover%% from the Main t...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_NOUN)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`
at line 153, Replace the English sentence "**Run %%Mover|mover%%**: Run
%%Mover|mover%% from the **Main** tab. Wait for it to finish and ensure that the
%%cache|cache%% is empty." with a German translation, preserving the
placeholders and bold formatting (%%Mover|mover%% and %%cache|cache%% and
**Main**); for example: "Führen Sie %%Mover|mover%% aus: Führen Sie
%%Mover|mover%% auf der Registerkarte **Main** aus. Warten Sie, bis der Vorgang
abgeschlossen ist, und stellen Sie sicher, dass der %%cache|cache%% leer ist."
...saurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
Show resolved
Hide resolved
| ## Nicht zugewiesene Laufwerke | ||
| ## Fehlerbehebung | ||
|
|
||
| Unassigned drives are storage devices connected to your Unraid server that aren't part of the main %%array|array%% or any %%cache pool|cache-pool%%. You can use these drives to transfer files, create backups, or provide fast storage for %%virtual machines|vm%%. |
There was a problem hiding this comment.
Untranslated English paragraph about unassigned drives.
Line 397 contains an English paragraph: Unassigned drives are storage devices connected to your Unraid server that aren't part of the main %%array|array%%... This should be translated to German.
🧰 Tools
🪛 LanguageTool
[grammar] ~397-~397: Korrigiere die Fehler
Context: ...s are storage devices connected to your Unraid server that aren't part of the main %%a...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Korrigiere die Fehler
Context: ...torage devices connected to your Unraid server that aren't part of the main %%array|ar...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Korrigiere die Fehler
Context: ...devices connected to your Unraid server that aren't part of the main %%array|array%%...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Korrigiere die Fehler
Context: ...es connected to your Unraid server that aren't part of the main %%array|array%% or any...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Korrigiere die Fehler
Context: ...ected to your Unraid server that aren't part of the main %%array|array%% or any %%ca...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Korrigiere die Fehler
Context: ... to your Unraid server that aren't part of the main %%array|array%% or any %%cache pool|cach...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Korrigiere die Fehler
Context: ...aren't part of the main %%array|array%% or any %%cache pool|cache-pool%%. You can ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Korrigiere die Fehler
Context: ...n't part of the main %%array|array%% or any %%cache pool|cache-pool%%. You can use ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~397-~397: Hier könnte ein Fehler sein.
Context: ...%array|array%% or any %%cache pool|cache-pool%%. You can use these drives to transfer f...
(QB_NEW_DE)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`
at line 397, Translate the English paragraph that starts "Unassigned drives are
storage devices connected to your Unraid server that aren't part of the main
%%array|array%% or any %%cache pool|cache-pool%%..." into German, preserving the
placeholder tokens exactly (%%array|array%%, %%cache pool|cache-pool%%,
%%virtual machines|vm%%) and the intended meaning about using unassigned drives
for transfers, backups, or fast VM storage; update the paragraph text
accordingly in the same location.
...ugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
Show resolved
Hide resolved
...ugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
Show resolved
Hide resolved
| :::tip | ||
| Antes de finalizar, revise las secciones sobre perfiles de asignación y topología para tomar una decisión informada. | ||
|
|
||
| Para añadir un disco %%ZFS|zfs%% al %%array|array%%: | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Tip content appears misplaced or incomplete.
This tip says "Para añadir un disco %%ZFS|zfs%% al %%array|array%%:" but it's located within the "Creating a ZFS pool" section (step 8 about choosing allocation profile). This topic is covered separately in the "Agregar un disco ZFS al array" section starting at line 125. The tip appears to be either misplaced or missing its actual content.
🤖 Prompt for AI Agents
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`
around lines 106 - 110, The tip block starting with ":::tip" that contains the
text "Para añadir un disco %%ZFS|zfs%% al %%array|array%%:" is misplaced and
incomplete within the "Creating a ZFS pool" content; either remove this empty
tip or relocate its full content into the dedicated "Agregar un disco ZFS al
array" section and replace it with a contextual tip relevant to allocation
profile choice. Locate the tip by searching for the literal markup ":::tip" and
the string "Para añadir un disco %%ZFS|zfs%% al %%array|array%%:" and then
either delete the block or move and expand it into the "Agregar un disco ZFS al
array" section (or add the missing explanatory lines) so the tip is complete and
placed with the related content.
| | Vdev de soporte (subpool) | Descripción | Detalles / Ejemplos | | ||
| | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------- | | ||
| | Vdev especial | Almacena la parte de appdata para contenedores y bases de datos rápidos y receptivos. Esto admite %%snapshot\|snapshot%%s para retrocesos fáciles y también puede alojar %%VM\|vm%%s para I/O alto. | Muchos usuarios eligen un espejo %%ZFS\|zfs%% de 2 discos para esto. Es fácil de expandir y ofrece un rendimiento sólido. | | ||
| | Vdev de deduplicación | Utiliza un espejo %%ZFS\|zfs%% o un pool RAIDZ2 para archivos insustituibles como fotos, registros fiscales y datos de %%user share\|user-share%%. %%ZFS\|zfs%% verifica la corrupción y se autocorrige con redundancia. | Esta configuración protege datos críticos con comprobaciones de integridad automáticas y capacidades de auto-saneamiento. | | ||
| | Vdev de log (SLOG) | Usa un disco %%ZFS\|zfs%% (incluso dentro del %%array\|array%% de Unraid) como objetivo de replicación. Puedes replicar otros pools localmente o desde otro servidor Unraid. | Utiliza `zfs send/receive` o herramientas como Syncoid para respaldos y restauraciones rápidas y confiables. | | ||
| | Vdev de cache (L2ARC) | Mantén %%snapshot\|snapshot%%s de punto en el tiempo de datos o contenedores críticos. Los %%snapshot\|snapshot%%s se pueden programar automáticamente y son eficientes en espacio. | Esta función permite una rápida recuperación de eliminaciones accidentales o errores de configuración. | | ||
| | Vdev de repuesto | No soportado en Unraid (a partir de la versión 7.1.2) | | |
There was a problem hiding this comment.
Support vdev table has incorrect descriptions.
The descriptions in this table appear to be incorrectly copied from the "use cases" table (lines 363-368) rather than describing actual support vdev functionality:
| Vdev Type | Current Description | Should Describe |
|---|---|---|
| Vdev especial | appdata for containers | Storing metadata/small blocks for performance |
| Vdev de deduplicación | mirrors for photos | Storing deduplication tables |
| Vdev de log (SLOG) | replication target | Synchronous write intent log |
| Vdev de cache (L2ARC) | snapshots | Read cache for frequently accessed data |
This content mismatch could confuse users about the purpose of each support vdev type.
🧰 Tools
🪛 LanguageTool
[grammar] ~305-~305: Aquí puede haber un error.
Context: ...pandir y ofrece un rendimiento sólido. | | Vdev de deduplicación | Utiliza un ...
(QB_NEW_ES)
[grammar] ~306-~306: Elimina la palabra o signo.
Context: ...ento sólido. | | Vdev de deduplicación | Utiliza un espejo %%ZFS|zfs%% o un p...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_SPACE)
[grammar] ~306-~306: Elimina la puntuación
Context: ...integridad automáticas y capacidades de auto-saneamiento. | | Vdev de log (SLOG) | Usa un...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_PUNCTUATION)
[grammar] ~306-~306: Aquí puede haber un error.
Context: ...cas y capacidades de auto-saneamiento. | | Vdev de log (SLOG) | Usa un disc...
(QB_NEW_ES)
[grammar] ~307-~307: Aquí puede haber un error.
Context: ...nes rápidas y confiables. | | Vdev de cache (L2ARC) | Mantén %%sn...
(QB_NEW_ES)
🤖 Prompt for AI Agents
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`
around lines 303 - 309, The support vdev table rows (entries "Vdev especial",
"Vdev de deduplicación", "Vdev de log (SLOG)", "Vdev de cache (L2ARC)") contain
incorrect descriptions copied from the use-cases table; replace each cell in the
"Descripción" column with the correct purpose: for "Vdev especial" say it stores
metadata/small blocks to improve metadata I/O performance, for "Vdev de
deduplicación" say it stores deduplication tables (DEDUP metadata), for "Vdev de
log (SLOG)" say it is a synchronous write intent log to accelerate sync writes,
and for "Vdev de cache (L2ARC)" say it is a read cache for frequently accessed
data; leave the "Detalles / Ejemplos" column adjusted if needed to match these
corrected descriptions.
| :::tip | ||
|
|
||
| Always assign every physical drive from your original %%ZFS|zfs%% pool, including all support vdevs, when importing into Unraid. This ensures smooth detection and integration. For new pools created in Unraid, support vdevs are optional and generally not needed for most users. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Untranslated English text in tip.
Lines 333-334 contain English text that should be translated to Spanish.
🤖 Prompt for AI Agents
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`
around lines 331 - 335, Translate the English sentences inside the :::tip block
(the lines containing "Always assign every physical drive from your original
%%ZFS|zfs%% pool, including all support vdevs, when importing into Unraid. This
ensures smooth detection and integration. For new pools created in Unraid,
support vdevs are optional and generally not needed for most users.") into
Spanish, keeping the surrounding :::tip ::: markers and the %%ZFS|zfs%% token
unchanged and preserving punctuation and meaning.
There was a problem hiding this comment.
Actionable comments posted: 9
Note
Due to the large number of review comments, Critical 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 (55)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/monitor-performance/smart-reports-and-disk-health.mdx (1)
22-26:⚠️ Potential issue | 🟡 MinorRemove the duplicated introductory sentence.
The line is repeated back-to-back, which reads as a copy/paste slip in the rendered doc.
🔧 Suggested fix
Einige %%SMART|smart%% Attribute, die Unraid standardmäßig überwacht, umfassen: Für eine genauere Betrachtung der Daten eines Laufwerks von %%SMART|smart%%, klicken Sie auf dessen Namen im **Main**-Tab der Unraid %%WebGUI|web-gui%%. -Einige %%SMART|smart%% Attribute, die Unraid standardmäßig überwacht, umfassen: - | **ID** | **Attribut** | **Was es bedeutet** | **Wann man besorgt sein sollte / Maßnahmen, die zu ergreifen sind** |i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx (2)
40-57:⚠️ Potential issue | 🔴 CriticalDuplicate section headers and conflated content structure.
Lines 40 and 51 contain identical
<h4>headers ("What to do if you encounter %%parity|parity%% errors"). Additionally, the first section (lines 40-47) has a structural problem:
- Line 42 introduces the text as "This mismatch can arise from several issues, including:" (implying a list of causes)
- Lines 44-46 then list actions to take (investigate, seek help, run another check)
- Line 47 lists a cause (unclean shutdowns)
This appears to be a merge or translation error. The content at lines 40-47 should likely be restructured to list causes of parity errors, while lines 51-57 correctly handle "what to do" steps.
🔧 Suggested fix: Remove duplicate and restructure
-<h4>What to do if you encounter %%parity|parity%% errors</h4> +<h4>Ursachen von Paritätsfehlern</h4> %%Parity|parity%% errors happen when the %%parity|parity%% information your system calculates doesn't match what's stored on your %%parity drives|parity-drives%%. This mismatch can arise from several issues, including: -- **Untersuchen Sie das Problem:** Beginnen Sie mit dem Überprüfen der %%SMART-Berichte|SMART-Reports%%, die detaillierte Informationen über den Gesundheitszustand Ihrer Festplatten bieten. Achten Sie auf Hinweise auf Festplatten- oder Verbindungsprobleme. -- **Hilfe in unseren Foren suchen:** Wenn Sie das Problem nicht selbst lösen können, ziehen Sie in Betracht, Rat in den Unraid-Foren einzuholen. Die Community kann wertvolle Einblicke und Vorschläge basierend auf ihren Erfahrungen bieten. -- **Führen Sie eine weitere Prüfung durch:** Nachdem Sie Hardwareprobleme behoben haben, ist es eine gute Idee, eine weitere %%parity check|parity-check%% durchzuführen, um sicherzustellen, dass alles wieder in Ordnung ist. - Unsaubere Shutdowns oder unerwartete Systemabstürze +- Festplatten- oder Verbindungsprobleme +- Hardwareausfälle
1-14:⚠️ Potential issue | 🟠 MajorSignificant untranslated English content in German localization file.
This German translation file contains substantial English text that should be translated, including:
- Lines 1, 6-8, 13 (parity check explanations)
- Lines 19, 21 (valid parity disk details)
- Lines 24, 36-37 (important notices)
- Lines 40, 42, 49, 51, 61 (section content)
For consistency and user experience, these sections should be translated to German to match the already-translated portions (e.g., lines 10-11, 26, 30, 44-46, 53-57).
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx (1)
145-174:⚠️ Potential issue | 🟠 MajorDuplicate section headers and jumbled content.
There are two identical section headers "### VPN-Tunneling-Zugriff für das System konfigurieren" (lines 145 and 158). The content between them appears jumbled:
- Lines 149-156: Mix Firefox installation with VPN-Manager import steps and dnsleaktest.com
- Lines 162-167: Repeat Firefox installation with different steps (whatismyipaddress.com)
- Lines 176-180: A third "Testen des Systemtunnels" section repeats Firefox/whatismyipaddress steps again
This looks like a translation merge issue where content was duplicated or incorrectly combined. Please consolidate into a single coherent section with proper step ordering.
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (5)
33-48:⚠️ Potential issue | 🟡 MinorUntranslated English content in Spanish documentation.
Lines 33 and 47 contain English text that should be translated to Spanish:
- Line 33:
"Unraid supports %%ZFS|zfs%% for any storage pool..."- Line 47:
"The hybrid %%ZFS|zfs%%-in-array approach is helpful..."This breaks localization consistency for Spanish-speaking users.
236-252:⚠️ Potential issue | 🟠 MajorDuplicated and misplaced content in "Compresión y RAM" section.
Line 236 and lines 251-252 contain identical text about importing ZFS pools and disk assignment:
"Cuando importas un pool %%ZFS|zfs%% en Unraid, necesitas asignar cada disco..."
This content is duplicated and also appears misplaced—it discusses pool importing, not compression or RAM. This paragraph belongs in the "Importando grupos ZFS" section (around line 275), not here.
Consider removing line 236 and keeping the tip at 251-252, or removing both from this section since the content already appears correctly in line 333.
339-346:⚠️ Potential issue | 🟡 MinorUntranslated English text in table and tip.
Several lines contain English text that should be translated:
- Line 339:
"These vdevs store critical metadata or deduplication tables..."- Lines 345-346:
"Always assign every physical drive from your original %%ZFS|zfs%% pool..."These break localization consistency for Spanish-speaking users.
223-223:⚠️ Potential issue | 🟡 MinorUntranslated English sentence.
Line 223 contains an untranslated English sentence:
"%%ZFS|zfs%% stripes data across vdevs, not individual disks, so more vdevs can lead to better performance...". This should be translated to Spanish for consistency.
390-390:⚠️ Potential issue | 🟡 MinorUntranslated English sentence.
Line 390 contains an untranslated English sentence:
"A single %%ZFS|zfs%%-formatted disk in the Unraid %%array|array%% does not offer the redundancy...". This should be translated to Spanish for consistency.i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (1)
138-179:⚠️ Potential issue | 🟠 MajorDuplicate "Gestión de licencias" sections detected.
There are two "Gestión de licencias" (License Management) sections in this document:
- Lines 148-164: Contains Tabs component with banner/organize/theme options
- Lines 168-179: Contains bullet list with license management actions
This appears to be a merge or translation synchronization error. The first section (lines 138-164) seems to be mislabeled as "Personalización" should contain the customization content, while lines 148-150 introduce "Gestión de licencias" prematurely.
Please verify which content belongs to which section and remove the duplicate.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (4)
244-271:⚠️ Potential issue | 🔴 CriticalSection contains misplaced and corrupted content.
This "Mindestfreier Speicherplatz" section has serious structural issues:
- Line 246: Contains disk replacement text instead of minimum free space content
- Lines 258-265: Steps describe disk assignment and pool management, not minimum free space configuration
- Line 274: Duplicate section header appears immediately after
This appears to be a merge/translation error where disk replacement steps were mixed into the minimum free space section. The content from lines 244-271 should be reviewed and corrected to match the intended topic or removed if duplicated.
276-293:⚠️ Potential issue | 🟠 MajorMultiple untranslated English paragraphs in minimum free space section.
Lines 276, 278-282, and 290-293 remain in English within a German localization file. These should be translated for consistency.
Example lines needing translation:
- Line 276: "Setting a minimum free space for your %%cache pool|cache-pool%%..."
- Line 290: "If your share uses a %%cache pool|cache-pool%% as Primary storage..."
21-27:⚠️ Potential issue | 🟠 MajorUntranslated English content in benefits list.
Lines 21, 23, 25, and 27 list cache pool benefits in English. For consistency with the German heading and introduction, these should be translated.
248-254:⚠️ Potential issue | 🟠 MajorPrerequisites note contains untranslated content.
Lines 248-253 have mixed English/German content. The note header and line 250 should be translated to German.
♻️ Proposed fix
-:::note\[Prerequisites] +:::note[Voraussetzungen] -- **Check your pool configuration:** Make sure your pool is set up with a redundant %%RAID|raid%% profile, like %%RAID 1|raid1%%. You can do this by going to ***Main → Pool → Balance Status*** (for %%BTRFS|btrfs%%) or ZFS pool status (for %%ZFS|zfs%%) in your management interface. +- **Überprüfen Sie Ihre Pool-Konfiguration:** Stellen Sie sicher, dass Ihr Pool mit einem redundanten %%RAID|raid%%-Profil wie %%RAID 1|raid1%% eingerichtet ist. Sie können dies unter ***Main → Pool → Balance Status*** (für %%BTRFS|btrfs%%) oder ZFS-Pool-Status (für %%ZFS|zfs%%) in Ihrer Verwaltungsoberfläche überprüfen. - **Die richtige Ersatzfestplatte wählen:** Die neue Festplatte muss gleich groß oder größer als die zu ersetzende sein.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (3)
33-48:⚠️ Potential issue | 🟠 MajorUntranslated English content in German localization file.
Lines 33–38 and 46–48 contain English text that should be translated to German for consistency with the rest of the document:
- Line 33:
Unraid supports %%ZFS|zfs%% for any storage pool...- Lines 35-38: The entire
:::info[Example]block- Lines 46-48: The
:::notecontent about hybrid ZFS-in-array approach
236-252:⚠️ Potential issue | 🟠 MajorDuplicate English content that needs translation.
Lines 236 and 251 contain identical untranslated English text:
When you import a %%ZFS|zfs%% pool into Unraid, you need to assign every drive from your original pool...This appears to be duplicated content. Additionally, this paragraph about importing pools seems out of place in the "Kompression und RAM" (Compression and RAM) section.
Consider:
- Translating this content to German
- Removing the duplicate
- Moving it to the appropriate section (likely "Importieren von auf anderen Systemen erstellten ZFS-Pools")
333-341:⚠️ Potential issue | 🟠 MajorTriple-duplicated English content and mixed-language table.
Line 333 contains the same English paragraph that also appears at lines 236 and 251. This text appears three times in the document and should be:
- Translated to German
- Consolidated to appear only once in the appropriate location
The table at lines 337-341 also contains mixed English/German:
- Line 339: English description for Spezial-vdev/Dedup vdev
- Lines 340-341: German descriptions
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx (1)
269-317:⚠️ Potential issue | 🟠 MajorTranslate the remaining English instructions in the cache reformat workflow.
Lines 269, 289, 303–305, 307, and 316 are English within German steps. Please localize these lines for consistency.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx (6)
28-28:⚠️ Potential issue | 🟡 MinorUntranslated English content.
This paragraph describing CPU Pinning functionality remains in English and should be translated to German for consistency with the rest of the localization.
44-44:⚠️ Potential issue | 🟡 MinorUntranslated English content.
The disk settings description is in English. Consider translating for consistency.
74-74:⚠️ Potential issue | 🟡 MinorUntranslated English content.
The management access description is in English. Consider translating for consistency.
82-82:⚠️ Potential issue | 🟡 MinorUntranslated English content.
The network settings description is in English. Consider translating for consistency.
214-231:⚠️ Potential issue | 🟠 MajorSection heading doesn't match content.
Line 214 has heading "## Benachrichtigungseinstellungen" (Notification Settings), but lines 216-231 contain content about Network Services (NFS, SMB). The English paragraph at line 216 describes network protocols, not notifications.
Either the heading should be changed to match the network services content, or the content needs to be reorganized.
🛠️ Suggested fix - restore correct heading
-## Benachrichtigungseinstellungen +## Netzwerkdienste **Network Services** let you configure network communication protocols...
216-220:⚠️ Potential issue | 🟡 MinorMultiple untranslated English paragraphs.
Lines 216 and 220 contain English descriptions for Network Services and NFS that should be translated to German.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx (1)
512-534:⚠️ Potential issue | 🟡 MinorAdditional mixed-language admonition titles.
Two more admonitions have inconsistent language mixing:
- Line 512:
:::danger[Important Erinnerung]— "Important" is English, "Erinnerung" (reminder) is German- Line 534:
:::tip[Transferring Dateien von externen Netzwerkfreigaben]— "Transferring" is English, rest is GermanSuggested fixes
-:::danger[Important Erinnerung] +:::danger[Wichtige Erinnerung]-:::tip[Transferring Dateien von externen Netzwerkfreigaben] +:::tip[Dateien von externen Netzwerkfreigaben übertragen]i18n/es/docusaurus-plugin-content-docs/current/API/cli.mdx (1)
9-13:⚠️ Potential issue | 🟠 MajorFix malformed admonition label.
Line 9 has an incomplete/malformed admonition label
:::info[Command Estructurawhich is missing content and uses mixed English-Spanish. The admonition body is also in English.🔧 Proposed fix
-:::info[Command Estructura +:::info[Estructura de Comandos] -All commands follow the pattern: `unraid-api <command> [options]` +Todos los comandos siguen el patrón: `unraid-api <comando> [opciones]` :::i18n/es/docusaurus-plugin-content-docs/current/API/index.mdx (1)
82-93:⚠️ Potential issue | 🟡 MinorUse fully Spanish admonition label.
Line 82 uses mixed English-Spanish label
Core Capacidades. Use a fully Spanish label for consistency.🔧 Proposed fix
-:::info[Core Capacidades] +:::info[Capacidades Principales] La API proporciona:i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (1)
98-109:⚠️ Potential issue | 🟠 MajorRemove duplicate section content.
Lines 98-109 contain duplicate content. The "Cifrado de copia de seguridad" section (Line 98) appears to be incomplete and merges into unrelated content about disabling backup (Lines 102-103). Then Lines 105-109 contain another "Privacidad y seguridad" section with "Cifrado de copia de seguridad" subsection that duplicates Line 100's content.
🔧 Proposed fix
-## Cifrado de copia de seguridad - -Actualmente, las copias de seguridad de flash se almacenan en la nube sin encriptación. Como precaución, los datos sensibles, incluidas todas las contraseñas de usuario y root, así como todas las claves de %%WireGuard|wireguard%%, nunca se incluyen en la copia de seguridad. - -1. En ***Configuración → Acceso de Gestión → API de Unraid***, haz clic en **Desactivar** para la copia de seguridad flash. -2. En el cuadro de diálogo de confirmación, marque **También eliminar la copia de seguridad en la nube** si desea eliminar su copia de seguridad inmediatamente. De lo contrario, las copias de seguridad se eliminarán automáticamente después de un período de inactividad. - ## Privacidad y seguridad ### Cifrado de copia de seguridad Actualmente, las copias de seguridad de flash se almacenan en la nube sin encriptación. Como precaución, los datos sensibles, incluidas todas las contraseñas de usuario y root, así como todas las claves de %%WireGuard|wireguard%%, nunca se incluyen en la copia de seguridad. + +### Desactivar copia de seguridad flash + +1. En ***Configuración → Acceso de Gestión → API de Unraid***, haz clic en **Desactivar** para la copia de seguridad flash. +2. En el cuadro de diálogo de confirmación, marque **También eliminar la copia de seguridad en la nube** si desea eliminar su copia de seguridad inmediatamente. De lo contrario, las copias de seguridad se elimininarán automáticamente después de un período de inactividad.i18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx (3)
30-36:⚠️ Potential issue | 🟡 MinorRemove duplicate "Salida:" label.
Lines 30 and 36 both contain
**Salida:**labels. Line 30 appears to be misplaced before the command, while Line 36 correctly labels the output. Remove the duplicate.🔧 Proposed fix
-**Salida:** - ```bash unraid-api apikey --create --name "workflow key" --roles ADMIN --jsonSalida:
</details> --- `209-222`: _⚠️ Potential issue_ | _🟡 Minor_ **Use fully Spanish admonition label.** Line 209 uses mixed English-Spanish label `Security Mejores Prácticas`. Use a fully Spanish label. <details> <summary>🔧 Proposed fix</summary> ```diff -:::info[Security Mejores Prácticas] +:::info[Mejores Prácticas de Seguridad] **Permisos Mínimos**
224-253:⚠️ Potential issue | 🟠 MajorFix structural issues in error handling and troubleshooting sections.
Lines 224-253 have significant structural problems:
- "Gestión de Errores" section (Lines 224-228) starts with a solution ("Elimine caracteres especiales...") before stating the problem
- "Nomenclatura de Claves" section (Lines 230-234) similarly starts with a solution
- Lines 240-253 contain a
:::noteblock with duplicate/misplaced contentThis appears to be a merge artifact where content was duplicated and rearranged incorrectly.
🔧 Proposed fix
### Gestión de Errores -- **Solución:** Elimine caracteres especiales como guiones, guiones bajos o símbolos - Usar `set -e` en scripts bash para fallar rápidamente - Implementar limpieza adecuada con `trap` ### Nomenclatura de Claves -- **Solución:** Use la bandera `--overwrite` o elija un nombre diferente - Los nombres deben contener solo letras, números y espacios - Se admiten letras Unicode ## Solución de problemas ### Problemas Comunes :::note[Common Mensajes de Error] -Para resolución de problemas, ejecute con registro de depuración: +**"El nombre de la clave contiene caracteres no válidos"** - **Solución:** Elimine caracteres especiales como guiones, guiones bajos o símbolos **"Una clave API con el nombre 'x' ya existe"** - **Solución:** Use la bandera `--overwrite` o elija un nombre diferente **"Por favor, añada al menos un rol o permiso a la clave"** - **Solución:** Especifique ya sea `--roles` o `--permissions` (o ambos) :::i18n/es/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx (4)
50-61:⚠️ Potential issue | 🟠 MajorRemove duplicate "Cuándo usar el Modo Simple" sections.
Lines 50-55 and 56-61 contain two nearly identical "Cuándo usar el Modo Simple" sections with the same bullet points. Remove the duplicate.
🔧 Proposed fix
**Cuándo usar el Modo Simple:** - Permitir dominios de correo específicos (por ejemplo, `@empresa.com`) - Permitir direcciones de correo específicas - Configurar quién puede acceder a tu servidor Unraid con una configuración mínima - -**Cuándo usar el Modo Simple:** - -- Deseas permitir a todos los usuarios de tu dominio corporativo -- Tienes una lista pequeña de usuarios específicos -- Eres nuevo en la configuración de OIDC
80-98:⚠️ Potential issue | 🟠 MajorRemove duplicate section headers and fix misplaced content.
Lines 80-98 contain:
- Duplicate "Ejemplos de Modo Simple" headers (Lines 80 and 85)
- Misplaced bullet points under "Permitir Dominio Corporativo" (Lines 91-92) that belong to a different section
🔧 Proposed fix
-## Ejemplos de Modo Simple - - -*Reglas avanzadas de autorización mostrando configuración de claims de JWT con operador de endsWith para control de acceso basado en dominio* - ### Ejemplos de Modo Simple #### Permitir Dominio Corporativo En Autorización Simple: -- **Direcciones de Correo Específicas**: Añadir correos individuales -- Haz clic en **Añadir Elemento** para añadir múltiples direcciones +- **Dominios de Correo Permitidos**: Añadir dominios sin @ (por ejemplo, `empresa.com`) +- Haz clic en **Añadir Elemento** para añadir múltiples dominios #### Permitir Usuarios Específicos
390-444:⚠️ Potential issue | 🟠 MajorRemove duplicate provider sections.
Lines 390-444 contain duplicate provider configuration sections. The Authentik and Okta sections each appear twice (Lines 390-403 and 418-431 for Authentik; Lines 404-416 and 432-444 for Okta). Remove the duplicates.
🔧 Proposed fix
Remove Lines 390-416 (the first occurrences of Authentik and Okta) and keep only Lines 418-444.
237-277:⚠️ Potential issue | 🟠 MajorRemove duplicate "Probando Tu Configuración" sections and fix structural issues.
Lines 237-277 contain significant structural duplication:
- Two "✅ Probando Tu Configuración" sections (Lines 220 and 237) with overlapping content
- Mismatched numbered list (Lines 242-246 jump from 1 to 2, 3, 4, 5 incorrectly)
- Duplicate problem descriptions under "Problemas Comunes"
This entire section needs consolidation to remove duplicate troubleshooting content.
i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx (1)
104-108:⚠️ Potential issue | 🟡 MinorAvoid duplicate “Plugin-System” heading hierarchy.
Line 104 adds an H3 immediately before the H2 “Plugin-System” on Line 109. This breaks heading structure. Consider folding the bullets under the H2.🛠️ Suggested cleanup
-### Plugin-System - -- **Speicherfreigabeerstellung & -einstellungen** - Erweiterte Freigabenkonfigurationsoptionen -- **Speicherfreigabeverwaltungsschnittstelle** - Einheitliches Freigabeverwaltungs-Dashboard - -## Plugin-System +## Plugin-System + +- **Speicherfreigabeerstellung & -einstellungen** - Erweiterte Freigabenkonfigurationsoptionen +- **Speicherfreigabeverwaltungsschnittstelle** - Einheitliches Freigabeverwaltungs-Dashboardi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx (4)
40-40:⚠️ Potential issue | 🟡 MinorTranslate remaining English sentence to German.
This is a German doc page, but this sentence is still in English.
✅ Suggested translation
-If you're using Windows, you might prefer %%PuTTY|putty%% for %%SSH|ssh%% access instead of the built-in terminal. It's lightweight, free, and allows you to save sessions for easy access later. +Wenn Sie Windows verwenden, bevorzugen Sie möglicherweise %%PuTTY|putty%% für den %%SSH|ssh%%‑Zugriff anstelle des integrierten Terminals. Es ist leichtgewichtig, kostenlos und ermöglicht das Speichern von Sitzungen für den späteren Zugriff.
110-124:⚠️ Potential issue | 🟠 Major
pssubsection showstopcommand.The heading says
ps, but the example and guidance are fortop. This will mislead readers. Either move thetopcontent under a### \top`subsection or replace it withps` examples.
178-254:⚠️ Potential issue | 🟠 MajorStorage command subsections are misaligned/duplicated.
Examples don’t match their headings (e.g.,
lsblkshowsdf -h,blockdev -getszshowsfdisk -l,blkidshowslsblk), andblockdev -getszappears twice. Please realign each subsection so its heading, description, and code block all match the same command, and remove duplicates.
258-314:⚠️ Potential issue | 🟠 MajorNetwork diagnostics subsections don’t match commands.
The
pingsubsection showssscommands, and theethtoolsubsection showsipcommands. Please move each command block under the correct heading soss/ping/ethtoolsections are accurate.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx (2)
72-114:⚠️ Potential issue | 🟠 MajorResolve duplicate “WebGUI” and “Array” steps.
There are two sets of steps 6 and 7; keep one set and merge the unique bullets (shares/Docker/VMs) into it.🔁 Proposed consolidation
- Wenn Autostart aktiviert ist, beginnt das %%array|array%% hier; andernfalls ist ein manueller Start erforderlich. - Laufwerke werden als `/dev/diskX` und `/mnt/cache` (falls vorhanden) eingehängt. + - Freigaben werden im Netzwerk als `/mnt/user/sharename` verfügbar. + - Docker-Container starten in der auf der Docker-Seite angegebenen Reihenfolge mit anpassbaren Verzögerungen. + - Automatisch startende virtuelle Maschinen (%%VMs|vm%%) werden ebenfalls gestartet. </details> - -<details> - <summary><strong>6. WebGUI</strong> - Zum Erweitern/Kollabieren klicken</summary> - - Die webbasiertem Verwaltungsoberfläche wird verfügbar und ermöglicht die Fernadministration und -konfiguration Ihres Servers. - - - Die %%WebGUI|web-gui%% startet an diesem Punkt. - - Die Datei `config/go` auf dem Flash-Gerät kann Benutzerbefehle vor oder nach dem Start der %%WebGUI|web-gui%% ausführen. -</details> - -<details> - <summary><strong>7. Array</strong> - Zum Erweitern/Kollabieren klicken</summary> - - Speichergeräte werden eingehängt und verfügbar gemacht, was den Bootvorgang abschließt. Hier werden Ihre Daten zugänglich. - - - Wenn Autostart aktiviert ist, beginnt das %%array|array%% hier; andernfalls ist ein manueller Start erforderlich. - - Laufwerke werden als `/dev/diskX` und `/mnt/cache` (falls vorhanden) eingehängt. - - Freigaben werden im Netzwerk als `/mnt/user/sharename` verfügbar. - - Docker-Container starten in der auf der Docker-Seite angegebenen Reihenfolge mit anpassbaren Verzögerungen. - - Automatisch startende virtuelle Maschinen (%%VMs|vm%%) werden ebenfalls gestartet. -</details>
137-151:⚠️ Potential issue | 🟡 MinorFix grammar and remove the duplicated paragraph in the important block.
The same sentence appears again after the block, and a few phrases are unidiomatic.✏️ Proposed fix
-Wenn Ihr Unraid-Bootlaufwerk ausfällt und Sie keinen aktuellen Backup oder kein Wissen darüber haben, welche Laufwerke Parität sind, können Sie Ihr System wiederherstellen, indem Sie Unraids Fähigkeit nutzen, Datenträger anhand ihrer Dateisysteme zu erkennen. %%Paritätslaufwerke|parity-drives%% haben kein gültiges Dateisystem, was sie unterscheidbar macht. +Wenn Ihr Unraid-Bootlaufwerk ausfällt und Sie kein aktuelles Backup und keine Kenntnis darüber haben, welche Laufwerke Parität sind, können Sie Ihr System wiederherstellen, indem Sie Unraids Fähigkeit nutzen, Datenträger anhand ihrer Dateisysteme zu erkennen. %%Paritätslaufwerke|parity-drives%% haben kein gültiges Dateisystem, was sie unterscheidbar macht. @@ -2. **Dokumentieren** Sie, welche Laufwerke zuvor Paritäts- vs. Datenträger waren -3. **Erwägen Sie Rat**, wenn Sie sich unsicher sind, in den [Unraid-Foren](https://forums.unraid.net/) einzuholen +2. **Dokumentieren** Sie, welche Laufwerke zuvor Paritäts- und Datenträger waren. +3. **Holen Sie Rat ein**, wenn Sie sich unsicher sind, z. B. in den [Unraid-Foren](https://forums.unraid.net/). @@ -Wenn Ihr Unraid-Bootlaufwerk ausfällt und Sie keinen aktuellen Backup oder kein Wissen darüber haben, welche Laufwerke Parität sind, können Sie Ihr System wiederherstellen, indem Sie Unraids Fähigkeit nutzen, Datenträger anhand ihrer Dateisysteme zu erkennen. %%Paritätslaufwerke|parity-drives%% haben kein gültiges Dateisystem, was sie unterscheidbar macht.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx (1)
66-79:⚠️ Potential issue | 🟡 MinorRemove the repeated guest‑agent paragraph and localize the note title.
The guest‑agent sentence appears twice and the label is still English (“Benefits”).
💡 Suggested cleanup
-:::note[Benefits des Ruhezustands] +:::note[Vorteile des Ruhezustands] @@ -Um den Ruhezustand zuverlässig zu nutzen, müssen Sie den %%QEMU|qemu%%-%%Guest-Agent|guest-agent%% in Ihrer Windows-%%VM|vm%% installieren. Dieser Agent ermöglicht es Unraid, mit der %%VM|vm%% für erweiterte Vorgänge wie Ruhezustand, Herunterfahren und Live-Statistikberichterstattung zu kommunizieren.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx (6)
24-29:⚠️ Potential issue | 🟡 MinorTranslate the English table cell for recommended storage.
The “Dedicated NVMe …” cell is still English.
💡 Suggested fix
-| **Speicher** | SSD- oder NVMe-**%%cache pool\|cache-pool%%** mit ausreichend Platz | Dedicated NVMe %%cache pool\|cache-pool%% for %%VM\|vm%% storage | +| **Speicher** | SSD- oder NVMe-**%%cache pool\|cache-pool%%** mit ausreichend Platz | Dedizierter NVMe-%%cache pool\|cache-pool%% für %%VM\|vm%%‑Speicher |
54-78:⚠️ Potential issue | 🟡 MinorTranslate the remaining English guidance in the conversion steps.
Two sentences are still English in the Linux conversion flow.
💡 Suggested fix
-- Store %%VM|vm%% images on a **%%cache pool|cache-pool%%** instead of an %%array|array%% for the [best performance](./overview-and-system-prep.mdx#user-shares-for-virtualization). +- Speichern Sie %%VM|vm%%‑Images für die [beste Leistung](./overview-and-system-prep.mdx#user-shares-for-virtualization) auf einem **%%cache pool|cache-pool%%** statt im %%array|array%%. @@ -- -O raw: Sets the output format to raw (Unraid's default). +- -O raw: Setzt das Ausgabformat auf raw (Unraid‑Standard).
153-169:⚠️ Potential issue | 🟡 MinorLocalize the “Choosing …” admonition title.
The label mixes English and German.
💡 Suggested fix
-:::important[Choosing Ihr Migrationsansatz] +:::important[Wählen Sie Ihren Migrationsansatz]
236-247:⚠️ Potential issue | 🟡 MinorDrop the duplicated “Schritt 4” heading.
Two consecutive sections share the same heading; keep one and continue the flow below it.
317-327:⚠️ Potential issue | 🟡 MinorTranslate the remaining English sentences in the Xen migration section.
Several lines are still English, which breaks the German flow.
Also applies to: 373-375, 434-435
13-20:⚠️ Potential issue | 🟠 MajorFix escaped admonition label syntax and translate the remaining English prerequisite.
The backslash before
[Prerequisites]breaks the admonition syntax and must be removed. Additionally, one prerequisite line on line 17 is still in English and needs translation.💡 Suggested fixes
-:::note\[Prerequisites] +:::note[Voraussetzungen] @@ -- Ensure you have enough free space in your **%%array|array%%** or **%%cache pool|cache-pool%%** to accommodate the new virtual disk image. +- Stellen Sie sicher, dass genügend freier Speicherplatz in Ihrem **%%array|array%%** oder **%%cache pool|cache-pool%%** vorhanden ist, um das neue virtuelle Festplatten-Image aufzunehmen.The same escaped bracket issue appears on line 171 and should also be fixed to
:::note[Voraussetzungen].i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx (1)
27-57:⚠️ Potential issue | 🟠 MajorTranslate the “Unter der Haube” details block to German.
This section is largely English inside a German page, which breaks localization consistency.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx (4)
78-90:⚠️ Potential issue | 🟡 MinorRemove duplicated template guidance.
The “Benutzervorlagen” steps and the “Unraid 7.x führt …” paragraph repeat or conflict with the surrounding section. Keep one canonical set of instructions.
105-146:⚠️ Potential issue | 🟠 MajorMerge the duplicated “Erweiterte Grafik‑ und GPU‑Sharing‑Optionen” blocks and translate English bullets.
Two sections share the same summary and one block is still English. Consolidate into one German list to avoid repetition.
431-440:⚠️ Potential issue | 🟠 MajorFix the mismatched “Steckenbleiben in der UEFI‑Shell” heading.
The section content explains ROM injection, not UEFI‑Shell recovery. Rename the heading (e.g., “Manuelle ROM‑Injektion”) or move this content under the troubleshooting “UEFI‑Shell” section to match the title.
97-103:⚠️ Potential issue | 🟠 MajorRemove the backslash from the admonition label.
The escape character in
:::tip\[Highlights]breaks MDX parsing. The backslash should be removed.Suggested fix
-:::tip\[Highlights] +:::tip[Highlights]i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx (1)
25-31:⚠️ Potential issue | 🟠 MajorFix the escaped admonition label.
The backslash before
[is invalid in Docusaurus MDX admonition syntax and will break parsing. Additionally, since this is a German documentation file, the label should be in German.💡 Suggested fix
-:::note\[Prerequisites] +:::note[Voraussetzungen]
🤖 Fix all issues with AI agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx`:
- Around line 15-21: The admonition marker :::important[Security erinnerung]
wraps a broken/duplicated intro ("Fernzugriff über Unraid Connect bietet:")
which is repeated immediately after; either remove the entire admonition block
(delete the :::important... start and matching ::: and keep the single intro
line) or replace the admonition body with a meaningful security reminder
sentence(s) and remove the duplicated standalone line so the phrase "Fernzugriff
über Unraid Connect bietet:" appears only once; locate the offending markers by
searching for the token :::important[Security erinnerung] and the duplicated
string "Fernzugriff über Unraid Connect bietet:" and update accordingly (ensure
proper MDX admonition syntax if you add content).
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx`:
- Around line 372-381: The JSX props on the TabItem components use German
opening quote characters („) which break the MDX parser; update the label props
on the TabItem elements (the instances using value="cpu", value="memory", and
value="storage") to use valid JS string delimiters (either straight double
quotes "..." or single quotes '...') so labels become e.g. "CPU-Info",
"RAM-Informationen", "Speicherinformationen".
- Line 28: The admonition opening is malformed: the title for the tip uses
":::tip[Wann sollte ich das Terminal verwenden?" but is missing the closing
bracket; update the admonition start to ":::tip[Wann sollte ich das Terminal
verwenden?]" so the MDX parser recognizes the title (also verify the
corresponding admonition close "::: " exists later in the document).
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx`:
- Around line 145-150: The JSX TabItem attributes use German smart quotes („ and
”) which are invalid; update the attribute delimiters on the TabItem components
(the ones rendering WireGuardConfigureMobile and WireGuardConfigureOtherDevices)
to use standard ASCII quotes (either " or ') for both value and label attributes
so the JSX parses correctly, e.g., fix the TabItem elements around
WireGuardConfigureMobile and WireGuardConfigureOtherDevices.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx`:
- Around line 56-61: Remove the duplicated admonition and duplicate heading:
keep a single opening admonition tag `:::caution[RAM Übertaktungsrisiken und
Empfehlungen]` paired with its closing `:::` and remove the extra
`:::caution[RAM Übertaktungsrisiken und Empfehlungen]` line, and delete the
redundant heading `**Risiken der Übertaktung:**` so only one heading remains;
ensure the admonition content remains between the single opening and closing
tags.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx`:
- Around line 283-358: The "Zuweisungsprofil" section contains misplaced and
repeated content: remove the four duplicate sentences "Hier ist eine kurze
Übersicht darüber, wofür jede Standardfreigabe ist" from the allocation profile
subsections (they belong in the "Standardfreigaben" section), move the "Um
Laufwerksfreigaben zu aktivieren:" block out of the "Hochwasser (Empfohlen)"
subsection into the proper "Standardfreigaben" or disk-shares configuration
section, rename the heading "#### Dateien von einer Netzwerkfreigabe übertragen"
to "#### Auffüllen" to match the Fill-up method content, and relocate the
Midnight Commander / Web-Terminal paragraph to the network/share tools section
(e.g., where command-line tools are documented); ensure the remaining
High-Water, Most-free, and Auffüllen subsections contain only the
allocation-method explanations and examples.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdx`:
- Around line 16-17: Replace the invalid admonition line "info[Examples von
Umgebungsvariablen]" with a proper Docusaurus admonition by prefixing it with
":::". For example, change that line to start with ":::info" (e.g., ":::info
Examples von Umgebungsvariablen") and ensure you add the matching closing ":::".
Update the admonition title/content placement in the file to follow the ":::info
... \<content\> :::" pattern so rendering succeeds.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx`:
- Around line 200-228: The file contains a duplicated "## Cierre de sesión"
section plus orphaned text and a stray separator that break structure; remove
the redundant block including the orphaned "Cuando cierres la sesión:" and the
extra '---' so that only one "## Cierre de sesión" section remains (the valid
instance before the "Desinstalación del complemento" section). Ensure the single
retained "Cierre de sesión" entry includes the uninstall bullet points and the
link to ./automated-flash-backup.mdx, and delete the duplicated copy that
repeats the same content.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx`:
- Around line 76-84: Fix the malformed note block by consolidating the duplicate
`:::note` openers into a single `:::note` block, remove the leftover English
sentence so only the Spanish translation remains, and ensure the block is
properly closed with a single `:::`; locate the offending `:::note` markers and
the English line near the `tour-the-web-gui.mdx` snippet and replace them with
one well-formed Spanish note containing the translated text.
| :::important[Security erinnerung] | ||
| Bevor Sie den Fernzugriff aktivieren, stellen Sie sicher, dass Ihr Root-Passwort stark und einzigartig ist. Aktualisieren Sie es auf der Seite **Benutzer**, wenn erforderlich. Halten Sie außerdem Ihr Unraid OS auf die neueste Version aktualisiert, um sich gegen Sicherheitslücken zu schützen. [Erfahren Sie hier mehr darüber, wie Sie Unraid aktualisieren können](../unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx). | ||
|
|
||
| Fernzugriff über Unraid Connect bietet: | ||
|
|
||
| ::: | ||
|
|
||
| Fernzugriff über Unraid Connect bietet: |
There was a problem hiding this comment.
Broken admonition block with duplicate content.
The :::important[Security erinnerung] block (lines 15-19) contains only "Fernzugriff über Unraid Connect bietet:" which is then repeated verbatim at line 21. This appears to be a translation merge issue:
- The "Security erinnerung" block should contain actual security reminder content, not introduction text
- Line 17 duplicates line 21
Either populate the security reminder block with meaningful content, or remove it entirely:
Option 1: Remove the broken admonition block
-:::important[Security erinnerung]
-
-Fernzugriff über Unraid Connect bietet:
-
-:::
-
Fernzugriff über Unraid Connect bietet:🧰 Tools
🪛 LanguageTool
[grammar] ~15-~15: Entferne ein Leerzeichen
Context: ...mpfohlene Lösung. :::important[Security erinnerung] Fernzugriff über Unraid Connect biete...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx`
around lines 15 - 21, The admonition marker :::important[Security erinnerung]
wraps a broken/duplicated intro ("Fernzugriff über Unraid Connect bietet:")
which is repeated immediately after; either remove the entire admonition block
(delete the :::important... start and matching ::: and keep the single intro
line) or replace the admonition body with a meaningful security reminder
sentence(s) and remove the duplicated standalone line so the phrase "Fernzugriff
über Unraid Connect bietet:" appears only once; locate the offending markers by
searching for the token :::important[Security erinnerung] and the duplicated
string "Fernzugriff über Unraid Connect bietet:" and update accordingly (ensure
proper MDX admonition syntax if you add content).
| Sie können auch extern über %%SSH|ssh%% (Secure Shell) mit einem Client wie %%PuTTY|putty%% auf Ihren Unraid-Server zugreifen. | ||
|
|
||
| :::tip\[When Sollte ich das Terminal verwenden? | ||
| :::tip[Wann sollte ich das Terminal verwenden? |
There was a problem hiding this comment.
Fix malformed admonition title syntax.
The tip title is missing the closing ], which breaks MDX parsing.
✅ Suggested fix
-:::tip[Wann sollte ich das Terminal verwenden?
+:::tip[Wann sollte ich das Terminal verwenden?]📝 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.
| :::tip[Wann sollte ich das Terminal verwenden? | |
| :::tip[Wann sollte ich das Terminal verwenden?] |
🧰 Tools
🪛 LanguageTool
[grammar] ~28-~28: Passe das Symbol an
Context: ...f Ihren Unraid-Server zugreifen. :::tip[Wann sollte ich das Terminal verwenden? ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx`
at line 28, The admonition opening is malformed: the title for the tip uses
":::tip[Wann sollte ich das Terminal verwenden?" but is missing the closing
bracket; update the admonition start to ":::tip[Wann sollte ich das Terminal
verwenden?]" so the MDX parser recognizes the title (also verify the
corresponding admonition close "::: " exists later in the document).
| <TabItem value="cpu" label=„CPU-Info"> | ||
| <CliCpuInfo /> | ||
| </TabItem> | ||
|
|
||
| <TabItem value="memory" label="RAM-Informationen"> | ||
| <TabItem value="memory" label=„RAM-Informationen"> | ||
| <CliMemoryInfo /> | ||
| </TabItem> | ||
|
|
||
| <TabItem value="storage" label="Speicherinformationen"> | ||
| <TabItem value="storage" label=„Speicherinformationen"> | ||
| <CliStorageInfo /> |
There was a problem hiding this comment.
Invalid quotes in JSX props break MDX build.
label=„…" uses German quotes, which are not valid JSX string delimiters. This will fail to parse.
✅ Suggested fix
- <TabItem value="cpu" label=„CPU-Info">
+ <TabItem value="cpu" label="CPU-Info">
<CliCpuInfo />
</TabItem>
- <TabItem value="memory" label=„RAM-Informationen">
+ <TabItem value="memory" label="RAM-Informationen">
<CliMemoryInfo />
</TabItem>
- <TabItem value="storage" label=„Speicherinformationen">
+ <TabItem value="storage" label="Speicherinformationen">
<CliStorageInfo />
</TabItem>🧰 Tools
🪛 LanguageTool
[typographical] ~376-~376: Zeichen ohne sein Gegenstück: ‚“‘ scheint zu fehlen
Context: ...bItem> <TabItem value="memory" label=„RAM-Informationen"> <CliMemoryInfo /...
(DE_UNPAIRED_QUOTES)
[grammar] ~376-~376: Ersetze das Satzzeichen
Context: ...> <TabItem value="memory" label=„RAM-Informationen"> <...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~377-~377: Hier könnte ein Fehler sein.
Context: ...AM-Informationen"> <TabItem value="storage" label=„Speicher...
(QB_NEW_DE)
[grammar] ~380-~380: Ersetze das Satzzeichen
Context: ...iMemoryInfo /> <TabItem value="storage" label=„Speicherinformationen"> <Cli...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_VALUEEQUALSQUOTESTORAGEQUOTE_VALUEEQUALS„STORAGEL_DOUBLE_QUOT)
[grammar] ~380-~380: Ersetze das Satzzeichen
Context: ... <TabItem value="storage" label=„Speicherinformationen"> </T...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx`
around lines 372 - 381, The JSX props on the TabItem components use German
opening quote characters („) which break the MDX parser; update the label props
on the TabItem elements (the instances using value="cpu", value="memory", and
value="storage") to use valid JS string delimiters (either straight double
quotes "..." or single quotes '...') so labels become e.g. "CPU-Info",
"RAM-Informationen", "Speicherinformationen".
| <TabItem value="mobil" label=„Mobiles Gerät" default> | ||
| <WireGuardConfigureMobile /> | ||
| </TabItem> | ||
|
|
||
| <TabItem value="sonstige" label="Andere Geräte"> | ||
| <TabItem value="sonstige" label=„Andere Geräte"> | ||
| <WireGuardConfigureOtherDevices /> |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, let's locate and read the specific file and lines
cat -n "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx" | sed -n '140,155p'Repository: unraid/docs
Length of output: 485
🏁 Script executed:
# Search for other TabItem labels in the codebase to understand the pattern
rg '<TabItem.*label=' --max-count 20 -A 1Repository: unraid/docs
Length of output: 50368
🏁 Script executed:
# Check if there are any other occurrences of smart quotes in JSX attributes in this specific file
rg 'label=' "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx"Repository: unraid/docs
Length of output: 161
Replace smart quotes with ASCII quotes in JSX attribute values.
Lines 145 and 149 use German typographic quotes („ and ") as JSX attribute delimiters, which is invalid syntax. JSX requires ASCII quotes to delimit attribute values.
🔧 Proposed fix
- <TabItem value="mobil" label=„Mobiles Gerät" default>
+ <TabItem value="mobil" label="Mobiles Gerät" default>
@@
- <TabItem value="sonstige" label=„Andere Geräte">
+ <TabItem value="sonstige" label="Andere Geräte">📝 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.
| <TabItem value="mobil" label=„Mobiles Gerät" default> | |
| <WireGuardConfigureMobile /> | |
| </TabItem> | |
| <TabItem value="sonstige" label="Andere Geräte"> | |
| <TabItem value="sonstige" label=„Andere Geräte"> | |
| <WireGuardConfigureOtherDevices /> | |
| <TabItem value="mobil" label="Mobiles Gerät" default> | |
| <WireGuardConfigureMobile /> | |
| </TabItem> | |
| <TabItem value="sonstige" label="Andere Geräte"> | |
| <WireGuardConfigureOtherDevices /> |
🧰 Tools
🪛 LanguageTool
[grammar] ~149-~149: Ersetze das Satzzeichen
Context: ...igureMobile /> <TabItem value="sonstige" label=„Andere Geräte"> <WireGuardCo...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_VALUEEQUALSQUOTESONSTIGEQUOTE_VALUEEQUALS„SONSTIGEL_DOUBLE_QUOT)
[typographical] ~149-~149: Zeichen ohne sein Gegenstück: ‚“‘ scheint zu fehlen
Context: ...tem> <TabItem value="sonstige" label=„Andere Geräte"> <WireGuardConfigureO...
(DE_UNPAIRED_QUOTES)
[grammar] ~149-~149: Ersetze das Satzzeichen
Context: ...<TabItem value="sonstige" label=„Andere Geräte"> ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~150-~150: Korrigiere das Wort
Context: ...> ### Konfigurationen,...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_SPACE)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx`
around lines 145 - 150, The JSX TabItem attributes use German smart quotes („
and ”) which are invalid; update the attribute delimiters on the TabItem
components (the ones rendering WireGuardConfigureMobile and
WireGuardConfigureOtherDevices) to use standard ASCII quotes (either " or ') for
both value and label attributes so the JSX parses correctly, e.g., fix the
TabItem elements around WireGuardConfigureMobile and
WireGuardConfigureOtherDevices.
| **Risiken der Übertaktung:** | ||
| :::caution[RAM Übertaktungsrisiken und Empfehlungen] | ||
| :::caution[RAM Übertaktungsrisiken und Empfehlungen] | ||
| **Einkauf:** Wenn möglich, kaufen Sie immer RAM, das in der QVL (Qualified Vendor List) Ihres Mainboards aufgeführt ist und nicht in der QVL des RAM-Herstellers. Dies gewährleistet eine bessere Kompatibilität und Stabilität. | ||
|
|
||
| **Fehlerbehebung:** Wenn Memtest86+ bestanden wird, Sie aber immer noch Probleme haben, deaktivieren Sie XMP/AMP und versuchen Sie es erneut. Der Leistungsunterschied ist in der Regel minimal, jedoch kann die Stabilitätsverbesserung erheblich sein. | ||
| ::: |
There was a problem hiding this comment.
Duplicate admonition block causes rendering error.
Lines 57 and 58 both contain :::caution[RAM Übertaktungsrisiken und Empfehlungen], creating a duplicate opening tag with only one closing tag on line 61. This will cause MDX parsing errors or malformed HTML output.
Additionally, the standalone heading "Risiken der Übertaktung:" on line 56 duplicates the same heading on line 65.
🐛 Proposed fix
-**Risiken der Übertaktung:**
-:::caution[RAM Übertaktungsrisiken und Empfehlungen]
:::caution[RAM Übertaktungsrisiken und Empfehlungen]
**Fehlerbehebung:** Wenn Memtest86+ bestanden wird, Sie aber immer noch Probleme haben, deaktivieren Sie XMP/AMP und versuchen Sie es erneut. Der Leistungsunterschied ist in der Regel minimal, jedoch kann die Stabilitätsverbesserung erheblich sein.
:::🧰 Tools
🪛 LanguageTool
[grammar] ~56-~56: Hier könnte ein Fehler sein.
Context: ...-Übertaktung Risiken der Übertaktung: :::caution[RAM Übertaktungsrisiken und E...
(QB_NEW_DE)
[grammar] ~57-~57: Hier könnte ein Fehler sein.
Context: ...AM Übertaktungsrisiken und Empfehlungen] :::caution[RAM Übertaktungsrisiken und E...
(QB_NEW_DE)
[grammar] ~60-~60: Passe das Symbol an
Context: ...ken und Empfehlungen] Fehlerbehebung: Wenn Memtest86+ bestanden wird, Sie abe...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx`
around lines 56 - 61, Remove the duplicated admonition and duplicate heading:
keep a single opening admonition tag `:::caution[RAM Übertaktungsrisiken und
Empfehlungen]` paired with its closing `:::` and remove the extra
`:::caution[RAM Übertaktungsrisiken und Empfehlungen]` line, and delete the
redundant heading `**Risiken der Übertaktung:**` so only one heading remains;
ensure the admonition content remains between the single opening and closing
tags.
| ### Zuweisungsprofil | ||
|
|
||
| Wenn Sie eine neue Benutzerfreigabe erstellen oder eine Datei oder einen Ordner darin hinzufügen, muss das System entscheiden, wo diese Daten gespeichert werden. In der Regel wird die Datenplatte gewählt, die am meisten freien Speicherplatz hat. Sie können jedoch anpassen, wie diese Entscheidung mithilfe bestimmter Einstellungen getroffen wird. | ||
| Wenn Sie Unraid mit **Docker** oder **Virtuellen Maschinen (VMs)** verwenden, erstellt es automatisch einige Standardfreigaben. | ||
|
|
||
| Es gibt drei einfache Optionen, die Sie auswählen können, wie das System den Speicherplatz für Ihre Benutzerfreigabe zuteilt: | ||
|
|
||
| <Tabs> | ||
| <TabItem value="hochwasser" label="Hochwasser (Empfohlen)" default> | ||
| <h4>Wie es funktioniert</h4> | ||
| #### Hochwasser (Empfohlen) | ||
|
|
||
| Die **High-Water**-Methode füllt Festplatten schrittweise mit "Schaltpunkten" basierend auf der Hälfte der Kapazität des größten Laufwerks. Dies balanciert die Festplattennutzung aus, hält zusammengehörige Dateien zusammen und minimiert das Hochdrehen der Festplatten. | ||
| Hier ist eine kurze Übersicht darüber, wofür jede Standardfreigabe ist: | ||
|
|
||
| <h4>Beispiel mit 8TB, 3TB und 2TB Laufwerken</h4> | ||
| Die **High-Water**-Methode füllt Festplatten schrittweise mit "Schaltpunkten" basierend auf der Hälfte der Kapazität des größten Laufwerks. Dies balanciert die Festplattennutzung aus, hält zusammengehörige Dateien zusammen und minimiert das Hochdrehen der Festplatten. | ||
|
|
||
| 1. **Erster Durchgang:** Fülle 8TB-Laufwerk, bis 4TB frei bleiben (die Hälfte von 8TB). | ||
| 2. **Zweiter Durchgang:** Fülle 8TB/3TB-Laufwerke, bis 2TB frei bleiben. | ||
| 3. **Dritter Durchgang:** Fülle alle Laufwerke, bis 1TB frei bleibt. | ||
| **Beispiel mit 8TB, 3TB und 2TB Laufwerken** | ||
|
|
||
| <h4>Am besten für:</h4> | ||
| 1. **Erster Durchgang:** Fülle 8TB-Laufwerk, bis 4TB frei bleiben (die Hälfte von 8TB). | ||
| 2. **Zweiter Durchgang:** Fülle 8TB/3TB-Laufwerke, bis 2TB frei bleiben. | ||
| 3. **Dritter Durchgang:** Fülle alle Laufwerke, bis 1TB frei bleibt. | ||
|
|
||
| - Medienserver (z.B. Plex) | ||
| - Szenarien, in denen das Halten von Dateien auf weniger Festplatten die Effizienz beim Ausschalten verbessert | ||
| - Arrays mit gemischten Laufwerksgrößen | ||
| **Am besten für:** | ||
|
|
||
| :::Hinweis | ||
| High-Water ist die Standardmethode und funktioniert gut für die meisten Benutzer. Es reduziert das Rattern der Festplatten im Vergleich zu "Most-free." | ||
| ::: | ||
| </TabItem> | ||
| - Medienserver (z.B. Plex) | ||
| - Szenarien, in denen das Halten von Dateien auf weniger Festplatten die Effizienz beim Ausschalten verbessert | ||
| - Arrays mit gemischten Laufwerksgrößen | ||
|
|
||
| :::note | ||
|
|
||
| Um Laufwerksfreigaben zu aktivieren: | ||
|
|
||
| <TabItem value="am meisten frei" label="Am meisten frei"> | ||
| <h4>Wie es funktioniert</h4> | ||
| ::: | ||
|
|
||
| Die **Most-free**-Methode wählt die Festplatte mit dem meisten freien Speicherplatz für jede neue Datei aus. Dies maximiert die Speichereffizienz, erhöht jedoch das Rattern der Festplatten. | ||
| #### Am meisten frei | ||
|
|
||
| <h4>Leistungs-Auswirkungen</h4> | ||
| Hier ist eine kurze Übersicht darüber, wofür jede Standardfreigabe ist: | ||
|
|
||
| - Häufige Laufwerkswechsel halten mehrere Laufwerke eingeschaltet | ||
| - May reduce %%parity|parity%% write speeds due to overlapping operations | ||
| Die **Most-free**-Methode wählt die Festplatte mit dem meisten freien Speicherplatz für jede neue Datei aus. Dies maximiert die Speichereffizienz, erhöht jedoch das Rattern der Festplatten. | ||
|
|
||
| <h4>Am besten für:</h4> | ||
| Aus Sicherheitsgründen ist es am besten, Ihre Freigaben im *Privat*-Modus zu halten und nur vertrauenswürdigen Benutzern Zugriff zu gewähren. | ||
| ::: | ||
|
|
||
| - Workflows mit hohem Durchsatz (z.B. Videobearbeitung) | ||
| - Temporary or %%cache|cache%%-like data | ||
| - Arrays, bei denen die Leistung höher bewertet wird als Energieeinsparungen | ||
| - Häufige Laufwerkswechsel halten mehrere Laufwerke eingeschaltet | ||
| - May reduce %%parity|parity%% write speeds due to overlapping operations | ||
|
|
||
| :::tip | ||
| Combine with **%%split level|split-level%%** settings to group related files despite frequent disk switching. | ||
| ::: | ||
| </TabItem> | ||
| **Am besten für:** | ||
|
|
||
| <TabItem value="auffüllen" label="Auffüllen"> | ||
| <h4>Wie es funktioniert</h4> | ||
| - Workflows mit hohem Durchsatz (z.B. Videobearbeitung) | ||
| - Temporary or %%cache|cache%%-like data | ||
| - Arrays, bei denen die Leistung höher bewertet wird als Energieeinsparungen | ||
|
|
||
| Die **Auffüllmethode** schreibt der Reihe nach auf Laufwerke, bis sie die **Mindestfreiraum**-Schwelle erreichen, dann auf das nächste Laufwerk. | ||
| :::tip | ||
|
|
||
| <h4>Anforderungen</h4> | ||
| Combine with %%split level|split-level%% settings to group related files despite frequent disk switching. | ||
|
|
||
| - Immer **Mindestfreiraum** festlegen (z.B. 2x größte Dateigröße) | ||
| - **Split-Level** konfigurieren, um Dateigruppierung zu steuern | ||
| ::: | ||
|
|
||
| <h4>Am besten für:</h4> | ||
| #### Dateien von einer Netzwerkfreigabe übertragen | ||
|
|
||
| - Statische Datenarchive | ||
| - Benutzer, die manuelle Laufwerksverwaltung bevorzugen | ||
| - Arrays mit identischen Laufwerksgrößen | ||
| Hier ist eine kurze Übersicht darüber, wofür jede Standardfreigabe ist: | ||
|
|
||
| :::Achtung | ||
| Ohne konfigurierten **Mindestfreier Speicherplatz** treten "Datenträger voll"-Fehler auf, wenn eine Festplatte fast voll ist. | ||
| ::: | ||
| </TabItem> | ||
| </Tabs> | ||
| Die **Auffüllmethode** schreibt der Reihe nach auf Laufwerke, bis sie die **Mindestfreiraum**-Schwelle erreichen, dann auf das nächste Laufwerk. | ||
|
|
||
| Unraid enthält **Midnight Commander** (`mc`), einen textbasierten Dateimanager mit zwei Fenstern. Sie können darauf über das [Web-Terminal](../../system-administration/advanced-tools/command-line-interface.mdx) zugreifen. | ||
|
|
||
| - **Öffnen Sie das Web-Terminal:** Diese Option finden Sie im Menü oben rechts der Unraid %%WebGUI|web-gui%%. | ||
| - **Midnight Commander starten:** | ||
|
|
||
| **Am besten für:** | ||
|
|
||
| - Statische Datenarchive | ||
| - Benutzer, die manuelle Laufwerksverwaltung bevorzugen | ||
| - Arrays mit identischen Laufwerksgrößen | ||
|
|
||
| :::caution | ||
|
|
||
| Ohne **Mindestfreiraum**-Konfiguration treten "Laufwerk voll"-Fehler auf, wenn ein Laufwerk fast die Kapazität erreicht. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Severe content misalignment in Allocation Profile section.
This section has multiple blocks of misplaced content:
-
Lines 285, 291, 315, 339: The phrase "Hier ist eine kurze Übersicht darüber, wofür jede Standardfreigabe ist" (overview of default shares) is repeated 4 times but belongs to the "Standardfreigaben" section (line 470), not here.
-
Lines 307-311: Content about enabling disk shares is misplaced under the High-Water subsection.
-
Line 337: The heading "#### Dateien von einer Netzwerkfreigabe übertragen" (Transfer files from network share) is completely unrelated to allocation methods—this should be "#### Auffüllen" (Fill-up) to match the content below it.
-
Lines 343-347: Content about Midnight Commander and Web Terminal doesn't belong in the allocation method section.
This appears to be a significant translation/merge error. The allocation method explanations (High-Water at 293-305, Most-free at 317-329, Fill-up at 341/348-357) are present but corrupted by misplaced content from other sections.
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx`
around lines 283 - 358, The "Zuweisungsprofil" section contains misplaced and
repeated content: remove the four duplicate sentences "Hier ist eine kurze
Übersicht darüber, wofür jede Standardfreigabe ist" from the allocation profile
subsections (they belong in the "Standardfreigaben" section), move the "Um
Laufwerksfreigaben zu aktivieren:" block out of the "Hochwasser (Empfohlen)"
subsection into the proper "Standardfreigaben" or disk-shares configuration
section, rename the heading "#### Dateien von einer Netzwerkfreigabe übertragen"
to "#### Auffüllen" to match the Fill-up method content, and relocate the
Midnight Commander / Web-Terminal paragraph to the network/share tools section
(e.g., where command-line tools are documented); ensure the remaining
High-Water, Most-free, and Auffüllen subsections contain only the
allocation-method explanations and examples.
| info[Examples von Umgebungsvariablen] | ||
|
|
There was a problem hiding this comment.
Missing ::: prefix for info admonition.
Line 16 has invalid syntax: info[Examples von Umgebungsvariablen] is not valid Docusaurus/MDX. Admonitions must begin with ::: followed by the type. This will cause rendering errors.
🐛 Proposed fix
-info[Examples von Umgebungsvariablen]
+:::info[Examples von Umgebungsvariablen]📝 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.
| info[Examples von Umgebungsvariablen] | |
| :::info[Examples von Umgebungsvariablen] | |
🧰 Tools
🪛 LanguageTool
[grammar] ~16-~16: Korrigiere die Fehler
Context: ...ind und welche Werte gültig sind. info[Examples von Umgebungsvariablen] - `TZ=America/...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdx`
around lines 16 - 17, Replace the invalid admonition line "info[Examples von
Umgebungsvariablen]" with a proper Docusaurus admonition by prefixing it with
":::". For example, change that line to start with ":::info" (e.g., ":::info
Examples von Umgebungsvariablen") and ensure you add the matching closing ":::".
Update the admonition title/content placement in the file to follow the ":::info
... \<content\> :::" pattern so rendering succeeds.
i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
Show resolved
Hide resolved
| :::note | ||
|
|
||
| This option will **only** appear in the Navigation Bar if your Unraid server meets the %%hardware virtualization|hvm%% requirements. | ||
|
|
||
| :::note | ||
|
|
||
| Esta opción **solo** aparecerá en la Barra de Navegación si tu servidor Unraid cumple con los requisitos de %%virtualización de hardware|hvm%%. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Malformed note block structure and untranslated English content.
The note block has two issues:
- Two
:::noteopeners (lines 76 and 80) but only one:::closer (line 84) — this will cause rendering errors in Docusaurus - English text remains on line 78 in a Spanish localization file
🐛 Proposed fix to consolidate into a single Spanish note block
:::note
-
-This option will **only** appear in the Navigation Bar if your Unraid server meets the %%hardware virtualization|hvm%% requirements.
-
-:::note
Esta opción **solo** aparecerá en la Barra de Navegación si tu servidor Unraid cumple con los requisitos de %%virtualización de hardware|hvm%%.
:::📝 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.
| :::note | |
| This option will **only** appear in the Navigation Bar if your Unraid server meets the %%hardware virtualization|hvm%% requirements. | |
| :::note | |
| Esta opción **solo** aparecerá en la Barra de Navegación si tu servidor Unraid cumple con los requisitos de %%virtualización de hardware|hvm%%. | |
| ::: | |
| :::note | |
| Esta opción **solo** aparecerá en la Barra de Navegación si tu servidor Unraid cumple con los requisitos de %%virtualización de hardware|hvm%%. | |
| ::: |
🧰 Tools
🪛 LanguageTool
[grammar] ~82-~82: Corrige la mayúscula.
Context: ...e Esta opción solo aparecerá en la Barra de Navegación si tu servidor Unraid cum...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~82-~82: Corrige la mayúscula.
Context: ...pción solo aparecerá en la Barra de Navegación si tu servidor Unraid cumple con los re...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
🤖 Prompt for AI Agents
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx`
around lines 76 - 84, Fix the malformed note block by consolidating the
duplicate `:::note` openers into a single `:::note` block, remove the leftover
English sentence so only the Spanish translation remains, and ensure the block
is properly closed with a single `:::`; locate the offending `:::note` markers
and the English line near the `tour-the-web-gui.mdx` snippet and replace them
with one well-formed Spanish note containing the translated text.
There was a problem hiding this comment.
Actionable comments posted: 3
Note
Due to the large number of review comments, Critical 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 (34)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/local.mdx (1)
7-8:⚠️ Potential issue | 🟡 MinorUntranslated English content in German localization file.
Lines 7–8 contain English text while the rest of the file is in German. These lines should be translated for consistency with the localization.
3. For best results and to ensure all %%syslog|syslog%% data (including boot events) is captured, set the **Remote %%syslog server|syslog-server%%** field to your server's own IP address (the "Loopback method"), or the %%syslog|syslog%% will not be saved to the set share. - This ensures %%syslog|syslog%% events are both stored locally and persist across reboots, without writing to the flash drive.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/monitor-performance/smart-reports-and-disk-health.mdx (1)
22-26:⚠️ Potential issue | 🟡 MinorDuplicate sentence detected.
Line 22 and line 26 contain identical text:
"Einige %%SMART|smart%% Attribute, die Unraid standardmäßig überwacht, umfassen:". One of these should be removed.Proposed fix to remove the duplicate
## Wie Unraid SMART nutzt -Einige %%SMART|smart%% Attribute, die Unraid standardmäßig überwacht, umfassen: - Für eine genauere Betrachtung der Daten eines Laufwerks von %%SMART|smart%%, klicken Sie auf dessen Namen im **Main**-Tab der Unraid %%WebGUI|web-gui%%. Einige %%SMART|smart%% Attribute, die Unraid standardmäßig überwacht, umfassen:i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md (1)
601-710:⚠️ Potential issue | 🟡 MinorNormalize German quote pairing in the changelog list.
Multiple entries use „ opening quotes with " closing quotes. Please normalize to matching German quotes.
✅ Suggested fix
-- rsyslog: Defektes „Syslog auf Flash spiegeln" reparieren +- rsyslog: Defektes „Syslog auf Flash spiegeln“ reparieren ... -- WebGUI: „Sicherer Modus" Einmalige Sicherheitsmodus Neustart-Option hinzugefügt +- WebGUI: „Sicherer Modus“ Einmalige Sicherheitsmodus Neustart-Option hinzugefügt ... -- WebGUI: Neue Einstellung „Benutzerfreigabezuweisung aktivieren" für Cache-Pool hinzugefügt +- WebGUI: Neue Einstellung „Benutzerfreigabezuweisung aktivieren“ für Cache-Pool hinzugefügt ... -- WebGUI: VM-Manager: Neue Einstellung „Netzwerkmodell" +- WebGUI: VM-Manager: Neue Einstellung „Netzwerkmodell“ ... -[„WireGuard" und das „WireGuard"-Logo sind eingetragene Marken von Jason A. Donenfeld.](https://www.wireguard.com/) +[„WireGuard“ und das „WireGuard“-Logo sind eingetragene Marken von Jason A. Donenfeld.](https://www.wireguard.com/)i18n/es/docusaurus-plugin-content-docs/current/contribute/style-guide.mdx (1)
169-169:⚠️ Potential issue | 🟡 MinorFix duplicate numbering.
The list item has "3. 3." which appears to be a copy/paste error.
✏️ Proposed fix
-3. 3. La [página del glosario](../glossary.mdx) se actualizará automáticamente para incluir nuevos términos. +3. La [página del glosario](../glossary.mdx) se actualizará automáticamente para incluir nuevos términos.i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx (1)
15-25:⚠️ Potential issue | 🟠 MajorMalformed admonition block creates duplicate content.
The
:::importantblock at lines 15-19 appears incomplete—it opens with[Security erinnerung], contains only the partial phrase "Fernzugriff über Unraid Connect bietet:" and then closes. This same phrase is then repeated at line 21 outside the block, followed by the bullet points.This looks like a merge/translation artifact. Either:
- The important block should contain actual security reminder content, or
- The block should be removed entirely
🛠️ Suggested fix (Option 1: Remove incomplete block)
-:::important[Security erinnerung] - -Fernzugriff über Unraid Connect bietet: - -::: - Fernzugriff über Unraid Connect bietet:i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (4)
142-144:⚠️ Potential issue | 🔴 CriticalCSS property names must remain in English.
The inline style uses Spanish translations for CSS properties (
margen,maxAnchura,columna,centro), but CSS only recognizes English property names. This will cause the styling to fail silently.🐛 Proposed fix
-<div style={{ margen: 'auto', maxAnchura: '600px', display: 'flex', flexDirection: 'columna', alignItems: 'centro' }}> +<div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}>
177-179:⚠️ Potential issue | 🔴 CriticalCSS property names must remain in English.
Same issue as above—Spanish translations for CSS properties will break the layout.
🐛 Proposed fix
-<div style={{ margen: 'auto', maxAnchura: '600px', display: 'flex', flexDirection: 'columna', alignItems: 'centro' }}> +<div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}>
194-196:⚠️ Potential issue | 🔴 CriticalCSS property names must remain in English.
Same CSS translation issue affecting layout rendering.
🐛 Proposed fix
-<div style={{ margen: 'auto', maxAnchura: '600px', display: 'flex', flexDirection: 'columna', alignItems: 'centro' }}> +<div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}>
148-168:⚠️ Potential issue | 🟠 MajorDuplicate "Gestión de licencias" sections.
There are two
## Gestión de licenciasheaders (lines 148 and 168). The first one (line 148) appears to be misplaced—it precedes the Tabs component that belongs to the Personalización section above. This looks like a merge or translation synchronization error.Review the section structure: remove the duplicate header at line 148 and ensure the Tabs component (lines 152-164) remains under the
## Personalizaciónsection.i18n/es/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx (1)
34-40:⚠️ Potential issue | 🟠 MajorDuplicate and likely misplaced section header.
Line 34 adds "### Seguridad y Autenticación" as a subsection under "Infraestructura Principal", but line 41 already has "## Seguridad y Autenticación" as a main section. This creates structural confusion.
Additionally, the table content (lines 36-39) about "Hacer API Código Abierto" and "Herramientas para Desarrolladores de Complementos" doesn't relate to security/authentication—it appears to belong under infrastructure planning.
Proposed fix - rename subsection header
-### Seguridad y Autenticación +### Planificado 📅i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (1)
98-109:⚠️ Potential issue | 🟡 MinorAvoid duplicated “Cifrado de copia de seguridad” content.
The paragraph at Lines 98–100 is duplicated again under “Privacidad y seguridad → Cifrado de copia de seguridad” (Lines 107–109). Consider keeping it only once to reduce repetition.
🧹 Suggested fix (keep the later subsection only)
-## Cifrado de copia de seguridad - -Actualmente, las copias de seguridad de flash se almacenan en la nube sin encriptación. Como precaución, los datos sensibles, incluidas todas las contraseñas de usuario y root, así como todas las claves de %%WireGuard|wireguard%%, nunca se incluyen en la copia de seguridad.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx (1)
56-74:⚠️ Potential issue | 🟠 MajorCritical structural issues: duplicate caution block and duplicated content.
Duplicate caution block declaration: Lines 57 and 58 both declare
:::caution[RAM Übertaktungsrisiken und Empfehlungen]. Only one should exist.Duplicated heading: "Risiken der Übertaktung:" appears on both line 56 and line 65.
Duplicated paragraph: Lines 72-73 contain identical text to lines 87-88 ("Die Systemstabilität hängt von mehr ab als...").
Mismatched closing tags: The structure has mismatched
:::opening/closing tags that will break rendering.🔧 Proposed fix
-**Risiken der Übertaktung:** -:::caution[RAM Übertaktungsrisiken und Empfehlungen] :::caution[RAM Übertaktungsrisiken und Empfehlungen] **Fehlerbehebung:** Wenn Memtest86+ bestanden wird, Sie aber immer noch Probleme haben, deaktivieren Sie XMP/AMP und versuchen Sie es erneut. Der Leistungsunterschied ist in der Regel minimal, jedoch kann die Stabilitätsverbesserung erheblich sein. ::: **Intel XMP und AMD AMP Profile sind Übertaktungen.** Für die beste Stabilität sollten Sie RAM immer mit SPD-Geschwindigkeiten betreiben, nicht mit XMP/AMP-Geschwindigkeiten. **Risiken der Übertaktung:** - Systeminstabilität und zufällige Abstürze - Datenkorruption und Dateisystemfehler - Verkürzte Hardware-Lebensdauer - Inkompatibilität mit anderen Komponenten -Die Systemstabilität hängt von mehr ab als nur der RAM- oder CPU-Leistung. Mehrere Hardware- und Softwarekomponenten arbeiten zusammen, um einen zuverlässigen Betrieb zu gewährleisten. Dieser Abschnitt deckt die Schlüsselbereiche ab, die die Stabilität Ihres Unraid-Servers beeinflussen, und bietet praktische Schritte, um Probleme zu verhindern und zu lösen. - -:::i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx (2)
34-34:⚠️ Potential issue | 🟡 MinorTranslate English sentence to German.
This line contains an English sentence in the German documentation file.
Proposed translation
-For instance, if you use an %%FTP|ftp%% client to connect to your Unraid server, you can easily transfer large files and even pause and resume your uploads or downloads if needed. +Wenn Sie beispielsweise einen %%FTP|ftp%%-Client verwenden, um eine Verbindung zu Ihrem Unraid-Server herzustellen, können Sie große Dateien einfach übertragen und Ihre Uploads oder Downloads bei Bedarf sogar pausieren und fortsetzen.
54-54:⚠️ Potential issue | 🟡 MinorTranslate English sentence to German.
This line contains an English sentence that should be translated for the German documentation.
Proposed translation
-By tweaking these options, you can manage who can see and access each share, making it easier to keep everything secure while ensuring the right people have the access they need, whether they are using %%SMB|samba%%, %%NFS|nfs%%, or %%FTP|ftp%% connections. +Durch Anpassen dieser Optionen können Sie verwalten, wer jede Freigabe sehen und darauf zugreifen kann, was es einfacher macht, alles sicher zu halten und gleichzeitig sicherzustellen, dass die richtigen Personen den benötigten Zugriff haben, unabhängig davon, ob sie %%SMB|samba%%-, %%NFS|nfs%%- oder %%FTP|ftp%%-Verbindungen verwenden.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx (2)
42-42:⚠️ Potential issue | 🟡 MinorTranslate English sentence to German.
This line contains untranslated English content in the German documentation.
Proposed translation
-The %%WebGUI|web-gui%% will automatically use the selected proxy for outgoing system traffic. If you have open web terminals or %%SSH|ssh%% sessions, close and reopen them to apply the new proxy settings. This usage is transparent—monitor proxy server logs to verify activity. +Das %%WebGUI|web-gui%% verwendet automatisch den ausgewählten Proxy für ausgehenden Systemverkehr. Wenn Sie offene Web-Terminals oder %%SSH|ssh%%-Sitzungen haben, schließen Sie diese und öffnen Sie sie erneut, um die neuen Proxy-Einstellungen anzuwenden. Diese Nutzung ist transparent – überwachen Sie die Proxy-Server-Protokolle, um die Aktivität zu überprüfen.
145-167:⚠️ Potential issue | 🟠 MajorDuplicate section headers with conflicting content.
Lines 145 and 158 both have the same section header "### VPN-Tunneling-Zugriff für das System konfigurieren" but contain different instructions:
- Lines 145-156: Instructions mentioning Firefox container, config import, DNS leak test
- Lines 158-167: Different instructions also mentioning Firefox but with different steps
This appears to be duplicate/conflicting content that should be consolidated or one section renamed.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx (1)
189-189:⚠️ Potential issue | 🟠 MajorDuplicate section header.
"### Konfigurationen, die vermieden werden sollten" appears twice in the document (lines 154 and 189). The second occurrence at line 189 contains a table that makes more sense for "configurations to avoid." Consider removing or renaming the first section (lines 154-179) which appears to contain misplaced content.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx (2)
151-151:⚠️ Potential issue | 🟡 MinorUntranslated English sentence.
Line 151 contains an English sentence that should be translated to German.
🌐 Suggested German translation
-Unraid identifies data drives by detecting existing valid file systems. %%Parity drives|parity-drives%%, which lack a file system, appear unmountable. This characteristic allows you to distinguish %%parity drives|parity-drives%% from data drives after booting with a new flash device. +Unraid erkennt Datenlaufwerke durch die Erkennung vorhandener gültiger Dateisysteme. %%Parity drives|parity-drives%%, die kein Dateisystem haben, erscheinen als nicht einbindbar. Diese Eigenschaft ermöglicht es Ihnen, %%parity drives|parity-drives%% von Datenlaufwerken zu unterscheiden, nachdem Sie mit einem neuen Flash-Gerät gebootet haben.
188-188:⚠️ Potential issue | 🟡 MinorUntranslated English sentence in identification method.
Line 188 contains an English sentence that should be translated.
🌐 Suggested German translation
- 3. Confirm that the number of unmountable drives matches your %%parity|parity%% count. + 3. Bestätigen Sie, dass die Anzahl der nicht einbindbaren Laufwerke mit Ihrer %%parity|parity%%-Anzahl übereinstimmt.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (1)
244-270:⚠️ Potential issue | 🔴 CriticalMajor content structure issue - wrong content under section header.
The section "Mindestfreier Speicherplatz für einen Cache-Pool" (line 244) contains content about disk replacement and prerequisites that doesn't belong here. This same header also appears at line 274. The content between lines 246-264 appears to be misplaced from a disk replacement section.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx (2)
22-26:⚠️ Potential issue | 🟡 MinorSection heading mismatch with introductory text.
Line 22 introduces an H2 heading "## CPU-Pinning", but line 24 describes "Systemeinstellungen" (System Settings) as the broader category. Then line 26 repeats "### CPU-Pinning" as an H3. The H2 should likely be "## Systemeinstellungen" to match the introductory paragraph and maintain proper document hierarchy.
Proposed fix
-## CPU-Pinning +## Systemeinstellungen **Systemeinstellungen** ermöglichen Ihnen die Konfiguration wichtiger Funktionen wie Netzwerk-, Freigabe-, %%VM|vm%%- und Laufwerkseinstellungen. ### CPU-Pinning
214-226:⚠️ Potential issue | 🟠 MajorSection heading does not match content.
Line 214 introduces "## Benachrichtigungseinstellungen" (Notification Settings), but line 216 contains English text about "Network Services" and NFS configuration. This is a significant structural mismatch - the heading and content belong to different topics.
The actual Benachrichtigungseinstellungen content appears later at line 301. Consider either:
- Renaming this H2 to "## Netzwerkdienste" (Network Services), or
- Moving the notification content here and relocating the network services content
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx (1)
17-17:⚠️ Potential issue | 🟠 MajorTranslate remaining English sentences.
Several lines still contain untranslated English content:
- Line 17: "Ensure you have enough free space..."
- Line 56: "Store %%VM|vm%% images on a %%cache pool|cache-pool%%..."
- Line 76: "-O raw: Sets the output format to raw..."
These should be translated for consistency with the rest of the German documentation.
Suggested translations
-Ensure you have enough free space in your **%%array|array%%** or **%%cache pool|cache-pool%%** to accommodate the new virtual disk image. +Stellen Sie sicher, dass Sie genügend freien Speicherplatz in Ihrem **%%Array|array%%** oder **%%Cache-Pool|cache-pool%%** für das neue virtuelle Festplatten-Image haben.-Store %%VM|vm%% images on a **%%cache pool|cache-pool%%** instead of an %%array|array%% for the [best performance](./overview-and-system-prep.mdx#user-shares-for-virtualization). +Speichern Sie %%VM|vm%%-Images auf einem **%%Cache-Pool|cache-pool%%** anstelle eines %%Arrays|array%% für [beste Leistung](./overview-and-system-prep.mdx#user-shares-for-virtualization).-- `-O raw`: Sets the output format to raw (Unraid's default). +- `-O raw`: Setzt das Ausgabeformat auf raw (Unraids Standard).Also applies to: 56-56, 76-76
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx (1)
171-177:⚠️ Potential issue | 🟡 MinorUntranslated English content in German document.
Several lines remain in English and should be translated to German for consistency:
- Line 171: "Note the serial numbers of drives that do not mount..."
- Line 172: "Do not click Format on any drive..."
- Line 175: "Go to Tools → New Config..."
- Line 177: "Check Parity is Valid only if..."
i18n/es/docusaurus-plugin-content-docs/current/API/cli.mdx (1)
9-13:⚠️ Potential issue | 🟠 MajorFix malformed admonition header to avoid MDX parse failure.
The admonition opener is missing the closing bracket, which can break MDX parsing.
✅ Proposed fix
-:::info[Command Estructura +:::info[Estructura de comandos]i18n/es/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx (2)
50-61:⚠️ Potential issue | 🟡 MinorAvoid repeating the same “Cuándo usar…” heading twice.
Two consecutive sections use the same header; consider differentiating the first (capabilities) from the second (use cases).
✍️ Suggested tweak
-**Cuándo usar el Modo Simple:** +**Qué permite el Modo Simple:**
80-86:⚠️ Potential issue | 🟡 MinorRemove duplicate “Ejemplos de Modo Simple” heading.
The section title is repeated at both H2 and H3 levels.
🧹 Proposed fix
-### Ejemplos de Modo Simple - #### Permitir Dominio Corporativoi18n/es/docusaurus-plugin-content-docs/current/API/index.mdx (1)
82-93:⚠️ Potential issue | 🟡 MinorUse a fully Spanish label for the capabilities block.
“Core Capacidades” mixes English/Spanish. Consider “Capacidades principales” or “Capacidades clave”.
✍️ Proposed fix
-:::info[Core Capacidades] +:::info[Capacidades principales]i18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx (2)
209-222:⚠️ Potential issue | 🟡 MinorUse a fully Spanish label for the security best practices block.
“Security Mejores Prácticas” mixes languages.
✍️ Proposed fix
-:::info[Security Mejores Prácticas] +:::info[Mejores prácticas de seguridad]
240-254:⚠️ Potential issue | 🟡 MinorUse a fully Spanish label for the error-messages note.
“Common Mensajes de Error” mixes languages; consider “Mensajes de error comunes”.
✍️ Proposed fix
-:::note[Common Mensajes de Error] +:::note[Mensajes de error comunes]i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (1)
11-18:⚠️ Potential issue | 🟡 MinorRemove the duplicated intro paragraph and localize the admonition title.
Line 13 repeats the same paragraph already present at Line 17, and the title “Special gracias” mixes languages. Consider keeping the paragraph once and using a Spanish title.
Proposed fix
-:::important[Special gracias] +:::important[Agradecimiento especial] @@ -%%ZFS|zfs%% aporta integridad de datos avanzada, configuraciones de almacenamiento flexibles y alto rendimiento a tu sistema Unraid. Esta guía explica los conceptos básicos de %%ZFS|zfs%% y te guía en la gestión de pools %%ZFS|zfs%% directamente desde el %%WebGUI|web-gui%% de Unraid. Ya sea que estés configurando un nuevo almacenamiento %%ZFS|zfs%% o integrando un pool existente, encontrarás los pasos y contexto que necesitas para comenzar con confianza. - -::: - -%%ZFS|zfs%% aporta integridad de datos avanzada, configuraciones de almacenamiento flexibles y alto rendimiento a tu sistema Unraid. Esta guía explica los conceptos básicos de %%ZFS|zfs%% y te guía en la gestión de pools %%ZFS|zfs%% directamente desde el %%WebGUI|web-gui%% de Unraid. Ya sea que estés configurando un nuevo almacenamiento %%ZFS|zfs%% o integrando un pool existente, encontrarás los pasos y contexto que necesitas para comenzar con confianza. +%%ZFS|zfs%% aporta integridad de datos avanzada, configuraciones de almacenamiento flexibles y alto rendimiento a tu sistema Unraid. Esta guía explica los conceptos básicos de %%ZFS|zfs%% y te guía en la gestión de pools %%ZFS|zfs%% directamente desde el %%WebGUI|web-gui%% de Unraid. Ya sea que estés configurando un nuevo almacenamiento %%ZFS|zfs%% o integrando un pool existente, encontrarás los pasos y contexto que necesitas para comenzar con confianza. +:::i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (1)
11-18:⚠️ Potential issue | 🟡 MinorRemove the duplicated intro paragraph and localize the admonition title.
Line 13 repeats Line 17, and “Special Danke” mixes languages.
Proposed fix
-:::important[Special Danke] +:::important[Besonderer Dank] @@ -%%ZFS|zfs%% bietet erweiterte Datenintegrität, flexible Speicherlösungen und hohe Leistung für Ihr Unraid-System. Dieser Leitfaden erklärt die Kernkonzepte von %%ZFS|zfs%% und führt Sie durch die Verwaltung von %%ZFS|zfs%%-Pools direkt über das Unraid %%WebGUI|web-gui%%. Egal, ob Sie neuen %%ZFS|zfs%%-Speicher einrichten oder einen bestehenden Pool integrieren, hier finden Sie die Schritte und den Kontext, die Sie benötigen, um sicher zu starten. - -::: - -%%ZFS|zfs%% bietet erweiterte Datenintegrität, flexible Speicherlösungen und hohe Leistung für Ihr Unraid-System. Dieser Leitfaden erklärt die Kernkonzepte von %%ZFS|zfs%% und führt Sie durch die Verwaltung von %%ZFS|zfs%%-Pools direkt über das Unraid %%WebGUI|web-gui%%. Egal, ob Sie neuen %%ZFS|zfs%%-Speicher einrichten oder einen bestehenden Pool integrieren, hier finden Sie die Schritte und den Kontext, die Sie benötigen, um sicher zu starten. +%%ZFS|zfs%% bietet erweiterte Datenintegrität, flexible Speicherlösungen und hohe Leistung für Ihr Unraid-System. Dieser Leitfaden erklärt die Kernkonzepte von %%ZFS|zfs%% und führt Sie durch die Verwaltung von %%ZFS|zfs%%-Pools direkt über das Unraid %%WebGUI|web-gui%%. Egal, ob Sie neuen %%ZFS|zfs%%-Speicher einrichten oder einen bestehenden Pool integrieren, hier finden Sie die Schritte und den Kontext, die Sie benötigen, um sicher zu starten. +:::i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx (1)
17-22:⚠️ Potential issue | 🟡 MinorUntranslated English blocks in German locale
Several paragraphs remain in English (e.g., Lines 17‑22, 34‑35, 42, 56, 66, 82, 96, 146‑148, 173‑206, 231‑236, 241, 255, 275, 322‑333, 364‑371, 420‑431, 487‑500, 523‑533). Please translate these to German or confirm they are intentionally left in English.
Also applies to: 34-35, 42-42, 56-56, 66-66, 82-82, 96-96, 146-148, 173-206, 231-236, 241-241, 255-255, 275-275, 322-333, 364-371, 420-431, 487-500, 523-533
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx (1)
242-244:⚠️ Potential issue | 🟡 MinorHeading wording is ungrammatical in German.
Consider “Neuformatieren eines Laufwerks” (or similar).✍️ Suggested revision
-## Neusformatiert eines Laufwerks +## Neuformatieren eines Laufwerks
🤖 Fix all issues with AI agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx`:
- Around line 53-66: The MDX admonitions are improperly nested: the opened tip
block (::::tip) and the inner note (:::note) are not closed before the caution
(:::caution) begins, breaking rendering; fix by closing the inner note with :::
right after the note content, then open the caution block and close it with :::
after its content, and finally close the outer tip with ::::: so that the
sequence uses :::note ... :::, :::caution ... :::, and ends with ::::: to
properly terminate the outer tip.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdx`:
- Around line 16-24: The admonition block is malformed: replace the invalid line
`info[Examples von Umgebungsvariablen]` with a proper Docusaurus admonition
opener `:::info Beispiele von Umgebungsvariablen` (note the German translation
and the leading `:::`), ensure the environment variable list follows inside that
block, and remove the stray/mismatched extra `:::` so there is exactly one
matching closing `:::` after the list to properly close the admonition.
In `@i18n/es/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx`:
- Around line 153-167: Remove the duplicated MDX admonition titled ":::tip[Have
Soporte]" so only the new ":::tip[Envía tu Feedback]" block remains;
specifically delete the entire old block that starts with ":::tip[Have Soporte]"
and its closing ":::" to fix the broken MDX structure and eliminate duplicate
content.
🟠 Major comments (24)
i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx-153-153 (1)
153-153:⚠️ Potential issue | 🟠 MajorUntranslated English word in German label.
"Have Unterstützung" mixes English ("Have") with German. This should be fully translated for consistency. Consider alternatives like "Unterstützung & Feedback" or "Hilfe & Unterstützung".
🌐 Proposed fix
-:::tip[Have Unterstützung] +:::tip[Unterstützung & Feedback]i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx-134-135 (1)
134-135:⚠️ Potential issue | 🟠 MajorDuplicate line - remove one instance.
Lines 134 and 135 contain identical content. This appears to be a copy-paste error.
🔧 Proposed fix
:::info[Full Veröffentlichungshistorie] Für eine vollständige Liste aller Veröffentlichungen, Änderungsprotokolle und Download-Links besuchen Sie die [Unraid API GitHub Releases](https://github.com/unraid/api/releases) Seite. -Für eine vollständige Liste aller Veröffentlichungen, Änderungsprotokolle und Download-Links besuchen Sie die [Unraid API GitHub Releases](https://github.com/unraid/api/releases) Seite. :::i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdx-99-103 (1)
99-103:⚠️ Potential issue | 🟠 MajorContent mismatch: Caution block discusses changing users instead of deletion warning.
This caution block is under the "Benutzer löschen" (Delete user) section, but the content talks about changing user accounts (
ändern). The same text appears verbatim at line 116 in the "Benutzer ändern" section where it belongs.A deletion section should warn users about the permanence of the action, not provide guidance about changing accounts. This appears to be a translation or copy-paste error.
Consider restoring an appropriate deletion warning, such as:
:::caution -Sie können ein Benutzerkonto in Unraid ändern, wenn der Benutzer sein Passwort vergessen hat oder einen anderen Zugriff auf die freigegebenen Ordner benötigt. +Das Löschen eines Benutzerkontos ist dauerhaft und kann nicht rückgängig gemacht werden. Stellen Sie sicher, dass Sie das richtige Konto ausgewählt haben. :::i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx-87-87 (1)
87-87:⚠️ Potential issue | 🟠 MajorUntranslated English text in step 2.
Line 87 contains English text that should be translated to German for consistency with the rest of the document:
-2. Enter the %%SMB|samba%% address of your Unraid server. For example, use the format `smb://[server-ip]/[Time Machine share name]` and click **Connect**. +2. Geben Sie die %%SMB|samba%%-Adresse Ihres Unraid-Servers ein. Verwenden Sie beispielsweise das Format `smb://[server-ip]/[Time Machine share name]` und klicken Sie auf **Verbinden**.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx-107-111 (1)
107-111:⚠️ Potential issue | 🟠 MajorOrphaned tip block with misplaced content.
This
:::tipblock contains a sentence that appears to belong in the Troubleshooting section below ("Wenn Time Machine-Sicherungen fehlschlagen oder unzuverlässig werden:") but provides no actual tip content before closing. This creates a confusing empty admonition.Either:
- Remove this orphaned tip block entirely, or
- Add meaningful tip content for the "Mehrere Time Machine-Setups" section
Suggested fix (remove orphaned block)
## Mehrere Time Machine-Setups -:::tip - -Wenn Time Machine-Sicherungen fehlschlagen oder unzuverlässig werden: - -::: - Für zusätzliche Hilfe bei der Fehlerbehebung siehe [Fehlerbehebung](../../troubleshooting/troubleshooting.mdx) oder besuchen Sie die [Unraid-Foren](https://forums.unraid.net/).i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx-200-228 (1)
200-228:⚠️ Potential issue | 🟠 MajorDuplicate "Cierre de sesión" sections and orphaned text.
This section has several structural issues:
- Line 200 has orphaned text "Cuando cierres la sesión:"
- Lines 204-213 form one "Cierre de sesión" section
- Line 214 has another orphaned text "Cuando cierres la sesión:"
- Lines 218-227 form a second "Cierre de sesión" section
The content from lines 208-213 and 222-227 appears to be uninstall-related content that is duplicated from the "Desinstalación del complemento" section (lines 230-237).
Remove the duplicate sections and orphaned text, keeping only the final "Desinstalación del complemento" section for uninstall content.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx-112-114 (1)
112-114:⚠️ Potential issue | 🟠 MajorDuplicate section content: "Wartungserwartungen" appears twice with identical text.
Lines 112-114 and 127-129 contain:
- The same section title "Wartungserwartungen" (as
##and###)- The exact same paragraph text verbatim
This creates a confusing document structure. The section at line 127 should either be removed or renamed to something distinct (e.g., "Laufende Verantwortlichkeiten").
🐛 Proposed fix: remove duplicate heading and paragraph
### Einreichungsvoraussetzungen ... Beiträge werden vom Moderationsteam der Community-Anwendungen überprüft... -### Wartungserwartungen - -Entwickler, die Anwendungen in Community Applications veröffentlichen, werden erwartet, dass sie ihre Projekte pflegen, um die Kompatibilität und Zuverlässigkeit für die Unraid-Community sicherzustellen. Dieser Abschnitt umreißt die laufenden Verantwortlichkeiten, die zur Aufrechterhaltung der Qualität der verfügbaren Anwendungen beitragen. +### Laufende Verantwortlichkeiten Einmal veröffentlicht, werden Entwickler erwartet:Also applies to: 127-129
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx-130-132 (1)
130-132:⚠️ Potential issue | 🟠 MajorDuplicate section headers will cause anchor conflicts.
The section "Zugriffssicherheit für Freigaben" appears twice (lines 104 and 130), and "Halten Sie Ihren Server auf dem neuesten Stand" also appears twice (lines 132 and 161). This will cause issues with anchor links and navigation. Consider renaming one of each duplicate or restructuring the content.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx-37-61 (1)
37-61:⚠️ Potential issue | 🟠 MajorDuplicate content blocks detected.
Lines 37-48 and 49-61 contain duplicate
:::tipand:::infoblocks with nearly identical content. The first:::infoblock (line 43) still has the English word "Proactive" while the second one (line 55) has the correct German "Proaktive". Remove the duplicate blocks and keep only the corrected versions.🔧 Proposed fix - remove duplicate blocks
:::tip[Modern Backup-Strategie] - -Mit Unraid 7.0 und höher aktivieren Sie [Unraid Connect](../../../unraid-connect/overview-and-setup.mdx) für automatisierte Cloud-Backups Ihres Flash-Geräts und Ihrer Konfiguration. Erwägen Sie die Nutzung von Duplicati, rclone oder ähnlichen Tools für wichtige Dateien und Freigaben, um geplante Backups an lokalen, entfernt zugänglichen oder Cloud-Zielen zu erstellen. Testen Sie immer Ihren Wiederherstellungsprozess, um sicherzustellen, dass Ihre Backups im Bedarfsfall funktionieren. - -::: - -:::info[Proactive Überwachung und Unterstützung] - -- **Benachrichtigungen aktivieren:** Richten Sie Benachrichtigungen in ***Einstellungen → Benachrichtigungen*** ein, um sofort Benachrichtigungen über Systemprobleme zu erhalten. -- **Suchen Sie Expertenunterstützung:** Wenn Sie unsicher über Wiederherstellungsschritte sind, konsultieren Sie die [Unraid-Foren](https://forums.unraid.net/), bevor Sie Maßnahmen ergreifen. -- **Regelmäßige Gesundheitsprüfungen:** Behalten Sie die [SMART-Daten](../../system-administration/monitor-performance/smart-reports-and-disk-health.mdx) Ihrer Laufwerke im Auge und führen Sie regelmäßige Dateisystemüberprüfungen durch. - -:::tip[Modern Backup-Strategie] Mit Unraid 7.0 und höher aktivieren Sie [Unraid Connect](../../../unraid-connect/overview-and-setup.mdx) für automatisierte Cloud-Backups Ihres Flash-Geräts und Ihrer Konfiguration. Erwägen Sie die Nutzung von Duplicati, rclone oder ähnlichen Tools für wichtige Dateien und Freigaben, um geplante Backups an lokalen, entfernt zugänglichen oder Cloud-Zielen zu erstellen. Testen Sie immer Ihren Wiederherstellungsprozess, um sicherzustellen, dass Ihre Backups im Bedarfsfall funktionieren. ::: :::info[Proaktive Überwachung und Unterstützung]i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx-329-340 (1)
329-340:⚠️ Potential issue | 🟠 MajorRemove duplicate step sections in Xen to KVM migration.
The Xen to KVM migration section contains duplicate steps:
- "Schritt 5: Installieren Sie die VirtIO-Treiber" appears at lines 329–340 AND 408–427
- "Schritt 6: Finalisieren Sie die VM-Konfiguration" appears at lines 342–351 AND 429–452
The first occurrences (lines 329–361) appear incomplete. Remove these duplicates and keep only the complete versions in the
<details>blocks.Also applies to: 342-361, 408-452
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx-150-172 (1)
150-172:⚠️ Potential issue | 🟠 MajorContent organization issue: unrelated PCI binding paragraph in snapshot section.
Line 164 contains a paragraph about PCI device binding (
Bevor Sie eine GPU oder ein anderes PCI-Gerät einer %%virtuellen Maschine|vm%% zuweisen können...) that appears misplaced within the snapshot explanation section. This content should be relocated to the GPU-Passthrough or PCI binding section.Additionally, the admonition at line 154 uses mixed language (
:::info[How tipps]) - translate to:::info[Hinweise]or:::info[So funktioniert es].i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx-224-234 (1)
224-234:⚠️ Potential issue | 🟠 MajorTranslate remaining English sentences in migration sections.
Multiple lines still contain untranslated English:
- Line 224: "Start the %%array|array%% if it's not already running."
- Line 232: "Start the %%array|array%% if it's not already running."
- Line 317: "Always create a backup of your %%Xen|xen-hvm%% virtual disk..."
- Line 327: "To convert a Windows VM from %%Xen|xen-hvm%% to %%KVM|kvm%%..."
- Line 373: "Select the Windows version that matches..."
- Line 434: "Confirm that the primary %%vDisk|vdisk%% points to..."
These should be translated to German for consistency.
Also applies to: 317-317, 327-327, 373-373, 434-434
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx-105-113 (1)
105-113:⚠️ Potential issue | 🟠 MajorRemove duplicate "Erweiterte Grafik- und GPU-Sharing-Optionen" details block.
There are two
<details>blocks with the identical heading "Erweiterte Grafik- und GPU-Sharing-Optionen" (lines 105–113 and 133–146). The second block (lines 133–146) contains untranslated English content on line 136. Either merge these blocks or remove the duplicate.Also applies to: 133-146
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx-190-214 (1)
190-214:⚠️ Potential issue | 🟠 MajorRemove duplicate Sysprep instructions.
Lines 192–195 contain a duplicate of the Sysprep instructions that also appear at lines 198–213. Keep only one complete version.
:::note[Bevor Sie Sysprep ausführen] -- **Sysprep ausführen:** -- **Installieren Sie die Festplatte in Ihrem Unraid-Server** nach dem Herunterfahren. - Beheben Sie problematische Microsoft Store-Anwendungen oder entfernen Sie diese, die verhindern könnten, dass Sysprep ausgeführt wird. ::: 1. **Sysprep ausführen:**i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx-158-166 (1)
158-166:⚠️ Potential issue | 🟠 MajorFix broken nested note blocks.
Lines 158–166 contain improperly nested
:::noteblocks that will cause rendering issues. The structure shows an empty outer note block with a properly translated inner block.:::note - -:::note - -Unraid erstellt zwei standardmäßige %%Benutzerfreigaben|user-share%% für %%Virtualisierung|virt%%: - -::: +Unraid erstellt zwei standardmäßige %%Benutzerfreigaben|user-share%% für %%Virtualisierung|virt%%: :::i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx-17-24 (1)
17-24:⚠️ Potential issue | 🟠 MajorDuplicate caution block must be removed.
The same caution warning appears twice in succession (lines 17-20 and lines 21-24). One instance should be removed.
🔧 Proposed fix
:::caution Wenn Sie Ihr Unraid USB-Flash-Gerät ersetzen, wird Ihre Lizenz auf das neue Gerät übertragen und das alte Flash-Gerät wird gesperrt **und kann nicht mehr mit Unraid verwendet werden.** Diese Aktion ist dauerhaft und kann nicht rückgängig gemacht werden. -:::caution -Wenn Sie Ihr Unraid USB-Flash-Gerät ersetzen, wird Ihre Lizenz auf das neue Gerät übertragen und das alte Flash-Gerät wird gesperrt **und kann nicht mehr mit Unraid verwendet werden.** Diese Aktion ist dauerhaft und kann nicht rückgängig gemacht werden. - :::i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx-152-164 (1)
152-164:⚠️ Potential issue | 🟠 MajorDuplicate tip blocks - both old and new versions present.
The tip about identifying drives appears twice:
- Lines 152-157: With English heading "Identifying Laufwerke"
- Lines 158-163: With German heading "Laufwerke identifizieren"
The first block (lines 152-157) should be removed. Additionally, the content inside remains in English and should be translated to German.
🔧 Proposed fix - remove duplicate and translate content
-:::tip[Identifying Laufwerke] - -- **%%Parity drives|parity-drives%%** do not have a mountable file system. If a drive cannot be mounted, it is likely a %%parity|parity%% drive. -- **Data drives** previously used by Unraid retain their data even after resetting the %%array|array%% configuration. -- If you find more unmountable drives than expected %%parity|parity%% drives, stop and seek help in the [Unraid forums](https://forums.unraid.net/). - :::tip[Laufwerke identifizieren] -- **%%Parity drives|parity-drives%%** do not have a mountable file system. If a drive cannot be mounted, it is likely a %%parity|parity%% drive. -- **Data drives** previously used by Unraid retain their data even after resetting the %%array|array%% configuration. -- If you find more unmountable drives than expected %%parity|parity%% drives, stop and seek help in the [Unraid forums](https://forums.unraid.net/). +- **%%Parity drives|parity-drives%%** haben kein einbindbares Dateisystem. Wenn ein Laufwerk nicht eingebunden werden kann, ist es wahrscheinlich ein %%parity|parity%%-Laufwerk. +- **Datenlaufwerke**, die zuvor von Unraid verwendet wurden, behalten ihre Daten auch nach dem Zurücksetzen der %%array|array%%-Konfiguration. +- Wenn Sie mehr nicht einbindbare Laufwerke finden als erwartete %%parity|parity%%-Laufwerke, stoppen Sie und suchen Sie Hilfe in den [Unraid-Foren](https://forums.unraid.net/). :::i18n/es/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx-315-317 (1)
315-317:⚠️ Potential issue | 🟠 MajorFix Spanish translation: Remove Google configuration from Unraid.net provider section.
The issuer URL and client configuration shown are for Google, not Unraid.net. The Spanish translation incorrectly includes Google values in the Unraid.net section. Per the English documentation, Unraid.net's issuer URL and client credentials should be marked as "Pre-configured (built-in provider)" instead of showing
https://accounts.google.comand requesting OAuth 2.0 credentials. Additionally, the reference to "Google Workspace" at line 329 should be removed from this section, as it belongs in the Google provider section.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx-159-165 (1)
159-165:⚠️ Potential issue | 🟠 MajorClose the
:::cautionblock to avoid MDX rendering issues.
The admonition opens but never closes.✅ Suggested fix
:::caution La sección %%Tailscale|tailscale%% permite el acceso remoto seguro mediante el %%VPN|vpn-tunnel%% %%Tailscale|tailscale%%. Aquí, puedes iniciar sesión para conectar tu servidor Unraid a tu %%Tailnet|tailnet%%, ver la dirección IP y nombre de host asignado, y habilitar o deshabilitar la conectividad %%Tailscale|tailscale%%. +::: ###### Máquinas virtualesi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx-92-99 (1)
92-99:⚠️ Potential issue | 🟠 MajorRemove the unrelated “User shares” paragraph from WiFi prerequisites.
That paragraph appears unrelated to WiFi setup and will confuse readers—likely a copy/paste from another section.✅ Suggested fix
-:::important[Initial requisitos de configuración] +:::important[Requisitos iniciales de configuración] -Las %%User shares|user-share%% pueden simplificar en gran medida la organización y el acceso de contenido a través de múltiples discos en el %%array|array%%. Tienes la opción de especificar qué discos están permitidos para participar en %%user shares|user-share%% a través de configuraciones globales de inclusión o exclusión. - - Un teclado local y monitor conectado a tu servidor (iniciar en modo GUI), o - Una conexión temporal por cable para acceder al %%WebGUI|web-gui%%i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx-293-296 (1)
293-296:⚠️ Potential issue | 🟠 MajorRemove unrelated plugins paragraph from Notifications.
This content describes third‑party plugins, not notifications.✅ Suggested fix
-Los complementos de terceros se muestran aquí, ampliando la funcionalidad de Unraid y dándote más control sobre tu servidor. Por ejemplo, el [Complemento de Aplicaciones de la Comunidad](../../using-unraid-to/run-docker-containers/community-applications.mdx) está incluido. Otros complementos ofrecen características para monitoreo del sistema, mantenimiento, gestión de almacenamiento y copias de seguridad `appdata`.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx-247-249 (1)
247-249:⚠️ Potential issue | 🟠 MajorWireGuard sentence is misplaced under Tailscale.
This line belongs in the VPN Manager section; it conflicts with the Tailscale focus.✅ Suggested fix
-Puedes establecer una conexión %%VPN|vpn-tunnel%% a tu servidor Unraid utilizando [%%Wireguard|wireguard%%](https://www.wireguard.com/) para conexiones de internet seguras.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx-203-207 (1)
203-207:⚠️ Potential issue | 🟠 MajorHeader/content mismatch: “Configuraciones de Notificaciones” vs. network services.
The paragraph describes network services (FTP, syslog, VPN), so the section title is misleading.✅ Suggested fix
-## Configuraciones de Notificaciones +## Servicios de redi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx-262-264 (1)
262-264:⚠️ Potential issue | 🟠 MajorUse stable identifier for
valueprop to preserve tab stateLine 262:
value="ausschließen"should bevalue="6.11"to match the pattern used in other tabs within the same group (e.g.,value="6.12",value="6.12+") and to maintain consistency with Docusaurus best practices. Thevalueprop serves as a stable identifier for localStorage persistence and deep linking; using localized strings breaks this functionality.🛠️ Proposed fix
- <TabItem value="ausschließen" label="Unraid 6.11 oder darunter"> + <TabItem value="6.11" label="Unraid 6.11 oder darunter">
| ::::tip[Daumenregel für den Austausch] | ||
|
|
||
| - Kaufen Sie USB-Laufwerke von seriösen Händlern und meiden Sie Auktionsseiten und unbekannte Verkäufer. | ||
| - Vermeiden Sie gebrauchte oder zuvor verwendete Laufwerke. | ||
| - Testen Sie das neue Laufwerk auf Ihrem Server, bevor Sie Ihre Lizenz übertragen. | ||
| - Seien Sie vorsichtig bei gefälschten Produkten, sogar von bekannten Marken. | ||
| :::note | ||
| ::: | ||
|
|
||
| Die [Forenankündigung über gefälschte SanDisk-Laufwerke](https://forums.unraid.net/topic/119052-psa-on-sandisk-usbs/) von Januar 2022 bestätigt, dass SanDisk aufgrund gefälschter Geräte und Herstellungsänderungen, die zu nicht-eindeutigen GUIDs führen, nicht empfohlen wird. Dies betrifft sowohl gefälschte als auch echte SanDisk-Laufwerke. | ||
| :::: | ||
|
|
||
| :::caution[Bevor Sie beginnen] | ||
| Stellen Sie sicher, dass **%%SMB|samba%%** im %%WebGUI|web-gui%% aktiviert ist: | ||
|
|
||
| --- |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
fd "changing-the-flash-device.mdx" --type fRepository: unraid/docs
Length of output: 657
🏁 Script executed:
cat -n "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx" | sed -n '40,100p'Repository: unraid/docs
Length of output: 4310
🏁 Script executed:
cat -n "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx" | sed -n '53,82p'Repository: unraid/docs
Length of output: 1910
Fix broken admonition structure—unclosed nested blocks.
Lines 53–66 have improperly nested admonitions: the :::note at line 59 is not closed before :::caution opens at line 63, and neither the note nor the tip (opened at line 53) is ever properly closed. This breaks MDX rendering.
Correct structure:
::::tip[Daumenregel für den Austausch]
- bullet points...
:::note
note content...
:::
:::caution[Bevor Sie beginnen]
caution content...
:::
::::
🧰 Tools
🪛 LanguageTool
[grammar] ~61-~61: Entferne ein Satzzeichen
Context: ...und Herstellungsänderungen, die zu nicht-eindeutigen GUIDs führen, nicht empfohle...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_PUNCTUATION_NICHTDASHEINDEUTIGEN)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx`
around lines 53 - 66, The MDX admonitions are improperly nested: the opened tip
block (::::tip) and the inner note (:::note) are not closed before the caution
(:::caution) begins, breaking rendering; fix by closing the inner note with :::
right after the note content, then open the caution block and close it with :::
after its content, and finally close the outer tip with ::::: so that the
sequence uses :::note ... :::, :::caution ... :::, and ends with ::::: to
properly terminate the outer tip.
| info[Examples von Umgebungsvariablen] | ||
|
|
||
| - `TZ=America/New_York`: Dies setzt die Zeitzone des Containers. | ||
| - `PUID=99` und `PGID=100`: Diese setzen die Benutzer- und Gruppen-IDs für Dateiberechtigungen. | ||
| - `UMASK=022`: Dies steuert die standardmäßigen Dateiberechtigungen für erstellte Dateien. | ||
| - `API_KEY=your_api_key_here`: Dies könnte von einer Anwendung zur Authentifizierung mit einem externen Dienst verwendet werden. | ||
| ::: | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Broken admonition syntax: missing ::: prefix on line 16.
Line 16 uses info[Examples von Umgebungsvariablen] which is invalid MDX syntax. Docusaurus admonitions require the ::: prefix to open. Additionally, "Examples" should be translated to German ("Beispiele").
The structure between lines 16-24 appears malformed—the ::: on lines 22 and 24 don't properly pair with an opening admonition.
🐛 Proposed fix for the admonition structure
-info[Examples von Umgebungsvariablen]
-
+:::info[Beispiele von Umgebungsvariablen]
- `TZ=America/New_York`: Dies setzt die Zeitzone des Containers.
- `PUID=99` und `PGID=100`: Diese setzen die Benutzer- und Gruppen-IDs für Dateiberechtigungen.
- `UMASK=022`: Dies steuert die standardmäßigen Dateiberechtigungen für erstellte Dateien.
- `API_KEY=your_api_key_here`: Dies könnte von einer Anwendung zur Authentifizierung mit einem externen Dienst verwendet werden.
- :::
-
-:::
+:::
:::tip🧰 Tools
🪛 LanguageTool
[grammar] ~16-~16: Korrigiere die Fehler
Context: ...ind und welche Werte gültig sind. info[Examples von Umgebungsvariablen] - `TZ=America/...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~18-~18: Entferne ein Satzzeichen
Context: ...bungsvariablen] - TZ=America/New_York: Dies setzt die Zeitzone des Containers....
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_PUNCTUATION_COLON)
[grammar] ~20-~20: Entferne ein Satzzeichen
Context: ...s für Dateiberechtigungen. - UMASK=022: Dies steuert die standardmäßigen Dateib...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_PUNCTUATION_COLON)
[grammar] ~21-~21: Entferne ein Satzzeichen
Context: ...e Dateien. - API_KEY=your_api_key_here: Dies könnte von einer Anwendung zur Aut...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_PUNCTUATION_COLON)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdx`
around lines 16 - 24, The admonition block is malformed: replace the invalid
line `info[Examples von Umgebungsvariablen]` with a proper Docusaurus admonition
opener `:::info Beispiele von Umgebungsvariablen` (note the German translation
and the leading `:::`), ensure the environment variable list follows inside that
block, and remove the stray/mismatched extra `:::` so there is exactly one
matching closing `:::` after the list to properly close the admonition.
| :::tip[Have Soporte] | ||
|
|
||
| ¡Comentarios de la comunidad recibidos; API de código abierto en enero de 2025! Por favor envíe solicitudes de funciones y comentarios a través de: | ||
|
|
||
| - [Unraid Forums](https://forums.unraid.net) | ||
| - [Problemas en GitHub](https://github.com/unraid/api/issues) - ¡La API ahora es de código abierto! | ||
|
|
||
| :::tip[Envía tu Feedback] | ||
|
|
||
| ¡Comentarios de la comunidad recibidos; API de código abierto en enero de 2025! Por favor envíe solicitudes de funciones y comentarios a través de: | ||
|
|
||
| - [Unraid Forums](https://forums.unraid.net) | ||
| - [Problemas en GitHub](https://github.com/unraid/api/issues) - ¡La API ahora es de código abierto! | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Critical: Duplicate tip blocks creating broken MDX structure.
Lines 153-159 contain the old :::tip[Have Soporte] block that was supposed to be replaced, but lines 160-167 have the new :::tip[Envía tu Feedback] block added without removing the old one. This results in:
- Broken MDX syntax (unclosed admonition at line 159 before new one starts)
- Duplicate content displayed to users
The first block (lines 153-159) should be removed entirely.
Proposed fix - remove duplicate block
## Comentarios de la Comunidad
-:::tip[Have Soporte]
-
-¡Comentarios de la comunidad recibidos; API de código abierto en enero de 2025! Por favor envíe solicitudes de funciones y comentarios a través de:
-
-- [Unraid Forums](https://forums.unraid.net)
-- [Problemas en GitHub](https://github.com/unraid/api/issues) - ¡La API ahora es de código abierto!
-
:::tip[Envía tu Feedback]
¡Comentarios de la comunidad recibidos; API de código abierto en enero de 2025! Por favor envíe solicitudes de funciones y comentarios a través de:
- [Unraid Forums](https://forums.unraid.net)
- [Problemas en GitHub](https://github.com/unraid/api/issues) - ¡La API ahora es de código abierto!
:::🧰 Tools
🪛 LanguageTool
[grammar] ~155-~155: Agrega un signo de puntuación.
Context: ...de código abierto en enero de 2025! Por favor envíe solicitudes de funciones y coment...
(QB_NEW_ES_OTHER_ERROR_IDS_MISSING_PUNCTUATION)
[grammar] ~160-~160: Corrige la mayúscula.
Context: ... es de código abierto! :::tip[Envía tu Feedback] ¡Comentarios de la comunidad recibido...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~162-~162: Agrega un signo de puntuación.
Context: ...de código abierto en enero de 2025! Por favor envíe solicitudes de funciones y coment...
(QB_NEW_ES_OTHER_ERROR_IDS_MISSING_PUNCTUATION)
🤖 Prompt for AI Agents
In `@i18n/es/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx`
around lines 153 - 167, Remove the duplicated MDX admonition titled ":::tip[Have
Soporte]" so only the new ":::tip[Envía tu Feedback]" block remains;
specifically delete the entire old block that starts with ":::tip[Have Soporte]"
and its closing ":::" to fix the broken MDX structure and eliminate duplicate
content.
There was a problem hiding this comment.
Actionable comments posted: 3
Note
Due to the large number of review comments, Critical 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 (45)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/local.mdx (1)
7-8:⚠️ Potential issue | 🟠 MajorUntranslated English text in German localization file.
Lines 7-8 contain English instructions that were not translated to German, while the rest of the file is in German. This breaks the localization consistency.
These lines should be translated to German to match the surrounding content.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx (2)
42-42:⚠️ Potential issue | 🟠 MajorUntranslated English text in German localization file.
This entire paragraph remains in English and needs to be translated to German for consistency with the rest of the document.
145-180:⚠️ Potential issue | 🟠 MajorDuplicate section headings and jumbled instructions.
There are two sections with identical headings "VPN-Tunneling-Zugriff für das System konfigurieren" (lines 145 and 158). Additionally:
Lines 162-167: Steps 1-3 describe installing/testing Firefox, but steps 4-5 suddenly switch to VPN tunnel configuration ("Übernehmen", "Tunnel-Schalter auf Aktiv") which doesn't follow logically.
Lines 176-180: The "Testen des Systemtunnels" section duplicates the Firefox testing steps already present in lines 162-165.
This appears to be a merge or translation error. The content should be restructured to have:
- One configuration section with VPN setup steps
- One testing section with Firefox verification steps
Suggested structure
### VPN-Tunneling-Zugriff für das System konfigurieren Um den gesamten Unraid-Verkehr durch einen kommerziellen VPN zu leiten: -1. Installieren Sie einen [Firefox](https://unraid.net/community/apps?q=Firefox) Docker-Container über Community Applications. -2. In ***Einstellungen → VPN-Manager*** wählen Sie **Konfig importieren** und laden Sie die Datei hoch. -3. Benennen Sie den Tunnel optional um. -4. Klicken Sie auf **Übernehmen**. -5. Setzen Sie den Tunnel-Schalter auf **Aktiv**. -6. Besuchen Sie [dnsleaktest.com](https://www.dnsleaktest.com/) und bestätigen Sie, dass nur die DNS-Server Ihres VPN erkannt werden. +1. In ***Einstellungen → VPN-Manager*** wählen Sie **Konfig importieren** und laden Sie die Datei hoch. +2. Benennen Sie den Tunnel optional um. +3. Klicken Sie auf **Übernehmen**. +4. Setzen Sie den Tunnel-Schalter auf **Aktiv**. -Sie können diesem Tunnel zusätzliche Container zuweisen oder mehrere Tunnel erstellen. - -### VPN-Tunneling-Zugriff für das System konfigurieren - -Um den gesamten Unraid-Verkehr durch einen kommerziellen VPN zu leiten: - -1. Installieren Sie den [Firefox](https://unraid.net/community/apps?q=Firefox) Docker-Container. -2. Akzeptieren Sie alle Vorgaben. -3. Starten Sie Firefox und besuchen Sie [whatismyipaddress.com](https://whatismyipaddress.com/). Ihre IP-Adresse sollte mit dem Standort Ihres VPN-Anbieters übereinstimmen. -4. Klicken Sie auf **Übernehmen**. -5. Setzen Sie den Tunnel-Schalter auf **Aktiv**. :::note ... ::: ### Testen des Systemtunnels 1. Installieren Sie den [Firefox](https://unraid.net/community/apps?q=Firefox) Docker-Container. 2. Akzeptieren Sie alle Vorgaben. 3. Starten Sie Firefox und besuchen Sie [whatismyipaddress.com](https://whatismyipaddress.com/). Ihre IP-Adresse sollte mit dem Standort Ihres VPN-Anbieters übereinstimmen. +4. Besuchen Sie [dnsleaktest.com](https://www.dnsleaktest.com/) und bestätigen Sie, dass nur die DNS-Server Ihres VPN erkannt werden.i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (3)
138-164:⚠️ Potential issue | 🟠 MajorMismatched section header and content.
The
## Personalizaciónheader (line 138) is followed by deep linking content, but the Tabs component (lines 152-164) contains customization content (banner, dashboard, themes) under## Gestión de licencias(line 148). This appears to be a content organization error where:
- The Tabs content belongs under
## Personalización## Gestión de licenciasat line 148 should not exist (it's duplicated at line 168)🔧 Suggested restructure
## Personalización -El enlace profundo en Unraid Connect te permite saltar directamente a secciones específicas de tu WebGUI de Unraid con un solo clic. Simplemente haz clic en cualquiera de los botones de enlace circulares (abajo) en la interfaz de Connect para ir directamente a la página de gestión relevante para tu servidor. - -<div style={{ margen: 'auto', maxAnchura: '600px', display: 'flex', flexDirection: 'columna', alignItems: 'centro' }}> -  -</div> - ---- - -## Gestión de licencias - -Gestionar tus licencias en Unraid Connect es fácil. Bajo la sección **Mis Claves**, puedes: - <Tabs> <TabItem value="banner" label="Cambiar imagen del banner" default> <ConnectChangeBanner />Move the deep linking content to an appropriate section or create a new
## Enlaces profundossection.
168-179:⚠️ Potential issue | 🟡 MinorDuplicate
## Gestión de licenciasheader.This section header is duplicated—it first appears at line 148 (incorrectly placed above the Tabs) and again here at line 168 with the actual license management content. Only one should remain.
142-144:⚠️ Potential issue | 🔴 CriticalInvalid CSS property names in inline styles.
The
styleattributes use Spanish property names (margen,maxAnchura) instead of valid CSS (margin,maxWidth). Additionally,alignItems: 'centro'andflexDirection: 'columna'are invalid CSS values.🔧 Suggested fix for all three occurrences
-<div style={{ margen: 'auto', maxAnchura: '600px', display: 'flex', flexDirection: 'columna', alignItems: 'centro' }}> +<div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}>Apply this fix to lines 142, 177, and 194.
Also applies to: 177-179, 194-196
i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (3)
55-57:⚠️ Potential issue | 🔴 CriticalCSS properties must use English keywords.
The inline style uses Spanish translations (
margen,maxAnchura,columna,centro) instead of valid CSS properties. This will cause the styling to fail completely.🐛 Proposed fix
-<div style={{ margen: 'auto', maxAnchura: '600px', display: 'flex', flexDirection: 'columna', alignItems: 'centro' }}> +<div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}>
98-109:⚠️ Potential issue | 🟠 MajorDuplicate and misplaced content in encryption/privacy sections.
There are structural issues in this section:
- Lines 100 and 109 contain identical text about backup encryption
- Lines 102-104 (instructions for disabling backup) appear under the "Cifrado de copia de seguridad" heading but should be in a separate "Desactivar copia de seguridad" section
This appears to be a merge conflict or copy-paste error during translation.
🔧 Suggested restructure
-## Cifrado de copia de seguridad - -Actualmente, las copias de seguridad de flash se almacenan en la nube sin encriptación. Como precaución, los datos sensibles, incluidas todas las contraseñas de usuario y root, así como todas las claves de %%WireGuard|wireguard%%, nunca se incluyen en la copia de seguridad. +## Desactivar copia de seguridad flash 1. En ***Configuración → Acceso de Gestión → API de Unraid***, haz clic en **Desactivar** para la copia de seguridad flash. 2. En el cuadro de diálogo de confirmación, marque **También eliminar la copia de seguridad en la nube** si desea eliminar su copia de seguridad inmediatamente. De lo contrario, las copias de seguridad se eliminarán automáticamente después de un período de inactividad. ## Privacidad y seguridad ### Cifrado de copia de seguridad Actualmente, las copias de seguridad de flash se almacenan en la nube sin encriptación. Como precaución, los datos sensibles, incluidas todas las contraseñas de usuario y root, así como todas las claves de %%WireGuard|wireguard%%, nunca se incluyen en la copia de seguridad.
118-122:⚠️ Potential issue | 🟡 MinorFix escaped bracket in admonition syntax.
The
\[escaping in:::note\[Reminder]may cause rendering issues in Docusaurus MDX.🔧 Proposed fix
-:::note\[Reminder] +:::note[Reminder]i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx (4)
69-69:⚠️ Potential issue | 🟡 MinorBroken glossary link syntax.
Missing opening
%in the glossary link—%SMART|smart%%should be%%SMART|smart%%.Proposed fix
- %SMART|smart%% Selbsttests starten:** + **%%SMART|smart%% Selbsttests starten:**
182-222:⚠️ Potential issue | 🟠 MajorSubsection headings don't match their command examples.
Several heading/content mismatches:
### lsblk(line 182) containsdf -hcommand### blkid(line 210) containslsblkcommandThe commands appear to be shifted one section down from their correct headings. Realign each heading with its corresponding command example.
196-208:⚠️ Potential issue | 🟠 MajorDuplicate
blockdev -getszsubsection headings.Lines 196 and 224 both have
### blockdev -getszheadings. The first (lines 196-208) showsfdiskusage while the second (lines 224-238) shows actualblockdevusage. Remove the duplicate heading at line 196 or rename it to### fdiskto match its content.Also applies to: 224-238
262-287:⚠️ Potential issue | 🟠 MajorDuplicate
pingsubsections.The
### pingheading and content appear twice (lines 262-287 and lines 315-329). Consolidate into a single subsection to avoid confusing readers and breaking anchor links.Also applies to: 315-329
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx (1)
189-189:⚠️ Potential issue | 🟡 MinorDuplicate section heading.
Line 189 contains the same heading "Konfigurationen, die vermieden werden sollten" that appears at line 154. This creates confusion as to which section contains the actual configurations to avoid.
Consider renaming one of these sections or consolidating the content.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx (3)
34-34:⚠️ Potential issue | 🟡 MinorUntranslated English sentence in German documentation.
This line contains English text that should be translated to German for consistency with the rest of the document.
For instance, if you use an %%FTP|ftp%% client to connect to your Unraid server, you can easily transfer large files and even pause and resume your uploads or downloads if needed.
54-54:⚠️ Potential issue | 🟡 MinorUntranslated English sentence in German documentation.
This line contains English text that should be translated to German.
By tweaking these options, you can manage who can see and access each share...
130-138:⚠️ Potential issue | 🟡 MinorMismatched heading and duplicate section name.
Duplicate heading: "Zugriffssicherheit für Freigaben" appears at both line 104 (as
###) and line 130 (as##)Heading-content mismatch: Line 132 has heading "Halten Sie Ihren Server auf dem neuesten Stand" (Keep your server up to date), but the content below (lines 134-138) discusses share settings and permissions, not updates. The actual "keep server updated" content appears later at lines 161-168.
Consider restructuring these sections to ensure headings accurately describe their content.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx (1)
112-129:⚠️ Potential issue | 🟡 MinorRemove the duplicated maintenance‑expectations paragraph.
The paragraph starting with “Entwickler, die Anwendungen in Community Applications veröffentlichen …” appears twice in this section, which adds redundancy and risks divergence.🧹 Suggested removal (keep the first instance)
-Entwickler, die Anwendungen in Community Applications veröffentlichen, werden erwartet, dass sie ihre Projekte pflegen, um die Kompatibilität und Zuverlässigkeit für die Unraid-Community sicherzustellen. Dieser Abschnitt umreißt die laufenden Verantwortlichkeiten, die zur Aufrechterhaltung der Qualität der verfügbaren Anwendungen beitragen.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx (4)
47-90:⚠️ Potential issue | 🟠 MajorMehrfach duplizierter Inhalt im Vorlagen-Abschnitt.
This section contains several duplications:
- Line 47 duplicates line 74 (identical paragraph about Benutzer-VM-Vorlagen)
- Lines 78-79 duplicate lines 88-89 (export/import instructions)
- Line 86 is misplaced content about VM Manager features that belongs in the "Neu in Unraid 7.x" section
Please consolidate and remove the duplicate content.
97-146:⚠️ Potential issue | 🟠 MajorSyntax-Fehler und duplizierte Details-Abschnitte.
- Line 97:
:::tip\[Highlights]has an escaped bracket that should be removed- Lines 106 and 134 both have the same summary text
Erweiterte Grafik- und GPU-Sharing-Optionenbut contain different content - one should be renamed for clarity- Line 136 contains untranslated English:
View all graphics cards and %%VM|vm%%-assigned IP addresses in the %%VM|vm%% tabProposed fix for line 97
-:::tip\[Highlights] +:::tip[Highlights]
410-414:⚠️ Potential issue | 🟡 MinorFehlplatzierte Überschrift.
Line 410 "Um ein ROM einzuspeisen:" is misplaced - it appears before the software requirements list (lines 412-413) instead of before the actual ROM injection steps (which start at line 435). This appears to be leftover content that should be removed.
-Um ein ROM einzuspeisen: - - Unraid 6.9+ mit aktivierter Virtualisierung. - %%OVMF|ovmf%% (%%UEFI|uefi%%) BIOS für %%VMs|vm%% (empfohlen gegenüber %%SeaBIOS|seabios%%).
549-551:⚠️ Potential issue | 🟡 MinorNicht übersetzter englischer Satz.
Line 550 contains untranslated English content:
- - Switch from %%SeaBIOS|seabios%% to %%OVMF|ovmf%% (%%UEFI|uefi%%) in %%VM|vm%% settings. + - Wechseln Sie in den %%VM|vm%%-Einstellungen von %%SeaBIOS|seabios%% zu %%OVMF|ovmf%% (%%UEFI|uefi%%).i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx (1)
199-201:⚠️ Potential issue | 🟡 MinorTranslate the English bullet.
Line 200 is still English; please localize it for consistency.
💬 Proposed fix
-Using SSDs in your %%cache pool|cache-pool%% significantly improves %%VM|vm%% responsiveness. +Die Verwendung von SSDs im %%Cache-Pool|cache-pool%% verbessert die Reaktionsfähigkeit von %%VMs|vm%% erheblich.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md (1)
207-219:⚠️ Potential issue | 🟡 MinorRemove duplicate "Ändern des Dateisystemtyps eines Pools" content.
Lines 207-213 and 214-219 contain identical content describing how to change pool filesystem types. Remove the duplicate occurrence.
🧹 Proposed fix to remove duplication
- Für Btrfs-Pools: - Slots == 1 => Single - Slots >= 2 => Raid1 (d.h., was Btrfs „Raid1" nennt) ### Poolüberlegungen -Ändern des Dateisystemtyps eines Pools: - -Für alle Einzel-Slot-Pools kann der Dateisystemtyp geändert werden, wenn das Array gestoppt ist. - -Für btrfs/zfs-Multiple-Slot-Pools kann der Dateisystemtyp nicht geändert werden. Um die Geräte wiederzuverwenden, -müssen Sie die Schaltfläche Pool löschen klicken. - Ändern des Dateisystemtyps eines Pools: Für alle Einzel-Slot-Pools kann der Dateisystemtyp geändert werden, wenn das Array gestoppt ist.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/monitor-performance/smart-reports-and-disk-health.mdx (1)
22-26:⚠️ Potential issue | 🟡 MinorRemove the duplicated intro sentence before the table.
The “Einige … umfassen:” line appears twice, which reads as a repetition just before the table.
✂️ Proposed fix
@@ -Für eine genauere Betrachtung der Daten eines Laufwerks von %%SMART|smart%%, klicken Sie auf dessen Namen im **Main**-Tab der Unraid %%WebGUI|web-gui%%. - -Einige %%SMART|smart%% Attribute, die Unraid standardmäßig überwacht, umfassen: +Für eine genauere Betrachtung der Daten eines Laufwerks von %%SMART|smart%%, klicken Sie auf dessen Namen im **Main**-Tab der Unraid %%WebGUI|web-gui%%.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx (1)
229-265:⚠️ Potential issue | 🟠 MajorMover content misplaced under Split Level section.
Lines 229-265 contain:
- Line 231: Text about managing file placement between cache pools and array (belongs to Mover/Primary-Secondary storage section)
- Lines 239-251: "Cache zum Array" subsection with tabs for 6.12/6.11
- Lines 253-265: "Array zum Cache" subsection
These Mover-related subsections should be under "Primärer und sekundärer Speicher" (lines 213-225), not under "Teilungsstufe" (Split Level). The Split Level section at line 362 contains the actual split level content.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx (4)
214-220:⚠️ Potential issue | 🟠 MajorSection header and content mismatch.
Line 214 declares
## Benachrichtigungseinstellungen(Notification Settings), but line 216 contains English text about "Network Services" and line 218 starts### NFS (Network File System). The content doesn't match the header.This appears to be a structural error where the section header was changed but the content below still belongs to a different section (Network Services).
226-231:⚠️ Potential issue | 🟡 MinorMissing section content for "Benutzerprogramme".
The
### Benutzerprogrammesection header has no descriptive text - it jumps directly to an SMB settings image. Additionally, the SMB image doesn't seem to match a "User Programs" section.
28-28:⚠️ Potential issue | 🟡 MinorUntranslated English paragraph.
Line 28 contains untranslated English text in the German localization file. This paragraph about CPU Pinning should be translated to German.
44-44:⚠️ Potential issue | 🟡 MinorMultiple untranslated English paragraphs throughout the file.
Several paragraphs remain in English in this German localization file:
- Line 44: Disk settings description
- Line 74: Management access description
- Line 82: Network settings description
- Line 216: Network Services description
- Line 220: NFS description
- Line 235: FTP description
- Line 462: Scheduler description
These should be translated to German for consistency.
i18n/es/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx (1)
390-444:⚠️ Potential issue | 🟠 MajorProvider sections are duplicated.
The provider configuration sections for Authentik (lines 390-402 and 418-430) and Okta (lines 404-416 and 432-443) appear twice in the document. This creates confusion and maintenance issues.
🔧 Recommendation
Remove the duplicate provider sections. Keep only one instance of each provider configuration:
- Authentik: Keep lines 418-430, remove lines 390-402
- Okta: Keep lines 432-443, remove lines 404-416
The second instances have the correct Issuer URLs:
- Authentik:
https://authentik.example.com/application/o/<application_slug>/- Okta:
https://YOUR_DOMAIN.okta.comThe first instances incorrectly reference Microsoft/Azure URLs for Authentik and have inconsistent content.
i18n/es/docusaurus-plugin-content-docs/current/API/cli.mdx (1)
9-13:⚠️ Potential issue | 🟡 MinorUntranslated admonition content.
The info block has a mixed label
Command Estructuraand the body content is entirely in English. This should be translated to Spanish.🔧 Proposed fix
-:::info[Command Estructura +:::info[Estructura de Comandos] -All commands follow the pattern: `unraid-api <command> [options]` +Todos los comandos siguen el patrón: `unraid-api <comando> [opciones]` :::Note: The opening bracket also appears to be missing its closing bracket.
i18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx (1)
240-254:⚠️ Potential issue | 🟠 MajorMixed English/Spanish admonition label and duplicated content.
The label
Common Mensajes de Errormixes English and Spanish. Additionally, the content inside duplicates what appears above (lines 242-243 duplicate lines 244-252).🔧 Proposed fix
-:::note[Common Mensajes de Error] - -Para resolución de problemas, ejecute con registro de depuración: - -- **Solución:** Elimine caracteres especiales como guiones, guiones bajos o símbolos +:::note[Mensajes de Error Comunes] **"Una clave API con el nombre 'x' ya existe"** - **Solución:** Use la bandera `--overwrite` o elija un nombre diferente **"Por favor, añada al menos un rol o permiso a la clave"** - **Solución:** Especifique ya sea `--roles` o `--permissions` (o ambos) :::i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx (3)
17-17:⚠️ Potential issue | 🟡 MinorBitte die verbleibenden englischen Sätze in der DE‑Lokalisierung übersetzen.
Die genannten Zeilen sind noch auf Englisch und wirken in der deutschen Dokumentation inkonsistent.Also applies to: 56-56, 76-76, 224-224, 232-232, 317-327, 373-373, 434-434
236-247:⚠️ Potential issue | 🟡 MinorSchritt‑Nummerierung ist doppelt (Schritt 4) und Schritt 3 fehlt.
Das wirkt wie ein Nummerierungsfehler und kann Leser verwirren.✅ Vorschlag zur Korrektur
-<h4>Schritt 4: Bearbeiten Sie das XML für Ihre virtuelle Maschine</h4> +<h4>Schritt 3: Erstellen Sie eine neue virtuelle Maschine</h4>
329-406:⚠️ Potential issue | 🟡 MinorSchritt‑Reihenfolge wirkt inkonsistent (5/6 vor 3/4, doppelte 5/6‑Sektionen).
Die Details‑Sektionen sind numerisch nicht in Reihenfolge, was die Anleitung schwer nachvollziehbar macht. Bitte neu nummerieren oder die Blöcke umordnen, damit 1→N sauber verläuft.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx (1)
66-79:⚠️ Potential issue | 🟡 MinorRemove the duplicated guest-agent paragraph.
The “Um den Ruhezustand zuverlässig zu nutzen…” paragraph appears twice; keep only one instance.Proposed fix
-Um den Ruhezustand zuverlässig zu nutzen, müssen Sie den %%QEMU|qemu%%-%%Guest-Agent|guest-agent%% in Ihrer Windows-%%VM|vm%% installieren. Dieser Agent ermöglicht es Unraid, mit der %%VM|vm%% für erweiterte Vorgänge wie Ruhezustand, Herunterfahren und Live-Statistikberichterstattung zu kommunizieren.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx (2)
73-93:⚠️ Potential issue | 🟡 MinorRemove or merge the duplicate WebGUI/Array blocks.
These new sections overlap with the existing WebGUI/Array details that still appear below (lines 95–114). Please consolidate to avoid duplication and conflicting guidance.
139-151:⚠️ Potential issue | 🟠 MajorTranslate the remaining English paragraph and remove the duplicate intro.
There’s a duplicate of the same paragraph right after the
:::importantblock, and line 151 is still English. Please remove the duplicate and translate the English text. Also fix the grammar in line 139 (“kein aktuelles Backup”).✏️ Grammar fix (line 139)
-Wenn Ihr Unraid-Bootlaufwerk ausfällt und Sie keinen aktuellen Backup oder kein Wissen darüber haben, welche Laufwerke Parität sind, ... +Wenn Ihr Unraid-Bootlaufwerk ausfällt und Sie kein aktuelles Backup oder kein Wissen darüber haben, welche Laufwerke Parität sind, ...Suggested German translation for the English paragraph (line 151):
Unraid identifiziert Datenlaufwerke, indem es vorhandene gültige Dateisysteme erkennt. %%Paritätslaufwerke|parity-drives%%, die kein Dateisystem besitzen, erscheinen nicht einhängbar. Dadurch können Sie %%Paritätslaufwerke|parity-drives%% nach dem Booten mit einem neuen Flash‑Gerät von Datenlaufwerken unterscheiden.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx (1)
111-142:⚠️ Potential issue | 🟡 MinorRemove duplicate section title "Wiederherstellung von einem verlorenen Flash-Gerät ohne Backup".
The same title appears at line 111 (H3) and line 142 (H2), creating duplicate anchors. Rename the H3 heading to differentiate it:
Suggested rename
-### Wiederherstellung von einem verlorenen Flash-Gerät ohne Backup +### Wiederherstellungsmethoden (ohne Backup)i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (2)
11-18:⚠️ Potential issue | 🟡 MinorRemove the duplicated intro paragraph.
Line 17 repeats the same paragraph already inside the
:::importantblock, so the content appears twice.🧹 Proposed fix
-%%ZFS|zfs%% bietet erweiterte Datenintegrität, flexible Speicherlösungen und hohe Leistung für Ihr Unraid-System. Dieser Leitfaden erklärt die Kernkonzepte von %%ZFS|zfs%% und führt Sie durch die Verwaltung von %%ZFS|zfs%%-Pools direkt über das Unraid %%WebGUI|web-gui%%. Egal, ob Sie neuen %%ZFS|zfs%%-Speicher einrichten oder einen bestehenden Pool integrieren, hier finden Sie die Schritte und den Kontext, die Sie benötigen, um sicher zu starten.
331-341:⚠️ Potential issue | 🟠 MajorTranslate the English paragraph and table cell in this section.
Line 333 and the “Spezial‑vdev oder Dedup vdev” row are still English.
🌐 Suggested translation
-When you import a %%ZFS|zfs%% pool into Unraid, you need to assign every drive from your original pool, including those used for support vdevs, to the pool slots. Unraid will automatically recognize each drive’s role (data, log, cache, special, or dedup) once the %%array|array%% starts. You don’t need to specify which drive serves what purpose manually. +Wenn Sie einen %%ZFS|zfs%%‑Pool in Unraid importieren, müssen Sie jedem Slot alle Laufwerke Ihres ursprünglichen Pools zuweisen – einschließlich der Laufwerke für Unterstützungs‑vdevs. Unraid erkennt die Rolle jedes Laufwerks (Daten, Log, Cache, Special oder Dedup) automatisch, sobald das %%array|array%% startet. Sie müssen nicht manuell angeben, welches Laufwerk welche Aufgabe übernimmt. @@ -| Spezial-vdev oder Dedup vdev | Pool wird nicht importiert oder ist unbenutzbar | These vdevs store critical metadata or deduplication tables. Without them, %%ZFS\|zfs%% cannot safely mount the pool. | +| Spezial-vdev oder Dedup vdev | Pool wird nicht importiert oder ist unbenutzbar | Diese vdevs speichern kritische Metadaten oder Deduplizierungstabellen. Ohne sie kann %%ZFS\|zfs%% den Pool nicht sicher einbinden. |i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (3)
244-265:⚠️ Potential issue | 🟠 MajorSection content doesn’t match “Mindestfreier Speicherplatz” heading.
This block describes disk replacement prerequisites/steps and repeats another “Mindestfreier Speicherplatz” section later. Please move this content to the disk‑replacement section or rename/dedupe appropriately.
276-292:⚠️ Potential issue | 🟠 MajorMinimum‑free‑space section still has English narrative and bullets.
Translate the introductory paragraph and the bullets describing Primary/Secondary storage behavior.
324-335:⚠️ Potential issue | 🟠 MajorDetails block explanation still English.
The long explanation inside the<details>block should be localized to German.
🤖 Fix all issues with AI agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx`:
- Around line 163-178: The admonition and duplicate-content block is malformed:
remove the duplicate Tailscale paragraph and the repeated "###### Virtuelle
Maschinen" header, close the first :::caution before the VM subsection, and
eliminate the nested/second :::caution so there's a single well-formed caution
block containing the Tailscale paragraph followed by one "###### Virtuelle
Maschinen" section; search for the tokens :::caution, %%Tailscale|tailscale%%,
and "###### Virtuelle Maschinen" to locate and restructure the content so the
admonition is opened, contains the Tailscale text, then closed, then the VM
header and the VM networking paragraph follow once.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx`:
- Around line 150-172: Die Überschrift "## Erweiterte Optionen" soll den
Snapshot-Inhalt korrekt widerspiegeln, ändere sie zu etwas passendem wie "##
VM-Snapshots" oder "## Snapshots"; passe das Info-Callout-Label `:::info[How
tipps]` auf deutsch zu `:::info[Hilfreiche Tipps]`; entferne den fehlplatzierten
Satz über das Binden von PCI-Geräten an den `vfio-pci`-Treiber (die ganze Zeile
mit "Bevor Sie eine GPU..." / "Dieser Prozess verbirgt das Gerät...") aus dem
Snapshot-Abschnitt und füge diesen stattdessen in die existierende "Binden von
PCI-Geräten für Passthrough" Sektion ein, sodass nur Snapshot-relevanter Text im
"VM-Snapshots" Abschnitt verbleibt (suche nach the header "## Erweiterte
Optionen", the info block `:::info[...]`, and the vfio-pci sentence to locate
changes).
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-license-issues.mdx`:
- Around line 18-19: Remove the two editorial/annotation artifact lines that
were accidentally left in the MDX content (the literal lines beginning with "#
(Lines 1-17 remain unchanged, line 18 is removed)" and "# Line 19 onwards
continue with the tip block") from the file
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-license-issues.mdx
so they do not render to users; simply delete those two lines and save the MDX
file, then run the site build/lint to confirm no stray content remains.
| :::caution | ||
|
|
||
| Der Abschnitt %%Tailscale|tailscale%% ermöglicht sicheren Fernzugriff über den %%Tailscale|tailscale%% %%VPN|vpn-tunnel%%. Hier können Sie sich anmelden, um Ihren Unraid-Server mit Ihrem %%Tailnet|tailnet%% zu verbinden, die zugewiesene IP-Adresse und den Hostnamen anzeigen sowie die %%Tailscale|tailscale%%-Konnektivität aktivieren oder deaktivieren. | ||
|
|
||
| ###### Virtuelle Maschinen | ||
|
|
||
| :::caution | ||
|
|
||
| Der Abschnitt %%Tailscale|tailscale%% ermöglicht sicheren Fernzugriff über den %%Tailscale|tailscale%% %%VPN|vpn-tunnel%%. Hier können Sie sich anmelden, um Ihren Unraid-Server mit Ihrem %%Tailnet|tailnet%% zu verbinden, die zugewiesene IP-Adresse und den Hostnamen anzeigen sowie die %%Tailscale|tailscale%%-Konnektivität aktivieren oder deaktivieren. | ||
| ::: | ||
|
|
||
| ###### Virtuelle Maschinen | ||
|
|
||
| Es wird empfohlen, Ihre %%VM|vm%% **Netzwerkquelle** auf **virbr0** (Private NAT) einzurichten. Dieser Modus funktioniert mit einer beliebigen Anzahl von %%VMs|vm%% und stellt den Netzwerkzugang über %%NAT|nat%% bereit. Beachten Sie, dass mDNS nicht über NAT funktioniert, sodass die %%VM|vm%% auf andere lokale Netzwerkgeräte über die IP-Adresse und nicht über den Hostnamen zugreifen muss. Sie können IP-Adressen und Hostnamen zur Hosts-Datei im Betriebssystem der %%VM|vm%% hinzufügen, um den Zugriff über den Hostnamen zu ermöglichen. Die %%VMs|vm%% sind nicht direkt von anderen Geräten in Ihrem LAN erreichbar, aber Sie können dennoch über %%VNC|vnc-session%% über den Host auf sie zugreifen. | ||
|
|
||
| Für weitere Informationen zur %%VM|vm%%-Vernetzung, siehe [Übersicht und Systemvorbereitung](../../using-unraid-to/create-virtual machines/overview-and-system-prep.mdx). |
There was a problem hiding this comment.
Severely malformed section with unclosed admonitions and duplicate content.
This block has critical structural issues that will break rendering:
- Line 163:
:::cautionopened but never properly closed before the next heading - Lines 165 & 171: Identical Tailscale paragraph appears twice
- Lines 167 & 174:
###### Virtuelle Maschinenheader appears twice - Line 169: Second
:::cautionopened, creating nested/broken admonition structure
The entire section needs restructuring.
Suggested fix - restructure the section
-:::caution
-
-Der Abschnitt %%Tailscale|tailscale%% ermöglicht sicheren Fernzugriff über den %%Tailscale|tailscale%% %%VPN|vpn-tunnel%%. Hier können Sie sich anmelden, um Ihren Unraid-Server mit Ihrem %%Tailnet|tailnet%% zu verbinden, die zugewiesene IP-Adresse und den Hostnamen anzeigen sowie die %%Tailscale|tailscale%%-Konnektivität aktivieren oder deaktivieren.
-
-###### Virtuelle Maschinen
-
:::caution
-Der Abschnitt %%Tailscale|tailscale%% ermöglicht sicheren Fernzugriff über den %%Tailscale|tailscale%% %%VPN|vpn-tunnel%%. Hier können Sie sich anmelden, um Ihren Unraid-Server mit Ihrem %%Tailnet|tailnet%% zu verbinden, die zugewiesene IP-Adresse und den Hostnamen anzeigen sowie die %%Tailscale|tailscale%%-Konnektivität aktivieren oder deaktivieren.
-:::
+Wenn Sie Docker-Container mit WiFi verwenden, beachten Sie die oben genannten Einschränkungen bezüglich benutzerdefinierter Netzwerke.
-###### Virtuelle Maschinen
+:::
+
+##### Virtuelle Maschinen
Es wird empfohlen, Ihre %%VM|vm%% **Netzwerkquelle** auf **virbr0** (Private NAT) einzurichten.🧰 Tools
🪛 LanguageTool
[grammar] ~165-~165: Korrigiere das Wort
Context: ...ugewiesene IP-Adresse und den Hostnamen anzeigen sowie die %%Tailscale|tailscale%%-Konne...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_VERB_FORM)
[grammar] ~165-~165: Hier könnte ein Fehler sein.
Context: ...eigen sowie die %%Tailscale|tailscale%%-Konnektivität aktivieren oder deaktivieren. ###### V...
(QB_NEW_DE)
[grammar] ~165-~165: Hier könnte ein Fehler sein.
Context: ...le|tailscale%%-Konnektivität aktivieren oder deaktivieren. ###### Virtuelle Maschin...
(QB_NEW_DE)
[grammar] ~171-~171: Korrigiere das Wort
Context: ...ugewiesene IP-Adresse und den Hostnamen anzeigen sowie die %%Tailscale|tailscale%%-Konne...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_VERB_FORM)
[grammar] ~171-~171: Hier könnte ein Fehler sein.
Context: ...eigen sowie die %%Tailscale|tailscale%%-Konnektivität aktivieren oder deaktivieren. ::: ####...
(QB_NEW_DE)
[grammar] ~171-~171: Hier könnte ein Fehler sein.
Context: ...le|tailscale%%-Konnektivität aktivieren oder deaktivieren. ::: ###### Virtuelle Mas...
(QB_NEW_DE)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx`
around lines 163 - 178, The admonition and duplicate-content block is malformed:
remove the duplicate Tailscale paragraph and the repeated "###### Virtuelle
Maschinen" header, close the first :::caution before the VM subsection, and
eliminate the nested/second :::caution so there's a single well-formed caution
block containing the Tailscale paragraph followed by one "###### Virtuelle
Maschinen" section; search for the tokens :::caution, %%Tailscale|tailscale%%,
and "###### Virtuelle Maschinen" to locate and restructure the content so the
admonition is opened, contains the Tailscale text, then closed, then the VM
header and the VM networking paragraph follow once.
| ## Erweiterte Optionen | ||
|
|
||
| VM-Snapshots ermöglichen es Ihnen, den aktuellen Zustand Ihrer %%VM|vm%% zu einem bestimmten Zeitpunkt zu speichern. Sie können zu diesem Zustand zurückkehren, falls etwas schiefgeht, oder Snapshots nutzen, um Änderungen sicher zu testen. Dies ist besonders nützlich, bevor Sie neue Software installieren, Konfigurationsänderungen vornehmen oder Systemupdates durchführen. | ||
|
|
||
| :::info[How tipps] | ||
|
|
||
| Wenn Sie einen Snapshot erstellen, generiert Unraid eine "Overlay-Datei", die alle nach diesem Zeitpunkt vorgenommenen Änderungen an Ihrer VM erfasst. Sie können es sich so vorstellen: | ||
|
|
||
| - **Original-VM-Disk**: Dies stellt den aktuellen Zustand Ihrer VM dar (ähnlich einem Foto). | ||
| - **Snapshot-Overlay**: Dies ist eine separate Datei, die alle nach dem Snapshot vorgenommenen Änderungen aufzeichnet (wie eine Liste von Bearbeitungen). | ||
| - **VM läuft weiter**: Ihre VM nutzt sowohl die Originaldisk als auch die Overlay-Datei zusammen. | ||
|
|
||
| Diese Einrichtung ermöglicht es Ihnen, mehrere Snapshots zu erstellen, wobei jeder eine eigene Overlay-Datei erzeugt. So können Sie problemlos zu einem beliebigen vorherigen Zustand zurückkehren. | ||
|
|
||
| Bevor Sie eine GPU oder ein anderes PCI-Gerät einer %%virtuellen Maschine|vm%% zuweisen können, ist es wichtig, das Gerät an den **vfio-pci** Treiber zu "binden". Dieser Prozess verbirgt das Gerät vor Unraid und widmet es ausschließlich Ihrer %%VM|vm%%. | ||
|
|
||
| 1. Sie erstellen einen Snapshot namens "Saubere Windows-Installation". | ||
| 2. Sie installieren einige Software und nehmen Änderungen vor. | ||
| 3. Sie erstellen einen weiteren Snapshot namens "Nach der Software-Installation". | ||
| 4. Sie können nun entweder zur sauberen Installation oder zum Zustand nach der Softwareinstallation zurückkehren. | ||
| 5. Sie können auch Block Commit oder Block Pull verwenden, um Änderungen dauerhaft zu machen. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Fehlplatzierter Inhalt und gemischte Sprache im Snapshot-Abschnitt.
Several issues in this section:
- Line 154:
:::info[How tipps]should be German (e.g.,:::info[Hilfreiche Tipps]) - Line 164 is critically misplaced: The paragraph about binding PCI devices to
vfio-pcidriver appears in the middle of the snapshot explanation. This content belongs in the "Binden von PCI-Geräten für Passthrough" section (around line 356). - The section header "Erweiterte Optionen" (line 150) doesn't match the content which is about snapshots
Proposed fix - remove misplaced line 164
Diese Einrichtung ermöglicht es Ihnen, mehrere Snapshots zu erstellen, wobei jeder eine eigene Overlay-Datei erzeugt. So können Sie problemlos zu einem beliebigen vorherigen Zustand zurückkehren.
-Bevor Sie eine GPU oder ein anderes PCI-Gerät einer %%virtuellen Maschine|vm%% zuweisen können, ist es wichtig, das Gerät an den **vfio-pci** Treiber zu "binden". Dieser Prozess verbirgt das Gerät vor Unraid und widmet es ausschließlich Ihrer %%VM|vm%%.
-
1. Sie erstellen einen Snapshot namens "Saubere Windows-Installation".🧰 Tools
🪛 LanguageTool
[grammar] ~154-~154: Passe das Symbol an
Context: ... Systemupdates durchführen. :::info[How tipps] Wenn Sie einen Snapshot erstellen, ge...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~156-~156: Ersetze das Satzzeichen
Context: ...apshot erstellen, generiert Unraid eine "Overlay-Datei", die alle nach diesem Zeitpunkt ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~156-~156: Ersetze das Satzzeichen
Context: ...stellen, generiert Unraid eine "Overlay-Datei", die alle nach diesem Zeitpunkt vorgeno...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~159-~159: Entferne ein Wort
Context: ... dar (ähnlich einem Foto). - Snapshot-Overlay: Dies ist eine separate Datei, die alle ...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_NOUN)
[grammar] ~160-~160: Entferne ein Wort
Context: ... Liste von Bearbeitungen). - VM läuft weiter: Ihre VM nutzt sowohl die Originaldisk a...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_NOUN)
[grammar] ~164-~164: Entferne ein Leerzeichen
Context: ...s wichtig, das Gerät an den vfio-pci Treiber zu "binden". Dieser Prozess verb...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~164-~164: Ersetze das Satzzeichen
Context: ...as Gerät an den vfio-pci Treiber zu "binden". Dieser Prozess verbirgt das Gerät vor ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~166-~166: Ersetze das Satzzeichen
Context: ... 1. Sie erstellen einen Snapshot namens "Saubere Windows-Installation". 2. Sie installie...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~166-~166: Ersetze das Satzzeichen
Context: ... einen Snapshot namens "Saubere Windows-Installation". 2. Sie installieren einige Software un...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[style] ~168-~168: Drei aufeinanderfolgende Sätze beginnen mit dem gleichen Wort. Evtl. können Sie den Satz umformulieren, zum Beispiel, indem Sie ein Synonym nutzen.
Context: ... Software und nehmen Änderungen vor. 3. Sie erstellen einen weiteren Snapshot namen...
(GERMAN_WORD_REPEAT_BEGINNING_RULE)
[grammar] ~168-~168: Ersetze das Satzzeichen
Context: ...rstellen einen weiteren Snapshot namens "Nach der Software-Installation". 4. Sie könn...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~168-~168: Ersetze das Satzzeichen
Context: ...eren Snapshot namens "Nach der Software-Installation". 4. Sie können nun entweder zur saubere...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[style] ~169-~169: Drei aufeinanderfolgende Sätze beginnen mit dem gleichen Wort. Evtl. können Sie den Satz umformulieren, zum Beispiel, indem Sie ein Synonym nutzen.
Context: ...ns "Nach der Software-Installation". 4. Sie können nun entweder zur sauberen Instal...
(GERMAN_WORD_REPEAT_BEGINNING_RULE)
[uncategorized] ~169-~169: Uneinheitliche Verwendung von Bindestrichen. Der Text enthält sowohl ‚Softwareinstallation‘ als auch ‚Software-Installation‘.
Context: ... Installation oder zum Zustand nach der Softwareinstallation zurückkehren. 5. Sie können auch Block ...
(DE_COMPOUND_COHERENCY)
[style] ~170-~170: Drei aufeinanderfolgende Sätze beginnen mit dem gleichen Wort. Evtl. können Sie den Satz umformulieren, zum Beispiel, indem Sie ein Synonym nutzen.
Context: ...r Softwareinstallation zurückkehren. 5. Sie können auch Block Commit oder Block Pul...
(GERMAN_WORD_REPEAT_BEGINNING_RULE)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx`
around lines 150 - 172, Die Überschrift "## Erweiterte Optionen" soll den
Snapshot-Inhalt korrekt widerspiegeln, ändere sie zu etwas passendem wie "##
VM-Snapshots" oder "## Snapshots"; passe das Info-Callout-Label `:::info[How
tipps]` auf deutsch zu `:::info[Hilfreiche Tipps]`; entferne den fehlplatzierten
Satz über das Binden von PCI-Geräten an den `vfio-pci`-Treiber (die ganze Zeile
mit "Bevor Sie eine GPU..." / "Dieser Prozess verbirgt das Gerät...") aus dem
Snapshot-Abschnitt und füge diesen stattdessen in die existierende "Binden von
PCI-Geräten für Passthrough" Sektion ein, sodass nur Snapshot-relevanter Text im
"VM-Snapshots" Abschnitt verbleibt (suche nach the header "## Erweiterte
Optionen", the info block `:::info[...]`, and the vfio-pci sentence to locate
changes).
| # (Lines 1-17 remain unchanged, line 18 is removed) | ||
| # Line 19 onwards continue with the tip block |
There was a problem hiding this comment.
Remove editorial/annotation comments from content.
Lines 18-19 contain what appear to be annotation artifacts that should not be in the actual MDX file:
# (Lines 1-17 remain unchanged, line 18 is removed)
# Line 19 onwards continue with the tip block
These lines will render as visible content to users. Remove them entirely.
🐛 Proposed fix
:::
-# (Lines 1-17 remain unchanged, line 18 is removed)
-# Line 19 onwards continue with the tip block
-
:::tip📝 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.
| # (Lines 1-17 remain unchanged, line 18 is removed) | |
| # Line 19 onwards continue with the tip block | |
| ::: | |
| :::tip |
🧰 Tools
🪛 LanguageTool
[grammar] ~18-~18: Ersetze das Satzzeichen
Context: ...indung mehr herstellen. ::: # (Lines 1-17 remain unchanged, line 18 is removed) #...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_DASH_–)
🤖 Prompt for AI Agents
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-license-issues.mdx`
around lines 18 - 19, Remove the two editorial/annotation artifact lines that
were accidentally left in the MDX content (the literal lines beginning with "#
(Lines 1-17 remain unchanged, line 18 is removed)" and "# Line 19 onwards
continue with the tip block") from the file
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-license-issues.mdx
so they do not render to users; simply delete those two lines and save the MDX
file, then run the site build/lint to confirm no stray content remains.
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
docs/unraid-os/troubleshooting/licensing-faq.mdx (1)
206-214:⚠️ Potential issue | 🟡 MinorFix trial extension duration to 15 days in line 214.
Line 214 incorrectly states "14 additional days each time" when the official Unraid policy is 15 additional days per extension. Change to "15 additional days each time" to match both line 210 and the correct total of 60 days (30 initial + 15 + 15 from extensions).
docs/API/programmatic-api-key-management.mdx (1)
135-167:⚠️ Potential issue | 🟡 MinorFix inconsistent API key header in curl example.
The "Using API Keys" section in
how-to-use-the-api.mdxdocuments the header asx-api-key, but this curl example usesAuthorization: Bearer. Update to match the documented API key header format:Suggested change
-curl -H "Authorization: Bearer $API_KEY" \ +curl -H "x-api-key: $API_KEY" \
🤖 Fix all issues with AI agents
In
`@docs/unraid-os/system-administration/advanced-tools/command-line-interface.mdx`:
- Around line 42-53: The details block whose summary is "How to install and use
PuTTY" incorrectly contains disk utility content (`hdparm -I /dev/sdX`); locate
the details element with that exact summary text and either restore the original
PuTTY installation/usage instructions (replace the hdparm snippet with the
correct PuTTY commands and brief usage notes) or remove the entire details block
if PuTTY guidance is obsolete, ensuring no residual `hdparm` content remains in
that PuTTY section.
In `@docs/unraid-os/troubleshooting/licensing-faq.mdx`:
- Around line 162-167: Update the table entries for "Devices per Pool" for the
Unleashed and Lifetime rows: change the value currently shown as "Up to 60" to
"Up to 200" so the table reflects the Unraid 7.2.1 limit; locate the "Devices
per Pool" column in the rows for "Unleashed" and "Lifetime" in the license table
and replace "Up to 60" with "Up to 200".
🧹 Nitpick comments (2)
docs/unraid-os/system-administration/advanced-tools/command-line-interface.mdx (1)
101-101: Optional: Consider rewording for style.Static analysis suggests that multiple successive sentences begin with "This." While the meaning is clear, you could improve variety by rewording:
-This used to be a script you would download from the Unraid forums. DiskSpeed is available now in a more refined package: +Previously available as a forum download, DiskSpeed is now available in a more refined package:docs/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx (1)
144-151: Use slug-stylevaluekeys for the new TabsLines 145–151 set
valueto human-readable strings with spaces. Docusaurus recommends treatingvalueas a stable, machine-readable ID using URL-safe slugs, whilelabelshould contain the human-friendly text. This is especially important if you later addgroupId(localStorage persistence) orqueryString(URL persistence) features, which can break ifvaluechanges.♻️ Suggested adjustment
- <TabItem value="Simplest method" label="Simplest method"> + <TabItem value="simplest" label="Simplest method"> <ManualDowngradeSimplest /> </TabItem> - <TabItem value="Command line method" label="Command line method"> + <TabItem value="command-line" label="Command line method"> <ManualDowngradeCommandLine /> </TabItem>
| <details> | ||
| <summary><strong>How to install and use PuTTY</strong> - Click to expand/collapse</summary> | ||
|
|
||
| **View drive information:** | ||
| **View drive information:** | ||
|
|
||
| ```bash | ||
| hdparm -I /dev/sdX | ||
| ``` | ||
| ```bash | ||
| hdparm -I /dev/sdX | ||
| ``` | ||
|
|
||
| This displays the model, firmware, cache size, and supported features, which helps verify disk type and controller behavior. | ||
| This displays the model, firmware, cache size, and supported features, which helps verify disk type and controller behavior. | ||
|
|
||
| </details> |
There was a problem hiding this comment.
Incorrect content in PuTTY installation section.
The details block titled "How to install and use PuTTY" contains hdparm command documentation instead of PuTTY installation/usage instructions. This appears to be a content replacement error during the Crowdin update.
The hdparm content shown here (hdparm -I /dev/sdX) is useful for viewing drive information but belongs in a disk utilities section, not in the PuTTY SSH client setup guide.
🔍 Recommended action
Please restore the original PuTTY installation and usage instructions in this details block, or remove this section entirely if PuTTY setup guidance is no longer needed in the documentation.
🤖 Prompt for AI Agents
In
`@docs/unraid-os/system-administration/advanced-tools/command-line-interface.mdx`
around lines 42 - 53, The details block whose summary is "How to install and use
PuTTY" incorrectly contains disk utility content (`hdparm -I /dev/sdX`); locate
the details element with that exact summary text and either restore the original
PuTTY installation/usage instructions (replace the hdparm snippet with the
correct PuTTY commands and brief usage notes) or remove the entire details block
if PuTTY guidance is obsolete, ensuring no residual `hdparm` content remains in
that PuTTY section.
| | License Tier | %%Parity\|parity%%-Protected %%Array\|array%% | Named Pools | Devices per Pool | Total Storage Devices | | ||
| | ------------ | --------------------------------------------- | ----------- | ---------------- | --------------------- | | ||
| | Starter | Up to 6 (including parity) | Up to 6 | Up to 6 | Up to 6¹ | | ||
| | Unleashed | Up to 30 (28 data + 2 %%parity\|parity%%) | Up to 34 | Up to 200 | Unlimited² | | ||
| | Lifetime | Up to 30 (28 data + 2 %%parity\|parity%%) | Up to 34 | Up to 200 | Unlimited² | | ||
| | Starter | Up to 6 | 1 | Up to 6 | 6 | | ||
| | Unleashed | Up to 30 (28 data + 2 %%parity\|parity%%) | Up to 35 | Up to 60 | Unlimited\* | | ||
| | Lifetime | Up to 30 (28 data + 2 %%parity\|parity%%) | Up to 35 | Up to 60 | Unlimited\* | | ||
|
|
There was a problem hiding this comment.
Update devices-per-pool limits for Unleashed/Lifetime.
Lines 165-166 still list “Devices per Pool” as up to 60; this should be updated to the current 200-device limit to avoid understating capacity. Based on learnings: As of Unraid 7.2.1, the maximum devices per pool limit for Unleashed and Lifetime licenses is 200 (increased from previous limits of 60 in 6.12 and 120 in later versions).
🤖 Prompt for AI Agents
In `@docs/unraid-os/troubleshooting/licensing-faq.mdx` around lines 162 - 167,
Update the table entries for "Devices per Pool" for the Unleashed and Lifetime
rows: change the value currently shown as "Up to 60" to "Up to 200" so the table
reflects the Unraid 7.2.1 limit; locate the "Devices per Pool" column in the
rows for "Unleashed" and "Lifetime" in the license table and replace "Up to 60"
with "Up to 200".
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (5)
docs/unraid-os/troubleshooting/faq.mdx (2)
267-275:⚠️ Potential issue | 🟡 MinorFix the escaped list item so it renders as a bullet.
Line 274 uses\--, which will render as plain text instead of a list item.Suggested fix
- \-- Always [back up your flash drive](../system-administration/secure-your-server/secure-your-flash-drive.mdx#backups) before starting this conversion process. + - Always [back up your flash drive](../system-administration/secure-your-server/secure-your-flash-drive.mdx#backups) before starting this conversion process.
345-351:⚠️ Potential issue | 🟠 MajorUse the
EFI~folder name (tilde), notEFI-.
Line 351 referencesEFI-, but the correct Unraid UEFI folder isEFI~before renaming toEFI. Using a dash will mislead users.Based on learnings: The folder name for enabling UEFI boot mode in Unraid documentation is specified as "EFI~" (with a tilde), which is then renamed to "EFI".Suggested fix
-On the flash drive, rename the `EFI-` folder to `EFI` (remove the dash `-`). +On the flash drive, rename the `EFI~` folder to `EFI` (remove the tilde `~`).docs/API/programmatic-api-key-management.mdx (3)
70-134:⚠️ Potential issue | 🟡 MinorUnify JSON error field names in deletion examples.
One JSON error block uses
errorwhile another usesmessage. If the CLI uses a single field, align the examples (or clarify when each appears) to avoid confusion.
168-202:⚠️ Potential issue | 🟡 MinorStandardize role casing across docs.
Role casing is inconsistent:
programmatic-api-key-management.mdxuses uppercase (ADMIN,CONNECT,VIEWER,GUEST), whilehow-to-use-the-api.mdxandapi-key-app-developer-authorization-flow.mdxuse lowercase (admin,connect,guest; notably, the OAuth scope patterns showrole:viewerandrole:admin). Verify whether the CLI accepts both cases or if lowercase is canonical, then standardize across all documentation.
135-166:⚠️ Potential issue | 🟡 MinorClarify API header format (Bearer vs. x-api-key).
The example uses
Authorization: Bearerwhile other documentation showsx-api-key; confirm which header format the API actually supports or update for consistency.Additionally, the suggested refactoring (moving trap earlier and using a variable for the key name) is good practice to avoid code duplication, though the EXIT trap will execute with
set -eregardless of registration order.
🤖 Fix all issues with AI agents
In
`@docs/unraid-os/system-administration/advanced-tools/command-line-interface.mdx`:
- Around line 45-51: The "How to install and use PuTTY" section currently
contains unrelated content showing the command "hdparm -I /dev/sdX"; replace
that hdparm block with actual PuTTY installation and usage instructions (or
remove the section if PuTTY belongs elsewhere). Specifically, update the section
under the "How to install and use PuTTY" header to include steps to install
PuTTY (e.g., package install or download links), how to open a session, set
hostname/IP, select SSH, and save/connect settings; ensure the incorrect "hdparm
-I /dev/sdX" example is deleted so the section matches its header.
In `@docs/unraid-os/troubleshooting/licensing-faq.mdx`:
- Around line 210-214: There’s a mismatch between the two statements of trial
extension length; verify the authoritative product policy and make both
sentences consistent: update the sentence starting "You can extend your trial
for 15 more days..." and the paragraph under the "How do I extend my trial?
{`#extend-trial`}" (the line that reads "extended twice for 14 additional days
each time") so they use the same correct number of days and adjust any
surrounding phrasing to match (ensure both the short summary line and the
detailed paragraph reflect the same verified extension duration).
🧹 Nitpick comments (1)
docs/unraid-os/troubleshooting/licensing-faq.mdx (1)
49-60: Consider cleaning up deprecated iframe attributes.The iframe uses some deprecated/vendor-prefixed attributes that could be modernized:
frameBorder="0"→ use CSSstyle={{ border: 0 }}orborder: "none"webkitAllowFullScreenandmozAllowFullScreenare largely unnecessary in modern browsers♻️ Optional cleanup
<iframe title="Loom walkthrough: Unraid licensing FAQ" width="560" height="315" src="https://www.loom.com/embed/3ceb40440240474aaa80a0b7e3e69cb2" - frameBorder="0" - webkitAllowFullScreen - mozAllowFullScreen allowFullScreen allow="autoplay; fullscreen" + style={{ border: 0 }} + loading="lazy" ></iframe>
| **View drive information:** | ||
|
|
||
| ```bash | ||
| hdparm -I /dev/sdX | ||
| ``` | ||
| ```bash | ||
| hdparm -I /dev/sdX | ||
| ``` | ||
|
|
||
| This displays the model, firmware, cache size, and supported features, which helps verify disk type and controller behavior. | ||
| This displays the model, firmware, cache size, and supported features, which helps verify disk type and controller behavior. |
There was a problem hiding this comment.
Critical content mismatch: Wrong content under PuTTY section.
The section header says "How to install and use PuTTY" but the content describes the hdparm command (a disk information utility), which is unrelated to PuTTY installation or usage. This will confuse users seeking PuTTY guidance.
Please replace this content with actual PuTTY installation and connection instructions, or remove this section if the PuTTY guidance was intentionally relocated elsewhere in the documentation.
🤖 Prompt for AI Agents
In
`@docs/unraid-os/system-administration/advanced-tools/command-line-interface.mdx`
around lines 45 - 51, The "How to install and use PuTTY" section currently
contains unrelated content showing the command "hdparm -I /dev/sdX"; replace
that hdparm block with actual PuTTY installation and usage instructions (or
remove the section if PuTTY belongs elsewhere). Specifically, update the section
under the "How to install and use PuTTY" header to include steps to install
PuTTY (e.g., package install or download links), how to open a session, set
hostname/IP, select SSH, and save/connect settings; ensure the incorrect "hdparm
-I /dev/sdX" example is deleted so the section matches its header.
| - You can extend your trial for 15 more days if you need more time to evaluate Unraid. You can do this twice for a total of 60 days (details below). | ||
|
|
||
| ### How do I extend my trial? {#extend-trial} | ||
|
|
||
| Unraid trial registration keys last for 30 days and can be extended twice for 15 additional days each time. After two trial extensions, no additional extensions can be granted. To request an extension, you must stop the array, navigate to the **Tools > Registration** page, and click "Request Extension." | ||
| Unraid trial registration keys last for 30 days and can be extended twice for 14 additional days each time. After two trial extensions, no additional extensions can be granted. To request an extension, you must stop the array, navigate to the **Tools > Registration** page, and click "Request Extension." |
There was a problem hiding this comment.
Inconsistent trial extension duration.
There's a discrepancy in the trial extension duration:
- Line 210 states: "extend your trial for 15 more days"
- Line 214 states: "extended twice for 14 additional days each time"
Please verify and correct the trial extension duration to be consistent throughout the document.
🤖 Prompt for AI Agents
In `@docs/unraid-os/troubleshooting/licensing-faq.mdx` around lines 210 - 214,
There’s a mismatch between the two statements of trial extension length; verify
the authoritative product policy and make both sentences consistent: update the
sentence starting "You can extend your trial for 15 more days..." and the
paragraph under the "How do I extend my trial? {`#extend-trial`}" (the line that
reads "extended twice for 14 additional days each time") so they use the same
correct number of days and adjust any surrounding phrasing to match (ensure both
the short summary line and the detailed paragraph reflect the same verified
extension duration).
Image paths were incorrectly changed from ./assets/ to /img/ but images still exist in the assets directory. This caused build failures. Reverted all 16 image references back to ./assets/ paths.
There was a problem hiding this comment.
Actionable comments posted: 7
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (3)
i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (1)
148-179:⚠️ Potential issue | 🟠 MajorDuplicate "Gestión de licencias" sections detected.
Lines 148 and 168 both define
## Gestión de licenciasheaders. The first occurrence (lines 148-164) contains the Tabs component for customization, while the second (lines 168-179) contains the license management bullet points. This appears to be a merge artifact where the customization section content was incorrectly placed under a "Gestión de licencias" header.The Tabs component at lines 152-164 (banner, dashboard tiles, themes) belongs under the "Personalización" section that starts at line 138, not under "Gestión de licencias".
🔧 Suggested fix: Remove duplicate header and restructure
## Personalización El enlace profundo en Unraid Connect te permite saltar directamente a secciones específicas de tu WebGUI de Unraid con un solo clic. Simplemente haz clic en cualquiera de los botones de enlace circulares (abajo) en la interfaz de Connect para ir directamente a la página de gestión relevante para tu servidor. <div style={{ margen: 'auto', maxAnchura: '600px', display: 'flex', flexDirection: 'columna', alignItems: 'centro' }}>  </div> ---- - -## Gestión de licencias - -Gestionar tus licencias en Unraid Connect es fácil. Bajo la sección **Mis Claves**, puedes: - <Tabs> <TabItem value="banner" label="Cambiar imagen del banner" default> <ConnectChangeBanner /> </TabItem> <TabItem value="organizar" label="Reorganizar mosaicos del panel de control"> <ConnectRearrangeDashboard /> </TabItem> <TabItem value="tema" label="Cambiar temas"> <ConnectSwitchThemes /> </TabItem> </Tabs> --- ## Gestión de licenciasi18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx (2)
240-253:⚠️ Potential issue | 🟡 MinorDuplicate troubleshooting content.
Lines 241-242 contain orphaned text "Para resolución de problemas, ejecute con registro de depuración:" which duplicates line 258. The admonition block structure appears corrupted with content from different sections mixed together.
🔧 Suggested fix: Clean up the admonition
:::note[Common Mensajes de Error] -Para resolución de problemas, ejecute con registro de depuración: +**"Caracteres inválidos en el nombre"** - **Solución:** Elimine caracteres especiales como guiones, guiones bajos o símbolos **"Una clave API con el nombre 'x' ya existe"** - **Solución:** Use la bandera `--overwrite` o elija un nombre diferente **"Por favor, añada al menos un rol o permiso a la clave"** - **Solución:** Especifique ya sea `--roles` o `--permissions` (o ambos) :::Also, consider using fully Spanish for the admonition label:
-:::note[Common Mensajes de Error] +:::note[Mensajes de Error Comunes]
30-36:⚠️ Potential issue | 🟡 MinorDuplicate "Salida:" label.
Line 30 has
**Salida:**followed by the bash command block, and then line 36 has another**Salida:**for the JSON output. The first label at line 30 appears to be misplaced—it should describe output, not the command.🔧 Suggested fix
### Creación Básica con Salida en JSON -**Salida:** - ```bash unraid-api apikey --create --name "workflow key" --roles ADMIN --jsonSalida:
</details> </blockquote></details> </blockquote></details>🤖 Fix all issues with AI agents
In `@i18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx`: - Around line 234-245: Remove the duplicated "## ⏱️ Limitación de Tasa" section and its repeated admonition block (the two consecutive blocks starting with "## ⏱️ Limitación de Tasa" and the admonitions beginning with ":::caution[Rate Límites]" / ":::caution[Límites de Tasa]"); keep a single heading and one admonition (prefer the Spanish label ":::caution[Límites de Tasa]") and delete the other duplicate so only one consolidated "Limitación de Tasa" section remains. - Around line 266-281: Remove the duplicated English info block and keep a single Spanish :::info[Learn Más] block: delete the first English block and the duplicated English closing sentence, then ensure the remaining Spanish block contains the translated closing sentence ("Para más información sobre comandos específicos y opciones de configuración, consulta la [documentación de la CLI](cli.mdx) o ejecuta `unraid-api --help`.") so there is only one consolidated Spanish resources section (look for the :::info[Learn Más] blocks in the file). - Around line 26-33: Remove the duplicated info block that repeats "Usar la GUI Web es la forma más fácil de habilitar el sandbox de GraphQL"—keep a single info block with the correct Spanish heading and content; specifically delete either the ":::info[Preferred Método]" block or the ":::info[Método Preferido]" block so only one instance of the "Usar la GUI Web..." message remains and ensure the remaining block uses the consistent heading text ("Método Preferido"). - Around line 60-67: Remove the duplicated warning block under the "Autenticación" section: keep a single :::warning block with the message "La mayoría de las consultas y mutaciones requieren autenticación. Siempre incluya las credenciales apropiadas en sus solicitudes." and delete the repeated :::warning block so only one consolidated warning remains; look for the two identical ":::warning[Required para la mayoría de las operaciones]" / ":::warning[Requerido para la mayoría de las operaciones]" blocks in the file and retain only one. - Around line 216-231: Consolidate the duplicated ":::tip[Pro Consejos]" blocks into a single tip block: remove the redundant second ":::tip[Pro Consejos]" section and keep only one tip block containing the Spanish bullet list (the five items about Apollo Sandbox, starting with "Usa el Sandbox de Apollo..."), ensuring the final content uses Spanish phrasing consistently; update the existing ":::tip[Pro Consejos]" block that contains English items by replacing its list with the Spanish list so there is only one tip block in the document. In `@i18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx`: - Around line 224-235: The two sections "Gestión de Errores" and "Nomenclatura de Claves" contain orphaned "**Solución:**" lines—update the document so each solution has its matching problem statement or remove/merge the duplicates into the existing "Solución de problemas" section: either add a brief problem bullet above the solution in "Gestión de Errores" and "Nomenclatura de Claves" describing the issue (e.g., "Problema: Nombres con caracteres especiales" and "Problema: Intento de crear una clave con nombre duplicado"), or delete the redundant "**Solución:**" lines and reference the canonical entries under "Solución de problemas"; locate the headings "Gestión de Errores", "Nomenclatura de Claves", and "Solución de problemas" to apply the change. - Around line 20-24: The tip label "Quick Iniciar" mixes English and Spanish; replace that label text with a fully Spanish phrase such as "Inicio rápido" in the tip block (the string "Quick Iniciar") in programmatic-api-key-management.mdx so the tip reads ":::tip[Inicio rápido]" and update any other similar mixed-label occurrences to maintain consistent Spanish localization.🧹 Nitpick comments (2)
docs/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (1)
376-376: Tighten wording for concision.Consider a shorter phrasing for clarity.
Proposed tweak
-- **Expanding RAIDZ vdevs via the %%WebGUI|web-gui%%:** While Unraid 7.1.x and newer support RAIDZ expansion via the command line, this feature isn't yet available in the %%WebGUI|web-gui%%. For the time being, expand via the CLI or add new vdevs through the GUI. +- **Expanding RAIDZ vdevs via the %%WebGUI|web-gui%%:** While Unraid 7.1.x and newer support RAIDZ expansion via the command line, this feature isn't yet available in the %%WebGUI|web-gui%%. For now, expand via the CLI or add new vdevs through the GUI.i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (1)
189-192: Instruction steps out of order with description.Line 189 states "La interfaz se actualizará automáticamente para reflejar tu selección" which describes what happens after selecting a language, but it appears before the numbered steps (191-198) that explain how to select a language. This sentence should come after step 3.
🔧 Suggested fix: Reorder content
## Localización del idioma Unraid Connect admite múltiples idiomas para satisfacer a una base de usuarios global. Puedes cambiar tu preferencia de idioma a través del selector de idioma en la interfaz de Connect. -La interfaz se actualizará automáticamente para reflejar tu selección. - 1. Abre la UI de Connect. 2. Ve al selector de idiomas. <div style={{ margen: 'auto', maxAnchura: '600px', display: 'flex', flexDirection: 'columna', alignItems: 'centro' }}>  </div> 3. Selecciona tu idioma preferido de la lista. + +La interfaz se actualizará automáticamente para reflejar tu selección.
| :::info[Preferred Método] | ||
|
|
||
| Usar la GUI Web es la forma más fácil de habilitar el sandbox de GraphQL. | ||
|
|
||
| :::info[Método Preferido] | ||
|
|
||
| Usar la GUI Web es la forma más fácil de habilitar el sandbox de GraphQL. | ||
|
|
There was a problem hiding this comment.
Evita el bloque duplicado en “Método GUI Web”.
Ahora hay dos bloques consecutivos con el mismo contenido. Deja solo uno para evitar repetición.
✂️ Consolidar el bloque de GUI Web
-:::info[Preferred Método]
-
-Usar la GUI Web es la forma más fácil de habilitar el sandbox de GraphQL.
-
-:::info[Método Preferido]
+:::info[Método Preferido]
Usar la GUI Web es la forma más fácil de habilitar el sandbox de GraphQL.🧰 Tools
🪛 LanguageTool
[grammar] ~28-~28: Corrige la mayúscula.
Context: ... :::info[Preferred Método] Usar la GUI Web es la forma más fácil de habilitar el s...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~30-~30: Corrige la mayúscula.
Context: ... el sandbox de GraphQL. :::info[Método Preferido] Usar la GUI Web es la forma más fácil...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~32-~32: Corrige la mayúscula.
Context: ... :::info[Método Preferido] Usar la GUI Web es la forma más fácil de habilitar el s...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
🤖 Prompt for AI Agents
In `@i18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx`
around lines 26 - 33, Remove the duplicated info block that repeats "Usar la GUI
Web es la forma más fácil de habilitar el sandbox de GraphQL"—keep a single info
block with the correct Spanish heading and content; specifically delete either
the ":::info[Preferred Método]" block or the ":::info[Método Preferido]" block
so only one instance of the "Usar la GUI Web..." message remains and ensure the
remaining block uses the consistent heading text ("Método Preferido").
| :::warning[Required para la mayoría de las operaciones] | ||
|
|
||
| La mayoría de las consultas y mutaciones requieren autenticación. Siempre incluya las credenciales apropiadas en sus solicitudes. | ||
|
|
||
| :::warning[Requerido para la mayoría de las operaciones] | ||
|
|
||
| La mayoría de las consultas y mutaciones requieren autenticación. Siempre incluya las credenciales apropiadas en sus solicitudes. | ||
|
|
There was a problem hiding this comment.
Evita el bloque duplicado en “Autenticación”.
Hay dos advertencias iguales con texto repetido. Mantén solo una.
✂️ Consolidar advertencia de autenticación
-:::warning[Required para la mayoría de las operaciones]
-
-La mayoría de las consultas y mutaciones requieren autenticación. Siempre incluya las credenciales apropiadas en sus solicitudes.
-
-:::warning[Requerido para la mayoría de las operaciones]
+:::warning[Requerido para la mayoría de las operaciones]
La mayoría de las consultas y mutaciones requieren autenticación. Siempre incluya las credenciales apropiadas en sus solicitudes.🤖 Prompt for AI Agents
In `@i18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx`
around lines 60 - 67, Remove the duplicated warning block under the
"Autenticación" section: keep a single :::warning block with the message "La
mayoría de las consultas y mutaciones requieren autenticación. Siempre incluya
las credenciales apropiadas en sus solicitudes." and delete the repeated
:::warning block so only one consolidated warning remains; look for the two
identical ":::warning[Required para la mayoría de las operaciones]" /
":::warning[Requerido para la mayoría de las operaciones]" blocks in the file
and retain only one.
| :::tip[Pro Consejos] | ||
|
|
||
| 1. Use the Apollo Sandbox to explore the schema and test queries | ||
| 2. Empieza con consultas pequeñas y gradualmente agrega campos según sea necesario | ||
| 3. Monitoree la complejidad de su consulta para mantener el rendimiento | ||
| 4. Use roles y permisos apropiados para sus claves API | ||
| 5. Mantenga sus claves API seguras y rótelas periódicamente | ||
|
|
||
| :::tip[Pro Consejos] | ||
|
|
||
| 1. Usa el Sandbox de Apollo para explorar el esquema y probar consultas | ||
| 2. Empieza con consultas pequeñas y gradualmente agrega campos según sea necesario | ||
| 3. Monitoree la complejidad de su consulta para mantener el rendimiento | ||
| 4. Usa roles y permisos apropiados para tus claves API | ||
| 5. Mantenga sus claves API seguras y rótelas periódicamente | ||
|
|
There was a problem hiding this comment.
Consolida “Mejores Prácticas” en un solo bloque.
Actualmente hay dos tips con listas duplicadas. Mantén un único bloque con la lista en español.
✂️ Consolidar “Pro Consejos”
-:::tip[Pro Consejos]
-
-1. Use the Apollo Sandbox to explore the schema and test queries
-2. Empieza con consultas pequeñas y gradualmente agrega campos según sea necesario
-3. Monitoree la complejidad de su consulta para mantener el rendimiento
-4. Use roles y permisos apropiados para sus claves API
-5. Mantenga sus claves API seguras y rótelas periódicamente
-
-:::tip[Pro Consejos]
-1. Usa el Sandbox de Apollo para explorar el esquema y probar consultas
-2. Empieza con consultas pequeñas y gradualmente agrega campos según sea necesario
-3. Monitoree la complejidad de su consulta para mantener el rendimiento
-4. Usa roles y permisos apropiados para tus claves API
-5. Mantenga sus claves API seguras y rótelas periódicamente
+:::tip[Pro Consejos]
+1. Usa el Sandbox de Apollo para explorar el esquema y probar consultas
+2. Empieza con consultas pequeñas y gradualmente agrega campos según sea necesario
+3. Monitoree la complejidad de su consulta para mantener el rendimiento
+4. Usa roles y permisos apropiados para tus claves API
+5. Mantenga sus claves API seguras y rótelas periódicamente🧰 Tools
🪛 LanguageTool
[grammar] ~218-~218: Cambia la palabra o signo.
Context: ...Prácticas :::tip[Pro Consejos] 1. Use the Apollo Sandbox to explore the schema an...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~218-~218: Oración con errores
Context: ...ro Consejos] 1. Use the Apollo Sandbox to explore the schema and test queries 2. ...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~218-~218: Oración con errores
Context: ...Consejos] 1. Use the Apollo Sandbox to explore the schema and test queries 2. Empieza ...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~218-~218: Oración con errores
Context: ...] 1. Use the Apollo Sandbox to explore the schema and test queries 2. Empieza con ...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~218-~218: Oración con errores
Context: .... Use the Apollo Sandbox to explore the schema and test queries 2. Empieza con consult...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~218-~218: Oración con errores
Context: ...he Apollo Sandbox to explore the schema and test queries 2. Empieza con consultas p...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~218-~218: Oración con errores
Context: ...pollo Sandbox to explore the schema and test queries 2. Empieza con consultas pequeñ...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~218-~218: Oración con errores
Context: ... Sandbox to explore the schema and test queries 2. Empieza con consultas pequeñas y gradualmente a...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~219-~219: Cambia la forma del verbo.
Context: ...a con consultas pequeñas y gradualmente agrega campos según sea necesario 3. Monitoree...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_VERB_FORM)
[grammar] ~219-~219: Cambia la palabra o signo.
Context: ...lmente agrega campos según sea necesario 3. Monitoree la complejidad de su consulta ...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~220-~220: Cambia la palabra o signo.
Context: ...su consulta para mantener el rendimiento 4. Use roles y permisos apropiados para sus...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~221-~221: Cambia la palabra o signo.
Context: ... permisos apropiados para sus claves API 5. Mantenga sus claves API seguras y rótela...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~222-~222: Aquí puede haber un error.
Context: ...ves API seguras y rótelas periódicamente :::tip[Pro Consejos] 1. Usa el Sandbox ...
(QB_NEW_ES)
[grammar] ~226-~226: Cambia la palabra o signo.
Context: ...a explorar el esquema y probar consultas 2. Empieza con consultas pequeñas y gradual...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~227-~227: Oración con errores
Context: ...lmente agrega campos según sea necesario 3. Monitoree la complejidad de su consulta para mant...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~228-~228: Cambia el articulo.
Context: ...ecesario 3. Monitoree la complejidad de su consulta para mantener el rendimiento 4...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_DETERMINER)
[grammar] ~228-~228: Cambia la palabra o signo.
Context: ...su consulta para mantener el rendimiento 4. Usa roles y permisos apropiados para tus...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~229-~229: Oración con errores
Context: ... permisos apropiados para tus claves API 5. Mantenga sus claves API seguras y rótelas periód...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~230-~230: Oración con errores
Context: ...opiados para tus claves API 5. Mantenga sus claves API seguras y rótelas periódicam...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~230-~230: Cambia la palabra según la sugerencia.
Context: ...PI 5. Mantenga sus claves API seguras y rótelas periódicamente ::: ## ⏱️ Limitación d...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_CONFUSION)
[grammar] ~230-~230: Aquí puede haber un error.
Context: ...ves API seguras y rótelas periódicamente ::: ## ⏱️ Limitación de Tasa :::cautio...
(QB_NEW_ES)
🤖 Prompt for AI Agents
In `@i18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx`
around lines 216 - 231, Consolidate the duplicated ":::tip[Pro Consejos]" blocks
into a single tip block: remove the redundant second ":::tip[Pro Consejos]"
section and keep only one tip block containing the Spanish bullet list (the five
items about Apollo Sandbox, starting with "Usa el Sandbox de Apollo..."),
ensuring the final content uses Spanish phrasing consistently; update the
existing ":::tip[Pro Consejos]" block that contains English items by replacing
its list with the Spanish list so there is only one tip block in the document.
| ## ⏱️ Limitación de Tasa | ||
|
|
||
| :::caution[Rate Límites] | ||
|
|
||
| La API implementa la limitación de tasas para prevenir abusos. Asegúrese de que sus aplicaciones manejen adecuadamente las respuestas de limitación de tasas. | ||
|
|
||
| ## ⏱️ Limitación de Tasa | ||
|
|
||
| :::caution[Límites de Tasa] | ||
|
|
||
| La API implementa la limitación de tasas para prevenir abusos. Asegúrese de que sus aplicaciones manejen adecuadamente las respuestas de limitación de tasas. | ||
|
|
There was a problem hiding this comment.
Elimina la sección duplicada de limitación de tasa.
Hay dos encabezados y dos admoniciones consecutivas. Deja solo una sección.
✂️ Consolidar “Limitación de Tasa”
-## ⏱️ Limitación de Tasa
-
-:::caution[Rate Límites]
-
-La API implementa la limitación de tasas para prevenir abusos. Asegúrese de que sus aplicaciones manejen adecuadamente las respuestas de limitación de tasas.
-
-## ⏱️ Limitación de Tasa
-
-:::caution[Límites de Tasa]
+## ⏱️ Limitación de Tasa
+
+:::caution[Límites de Tasa]
La API implementa la limitación de tasas para prevenir abusos. Asegúrese de que sus aplicaciones manejen adecuadamente las respuestas de limitación de tasas.📝 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.
| ## ⏱️ Limitación de Tasa | |
| :::caution[Rate Límites] | |
| La API implementa la limitación de tasas para prevenir abusos. Asegúrese de que sus aplicaciones manejen adecuadamente las respuestas de limitación de tasas. | |
| ## ⏱️ Limitación de Tasa | |
| :::caution[Límites de Tasa] | |
| La API implementa la limitación de tasas para prevenir abusos. Asegúrese de que sus aplicaciones manejen adecuadamente las respuestas de limitación de tasas. | |
| ## ⏱️ Limitación de Tasa | |
| :::caution[Límites de Tasa] | |
| La API implementa la limitación de tasas para prevenir abusos. Asegúrese de que sus aplicaciones manejen adecuadamente las respuestas de limitación de tasas. |
🧰 Tools
🪛 LanguageTool
[grammar] ~234-~234: Corrige la mayúscula.
Context: ...eriódicamente ::: ## ⏱️ Limitación de Tasa :::caution[Rate Límites] La API impleme...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~240-~240: Corrige la mayúscula.
Context: ...mitación de tasas. ## ⏱️ Limitación de Tasa :::caution[Límites de Tasa] La API impl...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~242-~242: Corrige la mayúscula.
Context: ...mitación de Tasa :::caution[Límites de Tasa] La API implementa la limitación de ta...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
🤖 Prompt for AI Agents
In `@i18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx`
around lines 234 - 245, Remove the duplicated "## ⏱️ Limitación de Tasa" section
and its repeated admonition block (the two consecutive blocks starting with "##
⏱️ Limitación de Tasa" and the admonitions beginning with ":::caution[Rate
Límites]" / ":::caution[Límites de Tasa]"); keep a single heading and one
admonition (prefer the Spanish label ":::caution[Límites de Tasa]") and delete
the other duplicate so only one consolidated "Limitación de Tasa" section
remains.
| :::info[Learn Más] | ||
|
|
||
| - Use the Apollo Sandbox's schema explorer to browse all available types and fields | ||
| - Check the documentation tab in Apollo Sandbox for detailed field descriptions | ||
| - Monitor the API's health using `unraid-api status` | ||
| - Generate reports using `unraid-api report` for troubleshooting | ||
|
|
||
| For more information about specific commands and configuration options, refer to the [CLI documentation](cli.mdx) or run `unraid-api --help`. | ||
| :::info[Learn Más] | ||
|
|
||
| - Usa el explorador de esquemas del Sandbox de Apollo para examinar todos los tipos y campos disponibles | ||
| - Consulta la pestaña de documentación en el Sandbox de Apollo para descripciones detalladas de campos | ||
| - Monitorea la salud de la API usando `unraid-api status` | ||
| - Genera reportes usando `unraid-api report` para solucionar problemas | ||
|
|
||
| For more information about specific commands and configuration options, refer to the [CLI documentation](cli.mdx) or run `unraid-api --help`. |
There was a problem hiding this comment.
Consolida “Recursos Adicionales” y mantén una sola versión en español.
Hay dos bloques y la línea final está duplicada en inglés. Mantén un solo bloque en español y traduce el cierre.
✂️ Consolidar recursos y traducir el cierre
-:::info[Learn Más]
-
-- Use the Apollo Sandbox's schema explorer to browse all available types and fields
-- Check the documentation tab in Apollo Sandbox for detailed field descriptions
-- Monitor the API's health using `unraid-api status`
-- Generate reports using `unraid-api report` for troubleshooting
-
-For more information about specific commands and configuration options, refer to the [CLI documentation](cli.mdx) or run `unraid-api --help`.
-:::info[Learn Más]
-
-- Usa el explorador de esquemas del Sandbox de Apollo para examinar todos los tipos y campos disponibles
-- Consulta la pestaña de documentación en el Sandbox de Apollo para descripciones detalladas de campos
-- Monitorea la salud de la API usando `unraid-api status`
-- Genera reportes usando `unraid-api report` para solucionar problemas
-
-For more information about specific commands and configuration options, refer to the [CLI documentation](cli.mdx) or run `unraid-api --help`.
+:::info[Learn Más]
+
+- Usa el explorador de esquemas del Sandbox de Apollo para examinar todos los tipos y campos disponibles
+- Consulta la pestaña de documentación en el Sandbox de Apollo para descripciones detalladas de campos
+- Monitorea la salud de la API usando `unraid-api status`
+- Genera reportes usando `unraid-api report` para solucionar problemas
+
+Para más información sobre comandos específicos y opciones de configuración, consulte la [documentación de la CLI](cli.mdx) o ejecute `unraid-api --help`.🧰 Tools
🪛 LanguageTool
[grammar] ~268-~268: Cambia la palabra o signo.
Context: ...to browse all available types and fields - Check the documentation tab in Apollo Sa...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~269-~269: Cambia la palabra o signo.
Context: ... Sandbox for detailed field descriptions - Monitor the API's health using `unraid-a...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~270-~270: Cambia la palabra o signo.
Context: ...iptions - Monitor the API's health using unraid-api status - Generate reports using `unraid-api repor...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~271-~271: Aquí puede haber un error.
Context: ... unraid-api report for troubleshooting For more information about specific comm...
(QB_NEW_ES)
[grammar] ~276-~276: Cambia la palabra o signo.
Context: ...nar todos los tipos y campos disponibles - Consulta la pestaña de documentación en ...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~277-~277: Cambia la palabra o signo.
Context: ... para descripciones detalladas de campos - Monitorea la salud de la API usando `unr...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~278-~278: Oración con errores
Context: ...de campos - Monitorea la salud de la API usando unraid-api status - Genera reportes usando `unraid-api repor...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~279-~279: Aquí puede haber un error.
Context: ...id-api report` para solucionar problemas For more information about specific comm...
(QB_NEW_ES)
🤖 Prompt for AI Agents
In `@i18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx`
around lines 266 - 281, Remove the duplicated English info block and keep a
single Spanish :::info[Learn Más] block: delete the first English block and the
duplicated English closing sentence, then ensure the remaining Spanish block
contains the translated closing sentence ("Para más información sobre comandos
específicos y opciones de configuración, consulta la [documentación de la
CLI](cli.mdx) o ejecuta `unraid-api --help`.") so there is only one consolidated
Spanish resources section (look for the :::info[Learn Más] blocks in the file).
| :::tip[Quick Iniciar] | ||
|
|
||
| Salte a la [Ejemplo Completo del Flujo de Trabajo](#complete-workflow-example) para ver todo en acción. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Mixed English-Spanish in tip label.
Line 20 uses "Quick Iniciar" which mixes English ("Quick") with Spanish ("Iniciar"). Use a fully Spanish phrase for consistency.
🔧 Suggested fix
-:::tip[Quick Iniciar]
+:::tip[Inicio Rápido]📝 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.
| :::tip[Quick Iniciar] | |
| Salte a la [Ejemplo Completo del Flujo de Trabajo](#complete-workflow-example) para ver todo en acción. | |
| ::: | |
| :::tip[Inicio Rápido] | |
| Salte a la [Ejemplo Completo del Flujo de Trabajo](`#complete-workflow-example`) para ver todo en acción. | |
| ::: |
🧰 Tools
🪛 LanguageTool
[grammar] ~21-~21: Cambia la forma del sustantivo.
Context: ...ura como código :::tip[Quick Iniciar] Salte a la [Ejemplo Completo del Flujo de Tra...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_NOUN_FORM)
🤖 Prompt for AI Agents
In
`@i18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx`
around lines 20 - 24, The tip label "Quick Iniciar" mixes English and Spanish;
replace that label text with a fully Spanish phrase such as "Inicio rápido" in
the tip block (the string "Quick Iniciar") in
programmatic-api-key-management.mdx so the tip reads ":::tip[Inicio rápido]" and
update any other similar mixed-label occurrences to maintain consistent Spanish
localization.
| ### Gestión de Errores | ||
|
|
||
| - Verificar códigos de salida (`$?`) después de cada comando | ||
| - **Solución:** Elimine caracteres especiales como guiones, guiones bajos o símbolos | ||
| - Usar `set -e` en scripts bash para fallar rápidamente | ||
| - Implementar limpieza adecuada con `trap` | ||
|
|
||
| ### Nomenclatura de Claves | ||
|
|
||
| - Usar nombres descriptivos que incluyan propósito y fecha | ||
| - **Solución:** Use la bandera `--overwrite` o elija un nombre diferente | ||
| - Los nombres deben contener solo letras, números y espacios | ||
| - Se admiten letras Unicode | ||
|
|
There was a problem hiding this comment.
Orphaned "Solución" entries without corresponding problem statements.
The "Gestión de Errores" section (lines 224-229) and "Nomenclatura de Claves" section (lines 230-235) contain "Solución:" entries that lack their corresponding problem statements. These appear to be duplicated from the "Solución de problemas" section (lines 244-252) which has the proper problem-solution format.
The current structure lists solutions without context:
- Line 226: Solution about special characters (no problem stated)
- Line 232: Solution about
--overwriteflag (no problem stated)
🔧 Suggested fix: Restructure with proper problem statements or remove duplicates
### Gestión de Errores
-- **Solución:** Elimine caracteres especiales como guiones, guiones bajos o símbolos
- Usar `set -e` en scripts bash para fallar rápidamente
- Implementar limpieza adecuada con `trap`
### Nomenclatura de Claves
-- **Solución:** Use la bandera `--overwrite` o elija un nombre diferente
- Los nombres deben contener solo letras, números y espacios
- Se admiten letras Unicode📝 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.
| ### Gestión de Errores | |
| - Verificar códigos de salida (`$?`) después de cada comando | |
| - **Solución:** Elimine caracteres especiales como guiones, guiones bajos o símbolos | |
| - Usar `set -e` en scripts bash para fallar rápidamente | |
| - Implementar limpieza adecuada con `trap` | |
| ### Nomenclatura de Claves | |
| - Usar nombres descriptivos que incluyan propósito y fecha | |
| - **Solución:** Use la bandera `--overwrite` o elija un nombre diferente | |
| - Los nombres deben contener solo letras, números y espacios | |
| - Se admiten letras Unicode | |
| ### Gestión de Errores | |
| - Usar `set -e` en scripts bash para fallar rápidamente | |
| - Implementar limpieza adecuada con `trap` | |
| ### Nomenclatura de Claves | |
| - Los nombres deben contener solo letras, números y espacios | |
| - Se admiten letras Unicode |
🧰 Tools
🪛 LanguageTool
[grammar] ~224-~224: Corrige la mayúscula.
Context: ...astro de auditoría ::: ### Gestión de Errores - Solución: Elimine caracteres especiale...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~226-~226: Aquí puede haber un error.
Context: ...toría ::: ### Gestión de Errores - Solución: Elimine caracteres especiales como gu...
(QB_NEW_ES)
[grammar] ~226-~226: Cambia la palabra o signo.
Context: ...s como guiones, guiones bajos o símbolos - Usar set -e en scripts bash para falla...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~227-~227: Cambia la palabra o signo.
Context: ... en scripts bash para fallar rápidamente - Implementar limpieza adecuada con trap...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~230-~230: Corrige la mayúscula.
Context: ...decuada con trap ### Nomenclatura de Claves - Solución: Use la bandera --overwrite...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~232-~232: Aquí puede haber un error.
Context: ...trap ### Nomenclatura de Claves - Solución: Use la bandera --overwrite o elija ...
(QB_NEW_ES)
[grammar] ~232-~232: Agrega un espacio.
Context: ... Nomenclatura de Claves - Solución: Use la bandera --overwrite o elija un ...
(QB_NEW_ES_OTHER_ERROR_IDS_MISSING_ORTHOGRAPHY_SPACE)
[grammar] ~232-~232: Cambia la palabra o signo.
Context: ...--overwrite` o elija un nombre diferente - Los nombres deben contener solo letras, ...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~233-~233: Cambia la palabra o signo.
Context: ...contener solo letras, números y espacios - Se admiten letras Unicode ## Solución d...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~234-~234: Aquí puede haber un error.
Context: ...s y espacios - Se admiten letras Unicode ## Solución de problemas ### Problemas Com...
(QB_NEW_ES)
🤖 Prompt for AI Agents
In
`@i18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx`
around lines 224 - 235, The two sections "Gestión de Errores" and "Nomenclatura
de Claves" contain orphaned "**Solución:**" lines—update the document so each
solution has its matching problem statement or remove/merge the duplicates into
the existing "Solución de problemas" section: either add a brief problem bullet
above the solution in "Gestión de Errores" and "Nomenclatura de Claves"
describing the issue (e.g., "Problema: Nombres con caracteres especiales" and
"Problema: Intento de crear una clave con nombre duplicado"), or delete the
redundant "**Solución:**" lines and reference the canonical entries under
"Solución de problemas"; locate the headings "Gestión de Errores", "Nomenclatura
de Claves", and "Solución de problemas" to apply the change.
1 participant
Summary by CodeRabbit
Documentation
Storage
WebGUI & Remote
Localization
✏️ Tip: You can customize this high-level summary in your review settings.