beautypg.com

Raid mode not supported, Kernel panic after disabling pci devices in rbsu – HP 10 User Manual

Page 39

background image

Troubleshooting 39


information, please refer to advisory

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=1

10&prodSeriesId=3454575&prodTypeId=15351&prodSeriesId=3454575&objectID=c01479945

Workaround—Edit /platform/i86pc/kernel/drv/pcie_pci.conf and add the entry

"pci-hotplug-type=0", then reboot the server.

For Solaris 10 5/08, the issue is fixed with patch 137122-04.

This issue is fixed in Solaris 10 10/08.

RAID mode not supported

Solaris 10 operating system will not deploy on an HP ProLiant BL260c G5 or BL280c G6 blade

server when the SATA controller is configured in RAID mode.

OS releases affected—Solaris 10

Hardware affected— HP ProLiant BL260c G5, BL280c G6

Description—Cannot install SUN Solaris 10 operating system on HP ProLiant when the SATA

controller is configured in RAID mode. Solaris 10 operating system does not have the device

driver support for the SATA Controller in RAID mode.

Workaround—Solaris does not support this controller in RAID mode. Deploy Solaris in IDE

mode.

Kernel Panic after disabling PCI devices in RBSU

Solaris stops responding or halts due to kernel panic when one or more PCI devices have been

disabled using ROM-Based Setup Utility (RBSU).

OS releases affected—All

Servers affected—All supported ProLiant servers

Description—Disabling PCI devices in RBSU might cause Solaris to stop responding, halt due to

kernel panic, or produce other undesirable behavior.

Workaround—Unless otherwise indicated, HP does not support using RBSU to disable PCI

devices while running Solaris. Add-on PCI devices should be removed from the system instead of

disabling them in RBSU.

Network configuration fails during interactive installation

Solaris installation fails during network configuration or Solaris is unable to configure network

interfaces after the post-installation reboot.

OS releases affected—Solaris 10 1/06, 6/06, 11/06, and 5/08

Servers affected—All supported ProLiant servers

Description—There is a known issue with network setup at installation time, and the installation

might fail, or Solaris will be unable to initialize the network after rebooting. This issue occurs if

driver updates (DUs) or installation time updates (ITU), such as the Smart Array driver, are added

during installation.
This issue is not reported if the extra drivers are installed into the miniroot prior to deployment.

Workaround—When prompted during the Solaris installation, select non-networked. After the

installation is complete and the system has rebooted, run sys-unconfig(1M). The system reboots

and the network can be configured properly.

This issue is fixed with Solaris 10 10/08.