T5-x System Does Not Recognize The Boot Disks. Ereport.chassis.post.io.test-fail@/SYS/MB/SASHBA
(Doc ID 2748251.1)
Last updated on OCTOBER 07, 2022
Applies to:
Oracle SuperCluster T5-8 Hardware - Version All Versions to All Versions [Release All Releases]SPARC T5-8 - Version All Versions to All Versions [Release All Releases]
SPARC T5-4 - Version All Versions to All Versions [Release All Releases]
SPARC T5-2 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Symptoms
1. T5-8 server failed to boot reporting "Can't open boot device"
0} ok boot /pci@300/pci@1/pci@0/pci@4/pci@0/pci@c/scsi@0/disk
Boot device: /pci@300/pci@1/pci@0/pci@4/pci@0/pci@c/scsi@0/disk File and args
Can't open boot device
Boot device: /pci@300/pci@1/pci@0/pci@4/pci@0/pci@c/scsi@0/disk File and args
Can't open boot device
2. The controller was detected by probe-scsi-all output, however the disks were not reported.
{0} ok probe-scsi-all
/pci@300/pci@1/pci@0/pci@4/pci@0/pci@c/scsi@0 <---- SASHBA0
{0} ok
/pci@300/pci@1/pci@0/pci@4/pci@0/pci@c/scsi@0 <---- SASHBA0
{0} ok
3. Disks were detected at the ILOM level
/SYS/SASBP0/HDD0
Properties:
type = Hard Disk
ipmi_name = SBP0/HDD0
/SYS/SASBP0/HDD0/OK2RM
Properties:
type = Indicator
ipmi_name = SBP0/HDD0/OK2RM
value = Off
/SYS/SASBP0/HDD0/SERVICE
Properties:
type = Indicator
ipmi_name = SBP0/HDD0/S
value = Off
/SYS/SASBP0/HDD1
Properties:
type = Hard Disk
ipmi_name = SBP0/HDD1
/SYS/SASBP0/HDD1/OK2RM
Properties:
type = Indicator
ipmi_name = SBP0/HDD1/OK2RM
value = Off
/SYS/SASBP0/HDD1/SERVICE
Properties:
type = Indicator
ipmi_name = SBP0/HDD1/S
value = Off
Properties:
type = Hard Disk
ipmi_name = SBP0/HDD0
/SYS/SASBP0/HDD0/OK2RM
Properties:
type = Indicator
ipmi_name = SBP0/HDD0/OK2RM
value = Off
/SYS/SASBP0/HDD0/SERVICE
Properties:
type = Indicator
ipmi_name = SBP0/HDD0/S
value = Off
/SYS/SASBP0/HDD1
Properties:
type = Hard Disk
ipmi_name = SBP0/HDD1
/SYS/SASBP0/HDD1/OK2RM
Properties:
type = Indicator
ipmi_name = SBP0/HDD1/OK2RM
value = Off
/SYS/SASBP0/HDD1/SERVICE
Properties:
type = Indicator
ipmi_name = SBP0/HDD1/S
value = Off
4. Verified no Hardware Raid Volumes were configured.
5. Server booted to OBP in factory-default (No LDOMs) configuration. Disks were still not reported.
6. FMA ereports show that SASHBA encountered a failure during POST.
2021-01-23 16:30:39.359 0:0:0>ERROR:
ereport.chassis.post.io.test-fail@/SYS/MB/SASHBA0 <-------
reporting PCPU ID=0
TestTitle=IO Trap Handler
Operation=Data Access Error (Type: 32)
Trap PC=0x00000000005666bc
Trap Level=0x01
NPESR=0x0000000000000001
NPEAR=0x0000805000800068
END_ERROR
ereport.chassis.post.io.test-fail@/SYS/MB/SASHBA0 <-------
reporting PCPU ID=0
TestTitle=IO Trap Handler
Operation=Data Access Error (Type: 32)
Trap PC=0x00000000005666bc
Trap Level=0x01
NPESR=0x0000000000000001
NPEAR=0x0000805000800068
END_ERROR
Changes
System Firmware was updated to version 9.6.24
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |