JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Troubleshooting Typical Issues in Oracle Solaris 11.1     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information

Preface

1.  Managing System Crash Information (Tasks)

2.  Managing Core Files (Tasks)

3.  Troubleshooting System and Software Problems (Tasks)

4.  Troubleshooting Miscellaneous System and Software Problems (Tasks)

What to Do If Rebooting Fails

What to Do If You Forgot the Root Password or Problem That Prevents System From Booting

What to Do If a System Hang Occurs

What to Do If a File System Fills Up

File System Fills Up Because a Large File or Directory Was Created

A TMPFS File System Is Full Because the System Ran Out of Memory

What to Do If File ACLs Are Lost After Copy or Restore

Index

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/sparcv9/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 Displaying and Setting Boot Attributes in Booting and Shutting Down Oracle Solaris 11.1 Systems.
The Oracle Solaris boot archive has become corrupted. 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.
There is an invalid entry in the /etc/passwd file.
The x86 boot loader (GRUB) is damaged. Or, the GRUB menu is missing or has become corrupt.
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 these steps fail, 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.