[OmniOS-discuss] test omnios on OI machine / solved

Wed Dec 3 16:11:32 UTC 2014

As a last resort I just turned off the machine and kept it off for a few minutes. Turned it back on and both controllers are now properly detected.

R

From: sim.ple at live.nl
To: omnios-discuss at lists.omniti.com
Date: Wed, 3 Dec 2014 11:59:11 +0100
Subject: Re: [OmniOS-discuss] test omnios on OI machine

when I do 

cfgadm -al
Ap_Id                          Type         Receptacle   Occupant     Condition
c7                             scsi-sas     connected    configured   unknown
c7::dsk/c7t500000E118E31592d0  disk         connected    configured   unknown
c9                             scsi-sas     connected    configured   unknown
c9::dsk/c9t5000C50055B2A5B1d0  disk         connected    configured   unknown
c9::dsk/c9t5000C50055B2A9A9d0  disk         connected    configured   unknown
c9::dsk/c9t5000C50055B2A139d0  disk         connected    configured   unknown
c9::dsk/c9t5000C50055B2A245d0  disk         connected    configured   unknown
c9::dsk/c9t5000C50055B2B081d0  disk         connected    configured   unknown
c9::dsk/c9t5000C50055B2B249d0  disk         connected    configured   unknown
c9::dsk/c9t5000C50055B2B255d0  disk         connected    configured   unknown
c9::dsk/c9t5000C50055B2BD6Dd0  disk         connected    configured   unknown
c9::es/ses0                    ESI          connected    configured   unknown
c9::es/ses1                    ESI          connected    configured   unknown
c9::es/ses2                    ESI          connected    configured   unknown
c9::smp/expd0                  smp          connected    configured   unknown
c9::smp/expd1                  smp          connected    configured   unknown
c9::smp/expd2                  smp          connected    configured   unknown
c10                            scsi-sas     connected    configured   unknown
c10::dsk/c10t5001517BB27F79F7  disk         connected    configured   unknown
c11                            scsi-sas     connected    unconfigured unknown
usb2/1                         usb-hub      connected    configured   ok
usb2/1.1                       unknown      empty        unconfigured ok
usb2/1.2                       unknown      empty        unconfigured ok
usb2/1.3                       unknown      empty        unconfigured ok
usb2/1.4                       unknown      empty        unconfigured ok
usb2/1.5                       unknown      empty        unconfigured ok
usb2/1.6                       unknown      empty        unconfigured ok
usb2/2                         unknown      empty        unconfigured ok
usb3/1                         usb-hub      connected    configured   ok
usb3/1.1                       unknown      empty        unconfigured ok
usb3/1.2                       unknown      empty        unconfigured ok
usb3/1.3                       unknown      empty        unconfigured ok
usb3/1.4                       usb-device   connected    configured   ok
usb3/1.5                       unknown      empty        unconfigured ok
usb3/1.6                       unknown      empty        unconfigured ok
usb3/1.7                       unknown      empty        unconfigured ok
usb3/1.8                       unknown      empty        unconfigured ok
usb3/2                         unknown      empty        unconfigured ok

i see c11 as unconfigured. Could this be the cause ?

From: sim.ple at live.nl
To: omnios-discuss at lists.omniti.com
Date: Wed, 3 Dec 2014 11:37:31 +0100
Subject: Re: [OmniOS-discuss] test omnios on OI machine

Anybody else had problems with two or more sas hba's in an omnios system ?
How was this solved?

From: sim.ple at live.nl
To: omnios-discuss at lists.omniti.com
Date: Wed, 3 Dec 2014 01:45:12 +0100
Subject: Re: [OmniOS-discuss] test omnios on OI machine

Hi, was indeed intended for the list.

dmesg | grep mptsas

gives nothing (no output). 

Hope you have an idea of what to do next. 

Going to test a current omnios with one hba by adding another to it to see what happens tomorrow.  

Will be testing with new Dell hardware and solarflare cards probably in the comming weeks also. If you are interrested, will keep you posted. 

> Subject: Re: [OmniOS-discuss] test omnios on OI machine
> From: danmcd at omniti.com
> Date: Tue, 2 Dec 2014 19:22:15 -0500
> CC: danmcd at omniti.com
> To: sim.ple at live.nl
> 
> Please share these with the community in the future, unless you're sharing confidential data of some sort.
> 
> 
> > On Dec 2, 2014, at 6:59 PM, Randy S <sim.ple at live.nl> wrote:
> > 
> > Hi Dan,
> > 
> > It's been a while...
> > 
> > I wanted to stay on r10 since that has been in use by quite a community for quite a while now. R12 is still new so usually unforseen hicups can be expected. (We are not frontrunners regarding systems intended for serious use  ;-) ). Have been testing omnios for quite a while on systems with one hba now. All was satisfactory. 
> > 
> > forgot to mention, I did do an fmdump -ev and saw 
> > Dec 02 23:32:37.1675 ereport.fs.zfs.vdev.open_failed       0x0077a03af6b00001
> > Dec 02 23:32:37.1675 ereport.fs.zfs.vdev.open_failed       0x0077a03af6b00001
> > Dec 02 23:35:17.6783 ereport.sensor.failure                0x02cd95a4cde05801
> > Dec 02 23:35:17.6868 ereport.sensor.failure                0x02cd9dbb53605801
> > 
> > I guess this is because the one controller cannot be found.
> 
> That's a fair assessment.
> 
> > dmesg | grep mpt_sa (done just now (not sleepy yet)) gives :
> > 
> > Dec  3 00:42:44 omni scsi: [ID 583861 kern.info] sd68 at mpt_sas3: unit-address w5000c50057ad9161,0: w5000c50057ad9161,0
> > Dec  3 00:42:44 omni scsi: [ID 583861 kern.info] sd69 at mpt_sas3: unit-address w5000c50057adb269,0: w5000c50057adb269,0
> > Dec  3 00:42:45 omni scsi: [ID 583861 kern.info] sd70 at mpt_sas3: unit-address w5000c50057adea91,0: w5000c50057adea91,0
> > Dec  3 00:42:45 omni scsi: [ID 583861 kern.info] ses2 at mpt_sas3: unit-address w5003048000b18d3d,0: w5003048000b18d3d,0
> > Dec  3 00:42:45 omni scsi: [ID 583861 kern.info] mpt_sas4 at mpt_sas0: scsi-iport 20
> > Dec  3 00:42:45 omni genunix: [ID 936769 kern.info] mpt_sas4 is /pci at 0,0/pci8086,3c04 at 2/pci1000,3030 at 0/iport at 20
> > Dec  3 00:42:45 omni genunix: [ID 408114 kern.info] /pci at 0,0/pci8086,3c04 at 2/pci1000,3030 at 0/iport at 20 (mpt_sas4) online
> > Dec  3 00:42:45 omni scsi: [ID 583861 kern.info] sd71 at mpt_sas4: unit-address w5001517bb27f79f7,0: w5001517bb27f79f7,0
> > Dec  3 00:42:45 omni scsi: [ID 583861 kern.info] mpt_sas5 at mpt_sas0: scsi-iport v0
> > Dec  3 00:42:45 omni genunix: [ID 936769 kern.info] mpt_sas5 is /pci at 0,0/pci8086,3c04 at 2/pci1000,3030 at 0/iport at v0
> > Dec  3 00:42:45 omni genunix: [ID 408114 kern.info] /pci at 0,0/pci8086,3c04 at 2/pci1000,3030 at 0/iport at v0 (mpt_sas5) online
> 
> Interesting... note that two mpt_sas controllers (4 and 5) came online.  I wonder why one isn't showing up?  Grep for "mptsas" as well, just in case?
> 
> Dan
> 

_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss at lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss 		 	   		  

_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss at lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss 		 	   		  

_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss at lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omniosce.org/ml-archive/attachments/20141203/9af25fea/attachment-0001.html>