What to Do If Rebooting Fails

Note - Some of the information in this section pertains to systems that are running the Oracle Solaris 10 release only.

If the system does not reboot completely, or if it reboots and then crashes again, there might be a software or hardware problem that is preventing the system from booting successfully.

Cause of System Not Booting	How to Fix the Problem
The system can't find /platform/`uname -m`/kernel/unix.	You may need to change the `boot-device` setting in the PROM on a SPARC based system. For information about changing the default boot device, see How to Change the Default Boot Device by Using the Boot PROM in System Administration Guide: Basic Administration.
Oracle Solaris 11 Express: The GRUB boot archive has become corrupted or the GRUB menu is lost. Or, the SMF boot archive service has failed. An error message is displayed if you run the `svcs` `-x` command.	Create a second boot environment (BE) that is a backup of the primary BE. In the event the primary BE is not bootable, boot the backup BE. Alternatively, you can boot from the live CD or USB media. For more information about creating and managing BEs, see Managing Boot Environments With Oracle Solaris 11 Express.
There's an invalid entry in the `/etc/passwd` file.	For information about recovering from an invalid `passwd` file, see Chapter 7, Booting an Oracle Solaris System (Tasks), in System Administration Guide: Basic Administration.
There's a hardware problem with a disk or another device.	Check the hardware connections: Make sure the equipment is plugged in. Make sure all the switches are set properly. Look at all the connectors and cables, including the Ethernet cables. If all this fails, turn off the power to the system, wait 10 to 20 seconds, and then turn on the power again.

If none of the above suggestions solve the problem, contact your local service provider.

Skip Navigation Links
Exit Print View
	System Administration Guide: Advanced Administration Oracle Solaris 11 Express 11/10