LSI Ultra320 SCSI HBA unconfigured state in cfgadm

Hi all

Configuration:

1. Sun X4200 with LSI Ultra320 SCSI HBA

2. Axus DemonRaid disk array

3. Solaris 10 x64 11/06 (without last kernel patch from 29.01.07)

During boot LSI controller checks the scsi-bus and see the array

HBA ID LUN VENDORPRODUCT REV SYNC WIDE CYL/ HD/SEC

-- -- - -- -- -

01 2 Demon SA -16U4PR0.0 80.0 16 1024/255/63

07 0 LSILogic 1020/1030[ 202] 1032700 320.0 16

But in Solaris SCSI device with scsi-id: 1 and LUN 2 doesnt appear

The main strange thing for me is that i cant cahnge state of scsi-bus to configured in cfgadm

#cfgadm -al

Ap_Id Type ReceptacleOccupantCondition

c0scsi-busconnectedconfiguredunknown

c0::dsk/c0t0d0disk connectedconfiguredunknown

c4scsi-busconnectedunconfigured unknown

#cfgadm -c configure c4

It takes about 30-40 seconds, then

#cfgadm -alv c4

Ap_Id ReceptacleOccupantCondition Information

When Type BusyPhys_Id

c4connectedunconfigured unknown

unavailable scsi-busn/devices/pci@0,0/pci1022,7450@2/pci1000,5110@1:scsi

In messages

Feb 7 15:35:09 wezen scsi: [ID 365881 kern.notice] /pci@0,0/pci1022,7450@2/pci1000,5110@1 (mpt0):

Feb 7 15:35:09 wezen scsi: [ID 365881 kern.notice] /pci@0,0/pci1022,7450@2/pci1000,5110@1 (mpt0):

Feb 7 15:35:09 wezenmpt0 supports power management.

Feb 7 15:35:09 wezen scsi: [ID 365881 kern.notice] /pci@0,0/pci1022,7450@2/pci1000,5110@1 (mpt0):

Feb 7 15:35:09 wezenmpt0 Firmware version v1.3.27.0 (IT)

Feb 7 15:35:09 wezen scsi: [ID 365881 kern.notice] /pci@0,0/pci1022,7450@2/pci1000,5110@1 (mpt0):

Feb 7 15:35:09 wezenmpt0: IOC Operational.

Feb 7 15:35:11 wezen pci_pci: [ID 370704 kern.notice] PCI-device: pci1000,5110@1, mpt0

Feb 7 15:35:11 wezen genunix: [ID 936769 kern.notice] mpt0 is /pci@0,0/pci1022,7450@2/pci1000,5110@1

But no information about devices on mpt0

What does mean "unconfigured" state of scsi-bus? The driver is not attached correctly or something else?

Thanx in advance

[2101 byte] By [Maxim_Cherniavskya] at [2007-11-26 17:46:53]
# 1
I would suggest downloading the correct driver from LSI. Followed by a "reboot -- -r"www.lsilogic.com
Lee_McCreerya at 2007-7-9 4:59:10 > top of Java-index,Storage Forums,Storage General Discussion...
# 2
Solution is to add to sd.conf this lines for 2'nd LUNname="sd" class="scsi" target=1 lun=2;
Maxim_Cherniavskya at 2007-7-9 4:59:10 > top of Java-index,Storage Forums,Storage General Discussion...