1. Oracle Solaris Management Tools (Road Map)
2. Working With the Solaris Management Console (Tasks)
3. Working With the Oracle Java Web Console (Tasks)
4. Managing User Accounts and Groups (Overview)
5. Managing User Accounts and Groups (Tasks)
6. Managing Client-Server Support (Overview)
7. Managing Diskless Clients (Tasks)
8. Introduction to Shutting Down and Booting a System
9. Shutting Down and Booting a System (Overview)
10. Shutting Down a System (Tasks)
11. Modifying Oracle Solaris Boot Behavior (Tasks)
12. Booting an Oracle Solaris System (Tasks)
13. Managing the Oracle Solaris Boot Archives (Tasks)
14. Troubleshooting Booting an Oracle Solaris System (Tasks)
Troubleshooting Booting on the SPARC Platform (Task Map)
SPARC: How to Stop the System for Recovery Purposes
SPARC: Forcing a Crash Dump and Reboot of the System
SPARC: How to Force a Crash Dump and Reboot of the System
SPARC: How to Boot a System for Recovery Purposes
SPARC: How to Boot to a ZFS Root Environment to Recover From a Lost Password or Similar Problem
SPARC: How to Boot the System With the Kernel Debugger (kmdb)
Troubleshooting Booting on the x86 Platform (Task Map)
x86: How to Stop a System for Recovery Purposes
x86: Forcing a Crash Dump and Reboot of the System
x86: How to Force a Crash Dump and Reboot of the System
x86: How to Boot a System With the Kernel Debugger in the GRUB Boot Environment (kmdb)
15. x86: GRUB Based Booting (Reference)
16. x86: Booting a System That Does Not Implement GRUB (Tasks)
17. Working With the Oracle Solaris Auto Registration regadm Command (Tasks)
18. Managing Services (Overview)
20. Managing Software (Overview)
21. Managing Software With Oracle Solaris System Administration Tools (Tasks)
22. Managing Software by Using Oracle Solaris Package Commands (Tasks)
|
If the keyboard and mouse are functional, become superuser. Then, type init 0 to stop the system. After the Press any key to reboot prompt appears, press any key to reboot the system.
If the keyboard and mouse are functional, become superuser, then, type init 6 to reboot the system.
Or, you can use the power switch to reboot the system.
Forcing a crash dump and reboot of the system are sometimes necessary for troubleshooting purposes. The savecore feature is enabled by default.
For more information about system crash dumps, see Chapter 17, Managing System Crash Information (Tasks), in System Administration Guide: Advanced Administration.
If you cannot use the reboot -d or the halt -d command, you can use the kernel debugger, kmdb, to force a crash dump. The kernel debugger must have been loaded, either at boot, or with the mdb -k command, for the following procedure to work.
Note - You must be in text mode to access the kernel debugger (kmdb). So, first exit any window system.
The method used to access the debugger is dependent upon the type of console that you are using to access the system.
If you are using a locally attached keyboard, press F1–A.
If you are using a serial console, send a break by using the method appropriate to that type of serial console.
The kmdb prompt is displayed.
[0]> $<systemdump
Panic messages are displayed, the crash dump is saved, and the system reboots.
Example 14-6 x86: Forcing a Crash Dump and Reboot of the System by Using halt -d
This example shows how to force a crash dump and reboot of the x86 based system neptune by using the halt -d and boot commands. Use this method to force a crash dump of the system. Reboot the system afterwards manually.
# halt -d 4ay 30 15:35:15 wacked.Central.Sun.COM halt: halted by user panic[cpu0]/thread=ffffffff83246ec0: forced crash dump initiated at user request fffffe80006bbd60 genunix:kadmin+4c1 () fffffe80006bbec0 genunix:uadmin+93 () fffffe80006bbf10 unix:sys_syscall32+101 () syncing file systems... done dumping to /dev/dsk/c1t0d0s1, offset 107675648, content: kernel NOTICE: adpu320: bus reset 100% done: 38438 pages dumped, compression ratio 4.29, dump succeeded Welcome to kmdb Loaded modules: [ audiosup crypto ufs unix krtld s1394 sppp nca uhci lofs genunix ip usba specfs nfs md random sctp ] [0]> kmdb: Do you really want to reboot? (y/n) y
This procedure shows the basics for loading the kernel debugger (kmdb). The savecore feature is enabled by default. For more detailed information about using the kernel debugger, see the Oracle Solaris Modular Debugger Guide.
The GRUB menu is displayed when the system is booted.
If you cannot use the arrow keys, use the ^ key to scroll up and the v key to scroll down.
The boot entry menu is displayed. In this menu, you can modify boot behavior by adding additional boot arguments to the end of the kernel$ line.
The method used to access the debugger is dependent upon the type of console that you are using to access the system:
If you are using a locally attached keyboard, press F1–A.
If you are using a serial console, send a break by using the method appropriate to that type of serial console.
A welcome message is displayed when you access the kernel debugger for the first time.
Example 14-7 x86: Booting a System With the Kernel Debugger (GRUB Multiboot Implementation)
This example shows how to manually boot a 64-bit capable x86 based system with the kernel debugger enabled.
kernel$ /platform/i86pc/multiboot kernel/amd64/unix -k -B $ZFS-BOOTFS
This example shows how to boot a 64-bit capable x86 based system 32-bit mode with the kernel debugger enabled.
kernel$ /platform/i86pc/multiboot kernel/unix -k -B $ZFS-BOOTFS