Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions
Privacy Policy

  




 

 

System Administration Guide: Advanced Administration
Previous Next

What to Do if Rebooting Fails

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 on changing the default boot device, see How to Change the Default Boot Device in System Administration Guide: Basic Administration.

Solaris 10: There is no default boot device on an x86 based system. The message displayed is:

Not a UFS filesystem.

Solaris 10: Boot the system by using the Configuration Assistant/boot diskette and select the disk from which to boot.

Solaris 10 1/06: The GRUB 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.

Solaris 10 1/06: Boot the failsafe archive.

There's an invalid entry in the /etc/passwd file.

For information on recovering from an invalid passwd file, see Chapter 12, Booting a 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.

Previous Next

 
 
  Published under the terms fo the Public Documentation License Version 1.01. Design by Interspire