Lacie 131018 User Manual - Page 198

Symptom, Reason, Solution

Page 198 highlights

StorView RAID Module Symptom Reason Solution Lost communication Service is hung. with the RAID Controllers.(continued) On Linux system access the process viewer and stop the StorView Process. Restart the process and click the Rescan button on the StorView Main screen. Hot spare not automatically starting when drive failure occurs in a redundant array in which a global or dedicated hot spare is defined. The Auto Rebuild option is not Open the Controller Information enabled in the Controller Parameters. window (click the Controller icon), Hot spare disk drive is too small to be place a check mark in the box by used for the drive replacement. clicking the check box on the Auto Waiting for a valid replacement drive Rebuild parameter. to be inserted. Ensure that the disk drive defined as a hot spare is equal to or greater than the size of the drive members of the arrays. Auto Rebuild is not selected and no hot spare drive is assigned, but Auto Hot Spare is enabled. The array will begin rebuilding once a valid replacement drive is inserted in the drive slot of the failed drive. Consistently occurring time out errors when the browser window is open. Host HBA parameter settings are not configured for best performance optimization. Access your Host HBA settings and make the following changes: Execution Throttle Improve general I/O performance by allowing more commands on the fibre bus. Do this by changing your host bus adapter's execution throttle parameter to 256. Scatter/Gather (Microsoft Windows) Increase the general I/O performance by allowing larger data transfers. Do this by editing the "MaximumSGList" parameter in the register. The recommended hexadecimal value is "ff." The path is: HKEY_LOCAL_MACHINE/System/ CurrentControlSet/Services//Parameters/Device/. Shared Memory Error is displayed. The CGI script manager may have not This may occur when heavy I/O is released a segment of shared happening at the same time you are memory. accessing StorView. If this occurs you will need to stop and then restart the StorView Server service. 190

  • 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
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214

StorView RAID Module
190
Lost communication
with the RAID
Controllers.(continued)
Service is hung.
On Linux system access the process
viewer and stop the StorView
Process. Restart the process and click
the Rescan button on the StorView
Main screen.
Hot spare not
automatically starting
when drive failure
occurs in a redundant
array in which a global
or dedicated hot spare
is defined.
The Auto Rebuild option is not
enabled in the Controller Parameters.
Hot spare disk drive is too small to be
used for the drive replacement.
Waiting for a valid replacement drive
to be inserted.
Open the Controller Information
window (click the Controller icon),
place a check mark in the box by
clicking the check box on the Auto
Rebuild parameter.
Ensure that the disk drive defined as a
hot spare is equal to or greater than
the size of the drive members of the
arrays.
Auto Rebuild is not selected and no
hot spare drive is assigned, but Auto
Hot Spare is enabled. The array will
begin rebuilding once a valid
replacement drive is inserted in the
drive slot of the failed drive.
Consistently occurring
time out errors when
the browser window is
open.
Host HBA parameter settings are not
configured for best performance
optimization.
Access your Host HBA settings and
make the following changes:
Execution Throttle
Improve general I/O performance by
allowing more commands on the fibre
bus. Do this by changing your host
bus adapter’s execution throttle
parameter to 256.
Scatter/Gather
(Microsoft Windows) Increase the
general I/O performance by allowing
larger data transfers. Do this by
editing the “MaximumSGList”
parameter in the register. The
recommended hexadecimal value is
“ff.” The path is:
HKEY_LOCAL_MACHINE/System/
CurrentControlSet/Services/<name of
HBA driver>/Parameters/Device/.
Shared Memory Error
is displayed.
The CGI script manager may have not
released a segment of shared
memory.
This may occur when heavy I/O is
happening at the same time you are
accessing StorView. If this occurs you
will need to stop and then restart the
StorView Server service.
Symptom
Reason
Solution