Table of Contents
Advertisement
6.5. Run system panic diagnostics
Running diagnostics after your storage system suffers a system panic can help
you to identify the possible cause of the panic.
1. At the storage system prompt, switch to the LOADER prompt:
2. Enter the following command at the LOADER prompt:
You must run this command from the LOADER prompt for system-level
diagnostics to function properly. The boot_diags command starts special
drivers designed specifically for system-level diagnostics.
3. Run diagnostics on all the devices by entering the following command:
4. View the status of the test by entering the following command:
Your storage system provides the following output while the tests are still running:
There are still test(s) being processed.
After all the tests are complete, you receive the following default response:
*> <SLDIAG:_ALL_TESTS_COMPLETED>
5. Identify the cause of the system panic by entering the following command:
status -long -state failed
The following example shows how the full status of the failures is displayed in a test run without
the appropriate hardware:
*> **sldiag device status -long -state failed**
TEST START ------------------------------------------
DEVTYPE: nvram_ib
NAME: external loopback test
START DATE: Sat Jan 3 23:10:55 GMT 2009
STATUS: Completed
ib3a: could not set loopback mode, test failed
END DATE: Sat Jan 3 23:11:04 GMT 2009
LOOP: 1/1
TEST END --------------------------------------------
TEST START ------------------------------------------
DEVTYPE: fcal
NAME: Fcal Loopback Test
START DATE: Sat Jan 3 23:10:56 GMT 2009
108
halt
boot_diags
sldiag device run
sldiag device status
sldiag device
Advertisement
Table of Contents
