[HowTo] SnapRAID in OMV

hm, i think something is wrong

if i save the script as *.sh (and change the first line to #!/bin/sh) and start the job, i get this

# I start on the console script
# omv does something
# after 2 seconds he is ready and inputline is free again
# there is no ouput (start, ready, error, ....)

i have try the script in a console, and get this:

root@Server:~# nano /bin/snapraid
root@Server:~# chmod +x /bin/snapraid
root@Server:~# /bin/snapraid
The file '/media/661c2cf1-dc76-45a1-9958-cdfe986fa8a2/mysql-data/MyVideos78/settings.MYD' has unexpected zero size! If this an expected state
you can 'diff' anyway usinge 'snapraid --force-zero diff'
Instead, it's possible that after a kernel crash this file was lost,
and you can use 'snapraid --filter mysql-data/MyVideos78/settings.MYD fix' to recover it.
The file '/media/661c2cf1-dc76-45a1-9958-cdfe986fa8a2/mysql-data/MyVideos78/settings.MYD' has unexpected zero size! If this an expected state
you can 'sync' anyway usinge 'snapraid --force-zero sync'
Instead, it's possible that after a kernel crash this file was lost,
and you can use 'snapraid --filter mysql-data/MyVideos78/settings.MYD fix' to recover it.
root@Server:~#

Stumbled upon this thread when reading and googling about snapraid.

I am trying to create a simple file server that would allow access to a few Linux and Windows PC on LAN and 2 more over internet. server would offer access to files as well as provide a backup of local files. and I am exploring my options.

What I am interested is about the recovery option. the OP mentiones this in the guide:

Zitat von "Solo0815"

6. A HDD is defect, what now?
edit/change the entry in snapraid from the old HDD to the new one.
after that run on CLI:

Code

snapraid -d name_of_the_defective_Disk -l /path/to/logfile fix

a sample output is this: ....

Alles anzeigen

I plant to have 2 hard disks on start. One would be a faster one where data is dumped, the other one would hold a backup copy of the files and would be a slower NAS/red drive. Now as I understand this instruction one disk holds the data the other one backup and this command is then used to restore data from the backup disk. or am I mistaking? can I switch either disk if any of them fails and then do a restore?

A quick question on parity drives. I've got 24 content drives in my OMV, and I'm busily converting from LVM to SnapRAID. As i read the FAQs, I see a recommended 4 parity drives with 24 content drives. I've got enough spare drives to implement 4 parity drives, but the GUI doesn't seem to support it. Can I edit the snapraid.conf manually to add additional parity drives without messing things up, or should I be satisfied with two parity drives?

Thx!

FON

Thanks ryeco! Can't wait to see it. Love the plugin thusfar. Thanks so much for it. I sleep better at night, knowing that my wife is less likely to be upset by the loss of her favorite shows.

FON

hi, i found this script here
https://github.com/walterheise…/master/omv-snapraid-diff

i try it, but i get

root@debian:~# sh /bin/cron-snapraid
/bin/cron-snapraid: 104: /bin/cron-snapraid: Syntax error: "(" unexpected (expecting ")")
root@debian:~#

I use this script --> http://sourceforge.net/p/snapr…n/1677233/thread/13a660e6

I run it in cron with the following dirty shell script:

#!/bin/bash
cd /home/kryspy/Scripts/SnapRAID
python ./snapraid-runner.py

Kryspy

Moved the Guide to the Guides section:
SnapRAID Plugin Guide

(There is just the guide, Questions / Problems / Diskussions can continue here)

Bei mir gab es bei der Umstellung von Version 0.5 auf 1.0.21 das Problem, dass das Snapraid Plugin zwar die Config File lesen konnte, aber Einstellungen wurden unter dem Reiter "Drives" nicht mehr dargestellt. Beim Status usw. wurde festgestellt das keine Content Daten gefunden werden konnten.

Also habe ich die Platten anhand des neuen Guides neu eingefügt. Beim 1. Sync erstellte es aber neuartige Parity und Content Files, was natürlich durch die bereits existierende Parity File in die Hose ging, da die Platte bereits durch die alte Parity Files blockiert war.

Ich konnte mir so helfen, in dem ich die neu erstellen Files gelöscht habe und die alten Files in die neue Schreibweise umbenannt habe. Und schon ging wieder alles.

Beispiel: Alt: parity.file - neu: snapraid.parity - Alt: .content - neu: snapraid.content - die "neue" Config File des Plugin sieht auch gang anders aus als die alte. Insofern denke ich, war das Umbenennen die unproblematischste Idee. Oder?

Hi,

This is my very first post in the OMV forum.
I am new to OMV + snapraid. So figuring out what I got so far took two evenings and a lot of reading.
My setup: DIY NAS with 3x1TB WD reds + 1 SSD with OMV on it.

I really like what SnapRAID is offering. Redundancy, fault correction, 1 disk spins up and snapshot functionality.. So I love to get this to work well. .
What I desire is 2 mirrored disks (so I can continue work with 1 fail) + 1 parity disk for rebuilding/fault correction.. Currently, this is what my config file looks like.

# this file is automatically generated.
block_size 256
autosave 0


# OMV-Name: data_drive1
content /media/df805e5e-1311-49b3-aa41-445a83e63e75/snapraid.content
# OMV-Name: data_drive1  Drive Label: sdbwcc4j4726757
disk data_drive1 /media/df805e5e-1311-49b3-aa41-445a83e63e75
# OMV-Name: data_drive2
content /media/633313dd-99f5-4eb6-bda3-df2ffcf87670/snapraid.content
# OMV-Name: data_drive2  Drive Label: sdcwcc4j4736118
disk data_drive2 /media/633313dd-99f5-4eb6-bda3-df2ffcf87670
# OMV-Name: parity_drive3
content /media/d7f47a2a-0595-4cf0-9b59-4db8702420b3/snapraid.content
# OMV-Name: parity_drive3
parity /media/d7f47a2a-0595-4cf0-9b59-4db8702420b3/snapraid.parity


exclude *.bak
exclude *.unrecoverable
exclude /tmp/
exclude lost+found/
exclude .content
exclude aquota.group
exclude aquota.user

To explain what you see above. I gave the ID's of the WD reds according to the serial number of the disk. This way making it easier to ID the broken disk. Anyway....

I see now I have 2 data disks and 1 parity disk. DataDisk 1 is mounted (all are) and contains a working shared folder. The folder is synced OK. But I have a question what my second datadisk is doing now. I see it is nearly empty in the OMV>filesystem tab, while the datadisk 1 + parity disk contains each about 240Gb. But I'd like the second datadisk to be a mirror of the contents of disk 1.

Q: Am I misunderstanding the way I should go about setting up snapraid? Do I need to have 1 data disk and 2 parity disk to get what I want? Or do I need to change my expectations. (open for discussion here )

Thank you very much for all the work done and time you are willing to spend on my querries