Go to main content

Managing SAN Devices and I/O Multipathing in Oracle® Solaris 11.4

Exit Print View

Updated: November 2020
 
 

How to Recover From a System Crash

Perform the following steps to recover your original multipathed configuration if your system hangs, panics, or fails to boot after a stmsboot enable (-e), disable (-d), or update (-u) operation.

  1. Boot the system from another bootable disk, installation DVD, or over the network.
    • SPARC platform: If you boot from installation media or an installation server on the network, select the text installation. If you boot from an installation server, use the following command:

      ok boot net:dhcp
    • x86 platform: If you boot from installation media or an installation server on the network, select this text installation option from the GRUB menu:

      Oracle Solaris 11.3 Text Installer and command line
    • Select option 3 Shell from the following menu:

              1  Install Oracle Solaris
              2  Install Additional Drivers
              3  Shell
              4  Terminal type (currently sun-color)
              5  Reboot
      
      Please enter a number [1]: 3
      To return to the main menu, exit the shell
  2. Import your ZFS root pool.
    # zpool import -f rpool
  3. Mount the root BE.
    # mkdir /a
    # beadm mount solaris /a
  4. Restore your original fp.conf file (for FC multipathing) or mpt.conf (for SAS multipathing) as follows.
    • If you ran the stmsboot –e command or stmsboot –d command:
      • For SAS multipathing:

        # cp /a/etc/mpxio/mpt.conf /a/etc/driver/drv/mpt.conf
      • For FC multipathing:

        # cp /a/etc/mpxio/fp.conf /a/etc/driver/drv/fp.conf
    • If you ran the stmsboot –u command, and you modified either the fp.conf file or the mpt.conf undo the changes you made to this file by editing either the /a/etc/driver/drv/fp.conf or the /a/etc/driver/drv/mpt.conf files.
  5. Undo any other changes you made to the multipathing configuration prior to running the stmsboot command.

    For example, if you modified the scsi_vhci.conf file, undo the changes you made to this file by editing the /a/etc/driver/drv/scsi_vhci.conf file.

    For example, if you modified the scsi_vhci.conf file, undo the changes you made to this file by editing the /a/kernel/drv/scsi_vhci.conf file.

    If you modified the device settings of your storage arrays, restore their original settings.

  6. Restore your original /etc/vfstab file:
    # cp /a/etc/mpxio/vfstab /a/etc/vfstab

    The /a/etc/mpxio/vfstab file is a copy your original /etc/vfstab file that the stmsboot command saved prior to updating your vfstab file. A /a/etc/mpxio/vfstab file will not exist if the stmsboot command has not modified your vfstab file.

  7. If the system is running on the Oracle Solaris OS on an x86 based system, perform the following steps:
    1. Restore your original /boot/solaris/bootenv.rc file.
      # cp /a/etc/mpxio/bootenv.rc /a/boot/solaris/bootenv.rc

      The /a/etc/mpxio/bootenv.rc file is a copy your original /boot/solaris/bootenv.rc file that the stmsboot command saved prior to updating your bootenv.rc file. A /a/etc/mpxio/bootenv.rc file will not exist if the stmsboot command has not modified your bootenv.rc file.

    2. Update the boot archive.
      # bootadm update-archive -R /a
  8. Disable the mpxio-upgrade service:
    # /usr/sbin/svccfg -f /a/etc/mpxio/svccfg_recover
  9. Unmount the BE and the USF root file system.
    # beadm umount solaris
    # umount /a
  10. Reboot the system.