What to Do If Rebooting Fails

If the system does not reboot completely, or if the system 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 Chapter 6, Modifying Boot Parameters on a SPARC Based System (Tasks), in Booting and Shutting Down Oracle Solaris on SPARC Platforms.
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 that is a backup of the primary boot environment. In the event the primary boot environment is not bootable, boot the backup boot environment. Alternatively, you can boot from the live CD or USB media. For more information about creating and managing BEs, see Creating and Administering Oracle Solaris 11 Boot Environments
There's an invalid entry in the `/etc/passwd` file.	For information about recovering from an invalid `passwd` file, see What to Do If You Forgot the Root Password or Problem That Prevents System From Booting.
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
	Oracle Solaris Administration: Common Tasks Oracle Solaris 11 Information Library