I am currently attempting a test migration from a Windows 2008 Server to UNRAID. Initially, I upgraded my MB, CPU, memory and boot drive and installed Windows 10 on an NVMe. All good. The second step was to move to UNRAID and run Windows 10 and Ubuntu under VM's. UNRAID is working fine with a test migration but I am having some problems getting VM's to work properly. Doing research, I ran across SnapRAID and I am considering this approach instead.
For my application, the revised approach is to install Oracle’s Virtual Box and then run both Windows 10 and Ubuntu under a VM. Then installing SnapRAID under Ubuntu (reliability & performance + EXT4 FS). Windows 10 VM will access shares and provide some media management, not available to Linux. (I suppose I can just install SnapRAID under Windows 10 and then do everything there - but I still want it running under a VM)
For my rebuild, I purchased a 10TB WD GOLD drive - that is currently acting as my UNRAID parity drive. It would get repurposed for the SnapRAID parity disk. I would purchase a second one for dual parity once the system is running. All of my other drives are <2 year old Seagate Ironwolf 8TB drives.
The general application is operating a home media server (64TBs) plus a data repository for a wide range of files including system backups on my network. This is on an 8TB drive backed up on a second 8TB drive.
Love to hear any thoughts on on how folks here might implement a SnapRAID solution based on the above scenario; pros and cons.
Thanks for your help!
PS: Just noticed Elucidate on git hub. Maybe I'll take the Windows approach instead.
Last edit: RAP 2021-10-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You set it up via snapraid.conf and then you use the following commands:
snapraid diff to see what has changes since last sync
snapraid sync to update parity
snapraid scrub to verify that files and parity is ok.
snapraid fix to restore files
Another important difference is that snapraid is great for large media files that rarely change but not so great for lots of small files like system backups. If you want to use it for the latter I would strongly recommend that you put the backups inside zip archives or similar.
Considering that you are comfortable with both Linux and VM:s I strongly doubt that you have any need for Elucidate. You just need to modify the example snapraid.conf file included with the installation to test it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK... downloaded the files extracted. I've decided to try it on a Windows 10 machine first... with one parity drive and one data drive.
Is there an installer or does it just run as an exe? Are there dependencies?
I read the isntall.txt - it seems all I have to modify the snapraid.conf file - within that directory - and then what? double click the exe? Sorry - if I'm slow on the uptake here, but its so basic that its questionable. :-)
So I am asking before I leap.
Cheers!
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I use Snapraid with mergerfs for my media/file server it's been fine. Only suggestion is stop any data change during a sync, this is not a solution for heavy i/o file servers. Slow changing media servers is the use case. I moved my backups to an ESOS SAN storage box I built to avoid heavy changes to the snapraid media server.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Understood. I will only use SnapRAID for my movie drives - my data backups, photos and music - which all change, will be mirrored separately.
I'm having trouble with the config file because - IMHO - the language is not precise enough to be 100% certain of a correct configuration.
For example; the use of the word "array" in the content list file and then later in the data file. Is this just part of the example path?
In the case of the Data Disk, my disks all have two words separated by a space. The format structure "data DISK_NAME DISK_MOUNT_POINT" would cause a problem for something like this: "data Movies ONE K:\" - where "Movies ONE" is the Disk Name.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
SR is dead simple to set up and use. Just edit the config file to add the drives. It really is that simple. https://www.snapraid.it/faq
I'd recommend using single words for drive names not only because it's much easier from a SR point of view, but also a maintenance POV, automation POV, and Windows is generally stupid about such things.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
in my snapraid config I just followed their examples and it worked, I have :
data d1 /mnt/data/data1/
data d2 /mnt/data/data2/
data d3 /mnt/data/data3/
data d4 /mnt/data/data4/
data d5 /mnt/data/data5/
data d6 /mnt/data/data6/
data d7 /mnt/data/data7/
data d8 /mnt/data/data8/
data d9 /mnt/data/data9/
data d10 /mnt/data/data10/
Hope that helps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@David:
I'm not over thinking it. I'm also not changing my Windows Disk Names and UNC paths because my 5000 movie data base is based on those. I have no interest is spending hours changing that stuff.
With apologies, but it might be "dead simple", once you know. I'm a software programmer, and career broadcast technologist - and when I see instructions with language this ambiguous - that potentially affects how 64 TB's of MY data is affected; I'm concerned. You might be more tolerant about me asking some basic (possibly naïve) questions; instead of suggesting to blindly go ahead and configure without full understanding of things.
I've also read the FAQ's... and BTW: there is nothing there about how to configure the actual snapraid.conf file. I just checked again. This is provided in the snapraid.conf.example file and some additional information in the snapraid.txt file. If there is more information elsewhere, that would indeed be useful. Thanks.
@Muddy Waters:
So your physical disks are actually named d1 through d10? Or, is this just how SnapRAID names them internally through the config file?
If that's the case, I can simply remove the spaces in my current drive names (which are also my UNC paths) - in that way, there is some correlation between the SnapRAID disk name and the Windows disk name. Please advise...
Regarding the second parameter: DISK_MOUNT_POINT
In Windows, my Disk Mount point is the drive letter. So, I'm confused by your /mnt/data/data1/ (as an example) Are you using Windows? Is this an NTS folder mount?
Assuming I can use whatever name I want for DISK_NAME and Windows drive letters for IDSK_MOUNT_POINT, I have this:
data MoviesONE H:\
data MoviesTWO I:\
data MoviesTHREE J:\
data MoviesFOUR K:\
data MoviesFIVE L:\
data MoviesSIX M:\
data MoviesSEVEN N:\
data MoviesEIGHT O:\
Yes, you're overthinking it. You're confusing simplicity for ambiguity.
In the config file, list your data drives, the parity drive or better drives, and your spare content files. Then run sync. It really is that simple. Later you can change things like the exclude folders and the autosave. The autosave feature is really nice. As you run SR you can see everything it does. SR isn't something that if you get wrong it's gonna wipe out half you data. Even if you misconfigured a data drive for a parity drive, it's not going to erase the drive. It'll either write a file until the drive is full or it will tell you that you don't have enough space. It will not wipe out your data.
SR only reads from the data drives and only writes to the parity file so your data, sorry, your data is safe. It's a config file. It's not some esoteric settings in binary that you have to get exactly perfect, compile, then hope it works. Simply play with it until everything works. One of the best things about SR is the abstraction.
BTW, my "intolerance?" Good Lord, was just trying to explain SR is dead simple to use. Intolerence? Get over yourself.
Anyway, Muddy is using some form of linux and those are his mount points. Windows is stupid about spaces so it's best not to use them. But since you were going to use EXT4, your database was going bye bye anyways.
There are no installers. There are no dependencies. All of this is in the faq and manual. Updating SR is just copying the new version over the old version.
Have you decided on Windows or linux? Are you still planning on using a hypervisor? If you are, I'd recommend going with a type 1 rather than virtualbox.
Open the config file and edit it to fit your system. Add your data drives, your parity drive(s), and pic a few places for spare content files. That's it. That's the whole install and configuration. It really is that simple.
Use taskschd.msc to schedule syncing and scrubs, but I'd really recommend not doing that. You could be in the middle of changing or rearranging the files and such and a sync automatcially runs . But that's up to you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@David - First thanks for that information - unfortunately none of it clarifies my actual question on the format of the config commands.
I know the difference between simplicity and ambiguity, and if you have a different opinion about that; well, opinions can differ.
You keep saying "list your data drives" without addressing how to define them; which is the basis of my query. I asked some specific questions on what I needed clarified. If it was so easy, why keep wasting my/your time simply repeating "its easy", instead of just answering my question? What is the point of that?
As a naïve user, when I ask some simple questions and you respond with: "its dead simple" - and then, not provide any useful information, - and then do it AGAIN - well sir: you imply that I'm too stupid to figure it out - and you are not really interested in responding to my question. You still haven't.
IMHO, if you want new users to adopt SnapRAID, I suggest you take a different approach.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You keep saying "list your data drives" without addressing how to define them;
Sample SR config file I substituted hypens for hashtags so the text isn't huge.
-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 [,FILE] ..."
Here is where you set your parity file. Don't put it on a data drive or on a partition with a data drive.
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 [,FILE] ..."
Here is where you set up multiple parity levels. Just uncomment and set the file on another drive. None of the parity drives have to be formatted or empty.
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"
These are content files. They store the metadata and such. You should have a copy of these on a few drives.
content C:\snapraid\snapraid.content
content K:\array\snapraid.content
content L:\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! - Format: "data DISK_NAME DISK_MOUNT_POINT"
Here are your data drives. Start with "data" then the drive name, and then the folder. You can use the root or a specific folder.
data -> SR use as a data drive
d1 -> the drive name As mentioned before, no idea what to do if you use a spaces. Try escapements. Could use quotes?
k:\array\ -> the folder you want SR to protect
I know; complicated and cryptic,
data d1 K:\array\
data d2 L:\array\
data d3 M:\array\
Excludes hidden files and directories (uncomment to enable).
-nohidden
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\"
Here are your exclusions
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).
WARNING: Changing this value is for experts only!
Default value is 256 -> 256 kibi bytes -> 262144 bytes
Format: "blocksize SIZE_IN_KiB" Shouldn't have to mess with this.
-blocksize 256
Defines the hash size in bytes (uncomment to enable).
WARNING: Changing this value is for experts only!
Default value is 16 -> 128 bits
Format: "hashsize SIZE_IN_BYTES"
Shouldn't need to mess with this either
-hashsize 16
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"
You should use this
-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"
This doesn't work well for me
-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.
Use if you want
- 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:
I don't use this.
-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
Dead simple and all the info is in the sample config file.
you imply that I'm too stupid to figure it out - and you are not really interested in responding to my question. You still haven't.
I don't think you're too stupid to figure it out. I think you don't really care to look over the extensive and easy to read faq and manual. I think you're too lazy to even try SR.
IMHO, if you want new users to adopt SnapRAID, I suggest you take a different approach.
I don't care if you use SR or not. I'd bet real money you won't.
Good luck.
Last edit: David 2021-10-28
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
parity Z:\Snapraid.parity
content C:\Snapraid\snapraid.content
content H:\snapraid.content
content I:\snapraid.content
data M1 H:\
data M2 I:\
data M3 J:\
data M4 K:\
data M5 L:\
data M6 M:\
data M7 N:\
data M8 O:\
You run snapraid sync from command prompt or powershell and wait for snapraid to create the following files:
Later you run the following commands:
snapraid diff to see what has changed since last sync
snapraid sync to update parity
snapraid scrub to verify that files and parity is ok.
snapraid fix to restore files
Last edit: Leifi Plomeros 2021-10-28
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@Leifi: Thank-you - confirming that I can use drive letters as mount points was one of the very simple questions that I asked. The example provided was not clear in that regard.
@David: Regurgitating the manual that I've already read is not helping. You should consider staying off this forum - or any forum for that matter. Your pretense of helping people is obvious to everyone but yourself. I would also say to you: good luck... in life.
This will be my last post here.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am currently attempting a test migration from a Windows 2008 Server to UNRAID. Initially, I upgraded my MB, CPU, memory and boot drive and installed Windows 10 on an NVMe. All good. The second step was to move to UNRAID and run Windows 10 and Ubuntu under VM's. UNRAID is working fine with a test migration but I am having some problems getting VM's to work properly. Doing research, I ran across SnapRAID and I am considering this approach instead.
For my application, the revised approach is to install Oracle’s Virtual Box and then run both Windows 10 and Ubuntu under a VM. Then installing SnapRAID under Ubuntu (reliability & performance + EXT4 FS). Windows 10 VM will access shares and provide some media management, not available to Linux. (I suppose I can just install SnapRAID under Windows 10 and then do everything there - but I still want it running under a VM)
For my rebuild, I purchased a 10TB WD GOLD drive - that is currently acting as my UNRAID parity drive. It would get repurposed for the SnapRAID parity disk. I would purchase a second one for dual parity once the system is running. All of my other drives are <2 year old Seagate Ironwolf 8TB drives.
The general application is operating a home media server (64TBs) plus a data repository for a wide range of files including system backups on my network. This is on an 8TB drive backed up on a second 8TB drive.
Love to hear any thoughts on on how folks here might implement a SnapRAID solution based on the above scenario; pros and cons.
Thanks for your help!
PS: Just noticed Elucidate on git hub. Maybe I'll take the Windows approach instead.
Last edit: RAP 2021-10-23
No one offering comments on a Media server implementation? Windows versus Linux on a VM? Elucidate?
Unlike UNRAID Snapraid is completely passive.
You set it up via snapraid.conf and then you use the following commands:
snapraid diff to see what has changes since last sync
snapraid sync to update parity
snapraid scrub to verify that files and parity is ok.
snapraid fix to restore files
Another important difference is that snapraid is great for large media files that rarely change but not so great for lots of small files like system backups. If you want to use it for the latter I would strongly recommend that you put the backups inside zip archives or similar.
Considering that you are comfortable with both Linux and VM:s I strongly doubt that you have any need for Elucidate. You just need to modify the example snapraid.conf file included with the installation to test it.
Thanks Leifi,
Is there an API for SnapRAID that allows one to run a script to least SYNC & SCRUB based on some schedule?
There are scripts created by users but I have no experience of using them and I'm not updated on which are better or more reliable.
Personally I just run a .bat file for sync and another .bat file for scrub every now and then.
OK... downloaded the files extracted. I've decided to try it on a Windows 10 machine first... with one parity drive and one data drive.
Is there an installer or does it just run as an exe? Are there dependencies?
I read the isntall.txt - it seems all I have to modify the snapraid.conf file - within that directory - and then what? double click the exe? Sorry - if I'm slow on the uptake here, but its so basic that its questionable. :-)
So I am asking before I leap.
Cheers!
Rob
I use Snapraid with mergerfs for my media/file server it's been fine. Only suggestion is stop any data change during a sync, this is not a solution for heavy i/o file servers. Slow changing media servers is the use case. I moved my backups to an ESOS SAN storage box I built to avoid heavy changes to the snapraid media server.
Understood. I will only use SnapRAID for my movie drives - my data backups, photos and music - which all change, will be mirrored separately.
I'm having trouble with the config file because - IMHO - the language is not precise enough to be 100% certain of a correct configuration.
For example; the use of the word "array" in the content list file and then later in the data file. Is this just part of the example path?
In the case of the Data Disk, my disks all have two words separated by a space. The format structure "data DISK_NAME DISK_MOUNT_POINT" would cause a problem for something like this: "data Movies ONE K:\" - where "Movies ONE" is the Disk Name.
You are really overthinking everything.
SR is dead simple to set up and use. Just edit the config file to add the drives. It really is that simple. https://www.snapraid.it/faq
I'd recommend using single words for drive names not only because it's much easier from a SR point of view, but also a maintenance POV, automation POV, and Windows is generally stupid about such things.
in my snapraid config I just followed their examples and it worked, I have :
data d1 /mnt/data/data1/
data d2 /mnt/data/data2/
data d3 /mnt/data/data3/
data d4 /mnt/data/data4/
data d5 /mnt/data/data5/
data d6 /mnt/data/data6/
data d7 /mnt/data/data7/
data d8 /mnt/data/data8/
data d9 /mnt/data/data9/
data d10 /mnt/data/data10/
Hope that helps.
@David:
I'm not over thinking it. I'm also not changing my Windows Disk Names and UNC paths because my 5000 movie data base is based on those. I have no interest is spending hours changing that stuff.
With apologies, but it might be "dead simple", once you know. I'm a software programmer, and career broadcast technologist - and when I see instructions with language this ambiguous - that potentially affects how 64 TB's of MY data is affected; I'm concerned. You might be more tolerant about me asking some basic (possibly naïve) questions; instead of suggesting to blindly go ahead and configure without full understanding of things.
I've also read the FAQ's... and BTW: there is nothing there about how to configure the actual snapraid.conf file. I just checked again. This is provided in the snapraid.conf.example file and some additional information in the snapraid.txt file. If there is more information elsewhere, that would indeed be useful. Thanks.
@Muddy Waters:
So your physical disks are actually named d1 through d10? Or, is this just how SnapRAID names them internally through the config file?
If that's the case, I can simply remove the spaces in my current drive names (which are also my UNC paths) - in that way, there is some correlation between the SnapRAID disk name and the Windows disk name. Please advise...
Regarding the second parameter: DISK_MOUNT_POINT
In Windows, my Disk Mount point is the drive letter. So, I'm confused by your /mnt/data/data1/ (as an example) Are you using Windows? Is this an NTS folder mount?
Assuming I can use whatever name I want for DISK_NAME and Windows drive letters for IDSK_MOUNT_POINT, I have this:
data MoviesONE H:\
data MoviesTWO I:\
data MoviesTHREE J:\
data MoviesFOUR K:\
data MoviesFIVE L:\
data MoviesSIX M:\
data MoviesSEVEN N:\
data MoviesEIGHT O:\
parity Y:\snapraid.parity
parity Z:\snapraid.parity
content C:\SnapRAID\snapraid.content
content Y:\snapraid.content
content Z:\snapraid.content
content X:\SnapRAID\snapraid.content
content G:\SnapRAID\snapraid.content
content N:\SnapRAID\snapraid.content
Yes, you're overthinking it. You're confusing simplicity for ambiguity.
In the config file, list your data drives, the parity drive or better drives, and your spare content files. Then run sync. It really is that simple. Later you can change things like the exclude folders and the autosave. The autosave feature is really nice. As you run SR you can see everything it does. SR isn't something that if you get wrong it's gonna wipe out half you data. Even if you misconfigured a data drive for a parity drive, it's not going to erase the drive. It'll either write a file until the drive is full or it will tell you that you don't have enough space. It will not wipe out your data.
SR only reads from the data drives and only writes to the parity file so your data, sorry, your data is safe. It's a config file. It's not some esoteric settings in binary that you have to get exactly perfect, compile, then hope it works. Simply play with it until everything works. One of the best things about SR is the abstraction.
BTW, my "intolerance?" Good Lord, was just trying to explain SR is dead simple to use. Intolerence? Get over yourself.
Anyway, Muddy is using some form of linux and those are his mount points. Windows is stupid about spaces so it's best not to use them. But since you were going to use EXT4, your database was going bye bye anyways.
There are no installers. There are no dependencies. All of this is in the faq and manual. Updating SR is just copying the new version over the old version.
Have you decided on Windows or linux? Are you still planning on using a hypervisor? If you are, I'd recommend going with a type 1 rather than virtualbox.
Open the config file and edit it to fit your system. Add your data drives, your parity drive(s), and pic a few places for spare content files. That's it. That's the whole install and configuration. It really is that simple.
Use taskschd.msc to schedule syncing and scrubs, but I'd really recommend not doing that. You could be in the middle of changing or rearranging the files and such and a sync automatcially runs . But that's up to you.
@David - First thanks for that information - unfortunately none of it clarifies my actual question on the format of the config commands.
I know the difference between simplicity and ambiguity, and if you have a different opinion about that; well, opinions can differ.
You keep saying "list your data drives" without addressing how to define them; which is the basis of my query. I asked some specific questions on what I needed clarified. If it was so easy, why keep wasting my/your time simply repeating "its easy", instead of just answering my question? What is the point of that?
As a naïve user, when I ask some simple questions and you respond with: "its dead simple" - and then, not provide any useful information, - and then do it AGAIN - well sir: you imply that I'm too stupid to figure it out - and you are not really interested in responding to my question. You still haven't.
IMHO, if you want new users to adopt SnapRAID, I suggest you take a different approach.
Sample SR config file I substituted hypens for hashtags so the text isn't huge.
-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 [,FILE] ..."
Here is where you set your parity file. Don't put it on a data drive or on a partition with a data drive.
parity E:\snapraid.parity
Here is where you set up multiple parity levels. Just uncomment and set the file on another drive. None of the parity drives have to be formatted or empty.
-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
These are content files. They store the metadata and such. You should have a copy of these on a few drives.
content C:\snapraid\snapraid.content
content K:\array\snapraid.content
content L:\array\snapraid.content
- Format: "data DISK_NAME DISK_MOUNT_POINT"
Here are your data drives. Start with "data" then the drive name, and then the folder. You can use the root or a specific folder.
data -> SR use as a data drive
d1 -> the drive name As mentioned before, no idea what to do if you use a spaces. Try escapements. Could use quotes?
k:\array\ -> the folder you want SR to protect
I know; complicated and cryptic,
data d1 K:\array\
data d2 L:\array\
data d3 M:\array\
-nohidden
Here are your exclusions
exclude *.unrecoverable
exclude Thumbs.db
exclude \$RECYCLE.BIN
exclude \System Volume Information
exclude \Program Files\
exclude \Program Files (x86)\
exclude \Windows\
Format: "blocksize SIZE_IN_KiB"
Shouldn't have to mess with this.
-blocksize 256
Defines the hash size in bytes (uncomment to enable).
Shouldn't need to mess with this either
-hashsize 16
Format: "autosave SIZE_IN_GB"
You should use this
-autosave 500
Defines the pooling directory where the virtual view of the disk
This doesn't work well for me
-pool C:\pool
Use if you want
- Format: "share UNC_DIR"
-share \server
I don't use this.
-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
Dead simple and all the info is in the sample config file.
I don't think you're too stupid to figure it out. I think you don't really care to look over the extensive and easy to read faq and manual. I think you're too lazy to even try SR.
I don't care if you use SR or not. I'd bet real money you won't.
Good luck.
Last edit: David 2021-10-28
This is how it works:
You edit snapraid.conf like this:
You run snapraid sync from command prompt or powershell and wait for snapraid to create the following files:
Z:\Snapraid.parity
H:\snapraid.content
I:\snapraid.content
Later you run the following commands:
snapraid diff to see what has changed since last sync
snapraid sync to update parity
snapraid scrub to verify that files and parity is ok.
snapraid fix to restore files
Last edit: Leifi Plomeros 2021-10-28
@Leifi: Thank-you - confirming that I can use drive letters as mount points was one of the very simple questions that I asked. The example provided was not clear in that regard.
@David: Regurgitating the manual that I've already read is not helping. You should consider staying off this forum - or any forum for that matter. Your pretense of helping people is obvious to everyone but yourself. I would also say to you: good luck... in life.
This will be my last post here.