topic Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows) in MSA Storage

MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

Grishko — Fri, 15 Dec 2017 05:52:20 GMT

Good day!

I have a MSA P2000 FC/iSCSI.

I created a vdisk and volume and try to connect it to VMware ESXi. The ESXi host sees this volume But when I try to create a datastore on it, I get an error:

"Failed to create vmfs datastore - cannot change the host configuration."

I tried to do this operation with different vdisks and volumes, the result is the same - an error.

Then I tried to add a volume on iSCSI in a machine with Windows. The volume appeared in Disk ManagementBut when I try to initialize it everything hangs and I get an input-output error.

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

Grishko — Fri, 15 Dec 2017 06:01:06 GMT

I tried this solution (for VMware ESXi):

https://www.webbosworld.co.uk/?p=610

Call “HostDatastoreSystem.QueryVmfsDatastoreCreateOptions” for object “ha-datastoresystem” on ESXi “host ip” failed.
Turns out the HP controller hadn’t initialized the array or written any data to it, so it had some GPT type partitions which VMware couldn’t write to (from what I can understand anyway!). Fortunately we were able to use partedUtil to resolve this –

Within the vSphere client under Configuration – Security Profile start the ESXi Shell and SSH services
Use a terminal program of your choice (e.g. Putty or XShell) and connect to the ESXi server
Find the Disk ID for the array (cd /dev/disks then ls)
Run the following command to partition them –partedUtil mklabel /dev/disks/diskid msdos
All Done!

But this did not work (Connection timed out during write on the iSCSI disk):

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

SUBHAJIT KHANBARMAN_1 — Fri, 15 Dec 2017 11:12:31 GMT

you haven't mentioned full details of the P2000 box like what firmware it's running with, if additional drive enclosure present, what type of drive installed and what type of firmware running on them.......if volume can be seen in host then generally it's not storage issue but still I would suggest if you can share the store.log file then may be I can check if any issue at the MSA or at the block level

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

Grishko — Fri, 15 Dec 2017 13:23:51 GMT

Just updated the firmware to the latest:

But the problem is not solved:

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

SUBHAJIT KHANBARMAN_1 — Fri, 15 Dec 2017 13:32:22 GMT

have you tried to create two separate vdisks given ownership to both controllers - may be to figure out if the issue related to any controller specific?

have you tried manually verify vdisk command to check if any block level issue?

Is it possible to share the MSA log file ?

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

Grishko — Mon, 11 Mar 2024 08:35:40 GMT

My disks:

[Moderator edit: Erased the confidential info.]

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

SUBHAJIT KHANBARMAN_1 — Tue, 19 Mar 2024 07:21:28 GMT

it looks to me all are unsupported drives for P2000 except one as per the MSA drive matrix as below,

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00052032en_us

Only drive with model number EG0300FCSPH supported drive but firmware version old. Please find the link to get latest firmware ( I have shared both fla and exe file for your help) ,

https://support.hpe.com/hpsc/swd/public/detail?sp4ts.oid=null&swItemId=MTX_20191725476e453cbc7d2e3aca&swEnvOid=4184

https://support.hpe.com/hpsc/swd/public/detail?sp4ts.oid=null&swItemId=MTX_2d235f9f17f54553a800ecc416&swEnvOid=4184#

My suggestion would be start using HPE supported drives in order to avoid any issue further

[Moderator edit: Updated the broken link. You may also refer to https://support.hpe.com/]

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

Grishko — Fri, 15 Dec 2017 15:58:17 GMT

Thank you for your answer!

But the firmware update on the HP drive fails:

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

Grishko — Fri, 15 Dec 2017 15:59:22 GMT

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

Grishko — Fri, 15 Dec 2017 16:04:13 GMT

--------------------------------------------------------------------------- Setup Session Beginned on 15.12.2017 - 18:49:56 --------------------------------------------------------------------------- Command Line Parameters Given: Controller IP is :10.0.20.71 Beginning Interactive Session... Name: Firmware Flash Component for Windows - HPE MSA 1040/2040 and P2000 G3 300GB, 450GB, 600GB and 900GB 6G SAS 10K rpm SFF Drive Models (EG0300FCSPH, EG0450FCSPK, EG0600FCSPL and EG0900FCSPN) New Version: HPD2 The software is installed but is not up to date. Current Version: HPD0 Device flash unsuccessful! - EG0300FCSPH : disk:1:8 Detailed log in :MSA2000_10_0_20_71.log The operation was not successful. --------------------------------------------------------------------------- Session Ended on 15.12.2017 - 18:58:37 ---------------------------------------------------------------------------

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

SUBHAJIT KHANBARMAN_1 — Fri, 15 Dec 2017 16:09:18 GMT

I hope you tried from both controllers and both from SMU and CLI/FTP method........Have you tried HP_EG0300FCSPH_HPD2.fla ?

if all are failed then better to log case with HPE support........next troubleshooting will be based on logs or may be some support engineer will look into your system by taking remote access

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

Grishko — Mon, 11 Mar 2024 08:39:24 GMT

The firmware on the disk has been successfully updated, but the problem is still not solved

: (((

[Moderator edit: Removed the confidential info.]

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

Grishko — Fri, 15 Dec 2017 16:30:33 GMT

Our logs:

https://www.dropbox.com/s/69w6i67l0wm85qp/store.zip

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

SUBHAJIT KHANBARMAN_1 — Fri, 15 Dec 2017 16:41:21 GMT

it looks like same volume presented to both Windows as well as ESX server with same LUN ID..........this is not correct.........please remove all mappings and present only to Windows host.............then initialize the volume at Windows...............please capture screenshots step by step and in english so that everyone can understand...............

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

Grishko — Mon, 11 Mar 2024 08:42:14 GMT

23456789

[Moderator edit: Removed the confidential info.]

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

Grishko — Fri, 15 Dec 2017 18:12:04 GMT

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

Grishko — Fri, 15 Dec 2017 18:16:33 GMT

thank you for your help!
Sorry, I do not have an English version of Windows Now.

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

Torsten. — Fri, 15 Dec 2017 19:49:42 GMT

Try GPT instead of MBR.

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

ifit — Sat, 16 Dec 2017 04:50:35 GMT

@Torsten. "partedUtil setptbl /vmfs/devices/disks/<id_disk> msdos" and "partedUtil mklabel /dev/disks/<id_disk> msdos" didn't help us.

Re: MSA P2000 iSCSI volume is not initialized (not in the VMWare, not in Windows)

ifit — Sat, 16 Dec 2017 05:29:15 GMT

it doesn't work when i initialize with mbr or gpt. No difference.