New translations array-check-parity.mdx (German)

Author: elibosley

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx

@@ -11,6 +11,7 @@ A %%parity check|parity-check%% is essential when your array includes at least o
   - **Nicht korrigierend (NOCORRECT):** Protokolliert nur gefundene Fehler, ohne die Parität zu aktualisieren.
 
   To avoid excessive logging, only the first 100 addresses with errors are reported during a %%parity check|parity-check%%. These mismatches are referred to as **sync errors** and indicate where the parity does not align with the data, typically due to issues such as sudden power losses or hardware problems. Each sync error is counted in 4KiB blocks - this is the system's I/O unit size (known as the Linux page size).
+
 </details>
 
 <details>
@@ -19,6 +20,7 @@ A %%parity check|parity-check%% is essential when your array includes at least o
   A **valid %%parity disk|parity-drives%%** indicates that after the last successful %%parity|parity%% sync, Unraid recognized the %%parity|parity%% as "good," meaning it's suitable for data recovery if a disk fails. The "valid" status applies to every disk in the array, not just the %%parity|parity%% one. If all disks except one are valid, Unraid can reconstruct the missing or failed disk's data using %%parity|parity%%.
 
   Unraid maintains the %%parity disk|parity-drives%%'s "valid" status even when some sync errors occur following a non-correcting check. This ensures that you can still recover a failed disk. If the %%parity|parity%% were marked as invalid, you would risk having two invalid disks after just one additional failure, leading to potential data loss.
+
 </details>
 
 While a %%parity check|parity-check%% is in progress, you can still use the array. However, be aware that performance may slow down due to drive contention, as both file operations and the check will compete for resources.