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

Document Information

Preface

Product Information Web Site

Related Books

About This Documentation (PDF and HTML)

Documentation Comments

Change History

Overview of the Sun Blade Storage Module M2 Product Notes

Supported Firmware, Hardware and Software

Storage Module Firmware Release History

Supported Hardware

Supported Operating Systems

Integrated Lights Out Manager (ILOM)

Get Software and Firmware Downloads

Hardware Issues

Hardware Current Issues

Hardware Fixed Issues

Solaris Operating System Issues

Solaris Operating System Current Issues

Disk Fault and Ready-to-Remove LEDs Do Not Work in Oracle Solaris 10 (6926642)

stmsboot Fails to Map Root Device After a Fresh OS Install (6931924)

Using stmsboot -d to Disable MPxIO Can Cause the System to Not Reboot Successfully (6923599)

Changes in Drive Physical Configuration Causes the Solaris format Utility to Hang (6890270, 6930996)

Removal of Devices Breaks mpathadm in Solaris (6908971, 6919439)

cfgadm -c unconfigure Fails if Path Specified is to an MPXIO Enabled Device (6948701)

Command for Creating RAID 10 Volume Not Named Correctly (6943131)

Storage Module Disk Ready-to-Remove LED Does Not Work Using cfgadm (6946124)

Linux Operating System Issues

Linux Operating System Current Issues

Using stmsboot -d to Disable MPxIO Can Cause the System to Not Reboot Successfully (6923599)

When a Sun Blade Storage Module M2 is connected through the chassis to a supported Sun Blade server module using a Sun Storage 6Gb SAS REM HBA (SGX-SAS6-REM-Z), if you use "stmsboot -d" to disable MPxIO, the system cannot be rebooted successfully. The standby path is used as the boot path and you will not be able to mount the root filesystem. The recovery instruction to a previous STMS configuration will be printed on the console. This includes the root device name. The instructions reside in file /etc/mpxio/recover_instructions.

Workaround

If you run into this issue, do the following:

  1. Boot from another boot device:

    • boot net

      —or—

    • CD/DVD

      —or—

    • Another disk which has the right OS image on it

  2. Use fsck access your root device and then mount your root device to a directory (for example: /mnt).

  3. Now you can restore the mpt_sas.conf and vfstab files using the cp command, and then use /usr/sbin/svccfg to recover.

    A sequence of sample commands are shown below, but remember that the timestamps are used for the backup files. Yours will be different. These are in the recovery instruction file and will be printed on the console.

    # cp /mnt/etc/mpxio/mpt_sas.conf.disable.2010_05_07_10_12 /mnt/kernel/drv/mpt_sas.conf
    # cp /mnt/etc/mpxio/vfstab.disable.2010_05_07_10_12 /mnt/etc/vfstab
    # /usr/sbin/svccfg -f /mnt/etc/mpxio/svccfg_recover
    # bootadm update-archive -R /mnt