SnapRAID Error after new installation of OMV 7

  • After a completely new installation of OMV7 because of a failed bootdrive I installed the SnapRAID-Plugin and now struggeling with the setup.

    I added my 4 data and 1 parity drive in the same SnapRAID-Pool.

    Initializing the SnapRAID pool shows the following error:


    3x OMV-NAS systems with ASUS H87I-PLUS

  • Obfuscating things like disk UUIDs is pointless and makes it difficult to provide help.

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


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

  • Obfuscating things like disk UUIDs is pointless and makes it difficult to provide help.

    OK, now without obfuscating:

    3x OMV-NAS systems with ASUS H87I-PLUS

  • It appears that you have left over SnapRaid content files on one or more of your disks, SnapRAID detects that one it knew about in the past has gone missing and it is using another it managed to find. This is usually not a problem if, when you configure SnapRAID again from scratch on a new install, and you added the disks in the same order as was done on the original install.


    Post your snapraid.conf file. It is either in /etc or in /etc/snapraid. If the latter, it will have your array name in the file name. It may be possible to tell in what order the disks should be selected when you reconfigure SnapRAID again.


    Also, posting the output of snapraid status might be helpful.

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


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

  • I mounted the 4 data drives and found files from my old SnapRAID.

    How can I delete them because this seems to be the problem?
    I can see the files when mounting via CIFS on my Windows client but I can't delete them.

    3x OMV-NAS systems with ASUS H87I-PLUS

  • Well, if you delete the content files this might render any existing parity file(s) useless, and to fix that you will have to do a full sync of the array. If this doesn't bother you you run these commands in the shell to find the content files:


    sudo updatedb (might take a while to finish)

    sudo locate snapraid.content


    If the above throws errors about not being able to find the locate command, then install the openmediavault-locate plugin.


    You'll get a list of the full path of each file it finds.


    Then you can remove them like so, one at a time.


    sudo rm -f /full-path/snapraid.content



    However, it would be a better idea to post your snapraid.conf file and the outpu of snapraid status for review. It might lead to an easier fix.

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


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

  • I've deleted the snapraid drives and afterwards the array.


    Code
    snapraid status


    shows:


    Code
    Self test...
    No configuration file found at '/etc/snapraid.conf'


    What seems logical, because I've deleted the snapraid drives and array.

    Now I "only" have to get rid of the old and from my point of view useless snapraid data on the drives to establish a new array with drives.

    3x OMV-NAS systems with ASUS H87I-PLUS

Participate now!

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