Trouble adding SCSI LUN drives

[wmccarty]

Hello,

I have an Adaptec 4805SAS which I am aware is not on the supported HCL. Attached to this device I have a SAS array of 8 drives. When I create a RAID 5 array the total space is approx 1TB.

I have been trying to add this as a datastore to the available datastores. We have SQL server databases running on this ESXi 5.0 box, and would like to use this as a separate device just for the data storage, and possibly a different device for the log files.

I originally created two arrays and they were detected properly when ESXi 5.0 installed.

When I tried to copy or move a vmdk disk file to one of these drives, the device became unavailable.

We then updated the firmware on the card and attempted to make a single array totalling all avaialble space on the drives. We have been unable to add this array after repeated attempts.

The log from the VMkernel.log is as follows.

2012-02-22T17:08:16.140Z cpu6:2855)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:08:16.194Z cpu5:2855)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:08:16.202Z cpu6:2855)Vol3: 647: Couldn't read volume header from control: Invalid handle
2012-02-22T17:08:16.202Z cpu6:2855)FSS: 4333: No FS driver claimed device 'control': Not supported
2012-02-22T17:08:16.215Z cpu6:2855)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:08:16.221Z cpu7:2855)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:08:16.228Z cpu7:2855)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:08:16.230Z cpu7:2855)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:08:16.235Z cpu7:2855)FSS: 4333: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported
2012-02-22T17:08:16.291Z cpu6:2855)VC: 1449: Device rescan time 60 msec (total number of devices 8)
2012-02-22T17:08:16.291Z cpu6:2855)VC: 1452: Filesystem probe time 48 msec (devices probed 6 of 8)
2012-02-22T17:08:16.613Z cpu1:2855)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:08:16.618Z cpu1:2855)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:08:16.626Z cpu1:2855)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:08:16.632Z cpu1:2855)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:08:16.639Z cpu1:2855)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:08:16.641Z cpu1:2855)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:08:16.647Z cpu1:2855)FSS: 4333: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported
2012-02-22T17:08:16.659Z cpu1:2855)Vol3: 647: Couldn't read volume header from control: Invalid handle
2012-02-22T17:08:16.659Z cpu1:2855)FSS: 4333: No FS driver claimed device 'control': Not supported
2012-02-22T17:08:16.679Z cpu1:2855)VC: 1449: Device rescan time 14 msec (total number of devices 8)
2012-02-22T17:08:16.679Z cpu1:2855)VC: 1452: Filesystem probe time 47 msec (devices probed 6 of 8)
2012-02-22T17:19:15.406Z cpu0:5177)WARNING: UserObj: 675: Failed to crossdup fd 8, /dev/ptyp0 type CHAR: Busy
2012-02-22T17:19:15.406Z cpu0:5177)WARNING: UserObj: 675: Failed to crossdup fd 10, /dev/ptyp0 type CHAR: Busy
2012-02-22T17:19:15.406Z cpu3:5181)WARNING: UserLinux: 1340: unsupported: (void)
2012-02-22T17:31:42.753Z cpu5:5671)WARNING: UserObj: 675: Failed to crossdup fd 8, /dev/ptyp1 type CHAR: Busy
2012-02-22T17:31:42.753Z cpu5:5671)WARNING: UserObj: 675: Failed to crossdup fd 10, /dev/ptyp1 type CHAR: Busy
2012-02-22T17:31:42.753Z cpu3:5675)WARNING: UserLinux: 1340: unsupported: (void)
2012-02-22T17:37:59.229Z cpu7:5856)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:37:59.256Z cpu7:5856)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:37:59.281Z cpu5:5856)Vol3: 647: Couldn't read volume header from control: Invalid handle
2012-02-22T17:37:59.281Z cpu5:5856)FSS: 4333: No FS driver claimed device 'control': Not supported
2012-02-22T17:37:59.288Z cpu5:5856)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:37:59.295Z cpu4:5856)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:37:59.301Z cpu4:5856)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:37:59.304Z cpu4:5856)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:37:59.309Z cpu4:5856)FSS: 4333: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported
2012-02-22T17:37:59.348Z cpu5:5856)VC: 1449: Device rescan time 44 msec (total number of devices 8)
2012-02-22T17:37:59.348Z cpu5:5856)VC: 1452: Filesystem probe time 47 msec (devices probed 6 of 8)
2012-02-22T17:37:59.610Z cpu1:5856)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:37:59.615Z cpu0:5856)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:37:59.623Z cpu1:5856)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:37:59.629Z cpu0:5856)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:37:59.636Z cpu0:5856)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:37:59.638Z cpu0:5856)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-22T17:37:59.643Z cpu0:5856)FSS: 4333: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported
2012-02-22T17:37:59.647Z cpu0:5856)Vol3: 647: Couldn't read volume header from control: Invalid handle
2012-02-22T17:37:59.647Z cpu0:5856)FSS: 4333: No FS driver claimed device 'control': Not supported
2012-02-22T17:37:59.674Z cpu0:5856)VC: 1449: Device rescan time 14 msec (total number of devices 8)
2012-02-22T17:37:59.674Z cpu0:5856)VC: 1452: Filesystem probe time 49 msec (devices probed 6 of 😎

The wizard error message is as follows:
An error occured during host configuration. See the error stack for details on the cause of this problem.

Call "HostDatastoreSystem.CreateVmfsDatastore" for object "ha-datastoresystem" on ESXi "xx.xx.xx.xx" failed.
Operation failed, diagnostics report:  Unable to create Filesystem, please see VMkernel log for more details: No such device or address

This is one of many similar error messages that we are receiving for this device.

I also tried to SSH into the ESXi server and issue a partedUtil command to list devices, then create a partition to which I could mount.

The output I get from that is:

~ # partedUtil setptbl "/vmfs/devices/disks/mpx.vmhba2:C0:T0:L0" gpt "1 128 2009900000 AA31E02A400F11DB9590000C2911D1B8 128"
gpt
0 0 0 0
1 128 2009900000 AA31E02A400F11DB9590000C2911D1B8 128
~ # partedUtil delete "/vmfs/devices/disks/mpx.vmhba2:C0:T0:L0" 1
Error: Unable to open /dev/disks/mpx.vmhba2:C0:T0:L0 - unrecognised disk label.
Unable to construct disk from device /vmfs/devices/disks/mpx.vmhba2:C0:T0:L0

~ # ls /vmfs/devices/disks/
mpx.vmhba2:C0:T0:L0

~ # partedUtil getptbl "/vmfs/devices/disks/mpx.vmhba2:C0:T0:L0"
unknown
125110 255 63 2009907200

I have two basic questions:

- Does the log file and the behaviours exhibited mean that the controller card is simply not supported?

- If the card is supported, how can I get this array to become a useful datastore. I did read somewhere that you would have to reinstall ESXi?

[wmccarty]

Anyone?

[Sreejesh_D]

It looks like there is no inbuilt driver for supporting the specific Raid controller.

2012-02-22T17:37:59.643Z cpu0:5856)FSS: 4333: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported

Try adding datastore after installing the following driver for Adaptec SAS controllers. 4805 is no there in the supported list of cardsm, still you can give a try.

http://downloads.vmware.com/d/details/dt_esxi50_pmc_sierra_aacraid_5_1_7_28700/dHRAYnRAamRiZHAlJQ==

[wmccarty]

We already have another SATA Adaptec card running the aacraid driver. Is this a different driver than the one that is already supplied with ESXi 5.0?

[Sreejesh_D]

yes, its not  bundled in ESXi 5.0 image which is downloadable.

[wmccarty]

So I added the Serria driver that you had linked to, thank you for your help. I still get the same results with the card. When I use the vSphere Client and attempt to add the datastore and create the partition I get:

Call "HostDatastoreSystem.CreateVmfsDatastore" for object "ha-datastoresystem" on ESXi "192.168.2.82" failed.

In the logfile:

2012-02-29T11:41:35.149Z cpu0:3382)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-29T11:41:35.174Z cpu2:3601)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x1a (0x41240073da80) to dev "naa.600050e04e0d0f0041e60000b13f0000" on path "vmhba4:C0:T0:L0" Failed: H:0x0 D:0x4 P:0x0 Possible sense data: 0x5 0x24 0x0.Act:NONE
2012-02-29T11:41:35.174Z cpu2:3601)ScsiDeviceIO: 2316: Cmd(0x41240073da80) 0x1a, CmdSN 0xfba to dev "naa.600050e04e0d0f0041e60000b13f0000" failed H:0x0 D:0x4 P:0x0 Possible sense data: 0x5 0x24 0x0.
2012-02-29T11:41:35.179Z cpu1:3382)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-29T11:41:35.201Z cpu4:3382)LVM: 8445: Device mpx.vmhba3:C0:T0:L0:1 detected to be a snapshot:
2012-02-29T11:41:35.201Z cpu4:3382)LVM: 8452:   queried disk ID: <type 1, len 14, lun 0, devType 0, scsi 0, h(id) 14407468780664188181>
2012-02-29T11:41:35.201Z cpu4:3382)LVM: 8459:   on-disk disk ID: <type 0, len 10, lun 0, devType 0, scsi 0, h(id) 4253278860640638102>
2012-02-29T11:41:35.214Z cpu5:3382)Vol3: 647: Couldn't read volume header from control: Invalid handle
2012-02-29T11:41:35.214Z cpu5:3382)FSS: 4333: No FS driver claimed device 'control': Not supported
2012-02-29T11:41:35.222Z cpu7:3382)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-29T11:41:35.229Z cpu0:3382)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-29T11:41:35.235Z cpu6:3382)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-29T11:41:35.238Z cpu3:3382)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-29T11:41:35.243Z cpu4:3382)FSS: 4333: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported
2012-02-29T11:41:35.343Z cpu5:3382)VC: 1449: Device rescan time 53 msec (total number of devices 😎
2012-02-29T11:41:35.343Z cpu5:3382)VC: 1452: Filesystem probe time 53 msec (devices probed 6 of 😎
2012-02-29T11:41:35.673Z cpu6:3382)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-29T11:41:35.680Z cpu2:3596)ScsiDeviceIO: 2316: Cmd(0x4124007b6340) 0x1a, CmdSN 0x105c to dev "naa.600050e04e0d0f0041e60000b13f0000" failed H:0x0 D:0x4 P:0x0 Possible sense data: 0x5 0x24 0x0.
2012-02-29T11:41:35.684Z cpu2:3382)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-29T11:41:35.693Z cpu5:3382)LVM: 8445: Device mpx.vmhba3:C0:T0:L0:1 detected to be a snapshot:
2012-02-29T11:41:35.693Z cpu5:3382)LVM: 8452:   queried disk ID: <type 1, len 14, lun 0, devType 0, scsi 0, h(id) 14407468780664188181>
2012-02-29T11:41:35.693Z cpu5:3382)LVM: 8459:   on-disk disk ID: <type 0, len 10, lun 0, devType 0, scsi 0, h(id) 4253278860640638102>
2012-02-29T11:41:35.725Z cpu7:3382)Vol3: 647: Couldn't read volume header from control: Invalid handle
2012-02-29T11:41:35.725Z cpu7:3382)FSS: 4333: No FS driver claimed device 'control': Not supported
2012-02-29T11:41:35.725Z cpu7:3382)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-29T11:41:35.732Z cpu2:3382)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-29T11:41:35.738Z cpu7:3382)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-29T11:41:35.741Z cpu2:3382)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2012-02-29T11:41:35.746Z cpu2:3382)FSS: 4333: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported
2012-02-29T11:41:35.748Z cpu0:3382)VC: 1449: Device rescan time 21 msec (total number of devices 😎
2012-02-29T11:41:35.748Z cpu0:3382)VC: 1452: Filesystem probe time 53 msec (devices probed 6 of 😎

I understand that when it says Not Supported that it is saying that the driver does not support it, yet the card shows up in the Storage Adapters under the AACRAID driver as

mpx.vmhba2:C0:T0:L0

The difference with the Sirra driver and the inbuilt one is that the inbuilt one shows the card correctly as a 4800SAS series, the Sierra driver does not.

So I guess to refine my question, even if the device shows up under AACRAID, and ESXi sees the device, from the contents of the log file above where it is croaking at saying no "FS driver claimed the device" that means that the AACRAID driver has not been written to support this card. Or, does that mean that I am buying a new card, and there is nothing else I can do within SSH to ESXi to get it to work?

[Sreejesh_D · Accepted solution]

Nothing much we can do here since the inbuilt and custom drivers are not supporting the device.

I would recommend to go ahead and change the card which is in HCL.

Before that, you can try contacting VMware Tech support once. Their engineering team may be working for a driver if many customers are hit with this issue.