Differences

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

--- docs_in_draft:snapraid [2024/12/11 14:55] – [Restore Data] crashtest
+++ docs_in_draft:snapraid [2025/02/24 15:17] (current) – crashtest
@@ Line 1: / Line 1: @@
+{{indexmenu_n>9}}
+\\
 <html><center><span style="color:#b7620b;font-size:300%;">Incomplete Document</span></center></html>
 <html><center><span style="color:#b7620b;font-size:300%;">Not for public use</span></center></html>
 {{ :underconstruction.jpg?400 |}}
 \\
 <html><!---
@@ Line 39: / Line 43: @@
   * [[https://wiki.omv-extras.org/doku.php?id=misc_docs:omv_extras|OMV-Extras]] must be pre-installed.
   * An additional (dedicated) drive is required to store SnapRAID parity data.  SnapRAID's parity drive must be the same size, or larger, than the largest protected drive.  This is a hard requirment.
-  * For reports on drive health and automating SnapRAID administrative tasks, setting up -> [[https://wiki.omv-extras.org/doku.php?id=omv6:new_user_guide#server_notifications|Server Notifications]] is **recommended**.
+  * For reports on drive health and automating SnapRAID administrative tasks, setting up -> [[https://wiki.omv-extras.org/doku.php?id=omv7:new_user_guide#server_notifications|Server Notifications]] is **recommended**.
   * Enabling -> [[https://wiki.omv-extras.org/doku.php?id=omv7:new_user_guide#hard_drive_health_and_smart|SMART]] and scheduling a weekly short test, for all protected drives, is recommended.
   * Consider testing the server's ram with a test program like -> [[https://www.memtest86.com/|memtest86]].  Faulty ram is a known cause for data loss when using SnapRAID.
@@ Line 187: / Line 191: @@
       <td style="background-color:#E6FEFF;height:25px;width:380px;">
         Split Parity is a new SnapRAID feature that is supported in OMV7:<br>
-        - While the rule, "<i><b>the parity drive must equal or exceed the size of the largest protected data drive</i></b>" still applies; split parity allows combing smaller drives to create what appears to be a single large parity drive.<br>
+        - While the rule, "<i><b>the parity drive must equal or exceed the size of the largest protected data drive</i></b>" still applies; split parity allows combining smaller drives to create what appears to be a single large parity drive.<br>
         - New users should note that split parity is an advanced feature that increases admin complexity. Split parity configurations are not recommended for users who are not familiar with SnapRAID.
     </tr>
@@ Line 344: / Line 348: @@
 \\
 **1**.  For most users, the defaults in these fields are fine.\\
-**2**.  **Send Mail** will work only if users have configured and tested notifications, as outlined here -> [[https://wiki.omv-extras.org/doku.php?id=omv6:new_user_guide#server_notifications|Server Notifications]].  Configuring Server Notifications and selecting **Send Mail** is highly recommended.\\
+**2**.  **Send Mail** will work only if users have configured and tested notifications, as outlined here -> [[https://wiki.omv-extras.org/doku.php?id=omv7:new_user_guide#server_notifications|Server Notifications]].  Configuring Server Notifications and selecting **Send Mail** is highly recommended.\\
 **3**.  **Run Scrub**   This is a recommended action to complete the SnapRAID maintenance cycle.  While **Diff** and **Sync** run quickly, dependent of the size of protected disks and other factors, **Scrub** may take considerable time.\\
 **4**.  **Pre-hash** is an option that is used together with the** Sync** command.  **Pre-hash** assigns a checksum before parity calculations are done.  It's an extra safety measure that reads data two times to insure integrity.\\
@@ Line 467: / Line 471: @@
 ----
 <html><center><b>Physically remove the drive.</b></center></html>
-<html><center>If necessary, refer to <b>Storage</b>, <b>Disks</b> and compare serial numbers to drive device names under <b>Storage</b>, <b>File Systems</b>.  The idea is to look at drive labels and find the serial number that is "missing" (not displayed), to insure that the correct physical drive is removed.</center></html>
+<html><center>If necessary, refer to <b>Storage</b>, <b>Disks</b> and compare serial numbers to drive device names under <b>Storage</b>, <b>File Systems</b>.  The idea is to look at the drive's physical label and find the serial number that is "missing" (not displayed), to insure that the correct physical drive is removed.</center></html>
 \\
 {{ :omv7:omv7_plugins:omv7-plugins-snapraid-19.jpg?nolink&800 |}}
@@ Line 502: / Line 506: @@
 \\
-<html><center>Click **Save** and **apply** the configuration change.</center></html>
+<html><center>Click <b>Save</b> and <b>apply</b> the configuration change.</center></html>
 \\
 ----
@@ Line 556: / Line 560: @@
 {{ ::omv6-plugins-snapraid-26.jpg?nolink&600 |}}
 \\
-<html><center>(The UNRECOVERABLE error may be due to a change made //after// the last **Sync** operation, that cannot be restored.)</center></html>
+<html><center>(The UNRECOVERABLE error may be due to a change made <i>after</i> the last **Sync** operation, that cannot be restored.)</center></html>
 ----
@@ Line 562: / Line 567: @@
 \\
 This concludes data restoration to a SnapRAID protected drive.\\
-**MergerFS users** skip see the section below titled; **Replacing a Failed Drive in MergerFS**. \\
+**MergerFS users** skip see the section below titled; **Replacing a Failed Drive in MergerFS**.\\
 ----
 The remainder of tasks, within OMV, would be to repointing **Shared Folders** and other services to the replacement drive.  To repoint shared folders, see the guidance provided -> [[https://wiki.omv-extras.org/doku.php?id=omv6:utilities_maint_backup#repointing_a_shared_folder|here]].\\
 \\
@@ Line 600: / Line 607: @@
 ----
 \\
-The result now shows mount points by UUID.  Where device names may be reordered on bootup, UUID's do not change.<html><center>\\
+The result now shows mount points by **UUID** (**U**niversally **U**nique **ID**entifier).  Where device names may be reordered by BIOS or UEFI on bootup, UUID's do not change.\\
 Note the "Copy and Paste" Icon{{:OMV6-Plugins-SnapRAID-05-06.jpg?25|}} at the end of each drive UUID.  This tool copies exact drive paths and UUID's to the clipboard.\\
@@ Line 635: / Line 642: @@
 ===== Source Code =====
--> [[https://github.com/OpenMediaVault-Plugin-Developers/snapraid|Source Code]]
+-> [[https://github.com/OpenMediaVault-Plugin-Developers/openmediavault-snapraid|Source Code]]
+===== A Closing Note =====
+We, who support the openmediavault project, hope you’ve found this guide to be useful and that you’ll find your openmediavault server to be efficient, easy to use, and enjoyable.\\
+\\
+If you found this plugin guide to be helpful, please consider a modest donation to support the hosting costs of this server.\\
+\\
+**OMV-Extras.org**
+\\
+<html>
+<form action="https://www.paypal.com/cgi-bin/webscr" method="post" target="_top">
+<input type="hidden" name="cmd" value="_s-xclick">
+<input type="hidden" name="hosted_button_id" value="2BQNGSC8HQJME">
+<input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_SM.gif" name="submit" title="PayPal - The safer, easier way to pay online!" alt="Donate with PayPal button" border="0">
+<img alt="" src="https://www.paypal.com/en_US/i/scr/pixel.gif" width="1" height="1" border="0">
+</form>
+</html>
+\\
+\\
+**Venmo: ryecoaaron** \\