Owner's Manual

file:///T|/htdocs/SOFTWARE/smsbu/1_1/en/readme/readme.txt[10/23/2012 1:20:19 PM]
Systems Build and Update Utility will always use the controller
listed first in the BIOS boot order list. If you want to use a
particular controller for the operating system, you must go to
the BIOS setup (F2 on boot) and set up the given controller as the
first boot device.
* Systems Build and Update Utility does not support the configuration
of partitions or the installation of operating systems on systems
with PERC 2/SC, PERC 2/DC, or PERC 2/QC controllers or any
type of Fibre Channel storage adapter.
* It is not recommended to start the server setup
program if any virtual disks are in a failed or degraded state.
Use the RAID controller's firmware utility (<Ctrl><A> or <Ctrl><M>
or <Ctrl><R> 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 be enough; enter the firmware utility
and reset 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, 6/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 Update
Utilitymay fail to install OS on the controller in non-RAID mode.
* On system with SAS 5/iR and/or SAS 6/iR controller cards connected to more
than 2 disks, Systems Build and Update Utility supports only