Using the bootadm Command to Manage the Boot Archives (System Administration Guide: Basic Administration) - Sun Microsystems

Do not attempt these instructions by yourself without first opening a case with Sun. Every problem is different, and just because these commands worked for me, does NOT mean they will work for your problem. You could make things worse by not seeking help from Sun. Don't make me tell you I told you so!

Sunday night I attempted to reboot one of my servers, and got output similar to the following (the names have been changed):



SunOS Release 5.10 Version Generic_141414-07 64-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: Unexpected EOF on line 14 of /kernel/drv/md.conf
Hostname: xyzzy

WARNING: The following files in / differ from the boot archive:

changed /kernel/drv/did.conf

The recommended action is to reboot to the failsafe archive to correct
the above inconsistency. To accomplish this, on a GRUB-based platform,
reboot and select the "Solaris failsafe" option from the boot menu.
On an OBP-based platform, reboot then type "boot -F failsafe". Then
follow the prompts to update the boot archive. Alternately, to continue
booting at your own risk, you may clear the service by running:
"svcadm clear system/boot-archive"

Sep 18 15:22:06 svc.startd[7]: svc:/system/boot-archive:default:
Method "/lib/svc/method/boot-archive" failed with exit status 95.
Sep 18 15:22:06 svc.startd[7]: system/boot-archive:default
failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run

Root password for system maintenance (control-d to bypass):



With help from Sun, and documentation similar to "Using the bootadm Command to Manage the Boot Archives (System Administration Guide: Basic Administration) - Sun Microsystems", I was able to get my system back up and running.

Thank you Sun!