amawing videos. i watched both part1 and part 2 and for someone who had no idea how the drivepool and SnapRaid are used i am quite confident i can take care of whatever i need now. thank you so much!
Hello, I’m a VideoMaker, I had 3 disk failures this year alone, so I’m looking for a repair from these occurrences, I think I’ll go with SnapRaid, also thanks to your really really clear explanations. Thank you!
Well made video, thanks. Acts as a good checklist for even experienced users. I tried Elucidate GUI but it doesnt seem to like me or the idea of data disks including Poolpart (mine are c:\Mounts\Disk1\PoolPart-nnnnnnnn and c:\Mounts\Disk2\PoolPart-nnnnnnnn etc as I dont want drive letters if I am storing files via the pool)
I'm not familiar with Elucidate, but I may give it a look. Seems there should be a way to edit the config file for your mount points? Seems like an oversight if that's not possible via that GUI. Author may offer some suggestions if you bring it to their attention.
Thank you for making the videos on using SnapRAID and DrivePool. I've been using both programs for a quite a few years in the manner you describe. I use multiple parity drives, but I know it is still recommended when deleting or replacing files to move them outside the protected array and only delete after the next sync. I saw you mention this in a Reddit post regarding "parity hole", and the SnapRAID FAQ states: "A way to be always safe, is to don't delete files, but move them to another directory in the same disk, but outside the directory tree checked by SnapRAID. Then you can run the "sync" command and only after its completion really delete the files." I'm confused by the FAQ statement "another directory IN THE SAME DISK, but outside the directory tree checked by SnapRAID". I can make a folder on each data drive outside the PoolPart folder, but using DrivePool I wouldn't know on which physical disk the file I'm moving resides. Can you clarify? Also did you ever produce a Part 3 discussing "parity hole"?
I've had several inquiries about Parity Hole part 3 so I may make that video soon then. Regarding the files outside folders protected by snapraid. Sorry for confusion. It doesn't need to be on the same disk. It just needs to be somewhere that SnapRAID isn't protecting. You can even put it on a disk or folder that is protected by snapraid and exclude the "deleted files" folder in the snapraid config file. Or you could store them on another disk altogether. Once you sync, then you can delete the contents in the folder of "deleted files". The whole idea behind it is to move "deleted" files to another location not protected by snapraid. If your snapraid rebuild fails or a disk fails before the next sync, then you can point to that folder of "deleted" files or just move them back to their original location so it can use those files in the calculation to rebuild the data. Drivepool does have the option to specify which folders exist on which disks, so you could go that route if desired.
Thanks. I was really scratching my head over the "another directory IN THE SAME DISK, but outside the directory tree checked by SnapRAID" wording on the SnapRAID FAQ. I wonder why he wrote it like that.
Hi, love your videos on Stablebit Drivepool and Snapriad. I heard that Drivepool will automatically transfer files from a failing drive to other drives in the pool with space on them. If that happens, what is the process for adding a new drive and what commands should I use for Snapraid to get everything in sync and running smoothly again?
Thanks for the feedback and question. If a disk does fail and data evacuated to other drives in the pool, I would disable any scheduled SnapRAID sync or scrub operations immediately. Once data is safely evacuated, remove the failing disk from the pool in Drivepool UI. Shut down and replace the failing disk. Power on, add the new disk to the pool in the DriverPool UI, then set Drivepool to rebalance the pool. When the balance is complete, disable Drivepool services. Update the SnapRAID config file with the new disk info, however, if using same drive letter or mount point it shouldn't be needed. Then just run a new "snapraid sync" command. It will take a lot longer because when Drivepool rebalanced the data, it will have changed the location of a lot of files. The ".content" file on the new disk will be regenerated automatically if missing as well if assigned in SnapRAID config file.
Thank you for taking time to put this series together , you help people that needed a detailed walk through, much appreciated,.
Excellent video bery helpful as I am now working with SR
Thank you so much for taking the time to make this very detailed tutorial! Absolutely invaluable!
Thank you for the kind words. I'm glad you found it helpful.
amawing videos. i watched both part1 and part 2 and for someone who had no idea how the drivepool and SnapRaid are used i am quite confident i can take care of whatever i need now. thank you so much!
No problem. Thank you for the kind words. Glad it helped!
Hello, I’m a VideoMaker, I had 3 disk failures this year alone, so I’m looking for a repair from these occurrences, I think I’ll go with SnapRaid, also thanks to your really really clear explanations. Thank you!
You are amazing, thanks again!!
Well made video, thanks. Acts as a good checklist for even experienced users. I tried Elucidate GUI but it doesnt seem to like me or the idea of data disks including Poolpart (mine are c:\Mounts\Disk1\PoolPart-nnnnnnnn and c:\Mounts\Disk2\PoolPart-nnnnnnnn etc as I dont want drive letters if I am storing files via the pool)
I'm not familiar with Elucidate, but I may give it a look. Seems there should be a way to edit the config file for your mount points? Seems like an oversight if that's not possible via that GUI. Author may offer some suggestions if you bring it to their attention.
Thank you so much for these very helpful videos! I don't see the Part 3 that you mention at the end of this video. Do you still plan to make one?
I did say that, didn't I? LOL. I don't have it planned at the moment.
Thank you for making the videos on using SnapRAID and DrivePool. I've been using both programs for a quite a few years in the manner you describe.
I use multiple parity drives, but I know it is still recommended when deleting or replacing files to move them outside the protected array and only delete after the next sync. I saw you mention this in a Reddit post regarding "parity hole", and the SnapRAID FAQ states:
"A way to be always safe, is to don't delete files, but move them to another directory in the same disk, but outside the directory tree checked by SnapRAID. Then you can run the "sync" command and only after its completion really delete the files."
I'm confused by the FAQ statement "another directory IN THE SAME DISK, but outside the directory tree checked by SnapRAID". I can make a folder on each data drive outside the PoolPart folder, but using DrivePool I wouldn't know on which physical disk the file I'm moving resides.
Can you clarify? Also did you ever produce a Part 3 discussing "parity hole"?
I've had several inquiries about Parity Hole part 3 so I may make that video soon then.
Regarding the files outside folders protected by snapraid. Sorry for confusion. It doesn't need to be on the same disk. It just needs to be somewhere that SnapRAID isn't protecting. You can even put it on a disk or folder that is protected by snapraid and exclude the "deleted files" folder in the snapraid config file. Or you could store them on another disk altogether. Once you sync, then you can delete the contents in the folder of "deleted files".
The whole idea behind it is to move "deleted" files to another location not protected by snapraid. If your snapraid rebuild fails or a disk fails before the next sync, then you can point to that folder of "deleted" files or just move them back to their original location so it can use those files in the calculation to rebuild the data.
Drivepool does have the option to specify which folders exist on which disks, so you could go that route if desired.
Thanks. I was really scratching my head over the "another directory IN THE SAME DISK, but outside the directory tree checked by SnapRAID" wording on the SnapRAID FAQ. I wonder why he wrote it like that.
Hi, love your videos on Stablebit Drivepool and Snapriad. I heard that Drivepool will automatically transfer files from a failing drive to other drives in the pool with space on them. If that happens, what is the process for adding a new drive and what commands should I use for Snapraid to get everything in sync and running smoothly again?
Thanks for the feedback and question. If a disk does fail and data evacuated to other drives in the pool, I would disable any scheduled SnapRAID sync or scrub operations immediately.
Once data is safely evacuated, remove the failing disk from the pool in Drivepool UI. Shut down and replace the failing disk. Power on, add the new disk to the pool in the DriverPool UI, then set Drivepool to rebalance the pool.
When the balance is complete, disable Drivepool services. Update the SnapRAID config file with the new disk info, however, if using same drive letter or mount point it shouldn't be needed.
Then just run a new "snapraid sync" command. It will take a lot longer because when Drivepool rebalanced the data, it will have changed the location of a lot of files. The ".content" file on the new disk will be regenerated automatically if missing as well if assigned in SnapRAID config file.
@@htwingnut Thanks for the detailed reply!