Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 193504

New ISCSI Device Being Assigned to Exisiting ISCSI Device

$
0
0

Hey All -

 

     Got an interesting problem here. As the title states, whenever I try to add an ISCSI Device, instead of mapping it to it's new device, vCenter adds it as a path to another device.

 

 

7-10-2013 10-10-32 AM.png

This is what pukes out of the vmkernel.log on the esxi server when I tried to attach...

 

2013-07-10T15:15:42.544Z cpu0:8758)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410017f3de10 network resource pool netsched.pools.persist.iscsi associated

2013-07-10T15:15:42.544Z cpu0:8758)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410017f3de10 network tracker id 1 tracker.iSCSI.192.168.105.4 associated

2013-07-10T15:15:42.797Z cpu0:8758)WARNING: iscsi_vmk: iscsivmk_StartConnection: vmhba38:CH:0 T:2 CN:0: iSCSI connection is being marked "ONLINE"

2013-07-10T15:15:42.797Z cpu0:8758)WARNING: iscsi_vmk: iscsivmk_StartConnection: Sess [ISID: 00023d000001 TARGET: iqn.2010-11.com.com.labnas01-iet-1 TPGT: 1 TSIH: 0]

2013-07-10T15:15:42.797Z cpu0:8758)WARNING: iscsi_vmk: iscsivmk_StartConnection: Conn [CID: 0 L: 192.168.105.19:51465 R: 192.168.105.4:3260]

2013-07-10T15:15:43.296Z cpu6:8314)ScsiScan: 888: Path 'vmhba38:C0:T2:L1': Vendor: 'IET     '  Model: 'VIRTUAL-DISK    '  Rev:'0   '

2013-07-10T15:15:43.296Z cpu6:8314)ScsiScan: 891: Path 'vmhba38:C0:T2:L1': Type: 0x0, ANSI rev: 4, TPGS: 0 (none)

2013-07-10T15:15:43.297Z cpu2:8314)ScsiScan: 1373: Add path: vmhba38:C0:T2:L1

2013-07-10T15:15:43.338Z cpu0:9363)ScsiPath: 4607: Plugin 'NMP' claimed path 'vmhba38:C0:T2:L1'

2013-07-10T15:15:43.339Z cpu0:9363)ScsiCore: 1483: Power-on Reset occurred on vmhba38:C0:T2:L1

2013-07-10T15:15:43.344Z cpu0:9363)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:43.353Z cpu0:9363)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:43.361Z cpu1:9363)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:43.367Z cpu1:9363)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:43.373Z cpu1:9363)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:43.379Z cpu1:9363)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:43.385Z cpu1:9363)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:43.387Z cpu1:9363)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:43.391Z cpu1:9363)FSS: 4972: No FS driver claimed device 'mpx.vmhba34:C0:T0:L0': Not supported

2013-07-10T15:15:43.400Z cpu1:9363)Vol3: 692: Couldn't read volume header from control: Not supported

2013-07-10T15:15:43.400Z cpu1:9363)Vol3: 692: Couldn't read volume header from control: Not supported

2013-07-10T15:15:43.400Z cpu1:9363)FSS: 4972: No FS driver claimed device 'control': Not supported

2013-07-10T15:15:43.432Z cpu0:9363)VC: 1547: Device rescan time 20 msec (total number of devices 9)

2013-07-10T15:15:43.432Z cpu0:9363)VC: 1550: Filesystem probe time 53 msec (devices probed 6 of 9)

2013-07-10T15:15:44.395Z cpu1:9361)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:44.406Z cpu1:9361)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:44.425Z cpu0:9361)Vol3: 692: Couldn't read volume header from control: Not supported

2013-07-10T15:15:44.425Z cpu0:9361)Vol3: 692: Couldn't read volume header from control: Not supported

2013-07-10T15:15:44.425Z cpu0:9361)FSS: 4972: No FS driver claimed device 'control': Not supported

2013-07-10T15:15:44.433Z cpu1:9361)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:44.439Z cpu1:9361)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:44.447Z cpu4:9361)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:44.453Z cpu5:9361)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:44.459Z cpu5:9361)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:44.461Z cpu4:9361)<3>ata5.00: bad CDB len=16, scsi_op=0x9e, max=12

2013-07-10T15:15:44.466Z cpu4:9361)FSS: 4972: No FS driver claimed device 'mpx.vmhba34:C0:T0:L0': Not supported

2013-07-10T15:15:44.471Z cpu5:9361)VC: 1547: Device rescan time 25 msec (total number of devices 9)

2013-07-10T15:15:44.471Z cpu5:9361)VC: 1550: Filesystem probe time 48 msec (devices probed 6 of 9)

 

 

Anyone have any thoughts?

 

Thanks -

 

Chris


Viewing all articles
Browse latest Browse all 193504

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>