[HowTo] SnapRAID in OMV

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Symbiot wrote:

      I'm unsure who's the dev behind the plugin for OMV but since you created the thread I'm pinging you

      Would it be possible to either add an "extra arguments" variable or alternatively add stuff like:

      SYNC_WARN_THRESHOLD and other snapraid options?
      I am the dev. I guess I could add that but I don't see it in the snapraid manual? What other options are you looking at?
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!

    • ryecoaaron wrote:

      Symbiot wrote:

      I'm unsure who's the dev behind the plugin for OMV but since you created the thread I'm pinging you

      Would it be possible to either add an "extra arguments" variable or alternatively add stuff like:

      SYNC_WARN_THRESHOLD and other snapraid options?
      I am the dev. I guess I could add that but I don't see it in the snapraid manual? What other options are you looking at?
      Hi

      I never thought to look if the variable was a native snapraid command.. I found it here:

      zackreed.me/snapraid-split-parity-sync-script/

      and thought it'd be a great addition :-|

    • Symbiot wrote:

      I never thought to look if the variable was a native snapraid command.. I found it here:

      zackreed.me/snapraid-split-parity-sync-script/

      and thought it'd be a great addition :-|
      That is a parameter of that script not snapraid itself. There has been talk of updating the current snapraid diff script to this but someone who uses snapraid would need to do it.
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!

    • ryecoaaron wrote:

      I am the dev. I guess I could add that but I don't see it in the snapraid manual? What other options are you looking at?
      Hi, is it "safe" to manually update/install SnapRAID (to 11.2). I'm assuming it will be fine as long as there are no breaking changes in snap itself.
      I browsed the plugin code on github but didn't find the parts that actually install snap, so I'm unsure of the logic when this plugin has an update. Thanks!

      p.s. I actually created a thread SnapRAID - Plugin Version is old?

    • da_guy2 wrote:

      Quick question. Is there any way to automate daily sync beyond writing your own script and schedualing it with a cron job?
      There are numerous already written SnapRaid scripts available. The one bundled with OMV is just one of them. I use this one on cron:

      Source Code

      1. https://gist.github.com/bfg100k/87a1bbccf4f15d963ff7

      Google for more scripts.
      OMV 4.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380

      The post was edited 1 time, last by gderf ().

    • What is the snapraid-diff.conf for?

      I want to set up my scrubs to run on specific days and not 100% every 7 days.

      Does this run automatically or can I just set up my scrubs via cron?
      OMV 4.1.4 Arrakis | 34TB SnapRAID+MergerFS
      Supermicro X10SLM+-F| Xeon E3-1285L | 16gb ECC Ram | LSI SAS9220-8i
      5 x 8TB WD Red | 2x 3TB WD Red | 128gb Samsung 830 EVO

    • snapraid-diff.conf holds the settings for the script that is provided by OMV.

      The settings come from what is entered in OMV Services | SnapRAID | Diff Script Settings, but the script does not run automatically unless scheduled as a task or via a manual cron entry.

      You can schedule whatever you want via cron or OMV's built in task scheduler - either OMV's provided script, or another freely available one, or something you write yourself.
      OMV 4.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380

    • I see, thank you.

      In your opinion is a weekly whole array scrub best practice or should I schedule a lower percentage to run every few days?

      How stressfuly for a drive is a scrub?
      OMV 4.1.4 Arrakis | 34TB SnapRAID+MergerFS
      Supermicro X10SLM+-F| Xeon E3-1285L | 16gb ECC Ram | LSI SAS9220-8i
      5 x 8TB WD Red | 2x 3TB WD Red | 128gb Samsung 830 EVO

    • I have the following array set up in SnapRAID:

      1 x disk of 2TB (parity)
      5 x HDDs of varied sizes (data)
      1 x SSD (data)

      I created this before I'd really got to grips with SnapRAID and it needs a bit of tweaking now I've had some more time to think things through. I want to remove the SSD from the array, because 1) the files on it change too often for SnapRAID to be useful and 2) they are covered by another form of backup. I also want to add a new 2TB parity drive.

      I'm having difficulty getting SnapRAID to accept me removing the drive from the array. If I remove it via the plugin (see pic 1 - the SSD is the last drive in the list) and then try to run the sync command, I get an error message stating that the drive has been removed from the config, and asking me to restore it (see pic 2). If I try to remove it by manually editing the snapraid.conf file via SSH and then forcing a sync, as per the instructions here, then I succeed in altering the snapraid.conf file as shown in my SSH window (pic 3), but it does not update the config as shown in the plugin (pic 4), and therefore I'm stuck with the same problem.

      What am I doing wrong here? What's the best way to permanently remove the SSD from the array? (I'll leave adding a new parity disk as I think that I know how to do that!

      Thanks!
      Images

      • pic 1.png

        87.06 kB, 1,441×1,136, viewed 101 times

      • pic 2.png

        40.71 kB, 1,448×554, viewed 93 times

      • pic 3.png

        82.36 kB, 1,419×879, viewed 102 times

      • pic 4.png

        64.51 kB, 1,301×653, viewed 97 times

    • bmhj2 wrote:

      OK, thank you @jollyrogr.

      So the correct procedure would be:

      [*]Delete the SSD from the drive list within the plugin
      [*]Then go to a terminal window and execute the command:
      [/list]

      Source Code

      1. snapraid sync -F
      Do I have that right? Or would it be the same command with the modifiers -FV?

      Thanks!
      Should be snapraid -e sync

      -f would force a full rebuild of parity which you would need to do if you added a parity drive.