SAS RAID module (43W3584) / ensure blade boots local disk/device - IBM BladeCenter S

Resolving The Problem

Source

RETAIN tip: H195405

Symptom

While attempting to install an Operating System (OS) on a blade, the incorrect device may get inadvertently selected when there is an existing Logical Unit Number (LUN) mapped to the same blade.

- OR -

The user wants the blade server to boot from its local drive, but the server keeps attempting to boot from drives attached to the IBM BladeCenter S SAS RAID Controller Module, Option 43W3584.

Affected configurations

The system may be any of the following IBM servers:

• BladeCenter S, Type 1948, any model
• BladeCenter S, Type 8886, any model

The system is configured with one or more of the following IBM Options:

• IBM BladeCenter S SAS RAID Controller Module, Option 43W3584

This tip is not software specific.

The system has the symptom described above.

Workaround

Perform either one of the following two (2) options:

Option 1:

The blade server Basic Input/Output System (BIOS) boot information must be changed to make this work.

If the blade is not able to find the OS because the blade is attempting to boot from the Serial Attached SCSI (SAS) Redundant Array of Independent Disks (RAID) Controller Module, the user will need to modify the blade BIOS by completing the following steps:

1. Reboot the blade.
2. Select F1 to enter the Configuration/Setup:
   
   For example (bootup screen):
   
   Press F1 for Configuration/Setup
   Press F2 for Diagnostics
   Press F12 for Boot Device Selection Menu
   
   
3. Enter the Devices and I/O ports section.
4. Ensure that the system board SAS is "Enabled".
5. Save the changes.
6. Reboot the blade.
7. Press Ctrl+C when the SAS BIOS has surfaced.
   
   For example (bootup screen):
   
   LSI Logic Corp. MPT IME BIOS
   Copyright 1995-2003 LSI Logic Corp
   MPTBIOS-IME-5.04.07
   I Build
   
   Press Ctrl+C to start LSI Logic Setup Utility...
   
   
8. Ensure that the "internal" SAS boot device has been set to "boot order 0".
9. Save the changes.
10. Reboot the blade.

Option 2:

If installing a new OS to a local drive in a blade, all external LUNs need to be unmapped during the OS installation. If the OS installation is to an external SAS drive array, there should only be one mapped path to LUN 0. LUN 0 is the LUN required for the OS installation and there should only be a single path established. Once the OS installation is complete, the additional LUNs and paths may be established.