Snapraid issue after OMV 6 --> 7 upgrade

  • Hey! I want to apologize if this has been asked and resolved before, I genuinely looked and couldn't find anything containing a solution for my specific issue. And ALSO if this is posted in the wrong place. This is also just a copy of what I posted on the subreddit, but I remembered I had an account here and figured I'd cover all my bases!


    I finally got around to doing a system drive backup and then upgrading OMV 6 to 7 a few days back, and everything went great. No issues with the Web UI, plugins, all my docker containers are completely fine. The only issue I'm having is, while my MergerFS/Snapraid array WORKS, as in, it reads/writes just fine, I can no longer perform any actions on it (Sync, check, scrub etc), cause I get this error:



    It doesn't matter what I do - whether it be a sync, check, diff etc. It's all the same error.


    Now to my understanding (which is limited, I'm no guru or anywhere close but I'm wanting to learn how to fix this), this has to do with the fact that the new Snapraid plugin supports multiple arrays, and the location of the config file is different? Or maybe I'm completely off base. I did as much research as I could muster before posting this.


    Is there a quick and easy fix to this? I'm not the most versed in this stuff, and this entire Journey with OMV over the last couple years has been a learning process for me haha.

    Thanks in advance <3,

  • Please do not post screenshots of text when you can post the text itself. It can make it a lot more difficult to provide help.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.


  • Alright, so here';s what I've tried...


    - Set default array (cause going from OMV 6 to 7 upgrades snapraid to support multiple arrays)

    - Checked the existing .conf files...and they appear to be nearly empty


    The thing is, the Snapraid array seems to be working just fine. I can read to it, write to it, I just can't do any of the snapraid stuff with it such as sync, diff, etc. So I'm genuinely confused. Doubly so since I can't seem to find a single instance of anyone else ever having this issue. On reddit, the snapraid forums, here, anywhere.

  • - Checked the existing .conf files...and they appear to be nearly empty

    What does this mean? Post your .conf file.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.


  • What does this mean? Post your .conf file.

    After a little digging, I managed to repopulate the config file, double and tripled checked all the drive UUIDs, everything is there, but I'm still getting the aforementioned error in the OP.


    Here's my config if you're curious.


  • Have you compared each of the .content files by calculating their MD5s or other hashes?

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.


  • Check the name of the .conf file. In my case it was changed with new plugin. It is now:

    /etc/snapraid/omv-snapraid-5b0cbdb3-1e2e-4ee9-959c-e087065634c1.conf


    So an example command becomes:


    # snapraid -c /etc/snapraid/omv-snapraid-5b0cbdb3-1e2e-4ee9-959c-e087065634c1.conf --force-full sync &

    Inwin MS04 case with 315 W PSU

    ASRock B660M-ITX board

    Two port PCI-E SATA card

    16GB Kingston DDR4

    Intel 12th gen i5 12400

    Crucial M.2 1 TB OS drive

    4x4TB WD Red NAS drives + 1x4TB + 1x5TB Seagate drives - MergerFS pool

    Seagate 5TB USB drives - SnapRAID parity x 2

  • # snapraid -c /etc/snapraid/omv-snapraid-5b0cbdb3-1e2e-4ee9-959c-e087065634c1.conf --force-full sync &

    Rather unwieldy and avoidable if you use the plugin to symlink /etc/snapraid/omv-snapraid-5b0cbdb3-1e2e-4ee9-959c-e087065634c1.conf to /etc/snapraid.conf


    Your example command then becomes


    Code
    # snapraid --force-full sync &

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.


  • Yes aware of that now but was originally caught out by the plugin change..

    Inwin MS04 case with 315 W PSU

    ASRock B660M-ITX board

    Two port PCI-E SATA card

    16GB Kingston DDR4

    Intel 12th gen i5 12400

    Crucial M.2 1 TB OS drive

    4x4TB WD Red NAS drives + 1x4TB + 1x5TB Seagate drives - MergerFS pool

    Seagate 5TB USB drives - SnapRAID parity x 2

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!