Owner's Manual

file:///T|/htdocs/SOFTWARE/smsbu/1_2/en/readme/readme.txt[10/23/2012 1:18:45 PM]
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 Utility may 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
Advanced RAID Configuration. In Advanced mode, it is mandatory that
user select disk with lowest drive ID for RAID configuration.
* When you use Systems Build and Update Utility with a
keyboard-video-monitor (KVM) switch, the GUI may not display due to
incompatibility with the Server Interface PODs (SIPs) used. To view
the GUI, connect your monitor directly to your system or change the
SIP.
* The "View Hardware" option in Systems Build and Update Utility
lists the L2 cache size as 4 MB for 5300-series processors running on
Red Hat Enterprise Linux version 4 operating system; however, the
"BIOS SETUP" option lists the L2 cache size as 8 MB.
This is because Linux "reads" a 5300-series processor in terms of
per-logical-CPU-thread. Hence, each logical thread (each set) would
still have access to only 4 MB cache, and so it is reported as such
by the "View Hardware" option.
The "BIOS SETUP" option "reads" the 5300-series processor as a
two-set package, each with a 4 MB L2 cache. In each set, the two
cores share the 4 MB cache. Hence, this option reports a total L2
cache size of 8 MB.
Therefore, the different L2 cache sizes listed are due to different