If the original boot file is damaged, boot the system interactively. Then you can choose to boot from a different /etc/system file or boot environment.
Before You Begin
Ensure that your role has the appropriate rights profiles to perform this procedure. See Using Rights Profiles to Administer Boot Features.
$ cp /etc/system /etc/system.bak $ cp /boot/solaris/filelist.ramdisk /boot/solaris/filelist.ramdisk.orig
$ echo "etc/system.bak" >> /boot/solaris/filelist.ramdisk
ok boot -a
$ reboot -p
For example:
Name of system file [etc/system]: /etc/system.bak
In the following example, the screen output is truncated to show only relevant parts in bold.
$ init 0 . ok boot -a . Name of system file [/etc/system]: /etc/system.bak . Retire store [/etc/devices/retire_store] (/dev/null to bypass): Press Enter . system-28 console login:Example 18 x86: Booting a System Interactively
In the following example, Oracle Solaris 11.3 is edited to boot interactively.
The sample screen output is truncated to show only the parts related to the steps.
$ reboot -p . (After some messages, the menu appears.) **************************************************************************** *Oracle Solaris 11.3 * * * * * ****************************************************************************
You would select Oracle Solaris 11.3 and type e to edit it. The edit is shown in bold.
+--------------------------------------------------------------------------+ | setparams 'Oracle Solaris 11.3' | | . | | . | | $multiboot /ROOT/s11.3/@/$kern $kern -B $zfs_bootfs -a | | . | +--------------------------------------------------------------------------+
After editing, you would press the appropriate keys to continue with the boot process. Additional prompts appear.
Name of system file [/etc/system]: /etc/system.bak
.
Retire store [/etc/devices/retire_store] (/dev/null to bypass): Press Enter
.
system-04 console login: