> On Nov 15, 2014, at 7:49 AM, Richard Elling > <richard.ell...@richardelling.com> wrote: > > Hi CJ, > I'm away from my notes at the moment, but know that an mptsas instance's > reported target number is not the same as the sd driver instance number. The > most expeditious way to cross reference is to use sasinfo or, failing that, > > echo ::mptsas -t | mdb -k > > which dumps the sas WWN to target port info.
in this output, the “devhdl” is the number you need to match — richard > > If that still doesn't narrow the field, look at the per-disk error counters: > iostat -E > > Note: resets are tricky and you can be sure sd is trying to reset devices to > wake them up. > > More later, when I get back to the office... > -- richard > > > >> On Nov 15, 2014, at 6:57 AM, CJ Keist <cj.ke...@colostate.edu> wrote: >> >> Hello, >> Need some help identifying physical disk on my system. My system got hung >> and last thing in the /var/adm/message file before the crash is follows: >> >> Nov 14 13:31:12 projects2 scsi: [ID 107833 kern.warning] WARNING: >> /pci@0,0/pci8086,340c@5/pci1000,3020@0 (mpt_sas0): >> Nov 14 13:31:12 projects2 Disconnected command timeout for Target 48 >> Nov 14 13:31:12 projects2 scsi: [ID 243001 kern.warning] WARNING: >> /pci@0,0/pci8086,340c@5/pci1000,3020@0 (mpt_sas0): >> Nov 14 13:31:12 projects2 mptsas_handle_event_sync: IOCStatus=0x8000, >> IOCLogInfo=0x31170000 >> Nov 14 13:31:16 projects2 scsi: [ID 365881 kern.info] >> /pci@0,0/pci8086,340c@5/pci1000,3020@0 (mpt_sas0): >> Nov 14 13:31:16 projects2 Log info 0x31140000 received for target 48. >> Nov 14 13:31:16 projects2 scsi_status=0x0, ioc_status=0x8048, >> scsi_state=0xc >> Nov 14 13:31:16 projects2 scsi: [ID 107833 kern.warning] WARNING: >> /pci@0,0/pci8086,340c@5/pci1000,3020@0 (mpt_sas0): >> Nov 14 13:31:16 projects2 mptsas_check_task_mgt: Task 0x3 failed. >> IOCStatus=0x4a IOCLogInfo=0x0 target=48 >> Nov 14 13:31:16 projects2 scsi: [ID 107833 kern.warning] WARNING: >> /pci@0,0/pci8086,340c@5/pci1000,3020@0 (mpt_sas0): >> Nov 14 13:31:16 projects2 mptsas_ioc_task_management failed try to >> reset ioc to recovery! >> >> Then using the command "cfgadm -alv" shows that the >> /pci@0,0/pci8086,340c@5/pci1000,3020@0 is the controller in front of all the >> disks. The output above does say "Target 48", I'm hoping that is the disk >> target so would be the one listed in the cfgadm command here: >> >> c6::w50014ee2b2e8dc6a,0 connected configured unknown Client >> Device: /dev/dsk/c3t50014EE2B2E8DC6Ad0s0(sd48) >> unavailable disk-path n >> /devices/pci@0,0/pci8086,340c@5/pci1000,3020@0/iport@f:scsi::w50014ee2b2e8dc6a,0 >> >> Would this be the disk being reported in /var/adm/messages? >> >> -- >> C. J. Keist Email: cj.ke...@colostate.edu >> Systems Group Manager Solaris 10 OS (SAI) >> Engineering Network Services Phone: 970-491-0630 >> College of Engineering, CSU Fax: 970-491-5569 >> Ft. Collins, CO 80523-1301 >> >> All I want is a chance to prove 'Money can't buy happiness' >> >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss@lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss -- richard.ell...@richardelling.com +1-760-896-4422
_______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
