- On certain versions of Linux, you may see messages concerning font
conversion errors. Font configuration under X-Windows is a known
JVM problem. It does not affect the proper operation of the
Adaptec Storage Manager software. To suppress these messages,
add the following line to your .Xdefaults file:
stringConversionWarnings: False
- On rare occasions, the online help system may generate a Java
exception. This is due to a known problem in the HTML rendering
section of JFC/Swing.
--------------------------------------------------------------------
5. RAID Level-Specific Notes
5.1 RAID 1 and RAID 5 Notes
- During pool migration from a RAID 1 or RAID 5 to a RAID 0, if
the original pool had a spare drive attached, the resulting
RAID 0 retains the spare drive.
5.2 RAID 10 Notes
- 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.
- Performing a Verify or Verify/Fix on an RAID 10 displays the
same message text in the event log, "Build/Verify started on
second level pool of pool 'Pool_0.'" You may see the message
three times for a Verify, but only once for a Verify/Fix.
- During a migration from a RAID 0 to any redundant pool, like
RAID 5 or 10, Adaptec Storage Manager shows the status as
"Degraded Reconfiguring" for a moment, then the status changes
to "Reconfiguring." The "Degraded" status does not appear in
the event log.
5.3 RAID x0 Notes
- After building or verifying a leg of a second-level pool, the
status of the second-level pool is displayed as a "Quick
Initialized" pool.
--------------------------------------------------------------------
6. ARCCONF Notes
- ARCCONF requires the latest drivers to operate properly. Failure
to update the drivers may result in the console hanging after
a command is issued.
- With Linux kernel versions 2.4 and 2.6, the ARCCONF
DELETE <logical_drive> command may fail with a Kernel Oops
error message. Even though the drives are removed from the