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

Enabling MPXIO manually on a newly installed system with a Sun Storage 6Gb SAS REM HBA (SGX-SAS6-REM-Z) will result in error messages. When stmsboot -e is manually run to enable MPxIO, the following harmless messages will print during the booting process:

Error: Your root device is not mapped.

In order to prevent or eliminate the message, perform the following workaround.

Workaround

1. Login as root user on the system displaying the message.

2. Run stmsboot -e to enable multipathing. For example:

   host-1-root@[/]>stmsboot -e
   
   WARNING: stmsboot operates on each supported multipath-capable controller
            detected in a host. In your system, these controllers are
   
   /pci@1f,700000/pci@0/pci@2/pci@0/pci@8/LSILogic,sas@1
   /pci@1f,700000/pci@0/pci@9/LSI,sas@0/iport@f0
   
   If you do NOT wish to operate on these controllers, please quit stmsboot
   and re-invoke with -D { fp | mpt | mpt_sas} to specify which controllers 
   you wish to modify your multipathing configuration for.
   
   Do you wish to continue? [y/n] (default: y) y

3. Reboot the system. For example:

   host-1-root@[/]>reboot

4. Login as root user and run stmsboot -e again. Answer y to the Do you wish to continue prompt. For example:

   host-1-root@[/]>stmsboot -e
   
   WARNING: stmsboot operates on each supported multipath-capable controller
            detected in a host. In your system, these controllers are
   
   /pci@1f,700000/pci@0/pci@2/pci@0/pci@8/LSILogic,sas@1
   /pci@1f,700000/pci@0/pci@9/LSI,sas@0/iport@f0
   
   If you do NOT wish to operate on these controllers, please quit stmsboot
   and re-invoke with -D { fp | mpt | mpt_sas} to specify which controllers 
   you wish to modify your multipathing configuration for.
   
   Do you wish to continue? [y/n] (default: y) y
   STMS is already enabled. No changes or reboots needed

   The system tells you that STMS is already enabled and no reboot is necessary. A reboot is still required to ensure the error message will be cleared.

5. Reboot the system. For example:

   host-1-root@[/]>reboot