In some instances, a drive controller might not be ready when the Oracle Solaris OS driver attempts to attach. If this issue affects the drive controller that services the boot drive, the following OBP messages display on the HOST console :
failed in wait-for-doorbell send-message / issue-ioc-facts failed issue-ioc-facts failed Can't open adapter ok>
If this issue affects the drive controller that does not service the boot drive, the following messages display on the HOST console and in the /var/adm/messages log:
Probing for device nodes ...
@ WARNING: /pci@3c0/pci@1/pci@0/pci@2/scsi@0 (mpt_sas1):
mptsas_ioc_get_facts failed
@ WARNING: /pci@3c0/pci@1/pci@0/pci@2/scsi@0 (mpt_sas1):
mptsas chip initialization failed
@ WARNING: /pci@3c0/pci@1/pci@0/pci@2/scsi@0 (mpt_sas1):
attach failed
Workaround 1:
If the controller servicing the boot drive fails to attach, do the following:
Login to the SP and disable the auto-boot parameter:
-> set /HOST/bootmode script="setenv auto-boot? false"
Probe the drives in the system.
From the ok> prompt, type:
ok> probe-scsi-all
Verify that all of the drives are attached.
Boot the server.
Workaround 2:
If the system boots but the driver does not attach to the second disk controller, type:
# devfsadm -C
Verify that all of the drives are attached.