| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||||||||||||||||||||||||||||
Solution Type Troubleshooting Sure Solution 1004094.1 : Troubleshooting disk boot problems from the OBP (“ok>” prompt)
PreviouslyPublishedAs 205698 Description Troubleshooting disk boot problems from the OBP (“ok>” prompt) Symptoms
ERROR: Can't open boot-device Boot device is unknown Error: improper device path Fast Data Access MMU Miss System Type and Configuration While the examples in this document were obtained from a 1280, this document can be used to troubleshoot most device path issues for SPARC(R) based systems running Solaris[TM]. The below variables must be true in order for this resolution path to be useful:
Steps to Follow Please validate that each troubleshooting step below is true for your environment. Each step will provide instructions via a link to the document for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step. 1) Confirm that we are able to reach the OBP ( ok> prompt) If the system is unable to get to the OK prompt please see the resolution path for Troubleshooting boot problems that occur prior to OBP initialization. Reference Technical Instruction <Document: 1003150.1> Navigating between shells on Sun Fire mid-range server. 2)Confirm probe-scsi-all is able to see the boot disk Reference Technical Instruction <Document: 1005013.1> for steps on performing probe-scsi-all 3) Confirm OBP parameter diag-switch is set to false Example output:
To correct the problem:
4) Using show-disks and devalias, output, verify that the boot-device alias matches a show-disks path. Reference Technical Instruction <Document: 1010006.1> Creating a boot device alias for help on configuring boot devices. 5) Following a reset-all, verify another boot attempt has failed while capturing script data. Below is an example of a successful boot on a SunFire v1280: {0} ok boot Reference the man page for script for help capturing scritpt data. 6) At this point, if you have validated that each troubleshooting step above is true for your environment, and the issue still exists, further troubleshooting is required. Collect data and collaborate with the next level of support. Collect printenv, devalia, probe-scsi-all, the script data from step 5, and show-disks output. Product Sun Fire V1280 Server Sun Fire E2900 Server Netra 1280 Server Netra 1290 Server Sun Fire E4900 Server Sun Fire E6900 Server Sun Fire 3800 Server Sun Fire 4800 Server Sun Fire 4810 Server Sun Fire 6800 Server Internal Comments Internal Reference: For more help in translating recognized device paths use the Solaris[TM] Device Path Decoder located at http://decoder.aus/ At this point, if the customer has validated that each troubleshooting step above is true for their environment, and the issue still exists, collaborate with the next level of technical support. This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the Document Feedback alias listed below:
can't boot, boot fails, system down, down, boot, failed, boot disk, alias, devalias, show-disks, probe-scsi-all, unbootable, normalized Previously Published As 88499 Attachments This solution has no attachment |
||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||