Adaptec 2410SA User Guide - Page 87

Array#&lt, > Status, BUILD/VERIFY <n&gt, CLEAR <n&gt, BUILD/VERIFY/CLEAR FAILED - fails verify

Get Adaptec 2410SA - Serial ATA RAID Controller PDF manuals and user guides
UPC - 760884142103
View all Adaptec 2410SA manuals
Add to My Manuals
Save this manual to your list of manuals

Page 87 highlights

DOS Utilities The ACU provides a way to do this. When you use record mode to record a controller's configuration and you specify a log file (/L switch), the ACU writes build/verify and clear status information about each array in the configuration to the log file. An application or batch file can then parse the resulting log file to determine whether an array's build/verify or clear is complete, in progress (a percentage of the task completed), or failed. The following example shows a log file of a recorded configuration consisting of three arrays: Reading array information ...Passed Scanning for Drives ...Passed Reading cache values...Passed Array #0 Status : OK Array #1 Status : BUILD/VERIFY 30% Array #2 Status : BUILD/VERIFY/CLEAR FAILED Each status line consists of the prefix: Array# Status : where is the array ID, followed by the status. The possible status values are as follows: I OK Indicates a nonredundant array (no build required) or a redundant array whose build task completed successfully. I BUILD/VERIFY % CLEAR % Indicates a build/verify (or clear) is currently in progress, where is the percentage of the operation that is complete. The percentage is an integer between 0 and 99, inclusive. I BUILD/VERIFY/CLEAR FAILED Indicates a build/verify or clear that did not complete due to a data error or other unexpected problem. When a build/verify task runs on a multilevel array, the build/verify occurs on the child arrays and not on the parent array. Consequently, the parent task always indicates 0 percent and the child task indicates 0 percent to 100 percent. When a clear task runs on a multilevel array, the clearing occurs on the parent array and not on the child arrays. Consequently, the parent task indicates 0 percent to 100 percent and the child tasks always indicates 0 percent. B-23

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
B-23
DOS Utilities
The ACU provides a way to do this. When you use record mode to
record a controller
’
s configuration and you specify a log file (
/L
switch), the ACU writes build/verify and clear status information
about each array in the configuration to the log file. An application
or batch file can then parse the resulting log file to determine
whether an array
’
s build/verify or clear is complete, in progress (a
percentage of the task completed), or failed.
The following example shows a log file of a recorded configuration
consisting of three arrays:
Reading array information ...Passed
Scanning for Drives ...Passed
Reading cache values...Passed
Array #0 Status : OK
Array #1 Status : BUILD/VERIFY 30%
Array #2 Status : BUILD/VERIFY/CLEAR FAILED
Each status line consists of the prefix:
Array#<
n
> Status :
where
<n>
is the array ID, followed by the status. The possible
status values are as follows:
■
OK
Indicates a nonredundant array (no build required) or a
redundant array whose build task completed successfully.
■
BUILD/VERIFY <n>%
CLEAR <n>%
Indicates a build/verify (or clear) is currently in progress,
where
<n>
is the percentage of the operation that is complete.
The percentage is an integer between 0 and 99, inclusive.
■
BUILD/VERIFY/CLEAR FAILED
Indicates a build/verify or clear that did not complete due to a
data error or other unexpected problem.
When a build/verify task runs on a multilevel array, the build/verify
occurs on the child arrays and not on the parent array. Consequently,
the parent task always indicates 0 percent and the child task indicates
0 percent to 100 percent. When a clear task runs on a multilevel array,
the clearing occurs on the parent array and not on the child arrays.
Consequently, the parent task indicates 0 percent to 100 percent and
the child tasks always indicates 0 percent.