How to Recover from a System Crash

Boot the system from another bootable disk, installation DVD, or over the network.
- Select one of the following to boot from a SPARC system or an x86 system:
  - SPARC: Select one of the following to boot from a UFS root file system or a ZFS root file system:
    - For a ZFS root file system, boot in failsafe mode.
```
ok boot -F failsafe


Mount the ZFS BE on /a when prompted.

.
.
.
ROOT/zfsBE was found on rpool.
Do you wish to have it mounted read-write on /a? [y,n,?] y
mounting rpool on /a
Starting shell.
```
    - For a UFS root file system, select one of the following to boot from media or from the network:
```
ok boot net -s
```
```
ok boot cdrom -s
```
    - Mount your original root file system's device.
```
# mount your-root-device /mnt
```
- x86: Select one of the following to boot from a UFS root file system or a ZFS root file system:
  
  For a UFS root file system:
  - Instruct the BIOS to boot from media or from the network.
  - If your system uses a specific keystroke sequence to boot from media or from the network, type the keystrokes when the BIOS screen is displayed.
  - If you need to manually modify the BIOS settings to boot from media or from the network, type the keystroke sequence to access the BIOS setup utility. Then, modify the boot priority to boot from media or from the network. When the GRUB menu is displayed, select the option that you want to install.
- For a ZFS root file system, boot in fail safe mode by selecting failsafe mode from the GRUB menu.
```
Mount the ZFS BE on /a when prompted.

.
.
.
ROOT/zfsBE was found on rpool.
Do you wish to have it mounted read-write on /a? [y,n,?] y
mounting rpool on /a
Starting shell.
```
For a UFS file system, check the file system consistency.
Run the fsck command where /dev/rdsk/devicename is your original root device.
```
# fsck /dev/rdsk/devicename
```
Mount your original UFS root file system.
```
# mount /dev/dsk/devicename /a
```
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/kernel/drv/mpt.conf
```
  - For FC multipathing:
```
# cp /a/etc/mpxio/fp.conf /a/kernel/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/kernel/drv/fp.conf or the /a/kernel/drv/mpt.conf files.
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/kernel/drv/scsi_vhci.conf file.
If you modified the device settings of your storage arrays, restore their original settings.
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.
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
```

Disable the mpxio-upgrade service:

# /usr/sbin/svccfg -f /a/etc/mpxio/svccfg_recover

Unmount the UFS root file system.
```
# umount /a
```
Reboot the system.

Skip Navigation Links
Exit Print View
	Oracle Solaris SAN Configuration and Multipathing Guide Oracle Solaris 10 1/13 Information Library