Jump to content
Covecube Inc.

happimeal

Members
  • Content Count

    10
  • Joined

  • Last visited

  1. So today I added two 120GB SSD's to my system. I added them to my pool, selected them as SSD drives, turned off all of the other balancers, yet when I copy files to my drivepool, I can watch in the Drivepool interface, the files just copy to my archive drives and never even touch the SSD's? Update: I think I got this working, I had removed the drive letters from the drives in Disk Management and after giving them a drive letter , it seems to be working. I did have another question though, I dont like to have a lot of drive letter cluttering up my explorer, so I created a pool with the 2 ssd's and added them to my main pool, removed the drive letters from the individual drives so now the only drive that shows is the "pooled" ssd cache drives. I know I have read that you really should be using 2 ssd's for this to work well, and while I do have 2 ssd's , they now look like 1 to DrivePool. Will that matter?
  2. @exterrestris hey, so I got a couple extra ssd's, just wondering the advantages of making them there own pool, but more specifically, making them part of the main pool, why not just leave them out of the main pool?
  3. So, i setup the snapraid-runner powershell script today, however I am getting a couple weird errors, and was hoping someone who has used this would have any idea how to fix it. First error is this, it still runs, just wondering what variable or whatever is not set to give me this error: Does anyone else use this, or have any idea what these errors mean? You cannot call a method on a null-valued expression. At D:\snapraidhelper\snapraid-helper.ps1:621 char:3 + $config[$line[0]] = $line[1].TrimEnd() + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [], RuntimeException + FullyQualifiedErrorId : InvokeMethodOnNull Second is i/o errors on disks its trying to check, the disk throwing the errors is the actual Drivepool Volume, which it should not be checking, disk 9 in disk management is the actual pooled volume. Active code page: 65001 Transcript started, output file is d:\SnapRAID\SnapRAID.log ---------------------------------------- Checking for Disk issues in Eventlog at 09/13/2019 12:30:36 ---------------------------------------- TimeGenerated,EntryType,Source,Message 09/13/2019 10:04:05,Warning,disk,The IO operation at logical block address 0x1 for Disk 9 (PDO name: \Device\0000003e) was retried. 09/13/2019 10:04:05,Warning,disk,The IO operation at logical block address 0x21 for Disk 9 (PDO name: \Device\0000003e) was retried. 09/13/2019 10:04:05,Warning,disk,The IO operation at logical block address 0x11 for Disk 9 (PDO name: \Device\0000003e) was retried. Any help would be greatly appreciated. Thanks
  4. happimeal

    Missing .covefs

    I noticed during my first snapraid sync that i got the warnings about the .covefs directory on 3 out of my 4 drives, so I peeked into the poolpart directory that did not give a warning and noticed the hidden .covefs folder is missing, is this ok?
  5. So I ran snapraid sync for the first time today, and i was a little troubled with the output, I thought the information in the poolpart directories is what is was supposed to be protecting, the output below seems to show its going to ignore those directories, does this look normal for a first sync? Also, not sure why it didn't ignore the special system poolpart directory on d3? Loading state from Q:/snapraidmounts/Data/d3/snapraid.content... WARNING! Content file 'Q:/snapraidmounts/Data/d3/snapraid.content' not found, trying with another copy... Loading state from Q:/snapraidmounts/Data/d4/snapraid.content... No content file found. Assuming empty. Scanning disk d1... WARNING! Ignoring special 'system-directory' file 'Q:/snapraidmounts/Data/d1/PoolPart.9bb7d5be-8a2d-42eb-b0a0-2e415a787370/.covefs' Scanning disk d2... WARNING! Ignoring special 'system-directory' file 'Q:/snapraidmounts/Data/d2/PoolPart.b91ae7a7-9156-4803-9073-43fe3785f076/.covefs' Scanning disk d3... Scanning disk d4... WARNING! Ignoring special 'system-directory' file 'Q:/snapraidmounts/Data/d4/PoolPart.ec2b1283-f632-4dd1-8969-a88122237186/.covefs' Using 342 MiB of memory for the file-system. Initializing... Resizing... Saving state to Q:/snapraidmounts/Parity/p1/snapraid.content... Saving state to Q:/snapraidmounts/Data/d1/snapraid.content... Saving state to Q:/snapraidmounts/Data/d2/snapraid.content... Saving state to Q:/snapraidmounts/Data/d3/snapraid.content... Saving state to Q:/snapraidmounts/Data/d4/snapraid.content... Verifying Q:/snapraidmounts/Parity/p1/snapraid.content... Verifying Q:/snapraidmounts/Data/d1/snapraid.content... Verifying Q:/snapraidmounts/Data/d2/snapraid.content... Verifying Q:/snapraidmounts/Data/d3/snapraid.content... Verifying Q:/snapraidmounts/Data/d4/snapraid.content...
  6. happimeal

    Content Files

    Just wondering if you can also put the content files in mount points, possibly the same drives you created mount points for the data disks? Like for example, would this work? In this example, the parity drive is its own drive, I am just mounting it to the same drive as the data drive mounts. # 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] ..." parity Q:\snapraidmounts\Parity\p1\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] ..." #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" content Q:\snapraidmounts\Parity\p1\snapraid.content content Q:\snapraidmounts\Data\d1\snapraid.content content Q:\snapraidmounts\Data\d2\snapraid.content content Q:\snapraidmounts\Data\d3\snapraid.content content Q:\snapraidmounts\Data\d4\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" data d1 Q:\snapraidmounts\Data\d1\PoolPart.9bb7d5be-8a2d-42eb-b0a0-2e415a787370 data d2 Q:\snapraidmounts\Data\d2\PoolPart.b91ae7a7-9156-4803-9073-43fe3785f076 data d3 Q:\snapraidmounts\Data\d3\PoolPart.0d01e48b-b40e-45b8-9804-1b1e87e69ed3 data d4 Q:\snapraidmounts\Data\d4\PoolPart.ec2b1283-f632-4dd1-8969-a88122237186 # 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\" exclude *.unrecoverable exclude Thumbs.db exclude \$RECYCLE.BIN exclude \System Volume Information exclude \Program Files\ exclude \Program Files (x86)\ exclude \Windows\
  7. @exterrestris Thank you again for the very well explained answer, this should be a breeze. Appreciate the time typing up such a well explained setup.
  8. Thank you for the amazing and thorough write up, it is thoroughly appreciated, I think I understand all of this, it seems pretty straight forward. Any chance you could post your snapraid.conf file, I would like to see what one looks like with a setup like this? I am also guessing I should have all by balancers unchecked except the SSD and the StableBit Scanner? With them all turned off Drivepool with just equally fill up each drive as files are copied to it by default, correct, which is the behaviour I want, I do not want any duplication across my main pool, as I will have snapraid, and I have backblaze and a local nas backup as well. As far as my settings page, should I have "Do not balance automatically checked" for the behavior I am looking for? Again, thank you!!
  9. Thank you for the amazing and thorough write up, it is thoroughly appreciated, I think I understand all of this, it seems pretty straight forward. Any chance you could post your snapraid.conf file, I would like to see what one looks like with a setup like this? Again, thank you!!
  10. So I am very familiar with using mergerfs and snapraid, just moved my media center from an OMV with unionfs and snapraid setup back to windows. I have drivepool setup with 4 x 4tb hard drives working perfectly. I will be adding a 5tb parity drive and setting up snapraid any day now, just waiting for my drive to get here. In the meantime I do have a backblaze backup and an local backup. My question is, I do not want to have each drive in the pool have to have a drive letter, so can anyone tell me if there is a different way to do this in windows? The plugin for OMV , kinda took care of the parity, content and the configuration file, if its possible to not have each drive have to have a drive letter, does anyone have a snapraid config they could share, and maybe any tips/best practices? Thanks in advance, any help is very appreciated.
×
×
  • Create New...