Owner's Manual

file:///T|/htdocs/SOFTWARE/smsbu/1.0/en/readme/readme.txt[10/25/2012 1:33:14 PM]
* It is not recommended that you start the system setup
program if any virtual disks are in a failed or degraded state.
Use the RAID controller's firmware utility ("<Ctrl><a>," "<Ctrl><m>,"
or "<Ctrl><c>" during boot) to reset the RAID controller's state.
If an array disk is removed, the firmware utility may indicate
the configuration has changed. Accepting these changes on the
command line may not suffice; enter the firmware utility
and reset the controller.
* On CERC ATA or CERC SATA RAID controller cards, disks that appear
in "Legacy" mode will not be available for RAID configuration in
Systems Build And Updates Utility. If you wish to use any disk that
is in "Legacy" mode as part of a RAID container, you need to use
the RAID controller firmware utility to initialize these disks.
Likewise, if all disks are in "Legacy" mode, then Systems Build
And Updates Utility may fail to configure RAID on the controller.
* The "Server Setup" program might fail if it runs when scrubbing is
active on a RAID virtual disk.
* Systems Build and Update Utility does not identify the boot device
When PERC (4DC/3DC) is in cluster mode and the adapter's BIOS is
disabled. This will put Systems Build and Update Utility in an
infinite "Write Disk signature" and reboot loop. Use Systems
Build and Update Utility to install the operating system
on PERC in a non-cluster mode.
* Systems Build and Update Utility cannot detect the correct
slot number of PCI slots containing Adaptec RAID controllers.
The message "Unknown Slot Number" is displayed.
* On systems with low memory (less than 256 MB) and more than one
RAID controller, Systems Build and Update Utility may fail during
RAID configuration. Install the additional adapters after the
operating system has been installed on the first adapter.
* When using the Custom install script feature, commands which do not
return cause the system to stop responding during booting of Red
Hat Enterprise Linux or while registering components on Windows
installations.
* On SAS 5/IR controller cards, disks that appear in "Foreign" state
will not be available for OS installation in non-RAID mode.
If you wish to use any disk that is in "Foreign"
state for OS installation, clear the physical disks using
"Erase All Physical Disks" feature under System Tools section.
If all disks are in "Foreign" state, Systems Build And Updates
Utility may fail to install OS on the controller in non-RAID mode.
* On a system with SAS 5iR controller cards connected to more
than 2 disks, Systems Build And Updates Utility supports only
"Advanced RAID Configuration." In Advanced mode, it is mandatory
that you select disk with lowest drive ID for RAID configuration.