Asset ID: |
1-79-2243496.1 |
Update Date: | 2017-08-14 |
Keywords: | |
Solution Type
Predictive Self-Healing Sure
Solution
2243496.1
:
M12-upset.io.boot - Failure to boot Solaris on a domain
Related Items |
- Fujitsu SPARC M12-1
- Fujitsu SPARC M12-2S
- Fujitsu SPARC M12-2
|
Related Categories |
- PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: Sun PSH
|
In this Document
Applies to:
Fujitsu SPARC M12-2 - Version All Versions and later
Fujitsu SPARC M12-2S - Version All Versions and later
Fujitsu SPARC M12-1
SPARC
Purpose
Provide additional information for message IDs: M12-upset.io.boot
03000002, 03000003, 03000007
Details
Type
- Hardware Fault
- upset.io.boot
Severity
- Major
Description
-
Upset due to a failure to boot Solaris on a domain.
Automated Response
- The domain drops to the OBP 'ok' prompt. The platform administrator should investigate the cause of the boot problem and schedule a service action if necessary.
- The domain drops to the OBP 'ok' prompt. The OBP fcode did not detect any fault with the device. The cause may be some difficult-to-diagnose hardware problem, a corrupted boot image, or some external problem.
Impact
- Nothing is deconfigured.
Indicted Hardware
- The precise cause of the failure to boot cannot really be determined.
The OBP fcode did not detect any fault with the device. The cause may be some difficult-to-diagnose hardware problem, a corrupted boot image, or some external problem.
The device with the failure is the first suspect on the suspect list for this upset.
Additionally, if the device is a HDD or a DVD drive, the SAS controller for the device is the second suspect on the suspect list.
In some cases, OBP cannot determine a specific device so the chassis is identified as the suspect.
Nothing is put in the resource cache for this fault.
An SNMP fault trap will be generated but this will not be populated with a message id in the usual format e.g. M12-<text string>, and the ASR back-end does not process the fault trap or generate an SR.
Suggested Action for System Administrator
- The recommended service action for this event is to schedule replacement of the affected component(s) at the earliest possible convenience. Although the hardware may be functioning, it is not intended nor recommended that the faulted component(s) remain in the system for a prolonged period of time.
Refer to the following document for the latest procedures for displaying event content in preparation for submitting a service request and applying any post-repair actions that may be required.
PSH Procedural Article for Fujitsu M10 Diagnosis (Doc ID 1525156.1)

Attachments
This solution has no attachment