Newly created array not appearing in ESXi

[mattx27]

Newly created array not appearing in ESXi

HP DL380 G5

ESXi 5.5.0

Smart Array P400

I've created the array using HP's command line utility via SSH using the command on 2x300 GB drives

hpssacli ctrl slot=1 create type=ld drives=1I:1:7,1I:1:8 size=300 raid=1

Great - lights are on and all is good - do a quick status check ( note the new array is array C )

array A

physicaldrive 1I:1:5 (port 1I:box 1:bay 5, SAS, 72 GB, OK)

physicaldrive 1I:1:6 (port 1I:box 1:bay 6, SAS, 72 GB, OK)

physicaldrive 2I:1:3 (port 2I:box 1:bay 3, SAS, 72 GB, OK)

physicaldrive 2I:1:4 (port 2I:box 1:bay 4, SAS, 72 GB, OK)

array B

physicaldrive 2I:1:1 (port 2I:box 1:bay 1, SAS, 36 GB, OK)

physicaldrive 2I:1:2 (port 2I:box 1:bay 2, SAS, 36 GB, OK)

array C

physicaldrive 1I:1:7 (port 1I:box 1:bay 7, SAS, 300 GB, OK)

physicaldrive 1I:1:8 (port 1I:box 1:bay 8, SAS, 300 GB, OK)

Problem I have now is that it's not appearing in the storage, even when I re-fresh it or try to add additional storage. Is there something else I need to do to the newly created array ? On a quick google I can't see anything. I'm wondering if it's because I created the mirror with the actual size of the drives however if this was going to be a problem I'm sure it would have bombed when I created it.

[bspagna89]

Hi,

Can you verify that the Smart Array P400 card is showing up under Storage adapters?

Click the Host -> Configuration -> Storage adapters.

[mattx27]

I can confirm that - see attached screen shot.

The HOST is already running 2 VMs

[bspagna89]

Do you know if the RAID has finished initializing?

[mattx27]

I would like to think so as it was yesterday ( over 24 hours ) since I created it. I've not manually initialized it as it was all done via the HP Smart Array CLI commands via SSH. I would have thought after creating the array it would have initialized automatically ? On checking I don't see any commands to do this via the HP Smart Array CLI - Array C is the new one I created.

~ # /opt/hp/hpssacli/bin/hpssacli ctrl all show config

Smart Array P400 in Slot 1                (sn: PAFGK0L9VWC0NT)

   Internal Drive Cage at Port 1I, Box 1, OK

   Internal Drive Cage at Port 2I, Box 1, OK

   array A (SAS, Unused Space: 0  MB)

      logicaldrive 1 (205.0 GB, RAID 5, OK)

      physicaldrive 1I:1:5 (port 1I:box 1:bay 5, SAS, 72 GB, OK)

      physicaldrive 1I:1:6 (port 1I:box 1:bay 6, SAS, 72 GB, OK)

      physicaldrive 2I:1:3 (port 2I:box 1:bay 3, SAS, 72 GB, OK)

      physicaldrive 2I:1:4 (port 2I:box 1:bay 4, SAS, 72 GB, OK)

   array B (SAS, Unused Space: 0  MB)

      logicaldrive 2 (33.9 GB, RAID 1, OK)

      physicaldrive 2I:1:1 (port 2I:box 1:bay 1, SAS, 36 GB, OK)

      physicaldrive 2I:1:2 (port 2I:box 1:bay 2, SAS, 36 GB, OK)

   array C (SAS, Unused Space: 571543  MB)

      logicaldrive 3 (298 MB, RAID 1, OK)

      physicaldrive 1I:1:7 (port 1I:box 1:bay 7, SAS, 300 GB, OK)

      physicaldrive 1I:1:8 (port 1I:box 1:bay 8, SAS, 300 GB, OK)

[bspagna89]

Can you list out the configuration/arrays and confirm it was created?  Try SSH into your ESX host  (Configuration -> Security Profile -> Turn on SSH under services) and login using root/local root password.. and type the following :

esxcli storage core device list       -- You should be able to see both arrays if this is working properly.

The other alternative might be to destroy/recreate it. After that, try Add Storage -> Disk/LUN -> See if it shows up.

[mattx27]

This is what I get on that - note I do have two VMs running off this HOST already.

~ # esxcli storage core device list

mpx.vmhba1:C0:T1:L0

   Display Name: Local VMware Disk (mpx.vmhba1:C0:T1:L0)

   Has Settable Display Name: false

   Size: 34699

   Device Type: Direct-Access

   Multipath Plugin: NMP

   Devfs Path: /vmfs/devices/disks/mpx.vmhba1:C0:T1:L0

   Vendor: VMware

   Model: Block device

   Revision: 1.0

   SCSI Level: 2

   Is Pseudo: false

   Status: on

   Is RDM Capable: false

   Is Local: true

   Is Removable: false

   Is SSD: false

   Is Offline: false

   Is Perennially Reserved: false

   Queue Full Sample Size: 0

   Queue Full Threshold: 0

   Thin Provisioning Status: unknown

   Attached Filters:

   VAAI Status: unsupported

   Other UIDs: vml.0000000000766d686261313a313a30

   Is Local SAS Device: false

   Is Boot USB Device: false

   No of outstanding IOs with competing worlds: 32

mpx.vmhba1:C0:T0:L0

   Display Name: Local VMware Disk (mpx.vmhba1:C0:T0:L0)

   Has Settable Display Name: false

   Size: 209924

   Device Type: Direct-Access

   Multipath Plugin: NMP

   Devfs Path: /vmfs/devices/disks/mpx.vmhba1:C0:T0:L0

   Vendor: VMware

   Model: Block device

   Revision: 1.0

   SCSI Level: 2

   Is Pseudo: false

   Status: on

   Is RDM Capable: false

   Is Local: true

   Is Removable: false

   Is SSD: false

   Is Offline: false

   Is Perennially Reserved: false

   Queue Full Sample Size: 0

   Queue Full Threshold: 0

   Thin Provisioning Status: unknown

   Attached Filters:

   VAAI Status: unsupported

   Other UIDs: vml.0000000000766d686261313a303a30

   Is Local SAS Device: false

   Is Boot USB Device: false

   No of outstanding IOs with competing worlds: 32

mpx.vmhba32:C0:T0:L0

   Display Name: Local USB Direct-Access (mpx.vmhba32:C0:T0:L0)

   Has Settable Display Name: false

   Size: 7512

   Device Type: Direct-Access

   Multipath Plugin: NMP

   Devfs Path: /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0

   Vendor: Lexar

   Model: JumpDrive

   Revision: 1100

   SCSI Level: 2

   Is Pseudo: false

   Status: on

   Is RDM Capable: false

   Is Local: true

   Is Removable: true

   Is SSD: false

   Is Offline: false

   Is Perennially Reserved: false

   Queue Full Sample Size: 0

   Queue Full Threshold: 0

   Thin Provisioning Status: unknown

   Attached Filters:

   VAAI Status: unsupported

   Other UIDs: vml.0000000000766d68626133323a303a30

   Is Local SAS Device: false

   Is Boot USB Device: true

   No of outstanding IOs with competing worlds: 32

mpx.vmhba0:C0:T0:L0

   Display Name: Local TEAC CD-ROM (mpx.vmhba0:C0:T0:L0)

   Has Settable Display Name: false

   Size: 0

   Device Type: CD-ROM

   Multipath Plugin: NMP

   Devfs Path: /vmfs/devices/cdrom/mpx.vmhba0:C0:T0:L0

   Vendor: TEAC

   Model: DV-W28E-RW

   Revision: G.B2

   SCSI Level: 5

   Is Pseudo: false

   Status: on

   Is RDM Capable: false

   Is Local: true

   Is Removable: true

   Is SSD: false

   Is Offline: false

   Is Perennially Reserved: false

   Queue Full Sample Size: 0

   Queue Full Threshold: 0

   Thin Provisioning Status: unknown

   Attached Filters:

   VAAI Status: unsupported

   Other UIDs: vml.0005000000766d686261303a303a30

   Is Local SAS Device: false

   Is Boot USB Device: false

   No of outstanding IOs with competing worlds: 32

~ #

[mattx27]

I've destroyed the logical drive and re-created it - now showing:

   array C (SAS, Unused Space: 0  MB)

      logicaldrive 3 (279.4 GB, RAID 1, OK)

      physicaldrive 1I:1:7 (port 1I:box 1:bay 7, SAS, 300 GB, OK)

      physicaldrive 1I:1:8 (port 1I:box 1:bay 8, SAS, 300 GB, OK)

But it's not showing up, even when I go to  Add Storage --> Disk/LUN

This is really really odd.

[bspagna89]

Try performing a rescan all? (Storage - > Rescan all)

[mattx27]

Done that, still the same.  :-(

[bspagna89]

Unfortunately, not the best answer but I think the only other option is to try restarting the host and seeing if that has any affect. Probably not doable which I understand..

Can you try running this again :

esxcli storage core device list

lets see what we get..

[mattx27]

Already did that and it only still sees the first two logical drives and not the newly created one :smileycry:

I agree - I think only a reboot now to see if this kicks in after that - I'll arrange some downtime over the weekend.

Many thanks for your help so far - the esxcli storage core device list is handy to know for future reference + my SSH skills for removing and creating arrays via the HP command line utility have improved.

[bspagna89]

Cool. Let us know how it goes.

Also, check this out for more commands on HP Command line - HP Smart Array CLI commands on ESXi | Kalle's playground

Mark an answer helpful if you may  :smileyhappy:.

[mattx27]

That's the very page I was getting my commands from.The only thing missing was the 'force' when removing the logical drive.

Now i need to find out how to stop getting alerts from other threads I have not subscribed to even though I've tuned off everything in my profile !!

[bspagna89]

mattx27 wrote:

I would like to think so as it was yesterday ( over 24 hours ) since I created it. I've not manually initialized it as it was all done via the HP Smart Array CLI commands via SSH. I would have thought after creating the array it would have initialized automatically ? On checking I don't see any commands to do this via the HP Smart Array CLI - Array C is the new one I created.

~ # /opt/hp/hpssacli/bin/hpssacli ctrl all show config

Smart Array P400 in Slot 1                (sn: PAFGK0L9VWC0NT)

   Internal Drive Cage at Port 1I, Box 1, OK

   Internal Drive Cage at Port 2I, Box 1, OK

   array A (SAS, Unused Space: 0  MB)

      logicaldrive 1 (205.0 GB, RAID 5, OK)

      physicaldrive 1I:1:5 (port 1I:box 1:bay 5, SAS, 72 GB, OK)

      physicaldrive 1I:1:6 (port 1I:box 1:bay 6, SAS, 72 GB, OK)

      physicaldrive 2I:1:3 (port 2I:box 1:bay 3, SAS, 72 GB, OK)

      physicaldrive 2I:1:4 (port 2I:box 1:bay 4, SAS, 72 GB, OK)

   array B (SAS, Unused Space: 0  MB)

      logicaldrive 2 (33.9 GB, RAID 1, OK)

      physicaldrive 2I:1:1 (port 2I:box 1:bay 1, SAS, 36 GB, OK)

      physicaldrive 2I:1:2 (port 2I:box 1:bay 2, SAS, 36 GB, OK)

   array C (SAS, Unused Space: 571543  MB)

      logicaldrive 3 (298 MB, RAID 1, OK)

      physicaldrive 1I:1:7 (port 1I:box 1:bay 7, SAS, 300 GB, OK)

      physicaldrive 1I:1:8 (port 1I:box 1:bay 8, SAS, 300 GB, OK)

Hmm.. Wait a sec.. Look at Array C..

SAS unused space is 57153MB .. That wouldn't be correct if you configured the two drives as RAID 1.

Also, have a look at logical drive 3 - 298 MB?? That should be like 279GB. Can you try destroying and recreating this logical disk ? It doesn't match the other logical drives.

[markzz]

The old P400 array controller has a couple of bugs.. These are not necessarily pertinent to the issue you seeing but I'll mention it..

Ensure your P400 firmware is at 7.22. If you use a higher version (7.23 or 7.24) of firmware you will not be able to set the boot volume from within the array firmware (important if you ever rebuild) There is however a configuration tool available from HP, it's a boot style environment..

I've personally never had much success with the CLI Array configuration interface..

I know this is not what you want to hear but a reboot of the host, go into the array bios "F8" and view your logical volume.. maybe even delete array "C" and recreate it. !

It will be quick and quite definitive. You'll know for sure your raid and logical volume are setup.

Just my 2 bob worth

[mattx27]

On checking the level of firmware ( if I'm looking at the correct place ) - it seems the level is way beyond what you suggest it should be - 5.20

I'll see if I can get hold of the version you suggest - just hope I can update it in one hit without having to go through ones before it.....

[a_p_]

Just in case that's interesting for you, you may take a look at VMware Front Experience: How to run the HP Online ACU CLI for Linux in ESXi 4.x where the author did some tests and mentioned "However, ESXi would not pick up the changed disk size, so I was not able to grow the VMFS volume without rebooting the host.".

André

[markzz]

Hey Matt

I'd suggest getting the server updated firmware wise..P400 firmware version 5.20 is very old..

If I recall firmware DVD version 9.3 will update everything to a supported level which complies with ESXi 5u3 "HP Release or VMWare release ". (although I'd suggest updating the ILO firmware to 2.25 after running the firmware DVD)

Burn the ISO to a DVD. (or mount the ISO from ILO)

Put it into the DVD drive on the server and reboot it..

You can then either select what is updated or let it install all firmware updates.. either way you should install all suggested updates as they are tested to be interoperable..

If your booting from the ISO via ILO don't update the ILO bios until afterwards..

[mattx27]

Thanks - I'm currently working out of an Office in the US so won't be back in the UK until next week, I'll do a quick search for the firmware DVD and will start to download it so at least it's then ready.

[mattx27]

I'm pulling my hair out with this now. I restarted HOST and great I can see the partition. Tried to add it and it errors with:

Call "HostDatastoreSystem.QueryVmfsDatastoreCreateOptions" for object "ha-datastoresystem" on ESXi "esxi-lon02" failed.

On some quick reading up I'm informed to delete the partition using PartedUtil however, every command I give on this just creates more problems. Running partedUtil getptbl "/vmfs/devices/disks/mpx.vmhba1:C0:T2:L0" brings up:

Error: Could not stat device /vmfs/devices/disks/mpx.vmhba1:C0:T2:l0 - No such file or directory.

Unable to get device /vmfs/devices/disks/mpx.vmhba1:C0:T2:l0

The name of the disk is correct as I checked it when trying to add it as storage and if I runL ls /vmfs/devices/disks/ I get this output which clearly shows you its the correct name:

mpx.vmhba1:C0:T0:L0	vml.0000000000766d686261313a303a30
mpx.vmhba1:C0:T0:L0:1	vml.0000000000766d686261313a303a30:1
mpx.vmhba1:C0:T1:L0	vml.0000000000766d686261313a313a30
mpx.vmhba1:C0:T1:L0:1	vml.0000000000766d686261313a313a30:1
mpx.vmhba1:C0:T2:L0	vml.0000000000766d686261313a323a30
mpx.vmhba1:C0:T2:L0:1	vml.0000000000766d686261313a323a30:1
mpx.vmhba1:C0:T2:L0:2	vml.0000000000766d686261313a323a30:2
mpx.vmhba32:C0:T0:L0	vml.0000000000766d68626133323a303a30
mpx.vmhba32:C0:T0:L0:1	vml.0000000000766d68626133323a303a30:1
mpx.vmhba32:C0:T0:L0:5	vml.0000000000766d68626133323a303a30:5
mpx.vmhba32:C0:T0:L0:6	vml.0000000000766d68626133323a303a30:6
mpx.vmhba32:C0:T0:L0:7	vml.0000000000766d68626133323a303a30:7
mpx.vmhba32:C0:T0:L0:8	vml.0000000000766d68626133323a303a30:8

If anyone can help me I would appreciate it. I can't believe I'm having all these problems when all I want to do is simply add more storage. I'm left wondering what hoops I now need to run though to get ESXi to see this storage.

[bspagna89]

Hey Matt,

Sorry you're having these issues. Let's see what we can do here.

Can you SSH into the host and run fdisk -lu /vmfs/devices/disks/devicename (I think you bolded the disk which is mpx.vmhba1:C0:T2:L0  ) -- replace devicename with that.

It should come back and say that its either valid or invalid. Here is an example of mine :

Found valid GPT with protective MBR; using GPT

Disk /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0: 1957887 sectors, 1911K

Logical sector size: 512

Disk identifier (GUID): 176b136a-17dc-4fef-b2dd-a6b28956a46b

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 1957853

Let me know what you get.

[mattx27]

Here is the output:

***

*** The fdisk command is deprecated: fdisk does not handle GPT partitions.  Please use partedUtil

***

Disk /vmfs/devices/disks/mpx.vmhba1:C0:T2:L0: 299.9 GB, 299966445568 bytes

255 heads, 63 sectors/track, 36468 cylinders, total 585871964 sectors

Units = sectors of 1 * 512 = 512 bytes

                                   Device Boot      Start         End      Blocks  Id System

/vmfs/devices/disks/mpx.vmhba1:C0:T2:L0p1   *        2048      718847      358400   7 HPFS/NTFS

Partition 1 does not end on cylinder boundary

/vmfs/devices/disks/mpx.vmhba1:C0:T2:L0p2          718848  2343483391  1171382272   7 HPFS/NTFS

Partition 2 does not end on cylinder boundary

I'm assuming the issue is the Partition 2 and 1 does not end on cylinder boundary ?

Does this mean there are 2 partitions on the disk when there should only be 1 ?

[a_p_]

The issue is likely that the partitions exist at all. Unless you need these NTFS partitions, take a look at http://kb.vmware.com/kb/1008886 (section "Clearing partitioning information in ESXi using the DD utility") to see whether this solves the issue.

André

[mattx27]

Done it !! Had to use Fdisk. Once I had removed the partition I then tried to add the storage again and this time it took !! At last !!! Very happy   :-)

Thanks for your help.

/dev/disks # fdisk -u /vmfs/devices/disks/mpx.vmhba1:C0:T2:L0

***

*** The fdisk command is deprecated: fdisk does not handle GPT partitions.  Please use partedUtil

***

The number of cylinders for this disk is set to 36468.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): d

Partition number (1-4): 1

Command (m for help): d

Selected partition 2

Command (m for help): 2

2: unknown command

Command Action

a       toggle a bootable flag

b       edit bsd disklabel

c       toggle the dos compatibility flag

d       delete a partition

l       list known partition types

n       add a new partition

o       create a new empty DOS partition table

p       print the partition table

q       quit without saving changes

s       create a new empty Sun disklabel

t       change a partition's system id

u       change display/entry units

v       verify the partition table

w       write table to disk and exit

x       extra functionality (experts only)

Command (m for help): w

The partition table has been altered.

Calling ioctl() to re-read partition table

/dev/disks # fdisk -lu

***

*** The fdisk command is deprecated: fdisk does not handle GPT partitions.  Please use partedUtil

***

Found valid GPT with protective MBR; using GPT

Disk /dev/disks/mpx.vmhba32:C0:T0:L0: 15384576 sectors, 14.6M

Logical sector size: 512

Disk identifier (GUID): b2b8f66f-3dc1-4180-9622-f15de631db88

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 15384542

Number  Start (sector)    End (sector)  Size       Code  Name

   1              64            8191        8128   0700

   5            8224          520191        499K   0700

   6          520224         1032191        499K   0700

   7         1032224         1257471        219K   0700

   8         1257504         1843199        571K   0700

Disk /dev/disks/mpx.vmhba1:C0:T2:L0: 299.9 GB, 299966445568 bytes

255 heads, 63 sectors/track, 36468 cylinders, total 585871964 sectors

Units = sectors of 1 * 512 = 512 bytes

                          Device Boot      Start         End      Blocks  Id System

Found valid GPT with protective MBR; using GPT

Disk /dev/disks/mpx.vmhba1:C0:T1:L0: 71065440 sectors, 67.7M

Logical sector size: 512

Disk identifier (GUID): 61e9575b-efa5-462c-afed-9f6367755dfb

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 71065406

Number  Start (sector)    End (sector)  Size       Code  Name

   1            2048        71063551       67.7M   0700

Found valid GPT with protective MBR; using GPT

Disk /dev/disks/mpx.vmhba1:C0:T0:L0: 429925920 sectors,  410M

Logical sector size: 512

Disk identifier (GUID): 2f7deffd-5579-4684-8f2e-625aeb688044

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 429925886

Number  Start (sector)    End (sector)  Size       Code  Name

   1            2048       429924351        410M   0700

[l3n0x]

Hi Chaps!

Sorry for bringing up an old thread, but I have the same issue.

HP DL380G7 ESXi HPE 6.0u3. If I create an array on the running host with ssacli it won't show up until I reboot the host. This is somewhat frustrating right now, as I'd like to test different raid levels with different amount of disks added to the array, while with some production VM's running on another controller in the machine. Is there a solution NOT TO reboot the host after creating a new array?

It's a P411 with an MSA60. But back in time I've experienced the same issue with the integrated P410i and the local drives - it's just that now I can't tolerate it anymore:D

Just to add some "fun" to the story, sometimes, if the stars are right, I can delete an array and recreate another one - even with a different raid level, and it would show up - most of the times not though.

I've done all the obvious, like rescanning the hba and so.

Cheers