- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Error creating VMFS Datastore on redundant FAS3240
Greetings,
I am trying to create a VMFS datastore of approximately 1TB in size on one controller in an active/active FAS3240 pair. If I create the iSCSI LUN on one controller, it works fine. On the other it does not and errors out with the error seen in the screenshot below. The odd thing is, I have plenty of direct iSCSI connections to this other controller and everything is fine (from Windows and Linux boxes using software initiators). I actually had this problem with two LUNs that I created today, but one of them inexplicably worked the last time I tried it. I've checked paths, Jumbo Frames end-to-end, VIF configs, QLogic initator configs, etc. and nothing seems to make a difference.
VMKernel logs from the event are below:
2011-11-18T20:02:41.326Z cpu4:3273)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2011-11-18T20:02:41.335Z cpu2:447519)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x1a (0x41240079d7c0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.Act:NONE
2011-11-18T20:02:41.335Z cpu2:447519)ScsiDeviceIO: 2316: Cmd(0x41240079d7c0) 0x1a, CmdSN 0x81a74 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2011-11-18T20:02:41.477Z cpu1:3273)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2011-11-18T20:02:42.821Z cpu6:3273)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2011-11-18T20:02:42.824Z cpu6:3273)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2011-11-18T20:02:42.827Z cpu6:3273)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2011-11-18T20:02:42.830Z cpu6:3273)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2011-11-18T20:02:42.836Z cpu6:3273)FSS: 4333: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported
2011-11-18T20:02:42.836Z cpu6:3273)Vol3: 647: Couldn't read volume header from control: Invalid handle
2011-11-18T20:02:42.836Z cpu6:3273)FSS: 4333: No FS driver claimed device 'control': Not supported
2011-11-18T20:02:42.851Z cpu6:3273)FSS: 4333: No FS driver claimed device 'mpx.vmhba32:C0:T0:L0': Not supported
2011-11-18T20:02:43.557Z cpu6:3273)VC: 394: Number of PEs for volume 470ca539-5df8e7f0-d25f-0019b9eac0a7 changed from 3 to 1. A VMFS volume rescan may be needed to use this volume
2011-11-18T20:02:43.590Z cpu6:3273)VC: 1449: Device rescan time 1241 msec (total number of devices 49)
2011-11-18T20:02:43.590Z cpu6:3273)VC: 1452: Filesystem probe time 1448 msec (devices probed 41 of 49)
2011-11-18T20:03:02.814Z cpu4:51414)<6>qla4xxx 0000:0f:01.1: qla4xxx_mark_device_missing: ddb[65] os[1] marked MISSING
2011-11-18T20:03:02.814Z cpu4:51414)iscsi_linux: [vmhba3: H:7 C:0 T:1] session blocked
2011-11-18T20:03:02.814Z cpu1:2049)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x2a (0x412400722b40) to dev "naa.60a98000646f6452534a675651324d37" on path "vmhba3:C0:T1:L13" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.Act:EVAL
2011-11-18T20:03:02.814Z cpu1:2049)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.60a98000646f6452534a675651324d37" state in doubt; requested fast path state update...
2011-11-18T20:03:02.814Z cpu1:2049)ScsiDeviceIO: 2305: Cmd(0x412400722b40) 0x2a, CmdSN 0x15d to dev "naa.60a98000646f6452534a675651324d37" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.
2011-11-18T20:03:13.041Z cpu5:2655)<6>qla4xxx 0000:0f:01.1: scsi7: qla4xxx_process_ddb_changed: ddb[65] os[1] marked ONLINE
2011-11-18T20:03:13.042Z cpu5:2655)iscsi_linux: [vmhba3: H:7 C:0 T:1] session unblocked
2011-11-18T20:03:13.575Z cpu7:2177)<6>qla4xxx 0000:0f:01.1: scsi7:0:1:13: ABORT ISSUED cmd=0x4124014a1800, pid=127589081, ref=1
2011-11-18T20:03:22.813Z cpu7:2177)<6>qla4xxx 0000:0f:01.1: scsi7:0:1:13: ABORT TASK - FAILED.
2011-11-18T20:03:22.813Z cpu4:2052)<6>qla4xxx 0000:0f:01.1: qla4xxx_mark_device_missing: ddb[65] os[1] marked MISSING
2011-11-18T20:03:22.813Z cpu4:2052)iscsi_linux: [vmhba3: H:7 C:0 T:1] session blocked
2011-11-18T20:03:22.813Z cpu0:2056)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.60a98000646f6452534a675651324d37" state in doubt; requested fast path state update...
2011-11-18T20:03:22.924Z cpu7:2177)<6>qla4xxx 0000:0f:01.1: scsi7:0:1:13: ABORT SUCCEEDED - cmd returned back to OS.
2011-11-18T20:03:22.975Z cpu0:617973)ScsiPath: 3478: CmdSN 0x0 to path vmhba3:C0:T1:L13 timed out: expiry time occurs 9399ms in the past
2011-11-18T20:03:23.779Z cpu3:627125)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.60a98000646f6452534a675651324d37" state in doubt; requested fast path state update...
2011-11-18T20:03:23.779Z cpu3:627125)ScsiDeviceIO: 2316: Cmd(0x412400722b40) 0x2a, CmdSN 0x15d to dev "naa.60a98000646f6452534a675651324d37" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.
2011-11-18T20:03:23.779Z cpu6:662475)BC: 1858: Failed to write (uncached) object 'naa.60a98000646f6452534a675651324d37': Timeout
2011-11-18T20:03:31.056Z cpu7:2655)<6>qla4xxx 0000:0f:01.1: scsi7: qla4xxx_process_ddb_changed: ddb[65] os[1] marked ONLINE
2011-11-18T20:03:31.056Z cpu7:2655)iscsi_linux: [vmhba3: H:7 C:0 T:1] session unblocked
2011-11-18T20:03:31.436Z cpu1:257738)ScsiCore: 1455: Power-on Reset occurred on vmhba3:C0:T1:L13
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
its on windows or linkux
_________________________________
Good luck!![]()
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I take it you have two controllres in active / active status as you state other luns are running off that controller. I'm also curious to if you failover your primary controller (The one that seems to work) Will those luns fire up properly on the secondary ? Seeing as the new luns are failing.
Possible the iSCSI initiator target in VMware is set to the wrong controller VIF? or IP or got mixed up somehow ? Silly question but figured I'd ask.