README.TXT
- While a drive is being cleared, DO NOT try to include it in a
new array. Doing so may cause unpredictable results.
- DO NOT move drives containing an array or volume from one
controller to another while the power is on. Doing so could
cause the loss of the array configuration or data, or both.
Instead, power off both affected controllers, move the drives,
and then restart.
3.2 General Notes
- When displaying information on a physical device, the device,
vendor and model information may be displayed incorrectly.
- During array migration from a RAID 1 or RAID 5 to a RAID 0, if
the original array had a spare drive attached, the resulting
RAID 0 retains the spare drive.
- After building or verifying a leg of a second-level array, the
status of the second-level array is displayed as a "Quick
Initialized" array.
- The Adaptec controller supports only new drives or drives
that have been initialized or low-level formatted.
Attaching used drives could cause problems, including:
o Existing/rebuilding arrays may go off line
o Interrupted rebuilds may continue on the wrong drive
- On motherboard BIOSes supporting BBS, BBS support is usually
enabled on the Adaptec controller. This can cause problems
during restart. WORKAROUND: Disable BBS.
- After using a hot spare to successfully rebuild a redundant
array, information about the hot spare drive may not display
as expected. CLI may continue to display it as a global
spare, but the array will not have a spare attached.
ARC (the BIOS utility) displays the spare attached to the
array as expected.
- Arrays created with stripe sizes greater than 64k cannot be
imported back to earlier firmware releases.
--------------------------------------------------------------------
4. Array Level-Specific Notes
4.1 RAID 10 Notes
- If a RAID-10 is degraded, the BIOS reports a degraded RAID-0
and a degraded RAID-1 instead of degraded RAID-10.
- You cannot change the priority of a RAID-10 verify. Setting
the priority at the start of a verify has no effect. The
priority is still shown as high. Changing the priority of
a running verify on a raid-10 changes the displayed priority
until a rescan is done, then the priority shows as high again.
- A RAID 10 created using the ACU using the CLEAR method shows as
"IMPACTED" until the CLEAR operation is complete. Also, the
drives' statuses are reported as Not Busy, even though the drives
are clearing.
Page 3
(33 Seiten)
(2 Seiten)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern