mirror of
https://github.com/amadvance/snapraid.git
synced 2026-10-26 02:49:02 -04:00
More documentation about the new "smart" command
This commit is contained in:
Andrea Mazzoleni
parent
f0fc3a8889
commit
f935c8f828
3 changed files with 81 additions and 15 deletions
48
snapraid.1
48
snapraid.1
|
|
@ -50,7 +50,11 @@ snapraid [\-c, \-\-conf CONFIG]
|
|||
.PD 0
|
||||
.PP
|
||||
.PD
|
||||
status|smart|up|down|diff|sync|scrub|fix|check|list|dup|up|down|pool|devices|rehash
|
||||
status|smart|up|down|diff|sync|scrub|fix|check|list|dup
|
||||
.PD 0
|
||||
.PP
|
||||
.PD
|
||||
|up|down|pool|devices|rehash
|
||||
.PD 0
|
||||
.PP
|
||||
.PD
|
||||
|
|
@ -653,13 +657,39 @@ Nothing is modified.
|
|||
Prints a SMART report of all the disks of the array.
|
||||
.PP
|
||||
It includes an estimation of the probability of failure in the next
|
||||
year of each disk allowing to plan maintenance replacements of the
|
||||
disks that show suspicious attributes.
|
||||
year allowing to plan maintenance replacements of the disks that show
|
||||
suspicious attributes.
|
||||
.PP
|
||||
If a SMART attribute reports that a disk is failing, \[dq]FAIL\[dq] or \[dq]PREFAIL\[dq]
|
||||
is printed for that disk, and SnapRAID returns with an error.
|
||||
This probability estimation obtained correlating the SMART attributes
|
||||
of the disks, with the Backblaze data available at:
|
||||
.PP
|
||||
.RS 4
|
||||
https://www.backblaze.com/hard\-drive\-test\-data.html
|
||||
.PD 0
|
||||
.PP
|
||||
.PD
|
||||
.RE
|
||||
.PP
|
||||
If SMART reports that a disk is failing, \[dq]FAIL\[dq] or \[dq]PREFAIL\[dq] is printed
|
||||
for that disk, and SnapRAID returns with an error.
|
||||
In this case an immediate replacement of the disk is highly recommended.
|
||||
.PP
|
||||
Other possible strings are:
|
||||
.RS 4
|
||||
.PD 0
|
||||
.HP 4
|
||||
.I logfail
|
||||
In the past some attributes were lower than
|
||||
the threshold.
|
||||
.HP 4
|
||||
.I logerr
|
||||
The device error log contains errors.
|
||||
.HP 4
|
||||
.I selferr
|
||||
The device self\-test log contains errors.
|
||||
.PD
|
||||
.RE
|
||||
.PP
|
||||
If the \-v, \-\-verbose option is specified a deeper statistical analysis
|
||||
is provided. This analysis can help you to decide if you need more
|
||||
or less parity.
|
||||
|
|
@ -1336,6 +1366,10 @@ smartctl parity \-d areca,1/1 /dev/sg0
|
|||
.PD 0
|
||||
.PP
|
||||
.PD
|
||||
smartctl 2\-parity \-d areca,2/1 /dev/sg0
|
||||
.PD 0
|
||||
.PP
|
||||
.PD
|
||||
.RE
|
||||
.PP
|
||||
An example of a typical configuration for Windows is:
|
||||
|
|
@ -1389,6 +1423,10 @@ smartctl parity \-d areca,1/1 /dev/arcmsr0
|
|||
.PD 0
|
||||
.PP
|
||||
.PD
|
||||
smartctl 2\-parity \-d areca,2/1 /dev/arcmsr0
|
||||
.PD 0
|
||||
.PP
|
||||
.PD
|
||||
.RE
|
||||
.SH PATTERN
|
||||
Patterns are used to select a subset of files to exclude or include in
|
||||
|
|
|
|||
24
snapraid.d
24
snapraid.d
|
|
@ -14,7 +14,8 @@ Synopsis
|
|||
: [-S, --start BLKSTART] [-B, --count BLKCOUNT]
|
||||
: [-L, --error-limit NUMBER]
|
||||
: [-v, --verbose] [-q, --quiet]
|
||||
: status|smart|up|down|diff|sync|scrub|fix|check|list|dup|up|down|pool|devices|rehash
|
||||
: status|smart|up|down|diff|sync|scrub|fix|check|list|dup
|
||||
: |up|down|pool|devices|rehash
|
||||
|
||||
:snapraid [-V, --version] [-H, --help] [-C, --gen-conf CONTENT]
|
||||
|
||||
|
|
@ -380,13 +381,24 @@ Commands
|
|||
Prints a SMART report of all the disks of the array.
|
||||
|
||||
It includes an estimation of the probability of failure in the next
|
||||
year of each disk allowing to plan maintenance replacements of the
|
||||
disks that show suspicious attributes.
|
||||
year allowing to plan maintenance replacements of the disks that show
|
||||
suspicious attributes.
|
||||
|
||||
If a SMART attribute reports that a disk is failing, "FAIL" or "PREFAIL"
|
||||
is printed for that disk, and SnapRAID returns with an error.
|
||||
This probability estimation obtained correlating the SMART attributes
|
||||
of the disks, with the Backblaze data available at:
|
||||
|
||||
:https://www.backblaze.com/hard-drive-test-data.html
|
||||
|
||||
If SMART reports that a disk is failing, "FAIL" or "PREFAIL" is printed
|
||||
for that disk, and SnapRAID returns with an error.
|
||||
In this case an immediate replacement of the disk is highly recommended.
|
||||
|
||||
Other possible strings are:
|
||||
logfail - In the past some attributes were lower than
|
||||
the threshold.
|
||||
logerr - The device error log contains errors.
|
||||
selferr - The device self-test log contains errors.
|
||||
|
||||
If the -v, --verbose option is specified a deeper statistical analysis
|
||||
is provided. This analysis can help you to decide if you need more
|
||||
or less parity.
|
||||
|
|
@ -1036,6 +1048,7 @@ Configuration
|
|||
:smartctl d1 -d sat %s
|
||||
:smartctl d2 -d usbjmicron %s
|
||||
:smartctl parity -d areca,1/1 /dev/sg0
|
||||
:smartctl 2-parity -d areca,2/1 /dev/sg0
|
||||
|
||||
An example of a typical configuration for Windows is:
|
||||
|
||||
|
|
@ -1051,6 +1064,7 @@ Configuration
|
|||
: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
|
||||
|
||||
Pattern
|
||||
Patterns are used to select a subset of files to exclude or include in
|
||||
|
|
|
|||
24
snapraid.txt
24
snapraid.txt
|
|
@ -18,7 +18,8 @@ snapraid [-c, --conf CONFIG]
|
|||
[-S, --start BLKSTART] [-B, --count BLKCOUNT]
|
||||
[-L, --error-limit NUMBER]
|
||||
[-v, --verbose] [-q, --quiet]
|
||||
status|smart|up|down|diff|sync|scrub|fix|check|list|dup|up|down|pool|devices|rehash
|
||||
status|smart|up|down|diff|sync|scrub|fix|check|list|dup
|
||||
|up|down|pool|devices|rehash
|
||||
|
||||
snapraid [-V, --version] [-H, --help] [-C, --gen-conf CONTENT]
|
||||
|
||||
|
|
@ -408,13 +409,24 @@ Nothing is modified.
|
|||
Prints a SMART report of all the disks of the array.
|
||||
|
||||
It includes an estimation of the probability of failure in the next
|
||||
year of each disk allowing to plan maintenance replacements of the
|
||||
disks that show suspicious attributes.
|
||||
year allowing to plan maintenance replacements of the disks that show
|
||||
suspicious attributes.
|
||||
|
||||
If a SMART attribute reports that a disk is failing, "FAIL" or "PREFAIL"
|
||||
is printed for that disk, and SnapRAID returns with an error.
|
||||
This probability estimation obtained correlating the SMART attributes
|
||||
of the disks, with the Backblaze data available at:
|
||||
|
||||
https://www.backblaze.com/hard-drive-test-data.html
|
||||
|
||||
If SMART reports that a disk is failing, "FAIL" or "PREFAIL" is printed
|
||||
for that disk, and SnapRAID returns with an error.
|
||||
In this case an immediate replacement of the disk is highly recommended.
|
||||
|
||||
Other possible strings are:
|
||||
logfail - In the past some attributes were lower than
|
||||
the threshold.
|
||||
logerr - The device error log contains errors.
|
||||
selferr - The device self-test log contains errors.
|
||||
|
||||
If the -v, --verbose option is specified a deeper statistical analysis
|
||||
is provided. This analysis can help you to decide if you need more
|
||||
or less parity.
|
||||
|
|
@ -1124,6 +1136,7 @@ An example of a typical configuration for Unix is:
|
|||
smartctl d1 -d sat %s
|
||||
smartctl d2 -d usbjmicron %s
|
||||
smartctl parity -d areca,1/1 /dev/sg0
|
||||
smartctl 2-parity -d areca,2/1 /dev/sg0
|
||||
|
||||
An example of a typical configuration for Windows is:
|
||||
|
||||
|
|
@ -1139,6 +1152,7 @@ An example of a typical configuration for Windows is:
|
|||
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
|
||||
|
||||
|
||||
8 PATTERN
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue