JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Blade Storage Module M2 Product Documentation
search filter icon
search icon

Document Information

Preface

Product Information Web Site

Related Books

About This Documentation (PDF and HTML)

Documentation Comments

Change History

Hardware Installation

Overview of the Sun Blade Storage Module M2

System Requirements

Installing the Storage Module Into the Chassis

Storage Module Indicators

Assigning and Managing Storage

Product Notes

Overview of the Sun Blade Storage Module M2 Product Notes

Supported Firmware, Hardware and Software

Hardware Issues

Hardware Current Issues

NEM 0 Cannot Be Empty (6956590)

Identifying a Single Disk When There are a Large Number of Virtual Disks Presented to the Host (6930346)

Sun Blade X6270 M2 BIOS Can Only See 24 Drives (6929975)

Storage Module Shows Powered Off When It is Actually Powered On (6823893)

Performing Hot Plug Actions During Sun Blade Zone Manager Configuration Can Cause Timeout Errors (6960734)

Storage Module Drives Might Not Be Listed In the Sun Storage 6Gb SAS REM BIOS Topology Menu (6951183)

REM BIOS Configuration Utility Might Show a Single Path to Dual Path SAS Drives (6981082)

Hardware Fixed Issues

Adding a Sun Blade Storage Module M2 Into an Chassis SAS-2 Domain Might Cause Existing Storage Module Drives to Go Offline (6971532)

Solaris Operating System Issues

Linux Operating System Issues

Administration

Assigning Storage to Hosts

Managing Storage

Performing Maintenance and Hot Plug Actions

Importing Existing Virtual Drives to a Replacement REM

Storage Module Sensors and Indicators

Troubleshooting

Service

Introduction to the Sun Blade Storage Module M2

Maintaining the Sun Blade Storage Module M2

Diagnosing Storage Module Faults

Specifications

Index

Identifying a Single Disk When There are a Large Number of Virtual Disks Presented to the Host (6930346)

If there is a large amount of single volume or multiple virtual disks presented to the host system, it might be difficult to identify the boot disk as seen by the host system BIOS.

Workaround
  1. If your server module REM is a Sun Storage 6Gb SAS REM HBA (SGX-SAS6-REM-Z), do the following:

    1. Allow the system to boot to the HBA MPT BIOS.

    2. When prompted select Ctrl-C to enter the MPT BIOS.

    3. Select the IR HBA from the prompt and press enter.

    4. Select the correct Hard Disk that the OS will be used to load the OS.

    5. Press Alt+B to mark the list as the preferred boot device.

    6. Record the WWN (World Wide Name, also known as SAS ID) from the selected list.

    7. Save the setting and reboot the host system.

    8. Enter the server's system BIOS by pressing F2 during boot.

    9. Select the appropriate boot disk in the Drive Priority list.

    10. Save the settings and reboot the host system.

    11. Load the appropriate OS and identify the boot disk by the recorded WWN.

  2. If your server module REM is a Sun Storage 6Gb SAS REM RAID HBA (SGX-SAS6-R-REM-Z), do the following:

    1. Allow the system to boot to the HBA WebBIOS Setup screen.

    2. When prompted select Ctrl-N to enter WebBIOS.

    3. Use the HBA WebBIOS set up to create the required RAID and Virtual Disk configuration as described in the MegaRAID HBA User's Guide.

    4. Record the Virtual Disk ID and WWN (World Wide Name, also known as SAS ID).

    5. Save the setting and reboot the host system.

    6. Enter the server's system BIOS by pressing F2 during boot.

    7. Select the appropriate boot disk in the Drive Priority list.

    8. Save the settings and reboot the host system.

    9. Load the appropriate OS and identify the boot disk by the recorded WWN.