Start a Conversation

Unsolved

This post is more than 5 years old

T

6194

January 29th, 2013 18:00

adding lun to another storage group

I got some luns on storage group1 which is a esx cluster.

So I added one lun from this storage group to my ucs host storage group.

But after a rescan of hbas, it does not show the lun under storage but it shows it as an available lun to add and format.

any idea why?

1K Posts

January 29th, 2013 18:00

Check you ESX/ESXi versions. Also, is it a VMFS3 or VMFS5 datastore?

470 Posts

January 29th, 2013 21:00

The UCS storage group is esxi 5.1 vmfs5.

The other storage group is esxi 5.0 vmfs5

470 Posts

January 29th, 2013 23:00

But when I add a lun from the UCS storage group to the 5.0 Cluster, a rescan of the hba shows the lun under storage.

What is causing it not to work the other way?

January 30th, 2013 01:00

Can you install VSI Storage viewer and confirm if VMAX LUNs are visible from UCS hosts?

1K Posts

January 30th, 2013 05:00

Is the HLU # the same for the LUN? I don't think that will prevent you from seeing the datastore but verify that as well.

26 Posts

January 30th, 2013 06:00

Hi,

you should check the vmkernel.log file after performing a rescan operation.

And you should check the following VMware article.

ESXi 5.x hosts fail to mount VMFS5 volumes that are formatted with ATS-only capabilities

Hth,

Ralf

470 Posts

January 30th, 2013 07:00

yes I can see the clariion luns in vsi.

470 Posts

January 30th, 2013 10:00

here is what i see in vmkernel

2013-01-30T18:23:07.740Z cpu18:9173)Vol3: 692: Couldn't read volume header from control: Not supported

2013-01-30T18:23:07.740Z cpu18:9173)Vol3: 692: Couldn't read volume header from control: Not supported

2013-01-30T18:23:07.740Z cpu18:9173)FSS: 4972: No FS driver claimed device 'control': Not supported

2013-01-30T18:23:07.841Z cpu18:9173)VC: 1547: Device rescan time 57 msec (total number of devices 7)

2013-01-30T18:23:07.841Z cpu18:9173)VC: 1550: Filesystem probe time 112 msec (devices probed 6 of 7)

2013-01-30T18:26:08.915Z cpu2:9173)Vol3: 692: Couldn't read volume header from control: Not supported

2013-01-30T18:26:08.915Z cpu2:9173)Vol3: 692: Couldn't read volume header from control: Not supported

2013-01-30T18:26:08.915Z cpu2:9173)FSS: 4972: No FS driver claimed device 'control': Not supported

2013-01-30T18:26:08.937Z cpu2:9173)VC: 1547: Device rescan time 58 msec (total number of devices 7)

2013-01-30T18:26:08.937Z cpu2:9173)VC: 1550: Filesystem probe time 113 msec (devices probed 6 of 7)

2013-01-30T18:26:08.974Z cpu2:9173)Vol3: 692: Couldn't read volume header from control: Not supported

2013-01-30T18:26:08.974Z cpu2:9173)Vol3: 692: Couldn't read volume header from control: Not supported

2013-01-30T18:26:08.974Z cpu2:9173)FSS: 4972: No FS driver claimed device 'control': Not supported

2013-01-30T18:26:08.992Z cpu2:9173)VC: 1547: Device rescan time 6 msec (total number of devices 7)

2013-01-30T18:26:08.992Z cpu2:9173)VC: 1550: Filesystem probe time 26 msec (devices probed 6 of 7)

2013-01-30T18:26:09.036Z cpu2:9173)Vol3: 692: Couldn't read volume header from control: Not supported

2013-01-30T18:26:09.036Z cpu2:9173)Vol3: 692: Couldn't read volume header from control: Not supported

2013-01-30T18:26:09.036Z cpu2:9173)FSS: 4972: No FS driver claimed device 'control': Not supported

2013-01-30T18:26:09.049Z cpu2:9173)VC: 1547: Device rescan time 6 msec (total number of devices 7)

2013-01-30T18:26:09.049Z cpu2:9173)VC: 1550: Filesystem probe time 25 msec (devices probed 6 of 7)

2013-01-30T18:26:09.110Z cpu2:9173)Vol3: 692: Couldn't read volume header from control: Not supported

2013-01-30T18:26:09.110Z cpu2:9173)Vol3: 692: Couldn't read volume header from control: Not supported

2013-01-30T18:26:09.110Z cpu2:9173)FSS: 4972: No FS driver claimed device 'control': Not supported

2013-01-30T18:26:09.123Z cpu2:9173)VC: 1547: Device rescan time 6 msec (total number of devices 7)

2013-01-30T18:26:09.123Z cpu2:9173)VC: 1550: Filesystem probe time 29 msec (devices probed 6 of 7)

2013-01-30T18:26:09.635Z cpu4:9171)Vol3: 692: Couldn't read volume header from control: Not supported

2013-01-30T18:26:09.635Z cpu4:9171)Vol3: 692: Couldn't read volume header from control: Not supported

2013-01-30T18:26:09.635Z cpu4:9171)FSS: 4972: No FS driver claimed device 'control': Not supported

2013-01-30T18:26:09.661Z cpu4:9171)VC: 1547: Device rescan time 7 msec (total number of devices 7)

2013-01-30T18:26:09.661Z cpu4:9171)VC: 1550: Filesystem probe time 29 msec (devices probed 6 of 7)

tried adding this lun into another ucs host storage group and still same issue...

January 31st, 2013 02:00

From what I see, LUNs are visible at SCSI or at storage adapter level but not from datastore level.                                    

Below error seems more of filesystem error

2013-01-30T18:26:09.635Z cpu4:9171)Vol3: 692: Couldn't read volume header from control: Not supported

2013-01-30T18:26:09.635Z cpu4:9171)FSS: 4972: No FS driver claimed device 'control': Not supported

Please refer http://kb.vmware.com/kb/2014155, which talks on one of the related issue.

Also refer http://kb.vmware.com/kb/2004605

470 Posts

January 31st, 2013 21:00

Is was an error on my part. I added the wrong lun which is a RDM formatted with ntfs. So other hosts will not see it as a vmfs partition.

thnak for your help

No Events found!

Top