User Manual
BC4000 Series RAID Controllers
02/13/06
B ro ad c om C o r p or at i on
Document
BC4000-UM100-R
Continue Booting from the BIOS
Page 59
3.
Do one of the following:
•
If you do not want to boot from an array, highlight
Toggle INT13 Installation
using the arrow keys, and
then press
Enter
to change the setting to
Disabled
. (Broadcom recommends disabling INT13 only if you
want to boot from another device and leaving the rest of the options enabled.)
Or
•
To turn off warnings due to critical arrays when booting, highlight
Toggle Pause if Critical
, and then press
Enter
to change the setting to
Disabled
.
Or
•
To turn off warnings due to offline arrays when booting, highlight
Toggle Pause if Offline
, and then press
Enter
to change the setting to
Disabled
.
Or
•
To turn off warnings due to controller configuration errors when booting, highlight
Toggle Pause if Error
,
and then press
Enter
to change the setting to
Disabled
(these warnings include errors generated when
the license key is not found or is corrupted, or when the license level does not match on all controllers in
the system and the lowest level found is used).
Or
•
To allow the BC4000 Series RAID controller to work with newer Linux kernels that load the libata driver,
highlight
Toggle Legacy Board ID
, and then press
Enter
to change the setting to
Disabled
.
When the libata driver is loaded by these newer Linux kernels, beginning with some errata kernels for
Fedora Core 2 and all kernels for Fedora Core 3, the BC4000 Series RAID controller is recognized as a
simple SATA controller and is taken over by the operating system. This makes it impossible to be used as
a RAID controller. If this problem occurs on your system, any previously created arrays do not appear as
arrays, but only as a group of individual disks.
By turning off the “legacy” ID used by all BC4000 Series RAID controllers, the newer Linux kernels can
recognize the BC445X or BC485X controller as a RAID controller, provided that a RAIDCore driver that is
version 1.4 or later is used (drivers that are version 1.3 or earlier will not be able to recognize the RAIDCore
controller). All Linux systems will work properly with the legacy board ID disabled. It can be enabled and
disabled as needed, so if you encounter any problems after disabling the legacy ID, it can be re-enabled
to get back to a working system.
Or
•
To limit the number of disks that can spin up at the same time, reducing power demands by the system,
highlight
Set Staggered Spinup Count
, and then press
Enter
. Using the arrow keys, specify the number
of disks that should be allowed to simultaneously spin up, and then press
Enter
again.
C
ONTINUE
B
OOTING
FROM
THE
BIOS
After you have created arrays, you can continue booting the system from the point where the RAIDCore BIOS
was entered. To resume the boot, highlight
Continue to Boot
in the
Main
menu, and then press
Enter
. No
reboot is required.
Note:
If the system has a BC4000 Series RAID controller board with legacy board ID disabled and
another board with legacy board ID enabled is added, the system may experience unpredictable
behavior due to the mismatch in legacy board ID settings. To clear this condition, go to the
Toggle
Legacy Board ID
option and change it. This changes the ID on all the boards. Depending on how
you want this option set, you may have to set it once (triggering an automatic reboot), and then
change it back to the setting you want (triggering a second reboot).
