Total Beginner - Snapraid array and OMV 4.1.35-1

  • Hello!

    I have been googling and searching and trying different options for a while but could not solve this problem. I do not have a good understanding of linux and mostly work by following internet advice. I originally set up OMV about a year ago and have some basic understanding of using the GUI and the CLI via Putty from my windows laptop. I use this as a NAS to store media which is mostly family videos and pictures that can be accessed over the network. The filesharing, etc. all works great and continues to work.


    I originally thought that I had Snapraid setup well, following a tutorial, and after I was re-evaluating things after updating OMV from 3 to 4, realized I probably never set it up properly because anytime I tried to sync it would tell me that the array appears to be empty and I would not be able to sync. I had set everything up in Snapraid only through the GUI so the parity drive was added through the GUI. I have 4 x 4 TB harddrives. I use three for content and data and 1 for parity, theoretically. I believe I made an error in also adding the pool drive (union filesystem pool of drive1 drive2 drive3) onto the snapraid drives as a data and content drive and realized on re-reading the tutorials nobody mentions adding the pool drive back onto snapraid after making it.


    Since I was unable to sync, I decided (another error I think) to delete the pool drive from snapraid thinking that might help and now I am stuck because I get the error:



    Loading state from /srv/dev-disk-by-label-drive1/snapraid.content...

    Decoding error in '/srv/dev-disk-by-label-drive1/snapraid.content' at offset 108

    The file CRC is correct!

    Disk 'pool' with uuid '' not present in the configuration file!

    If you have removed it from the configuration file, please restore it


    This happens if I try snapraid sync, diff or fix with -f or -e which were suggestions I found online. I was able to open the config file with nano through putty but did not see anything that mentioned the pool disk. The current config file is:


    # this file was automatically generated from

    # openmediavault Arrakis 4.1.35-1

    # and 'openmediavault-snapraid' 3.7.7


    block_size 256

    autosave 0

    #####################################################################

    # OMV-Name: Main1 Drive Label: drive1

    content /srv/dev-disk-by-label-drive1/snapraid.content

    disk Main1 /srv/dev-disk-by-label-drive1


    #####################################################################

    # OMV-Name: Parity1 Drive Label: disc4

    parity /srv/dev-disk-by-label-disc4/snapraid.parity


    #####################################################################

    # OMV-Name: main2 Drive Label: drive2

    content /srv/dev-disk-by-label-drive2/snapraid.content

    disk main2 /srv/dev-disk-by-label-drive2


    #####################################################################

    # OMV-Name: Main3 Drive Label: drive3

    content /srv/dev-disk-by-label-drive3/snapraid.content

    disk Main3 /srv/dev-disk-by-label-drive3




    exclude /snapraid.conf*

    exclude *.unrecoverable

    exclude lost+found/

    exclude aquota.user

    exclude aquota.group

    exclude /tmp/

    exclude .content

    exclude *.bak


    I did try re-adding the Pool drive but that did not help. I did read the Snapraid FAQ , search google and forums to look for a solution but I am not 100% sure what it means to edit the config file and since I do not see the pool mentioned in the config file I am not sure what or how to edit.


    One forum site said to use snapraid -c snapraid.content to see the drives and figure out where the issue is.



    sudo snapraid -C snapraid.content

    Loading state from snapraid.content...

    No content file found. Assuming empty.

    # Configuration file generated from snapraid.content


    # Use this blocksize

    blocksize 256


    # Use this hashsize

    hashsize 16


    # Set the correct path for the Parity files

    # You had 0 of them:

    parity ENTER_HERE_THE_PARITY_FILES_COMMA_SEPARATED


    # Add any other content file

    content snapraid.content


    So this looks to me like the parity is not even set up but again I do not know how I can fix this.


    Is there a way to just uninstall and re-install Snapraid to start over?


    Thank you in advance, thank you for your advice, and sorry if I missed an easy solution to this in my searches.

  • Just use the SnapRAID GUI to set which disks are content and data and which disk is/are parity. Then save and apply the configuration.


    Then examine the config file to see if it now appears correct.

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


    OMV AMD64 5.x on Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 16GB ECC RAM.

  • Thank you for your reply.


    I have the Drive1, Drive2 and Drive3 set as data and content with those sliders set,Disk4 is set to parity with data and content not selected. This is under services -> snapraid. I am still getting the same error re: pool.


    Config file is:


    # this file was automatically generated from

    # openmediavault Arrakis 4.1.35-1

    # and 'openmediavault-snapraid' 3.7.7


    block_size 256

    autosave 0

    #####################################################################

    # OMV-Name: Main1 Drive Label: drive1

    content /srv/dev-disk-by-label-drive1/snapraid.content

    disk Main1 /srv/dev-disk-by-label-drive1


    #####################################################################

    # OMV-Name: Parity1 Drive Label: disc4

    parity /srv/dev-disk-by-label-disc4/snapraid.parity


    #####################################################################

    # OMV-Name: main2 Drive Label: drive2

    content /srv/dev-disk-by-label-drive2/snapraid.content

    disk main2 /srv/dev-disk-by-label-drive2


    #####################################################################

    # OMV-Name: Main3 Drive Label: drive3

    content /srv/dev-disk-by-label-drive3/snapraid.content

    disk Main3 /srv/dev-disk-by-label-drive3


    exclude /snapraid.conf*

    exclude *.unrecoverable

    exclude lost+found/

    exclude aquota.user

    exclude aquota.group

    exclude /tmp/

    exclude .content

    exclude *.bak

  • Unfortunately removing a content/data drive using the OMV SnapRAID GUI does not seem to work properly as it triggers errors later.


    You are going to have to follow the directions for removing a data drive given in the documentation available at snapraid.it See:


    https://www.snapraid.it/faq#remdatadisk

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


    OMV AMD64 5.x on Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 16GB ECC RAM.

  • Hi gderf,


    thank you again for helping. I appreciate your directions. I dont want to annoy you with my lack of knowledge but I just want to check that I am doing what I am supposed to do.


    I followed the instructions in that I modified the config file to point to an empty directory for the pool directory that was no longer there and removed its content file.


    So I changed the removed disk portion of config to this:


    #####################################################################

    # OMV-Name: Pool Drive Label: Pool1

    disk Pool /test





    test is an empty directory I created for this.

    .....


    When I ran that I still got the error:


    Loading state from /srv/dev-disk-by-label-drive1/snapraid.content...

    Decoding error in '/srv/dev-disk-by-label-drive1/snapraid.content' at offset 108

    The file CRC is correct!

    Disk 'pool' with uuid '' not present in the configuration file!

    If you have removed it from the configuration file, please restore it


    so then I removed the content information from all drives in the config file, thinking that because it was a pooled drive they shared data or something like that. This is the step I am not sure I am doing correctly. After doing that I got this error:


    Self test...

    Empty 'content' specification in '/etc/snapraid.conf' at line 28



    I even thought screw it I will look to remove all disks and just try to redo everything, so I changed the config to:


    block_size 256

    autosave 0

    #####################################################################

    # OMV-Name: Main1 Drive Label: drive1

    disk Main1 /test


    #####################################################################

    # OMV-Name: Parity1 Drive Label: disc4

    parity /srv/dev-disk-by-label-disc4/snapraid.parity


    #####################################################################

    # OMV-Name: main2 Drive Label: drive2

    disk main2 /test


    #####################################################################

    # OMV-Name: Main3 Drive Label: drive3

    disk Main3 /test


    #####################################################################

    # OMV-Name: Pool Drive Label: Pool1

    disk Pool /test


    exclude /snapraid.conf*

    exclude *.unrecoverable

    exclude lost+found/

    exclude aquota.user

    exclude aquota.group

    exclude /tmp/

    exclude .content

    exclude *.bak


    to try and remove all the disks.

    So I am missing something on how to edit the config file properly to remove the disks and make this work.


    Thank you again for your time.

  • You are making too many changes all at once. This rarely works. This is what I suggest you do at this point. Put EVERYTHING back the way it was, including this pool drive (whatever that was). Run a sync and then a scrub. Report the results, the goal is to have this run error free..

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


    OMV AMD64 5.x on Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 16GB ECC RAM.

  • Hello,


    sorry I kept getting errors so kept trying things. I have restored everything back to how it was originally.

    So I have taken a screenshot of my GUI.

    when I run any command the output is:

    Self test...

    Loading state from /srv/dev-disk-by-label-drive1/snapraid.content...

    Decoding error in '/srv/dev-disk-by-label-drive1/snapraid.content' at offset 108

    The file CRC is correct!

    Disk 'pool' with uuid '' not present in the configuration file!

    If you have removed it from the configuration file, please restore it


    I have set config back to


    #####################################################################

    # OMV-Name: Main1 Drive Label: drive1

    content /srv/dev-disk-by-label-drive1/snapraid.content

    disk Main1 /srv/dev-disk-by-label-drive1


    #####################################################################

    # OMV-Name: Parity1 Drive Label: disc4

    parity /srv/dev-disk-by-label-disc4/snapraid.parity


    #####################################################################

    # OMV-Name: main2 Drive Label: drive2

    content /srv/dev-disk-by-label-drive2/snapraid.content

    disk main2 /srv/dev-disk-by-label-drive2


    #####################################################################

    # OMV-Name: Main3 Drive Label: drive3

    content /srv/dev-disk-by-label-drive3/snapraid.content

    disk Main3 /srv/dev-disk-by-label-drive3


    #####################################################################

    # OMV-Name: Pool Drive Label: Pool1

    content /srv/c534e584-9ac4-40a4-a8ae-c57d5436b58f/snapraid.content

    disk Pool /srv/c534e584-9ac4-40a4-a8ae-c57d5436b58f


    exclude /snapraid.conf*

    exclude *.unrecoverable

    exclude lost+found/

    exclude aquota.user

    exclude aquota.group

    exclude /tmp/

    exclude .content

    exclude *.bak

  • The error mentions a disk named pool but you are using Pool (uppercase P). Which is it? It matters.

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


    OMV AMD64 5.x on Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 16GB ECC RAM.

  • Ok that definitely improved things. I am now back to the original issue I had before I started all this mess.


    When I run a scrub I get this:


    Loading state from /srv/dev-disk-by-label-drive1/snapraid.content...

    Using 225 MiB of memory for the file-system.

    Initializing...

    The array appears to be empty.


    I ran a sync anyway to see if that would create the array:


    from /srv/dev-disk-by-label-drive1/snapraid.content...

    Scanning disk main1...

    Scanning disk main2...

    Scanning disk main3...

    Scanning disk pool...

    WARNING! Files '/srv/c534e584-9ac4-40a4-a8ae-c57d5436b58f/SharedFolder2/.DS_Store' and '/srv/c534e584-9ac4-40a4-a8ae-c57d5436b58f/SharedFolder2/CGCV2018.doc' have the same physical offset 3.

    WARNING! Files '/srv/c534e584-9ac4-40a4-a8ae-c57d5436b58f/SharedFolder2/CGCV2018.doc' and '/srv/c534e584-9ac4-40a4-a8ae-c57d5436b58f/SharedFolder2/TV/The Wire/TSV Torrents/SGU Stargate Universe Season 1 & 2 HDTV + Extras.torrent' have the same physical offset 3.

    a bunch more about same physical offset of several files


    then:

    WARNING! Physical offsets not supported for disk 'pool'. Files order won't be optimal.

    WARNING! Inodes are not persistent for disks: 'pool'. Not using inodes to detect move operations.

    WARNING! UUID is unsupported for disks: 'pool'. Not using inodes to detect move operations.

    Using 390 MiB of memory for the file-system.

    Initializing...

    Resizing...

    Saving state to /srv/dev-disk-by-label-drive1/snapraid.content...

    Saving state to /srv/dev-disk-by-label-drive2/snapraid.content...

    Saving state to /srv/dev-disk-by-label-drive3/snapraid.content...

    Saving state to /srv/c534e584-9ac4-40a4-a8ae-c57d5436b58f/snapraid.content...

    Verifying /srv/dev-disk-by-label-drive1/snapraid.content...

    Error reopening the temporary content file '/srv/dev-disk-by-label-drive1/snapraid.content.tmp'. No such file or directory.



    I tried the command with -E and -F for whatever that is worth


    So I ran a fix which is ongoing to do something in the interim.

  • It would be helpful to know exactly what this 'pool' disk is all about........all of it.

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


    OMV AMD64 5.x on Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 16GB ECC RAM.

  • The pool disk is just the pool that I created of disk 1,2 and 3. I created this under storage-> unionfilesystem tab in the OMV GUI. It shows up as a separate harddrive under the toggle in snapraid and so I added it as a drive and I think that's how the whole problem started. Maybe if I cycle back to the idea of deleting it properly based on the Snapraid instructions it will help?

  • You really do not need a seperate entire disk for that pool, only a directory on any one of your disks is needed as the mount point. snapRAID will not dive into the pool directory anyway when performing operations. You should have seen warnings about that anyway.


    If you have other data on that 'pool' disk that you want protected by snapRAID then you must include that disk as having data on it in snapRAID.

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


    OMV AMD64 5.x on Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 16GB ECC RAM.

  • Thank you gderf. This situation was really frustrating me and your knowledge of Pool vs pool was the lifesaver. To close the loop on this, I removed the pool drive with the instructions on Snapraid on how to remove drive through the CLI and that solved that portion of the problem. I added the other drives that had been part of the pool and have now successfully run a sync and everything seems to be working correctly. :thumbup:

  • gillitron

    Added the Label resolved
  • OK. Good to hear. Keep an eye on what snapRAID sync and scrub tells you. Once it is all properly set up you shouldn't have any problems with routine operations.

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


    OMV AMD64 5.x on Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 16GB ECC RAM.

Participate now!

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