Occasionally, when you boot the server, a drive controller might not be ready at the time the driver tries to attach.
If this problem occurs on the disk controller that serves the boot drive, you see these OpenBoot messages on the host console:
failed in wait-for-doorbell send-message / issue-ioc-facts failed issue-ioc-facts failed Can't open adapter ok
In this situation, use Workaround A.
If this problem occurs on the disk controller that does not serve the boot drive, you see these messages from the Oracle Solaris driver on the host console and in /var/adm/messages:
Probling 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
In this situation, use Workaround B.
Workaround: If your server did not boot, use Workaround A.If the driver did not attach to the second disk controller, use Workaround B.
Workaround A:
Log in to the SP and disable autoboot.
-> set /HOST/bootmode script="setenv auto-boot? false"
Power off the host and then power on to reach the OpenBoot prompt.
Probe the drives in the system.
ok probe-scsi-all
Examine the output to verify that you see all of the drives.
Type the boot command to boot the server.
Workaround B:
In Oracle Solaris, log in as root and bring the drives online.
# devfsadm -C
Determine if any services did not start because the service depends on drives to be online during boot. In this case, manually restart any of these services. Or, if you are not sure how to restart a service, reboot the server to restart all services.