Activity for David
-
David modified a comment on discussion Help
This seems trivial, and I understood your predicament, but next time maybe not use the same word to describe two different things? First, don't run a sync. I would guess you would be able to recover all of the files on the first disk that did not have any matching files on the second disk. Here's what I mean. (God, this editor is freakin' stupid. Just show the same damn thing in the editor before and after posting) X............X X.....X....X X....X X X X....X X X X X X X X 1 2 3 4 P Here's your...
-
This seems trivial, and I understood your predicament, but next time maybe not use the same word to describe two different things? First, don't run a sync. I would guess you would be able to recover all of the files on the first disk that did not have any matching files on the second disk. Here's what I mean. (God, this editor is freakin' stupid. Just show the same damn thing in the editor before and after posting) X............X X.....X....X X.....X X X X.....X X X X X X X X 1 2 3 4 P Here's your...
-
This seems trivial, and I understood your predicament, but next time maybe not use the same word to describe two different things? First, don't run a sync. I would guess you would be able to recover all of the files on the first disk that did not have any matching files on the second disk. Here's what I mean. (God, this editor is freakin' stupid. Just show the same damn thing in the editor before and after posting) X.................X X.......X.......X X.......X . X . X X.......X . X. X X X X X X...
-
This seems trivial, and I understood your predicament, but next time maybe not use the same word to describe two different things? First, don't run a sync. I would guess you would be able to recover all of the files on the first disk that did not have any matching files on the second disk. Here's what I mean. (God, this editor is freakin' stupid. Just show the same damn thing in the editor before and after posting) X.................X X.......X.......X X.......X . X . X X.......X . X. X X . X . X...
-
This seems trivial, and I understood your predicament, but next time maybe not use the same word to describe two different things? First, don't run a sync. I would guess you would be able to recover all of the files on the first disk that did not have any matching files on the second disk. Here's what I mean. (God, this editor is freakin' stupid. Just show the same damn thing in the editor before and after posting) X.................X X.......X.......X X.......X X X X.......X X X X X X X X 1 2 3...
-
This seems trivial, and I understood your predicament, but next time maybe not use the same word to describe two different things? First, don't run a sync. I would guess you would be able to recover all of the files on the first disk that did not have any matching files on the second disk. Here's what I mean. (God, this editor is freakin' stupid. Just show the same damn thing in the editor before and after posting) X.................X X.......X.......X X.......X X X X.......X X X X X X X X 1 2 3...
-
This seems trivial, and I understood your predicament, but next time maybe not use the same word to describe two different things? First, don't run a sync. I would guess you would be able to recover all of the files on the first disk that did not have any matching files on the second disk. Here's what I mean. X X X X X X X X X X X X X X X X X X 1 2 3 4 P Here's your layout with me guessing capacity usage. You lose drives 1 & 2 and the parity drive provides for 1 drive loss. . X . X X . X X X . X...
-
This seems trivial, and I understood your predicament, but next time maybe not use the same word to describe two different things? First, don't run a sync. I would guess you would be able to recover all of the files on the first disk that did not have any matching files on the second disk. Here's what I mean. X X X X X X X X X X X X X X X X X X 1 2 3 4 P Here's your layout with me guessing capacity usage. You lose drives 1 & 2 and the parity drive provides for 1 drive loss. X X X X X X X X X X X...
-
You may want to consider using the "autosave" feature.
-
You're creating a new parity file that allows for two drive recovery, not duplicating the first parity file. Data will be safe on the first parity drive. It will be just my luck that a drive or two fails when trying to add more parity, Ironically, this is why you want multilevel parity. When you're recovering a drive, you are hammering all of the drives at 100% for possibly days. If a drive is close to dying, this can push it over the edge. That's why having multiple parity drives is a good thing....
-
You're creating a new parity file that allows for two drive recovery, not duplicating the first parity file. Data will be safe on the first parity drive. It will be just my luck that a drive or two fails when trying to add more parity, Ironically, this is why you want multilevel parity. When you're recovering a drive, you are hammering all of the drives at 100% for possibly days. If a drive is close to dying, this can push it over the edge. That's why having multiple parity drives is a good thing....
-
If you don't know what you're talking about, don't give advice. Oh no, I misunderstood something about snapraid. A thousand apologies. And I didn't crap on him, I told him to RTFM, since he had no clue what my question was even about, or the previous one from 4 years ago. Yeah, you were being a dick. I didn't care and that's why I let it slide. I figure everyone in this field has limited social skills. And you, what does your response have to do with my situation? Why even reply? He's pointing out...
-
You can defrag the data and parity drives any time you want.
-
Am I doing anything wrong or how can I make sure the sync operation does not run if I accidentally use a disk of a different set? As mentioned by others, the flaw is you and your process. If you're determined to keep doing things the ways you are, I'd recommend using the high-tech solution of boxes. Label each set of drives with big labels and segregate each set in their own box to prevent mixing.
-
Why? What problem are you trying to solve? I don't think that would work because a user can always drop the higheset level of parity and when you're swapping 2 for 1, you're removing the "base" level of parity. If you wanted to do something like that, you could always set up two config files and use a single level of parity for each.
-
When that happened to me and I ran fix, I'm positive I was presented with a list of files that were required to recreate the missing files. I piped that list into a file, looked for those files, and downloaded any files that were missing.
-
When that has happened to me and I ran fix, I'm positive I was presented with a list of files that were required to recreate the missing files. I piped that list into a file, looked for those files, and downloaded any files that were missing.
-
How can you suggest so buggy app to use with important data? Well, it's less buggy now, right? And they're working on making it better. Also it comes with proprietary driver for combine disks. Its dead block for using this software. Is it? You don't have to use the pooling software. Doesn't all drive pooling solutions use a proprietary driver? BTW, some day snapraid will be gone. That's now things work. I really miss flexraid. I loved that software. I'd still be running it now if I didn't change...
-
So you're upset because you can't convince me? Yes, people can suggest features. Other people can respectfully comment on said suggestions. One of my suggestions is to get exactly what you want, DrivePool already offers it. Right now. And if you have a wrapper that mostly what you want, wouldn't it make sense to expand that and offer it yourself? After all, why should Andrea duplicate your finished work to get the same result? But, you know what? I could be wrong. Andrea could look at your suggestion...
-
So you're upset because you can't convince me? Yes, people can suggest features. Other people can respectfully comment on said suggestions. One of my suggestions is to get exactly what you want, DrivePool already offers it. Right now.
-
If you've got what you want, then use that. If you need functionality that isn't SR, keep building what you need then distribute and support that rather than pushing the idea off to Andrea. I could be wrong, but what you're asking for sounds extremely niche and again, completely out of the ethos of SR. Having SR move files changes it completely. Again, DrivePool does exactly what you want and will distribute the files according to many different conditions that the user predetermines. If you want...
-
If you've got what you want, then use that. If you need functionality that isn't SR, keep building what you need then distribute and support that rather than pushing the idea off to Andrea. I could be wrong, but what you're asking for sounds extremely niche and again, completely out of the ethos of SR. Having SR move files changes it completely.
-
It may sound easy, but "easy to implement" never is. What I understand you want is "You copy data to a folder and SR distributes that data automatically," right? That sounds like unRAID. That requires much more than I think you understand. SR would have to continually run to monitor that folder. Then SR would have to intelligently move and verify the data to any drive (you did mention if a drive was full then move it to a drive with more space) and be aware of drive capacities. SR would have to automatically...
-
That's not what SR does. I understand you're suggesting it, but that isn't in SR's philosophy. You can use something like DrivePool that will do exactly that and SR will handle the parity.
-
I'm sure some people have had problems with SR, but yes, you are the only one who has tried Snapraid "on 3 different computers, 20 different hard disks, freshly installed Windows 11, etc." and had unrecoverable problems every time something is tried. I'v been using SR for over 11 years and while I'm sure there has been a problem at some point, I don't remember. And I've replaced multiple drives due to size changes, changed parity levels at least half a dozen times, recovered two or three drives,...
-
Congrats. SR has been out for over a decade and you're the only one.
-
The nice thing about SR, well, what I like most, is it's completely abstracted from the OS. I use DrivePool to create a shared drive and Stablebit Scanner to monitor my drives. You can use SR to run a smart scan on your drives and I'm sure there's a way to externally schedule that, parse the output, and send an email if a certain string is present. Here's the thing about a downloads drive. If the files on it are always changing, then it can be effectively a "lost" drive depending on when you sync....
-
SR will not "disconnect the other drives." Writing new files to the data drives is fine. Changing files or deleting files isn't. As long as new files are written, you're fine. 10 data disks to 1 parity is risky, but that means you can lose 1 drive and still recover files. If you lose a file/drive, you can still recover that file or drive. But if you lose a file/drive and change the files on the other drives, then you probably won't be able to recover some of the files. Files across drives create...
-
Nope. As long as you remove the last parity drive, everything else is fine. https://www.snapraid.it/faq#addpardisk
-
Chainging a parity to a data disk is easy as long as you pick the LAST parity drive. So if you had three parity drives, remove the third parity drive form the config, format it, and add it to the config as a data drive. SR "pooling" creates links in a directory to the files. It may work fine for most cases, but in my experience, bluray structures wouldn't play. DrivePool works great, but I turn off the balancing and all of the other features. I use just the pooling to a drive.
-
Have you tried doin a 1% scrub?
-
3.6T. That's 4
-
So, running Snapraid on two drives works just fine - running on 20 drives does not on my current setup. And apparently no hw errors on the controller or cables, or this test-sync should've failed as well, right? Not if it's a total load failure on the PSU. Follow my suggestion. I had the exact same problem. This is how I diagnosed the solution. I'm not sure why you are testing a two drive sync. I would recommend moving everything to a single variable; the PSU output. Test your system using my suggestion...
-
Ok, just so I understand. My method, which is the easiest and fastest, is to open a command prompt, run check disk on a drive, and wait 30 seconds for an error. If no error, do it again. And keep doing that until an error occurs. Once an error occurs, do the same thing in a different order and if an error occurs at about the same number of drives, you know it's the PSU. Easier to just amend the conf file with a # and add 1 drive at a time to SR scrub.. Your suggestion is to edit the config file,...
-
I'm not sure if copying the a file would work. You want to emulate the conditions of a scrub which are 100% utilization of every drive, but you want to do it incrementally while keeping the spinning drives at 100%. In other words, you are testing the power supply with the drives. If you're getting errors while the approximately the same number of drives are being checked in a different order each time, it's the PSU.
-
I'm not sure if copying the a file would work. You want to emulate the conditions of a scrub which are 100% utilization of every drive, but you want to do it incrementally while keeping the spinning drives at 100%.
-
Also, there is no need to do what David tries to get you to do, it does NOTHING a scrub wouldn't do, True, but what it does is allow the person to spin up the drives incrementally. Scrub runs them all 100% immediately and an error could be caused by almost anything. But if you spin up 12 drives and you start getting errors on the 13th, then you know there is a problem there. and what you get is non-result, a "failure" on same drive everytime, if you spin them up in the same order. After getting the...
-
1150W should be enough, if that's what you're getting under load. I'd recommend my earlier advice. Open up a cmd prompt and run chkdsk, or the linux equivalent. Wait a minute, and do it again on another drive. Keep doing it until you get an error or all drives are running.
-
If you want to use a 14TB data drive, you'll either need all of your parity drives to be 14TB or you'll need to build a split parity volume out of multiple drives. For example 1 14tb drive data, 1 parity 2 6tb drives data 1 2tb drive data 14tb split parity volume of 6tb+2tb+2tb+2tb+2t or some other combination that equals 14tb If you can't create a split parity volume, then both 14tb drives will have to be parity.
-
"Sure, I don't like to throw money at problems myself. But in this case it's only like $40 for a used PSU." He doesn't want help. He wants to argue. I told him what happened to me and how to stress his machine to see if that produced an error, but he'd rather argue. He has the money to replace every part of his machine except the PSU is "too expensive." He wants to argue. EDIT: Case in point, see his reply. He wants to argue. He doesn't want to solve the problem.
-
"Sure, I don't like to throw money at problems myself. But in this case it's only like $40 for a used PSU." He doesn't want help. He wants to argue. I told him what happened to me and how to stress his machine to see if that produced an error, but he'd rather argue. He has the money to replace every part of his machine except the PSU is "too expensive." He wants to argue.
-
I can't help. Good luck.
-
Run a surface scan on a drive. After a minute, do the same thing on another drive. Wait another minute, rinse and repeat. What you're doing in spinning all of the drives up at the same time and stressing the PSU. Like a scrub.
-
I tested the machine by using chkdsk. I kept opening up command prompts and doing concurrent disk scans until errors occured.
-
I have no idea about error 21, but I had SR throw errors during sync when I had a failing PSU.
-
Right now, the autosave line includes the percetnage done, CPU load, and the ETA another a few other things. Adding a simple time stamp would be nice to see exactly when the autosave occurred and how much time passed between autosaves.
-
What is your process? What are you trying to accomplish? If you run a batch file, sync will run milliseconds after the diff.
-
Use a batch file. It's that simple.
-
What you want is a drive recovery program. Which SR is. If you want to recover an entire drive, that's what you can do. No. This is not normal. All backup systems restore files AND FOLDERS to a previously saved state. Nope. If I restore a folder with a backup program, it will restore THAT folder with THOSE files under A specific folder. The backup program doesn't look for new, renamed, or older folders and delete the folder with everything under it. What SR also does, is file and directory recovery....
-
What you want is a drive recovery program. Which SR is. If you want to recover and entire drive, that's what you can do. No. This is not normal. All backup systems restore files AND FOLDERS to a previously saved state. Nope. If I restore a folder with a backup program, it will restore THAT folder with THOSE files under A specific folder. The backup program doesn't look for new, renamed, or older folders and delete the folder with everything under it. What SR also does, is file and directory recovery....
-
I can't tell if you're trolling or not. It reads like you are. How is SR supposed to know if you've renamed a directory with the express purpose of restoring to that directory or if you've renamed a directory for any of a thousand other more common reasons?
-
I agree spinning drives up an down isn't a good idea. I believe in leaving the drives running all the time for max reliability. What I'm suggesting is your last sentence; throttling speed or starting and stopping read and writing.
-
If he wants that, then use a batch file. That's what I do. I run a batch file that does a status, then diff, then sync.
-
Many people like to run SR with a single parity drive. This is dangerous becasue if a drive is close to dying, running 100% for a day or so could kill it. So what if there was a "gnetle recovery" option? SR takes double the amount of time to recover the failed drive, but the drives run at half speed. Maybe recovery a percent then idle for a minute or two for the drives to cool down or something like that. Some idle time to prevent all of the drives running at 100% for a day or two. Just an idea.
-
While one parity drive is better than nothing, if possible you should have more than one. If a drive dies and you need to do a rebuild, it is very stressful on all of the drives. Recovery means running all of the drives at 100% for multiple hours and possibly days and if you have a drive that is close to failing, that stress could kill a drive. If that happens, the files on both drives are unrecoverable. Just something to think about.
-
Why would you add files to the disk while syncing? I could be wrong, but I don't think the files added during syncing would sync.
-
Sure, SR is safe. There are pros and cons to everything. My philosophy with data is keep everything as simple as possible. 1) Always use one drive per level of parity 2) Don't split the same directory over drives although pooling can combine them 3) Only use pooling software to read 4) Write files where I want them 5) Make recovery as simple as possible. What I mean 1) People like to reuse drives to make split parity files. Fine if they want to, I don't. 2) If I have a BR structure I've ripped, I...
-
Ok, that explains it. Because SR works at the file level, it has a relatively unknown quirk that most people don't consider and I only learned about by reading this forum. Earlier you asked how does SR know from which parity file to read to recover. SR reads from all of them, Here is a very basic explanation of how the a single parity works. 1 0 0 1 0 1 0 0 1 0 1 1 1 1 0 0 0 0 0 0 0 1 1 1 1 1 1 1 0 0 0 0 0 1 1 1 1 2 3 4 5 6 7 8 Parity. (Drives 1 - 8 and parity) Drives 1 - 8 have either a 1 or a 0....
-
Was the data on 3 drives like you just mentioned, or on two drives like you mentioned in the first post?
-
You've got the data off the good disks and professional recovery could be an option. You could do a list piped to a file to see what you're missing if you can get the files from somewhere else. One parity drive means you can recover data if any one drive has died. With a single parity drive, if two drives are unavailable, no data can be recovered. Going forward, you could consider at least two parity drives per array. Not specifically for this situation, but recovery is very difficult on drives and...
-
0% could be rounded down. Defragmented doesn't necessarily mean contiguous. SR doesn't care about fragmentation and you can always defrag at any time.
-
Think of it this way. Here's your drive xxx xxxx xxxxx xxxxxx xxxxxxxxx When you add the files xxxyxxxxyxxxxxyxxxxxxyxxxxxxxxxyyyyy Your drive is fragmented so when you add files, they are fragmented. Defrag your drive first.
-
The sync "creates" the parity files but it fills them in during the sync. You need to let it run all the way through. Uncomment autosave and set it so the sync doesn't have to run all the way through in a single pass. Mine is set to 20000. After you see it set a save spot, you can break the sync and it will pick up at that point later.
-
You would have needed to copy or move the original parity file to a 14TB drive, Then add the second 14tb parity drive and sync. To fix this, remove and format the 3rd parity drive. Sync. Then copy the 10GB party file to the empty 14TB drive. Change the config so that it's the first parity file and sync.
-
What is "quite a few?" The problem with having a parity/data drive is if you lose that physical drive then you effecively lose two drives at once. You don't need to partition the drive. You can store another 6tb of storage on that drive. It just isn't protected by SR.
-
Why not use use the 8tb as parity from the start? It'll eliminate a bunch of hassle later and give you more protected data now.
-
He answered your question and typed out his logic. For some reason, you acted defensively. AFAIK, everything you to tell SR to back up, it'll back up except for content files. Everything is in in manula https://www.snapraid.it/manual
-
How often is it interupted
-
Have you tried turning it off? 100 seems very low.
-
That's pretty much the same hardware I have although I am using Windows.
-
How are your drives connected? JBOD RAID card? Motherboard SATA? PCI SATA cards? After you receive your new parity drive, I would try this. Disconnect your original parity drive and rename the content files. Edit your config file and remark out all drives except for two or three. Add the new parity drive as a single parity and run a sync. See what the speed it. If it's still low, remark out those drives and pick out three more. If it's quicker, add another drive and do another sync. Keep doing that...
-
How are your drives drives? JBOD RAID card? Motherboard SATA? PCI SATA cards? After you receive your new parity drive, I would try this. Disconnect your original parity drive and rename the content files. Edit your config file and remark out all drives except for two or three. Add the new parity drive as a single parity and run a sync. See what the speed it. If it's still low, remark out those drives and pick out three more. If it's quicker, add another drive and do another sync. Keep doing that...
-
I'm running a sync right now and snapraid is using 21GB of memory. How are the drives connected? Have you done a speedtest on each individual drive to see if there is a bad port, cable, or socket?
-
Check your swap file and memory usage when you sync. I'm guessing there's the problem.
-
That 300MB/s seems slow. I'm running 19 drives with 3 parity, AMD 5, 40GB RAM and I'm getting 1730MB/s speeds. Your RAM may be low so your hitting swap. I'd really recommend running at least a second parity drive. Restoring a drive is very disk intensive due to all drives running at 100% for days and if a drive is close to dying, doing a restore can be enough to push it over the edge. Then you'll have two drives gone with only a single parity. Just a thought.
-
This is personal use, so I don't need extensive support, but I'm not a fan of restricting the software itself based on price.* I'm not defending unraid, but that's how they make their product cheaper for people that don't need the more expensive full version. Would it be a better option if they didn't have the limited version and required people to pay only for the full version? You could always do that. You could always use task scheduler to fire off a batch file that uses voidtools' command line...
-
Unraid is a one time purchase, but to be honest you should be paying for SnapRAID. If you find use for it, you should support it.
-
If you have a program that is updating or replacing files, that is effectively the same as a delete for a RAID. The dedicated RAID hardware and software constantly update the parity. That's how they are able to work with a degraded system while other programs update files. I've used dedicated hardware RAIDs before and like I mentioned, I still use a couple of drobos. I'm perfectly happy with them. SR is generally designed for files that don't change after adding. I'd recommend adding another parity...
-
No idea. I run manual syncs under windows. SR should refuse to sync if a drive is missing. Personally I like SR over hardware RAID. I've used dedicated hardware RAID where the drive's firmware had to match and DAS/NAS systems where drives could be mixed. I still have two drobos and I think they're great. While it's more convenient, I prefer SR. With SR there is no funky formatting and if the absolute worst happens, I have readable data on each of my drives so I can simply pop them out and have my...
-
Right. Recovery computes the remaining drives with the parity drive to see what value is missing. Single parity works like this. Same four drive array with a single parity drive. Again very simplified. Sometimes I don't explain things in the best way, so if any of this is confusing let me know and I'll try to explain better. 1 2 3 4 1 0 0 0 1 1 1 1 0 0 1 0 0 0 1 1 1 0 1 0 Parity looks at the data and computes a value with XOR. 1 2 3 4 P 1 0 0 0 1 1 1 1 1 0 0 0 1 0 1 0 0 1 1 0 1 0 1 0 0 So let's say...
-
Snapraid is great and my first contribution to Andrea was almost nine years ago, but SR isn't real-time. This is how I understand how SR works and this is very simplified, so if I'm wrong, someone let me know. Here's an array with 4 drives and a parity drive with 5 sectors each 1 2 3 4 5 x x x x y x x x x y x x x x y x x x x y x x x x y Let's say drive 4 dies. 1 2 3 4 5 x x x......y x x x......y x x x......y x x x......y x x x......y SR can rebuild drive 4 by figuring out how the parity was built...
-
Snapraid is great and my first contribution to Andrea was almost nine years ago, but SR isn't real-time. This is how I understand how SR works and this is very simplified, so if I'm wrong, someone let me know. Here's an array with 4 drives and a parity drive with 5 sectors each 1 2 3 4 5 x x x x y x x x x y x x x x y x x x x y x x x x y Let's say drive 4 dies. 1 2 3 4 5 x x x......y x x x......y x x x......y x x x......y x x x......y SR can rebuild drive 4 by figuring out how the parity was built...
-
Snapraid is great and my first contribution to Andrea was almost nine years ago, but SR isn't real-time. This is how I understand how SR works and this is very simplified, so if I'm wrong, someone let me know. Here's an array with 4 drives and a parity drive with 5 sectors each 1 2 3 4 5 x x x x y x x x x y x x x x y x x x x y x x x x y Let's say drive 4 dies. 1 2 3 4 5 x x x. . y x x x. . y x x x. . y x x x. . y x x x. . y SR can rebuild drive 4 by figuring out how the parity was built against the...
-
Snapraid is great and my first contribution to Andrea was almost nine years ago, but SR isn't real-time. This is how I understand how SR works and this is very simplified, so if I'm wrong, someone let me know. Here's an array with 4 drives and a parity drive with 5 sectors each 1 2 3 4 5 x x x x y x x x x y x x x x y x x x x y x x x x y Let's say drive 4 dies. 1 2 3 4 5 x x x y x x x y x x x y x x x y x x x y SR can rebuild drive 4 by figuring out how the parity was built against the other 3 drives...
-
What would happen when recovering from a drive failure on a system with one parity drive if one of the drives had five or ten percent of the files missing? The full drive couldn't be rebuilt.
-
It'll work, but you don't need to partition the 8TB drive.
-
I use "A" as my drive letter pool. I don't know if this will transfer to mounting points, but I changed the data drive drive letters and as long as I kept the original order of the drives, everything was fine.
-
You can use the 5TB as parity and store as many files as it as you want as long as there is room for the parity file. For example, my largest data drive is 10TB. I have a 12TB parity drive. I nightly close about 1.5TB to a folder on the parity drive.
-
Those drives aren't too bad, not great though, for large files, but they seriously suck for bluray structures due to the small file sizes. I've moved to only buying hitachi & WD refurbished enterprise drives. They have always been rock solid, lightning fast, and relatively cheap. I just purchased a 10TB for $130 and a 12TB for $160. Sometimes they'll be SAS, but SATA can be had at generally the same prices.
-
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....
-
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....
-
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....
-
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....
-
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....
-
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...
-
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.
-
No problem at all and you can use as much drive capacity as you want as long as you leave enough space for the parity file.
-
No problem at all and you can use as much drive capacity as you want as long as you leave enough enough space for the parity file.
-
You can always try undelete software on the drive or or drives if you haven't written any data to them.
-
Here's the thing about recovery. Say you lost a drive. You replace the failed drive and begin recovery. Every drive is now running at 100% for a day? Two days? Longer? So if you have a drive that was close to giving out, the high stress of recovery could casue it to fail.
1 >