docs_in_draft:snapraid

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
docs_in_draft:snapraid [2023/04/28 23:10] – Various Pre-Draft edits. crashtestdocs_in_draft:snapraid [2023/04/28 23:27] – [Replacing a Failed Drive in MergerFS] crashtest
Line 325: Line 325:
   * Docker Containers that are stored on data drives should be paused or stopped during a sync.  Otherwise Sync errors may result.   * Docker Containers that are stored on data drives should be paused or stopped during a sync.  Otherwise Sync errors may result.
   * It is recommended that SnapRAID's parity drive is relatively new and closely monitored using SMART.  Without parity data, recoveries are not possible.   * It is recommended that SnapRAID's parity drive is relatively new and closely monitored using SMART.  Without parity data, recoveries are not possible.
 +  * For a better understanding of the SnapRAID works and it's features, reading the -> [[https://www.snapraid.it/manual|SnapRAID manual]] is recommended.  
 \\ \\
 \\ \\
Line 340: Line 341:
 ---- ----
  
-===== Source Code ===== 
- 
--> [[https://github.com/OpenMediaVault-Plugin-Developers/snapraid|Source Code]] 
  
 \\ \\
Line 371: Line 369:
   * Do not run a **Snyc** operation until after the replacement is completed.   * Do not run a **Snyc** operation until after the replacement is completed.
   * If user / admins have automated processes (downloaders, media centers, etc.) that save or move files on protected drives, they should be paused or turned off.   * If user / admins have automated processes (downloaders, media centers, etc.) that save or move files on protected drives, they should be paused or turned off.
-  * Users should be informed to not use the server during the drive replacement.  (This could be enforced by temporarily disabling file sharing services like SMB or NFS.)+  * Server users should be informed to not use the server during the drive replacement.  (This could be enforced by temporarily disabling file sharing services like SMB or NFS.)
  
  
Line 380: Line 378:
 In the following scenario, a SnapRAID protected drive has failed completely.\\  In the following scenario, a SnapRAID protected drive has failed completely.\\ 
 \\ \\
-When server notifications are -> [[https://wiki.omv-extras.org/doku.php?id=omv6:new_user_guide#server_notifications|configured as recommended]] , user / admins are notified by e-mail of **file system failures** and other issues. +When server notifications are -> [[https://wiki.omv-extras.org/doku.php?id=omv6:new_user_guide#server_notifications|configured as recommended]] , user / admins are notified by e-mail of **file system failures** and other issues.\\ 
 +\\
 {{ ::omv6-plugins-snapraid-14.jpg?nolink&600 |}}  {{ ::omv6-plugins-snapraid-14.jpg?nolink&600 |}} 
  
Line 547: Line 545:
 ---- ----
  
-Under **Storage**, **File Systems**, the **missing** drive should no longer be "**Referenced**" Highlight the **missing** drive, **unmount** it and **Apply** the change. +Under **Storage**, **File Systems**, the **missing** drive should no longer be "**Referenced**" Highlight the **missing** drive, **unmount** it and **Apply** the change.\\
- +
-This concludes adding a SnapRAID restored drive to a MergerFS array. +
 Finally, re-enable all automated tasks and enable network shares (if previously disabled.)\\ Finally, re-enable all automated tasks and enable network shares (if previously disabled.)\\
 +\\
 +This concludes adding a SnapRAID restored drive to a MergerFS array.\\
 +\\
 +\\
 +===== Source Code =====
 +
 +-> [[https://github.com/OpenMediaVault-Plugin-Developers/snapraid|Source Code]]
  
  
  • docs_in_draft/snapraid.txt
  • Last modified: 2024/05/05 02:35
  • by crashtest