This project has moved and is read-only. For the latest updates, please go here.

Does not work with new version of SnapRAID :/

Sep 3, 2016 at 8:20 PM
Edited Sep 4, 2016 at 7:09 PM
You can not configure more than 2 parities and snapraid changed the way it codes drives.

Will this be updated to work with the newest snapraid?

As you can see the config file is written differently now.

Example configuration for snapraid for Windows

Defines the file to use as parity storage

It must NOT be in a data disk

Format: "parity FILE_PATH"

parity E:\snapraid.parity

Defines the files to use as additional parity storage.

If specified, they enable the multiple failures protection

from two to six level of parity.

To enable, uncomment one parity file for each level of extra

protection required. Start from 2-parity, and follow in order.

It must NOT be in a data disk

Format: "X-parity FILE_PATH"

2-parity F:\snapraid.2-parity
3-parity G:\snapraid.3-parity

4-parity H:\snapraid.4-parity

5-parity I:\snapraid.5-parity

6-parity J:\snapraid.6-parity

Defines the files to use as content list

You can use multiple specification to store more copies

You must have least one copy for each parity file plus one. Some more don't hurt

They can be in the disks used for data, parity or boot,

but each file must be in a different disk

Format: "content FILE_PATH"

content C:\snapraid\snapraid.content
content H:\array\snapraid.content
content I:\array\snapraid.content
content J:\array\snapraid.content
content K:\array\snapraid.content
content L:\array\snapraid.content
content M:\array\snapraid.content
content N:\array\snapraid.content
content O:\array\snapraid.content

Defines the data disks to use

The name and mount point association is relevant for parity, do not change it

WARNING: Adding here your boot C:\ disk is NOT a good idea!

SnapRAID is better suited for files that rarely changes!


data d1 H:\array\
data d2 I:\array\
data d3 J:\array\
data d4 K:\array\
data d5 L:\array\
data d6 M:\array\
data d7 N:\array\
data d8 o:\array\

Excludes hidden files and directories (uncomment to enable).


Defines files and directories to exclude

Remember that all the paths are relative at the mount points

Format: "exclude FILE"

Format: "exclude DIR\"

Format: "exclude \PATH\FILE"

Format: "exclude \PATH\DIR\"

exclude *.unrecoverable

exclude Thumbs.db

exclude \$RECYCLE.BIN

exclude \System Volume Information

exclude \Program Files\

exclude \Program Files (x86)\

exclude \Windows\

Defines the block size in kibi bytes (1024 bytes) (uncomment to enable).

Default value is 256 -> 256 kibi bytes -> 262144 bytes

Format: "blocksize SIZE_IN_KiB"

blocksize 128

Automatically save the state when syncing after the specified amount

of GB processed (uncomment to enable).

This option is useful to avoid to restart from scratch long 'sync'

commands interrupted by a machine crash.

It also improves the recovering if a disk break during a 'sync'.

Default value is 0, meaning disabled.

Format: "autosave SIZE_IN_GB"

autosave 500

Defines the pooling directory where the virtual view of the disk

array is created using the "pool" command (uncomment to enable).

The files are not really copied here, but just linked using

symbolic links.

This directory must be outside the array.

Format: "pool DIR"

pool C:\pool

Defines the Windows UNC path required to access disks from the pooling

directory when shared in the network.

If present (uncomment to enable), the symbolic links created in the

pool virtual view, instead of using local paths, are created using the

specified UNC path, adding the disk names and file path.

This allows to share the pool directory in the network.

See the manual page for more details.

Format: "share UNC_DIR"

share \server

Defines a custom smartctl command to obtain the SMART attributes

for each disk. This may be required for RAID controllers and for

some USB disk that cannot be autodetected.

In the specified options, the "%s" string is replaced by the device name.

Refers at the smartmontools documentation about the possible options:


USB ->

smartctl d1 -d sat %s

smartctl d2 -d usbjmicron %s

smartctl parity -d areca,1/1 /dev/arcmsr0

smartctl 2-parity -d areca,2/1 /dev/arcmsr0

Sep 22, 2016 at 8:19 AM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Sep 22, 2016 at 8:21 AM
Thanks for the report,
I'm still using an old config file with version 10.0

Can you state what version you are using and on what OS ?

Also this has now been copied to

so please add replies in there
Sep 22, 2016 at 6:10 PM
Edited Sep 22, 2016 at 6:12 PM
not sure how an old config works with v10. I got errors and it never worked for me. I don't think you are using v10 or if you are you should be careful because it might not be working right.
Apr 12, 2017 at 3:05 AM
so is updating this dead?
May 15, 2017 at 9:44 PM
Edited May 15, 2017 at 9:46 PM
Someguy123123 wrote:
not sure how an old config works with v10. I got errors and it never worked for me. I don't think you are using v10 or if you are you should be careful because it might not be working right.
First time user of snapRAID and Elucidate and I think I figured out a work around.

Configure a snapraid.config file with Elucidate and save it. Open up the Elucidate generated config file you saved, using a text editor. Look for where Elucidate specifies the disks to be included:

disk dx X:\array\

Change these commands to look like this (replacing "disk" with "data"):

data dx X:\array\

Save the modified config file in your text editor. You should be done.

Also I noticed Elucidate was inserting an extra (empty) content specification in the content file area of the config file. Seems like SnapRAID has been ignoring this error but I would remove it to be on the safe side: For example:

"content C:\snapraid\snapraid.content
content K:\array\snapraid.content
content L:\array\snapraid.content

Should now read:

"content C:\snapraid\snapraid.content
content K:\array\snapraid.content
content L:\array\snapraid.content"