![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Troubleshooting Sure Solution 1004094.1 : Troubleshooting disk boot problems from the OBP (ok> prompt)
PreviouslyPublishedAs 205698 Applies to:Sun Fire V1280 ServerSun Netra 1280 Server Sun Fire 3800 Server Sun Fire 4800 Server Sun Fire 4810 Server All Platforms PurposeTroubleshooting disk boot problems from the OBP (ok> prompt) Troubleshooting StepsSymptoms
ERROR: Can't open boot-device Boot device is unknown Error: improper device path Fast Data Access MMU Miss Note: error messages like "Fast Data Access MMU Miss" could also be observed while booting from the correct disk partition and alias (i.e.: in case of boot image corruption or issue over the root filesystem); please perform a boot attempt using cdrom/network image, after having performed five troubleshooting steps below, and check if issue persists.
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:
1) Confirm that you 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: Sun Fire[TM] 3800, 4800, 4810, 6800, E4900, and E6900: Navigating Between Shells on Sun Fire Mid-range Servers [Video] (Doc ID 1003150.1)
2) Confirm probe-scsi-all is able to see the boot disk Reference: probe-scsi-all may fail without reset-all on all Sun[TM] Systems (Doc ID 1005013.1)
3) Confirm OBP parameter diag-switch? is set to false Example output: ok> printenv diag-switch? To correct the problem: ok> setenv diag-switch? false
4) Using show-disks and devalias, output, verify that the boot-device alias matches a show-disks path. Reference: How to create a boot device alias (Doc ID 1010006.1)
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 script 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 raise a Service Request
At the OK-prompt collect the output of the following commands: printenv, devalias, probe-scsi-all and show-disks and the script data from step 5
Attachments This solution has no attachment |
||||||||||||
|