Jump to content
  • 0

Repairing HDD in pool with SnapRaid


Zammo

Question

One of my data HDD's went today, a 6tb one, I have DrivePool with SnapRaid. I have a single 8tb parity drive. Given my drives are mounted to folders on the C drive and not letters, how do I repair it ? Also once repaired will DrivePool see it as though it is the same drive that was there before ? Will it matter than I synced it 7 days ago and so the other working drives will have newer data ? I presume I just lose everything added the last 7 days only off the drive that broke ?

I have pasted below my SnapRaid config in case it helps. It is the D2 drive that failed. Thanks everyone in advance !!

# 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 C:\Mounts\PARITY1\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] ..."

# 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 C:\SnapRAID\snapraid.content
content C:\Mounts\D1\snapraid.content
content C:\Mounts\D2\snapraid.content
content C:\Mounts\D3\snapraid.content
content C:\Mounts\D4\snapraid.content
content C:\Mounts\D5\snapraid.content
content C:\Mounts\D6\snapraid.content
content C:\Mounts\D7\snapraid.content
content C:\Mounts\D8\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 C:\Mounts\D1\PoolPart.9e511ba4-d2d2-4bff-8ae7-0c5f9fa82209
data d2 C:\Mounts\D2\PoolPart.553ace38-e6ff-463c-8a9a-54a2b0725b30
data d3 C:\Mounts\D3\PoolPart.af703e7a-33f5-46ce-9865-81ea6ed96a87
data d4 C:\Mounts\D4\PoolPart.7424422f-0989-444a-9a5e-40fd4f00980a
data d5 C:\Mounts\D5\PoolPart.a8fb213f-a2de-4b3b-81dc-56a569cb6301
data d6 C:\Mounts\D6\PoolPart.233fe9e1-8151-4cda-88ee-0297350ac92a
data d7 C:\Mounts\D7\PoolPart.9efe5915-5cd0-4bbe-9dd9-716502869531
data d8 C:\Mounts\D8\PoolPart.4247ddb6-c80d-446f-ae20-b7f3cf1b8956

# 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 *.covefs
exclude *.unrecoverable
exclude Thumbs.db
exclude \$RECYCLE.BIN
exclude \System Volume Information
exclude \Program Files\
exclude \Program Files(x86)\
exclude \Program Files (x86)\
exclude \Windows\
exclude \Windows.old\

# 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"
block_size 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"
#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"
autosave 800

# 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:
# RAID -> https://www.smartmontools.org/wiki/Supported_RAID-Controllers
# USB -> https://www.smartmontools.org/wiki/Supported_USB-Devices
#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

 

 

Link to comment
Share on other sites

0 answers to this question

Recommended Posts

There have been no answers to this question yet

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...