MSA Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

MSA 2040 - VMWARE 6.7 - ReadCache

 
Highlighted
TigerRool10-1
Occasional Advisor

MSA 2040 - VMWARE 6.7 - ReadCache

Hi There

Just in case anyone else has this trouble.  I added a read-cache (SSD disk) to Pool A on my MSA 2040.  Pool A held the datastore for my VMWARE 6.7 environment.  Pool A had been up and running for months.  I decided to add the read cache to improve read perfromance (as best practice suggests).

As a test I rebooted one of the esxi hosts after doing this.  The datastore would no longer mount. The vmkernel log showed the error "Invalid physDiskBlockSize 512".

After much faffing about - I decided to remove the read-cache - the Datastore mounted correctly.

FYI.

fresh
5 REPLIES 5
Navaneetha1
HPE Pro

Re: MSA 2040 - VMWARE 6.7 - ReadCache

TigerRool10-1 , 

I understand your concern. However , Read cahce is an extension of controller cache , addition or deletion of read cache should not affect data access. 
Also , VMware 6.7 is not supported on MSA 2040. 

Please refer to the below link for the list of supported OS
https://downloads.hpe.com/pub/softlib2/software1/pubsw-linux/p1158764188/v144456/723983-006.html

I am an HPE Employee

Accept or Kudo

TigerRool10-1
Occasional Advisor

Re: MSA 2040 - VMWARE 6.7 - ReadCache

Hi There and thanks for replying

The firmware mentioned,GL225R003, was release in December 2017. (We are using that version)

ESXi 6.7 was not released until April 2018.....so it would have been impossible for the MSA firmware doucment to be aware of esxi 6.7

Having said that would you think that a firmware upgrade is required ?  GL225R003 is the latest version.

regards

 

fresh
TigerRool10-1
Occasional Advisor

Re: MSA 2040 - VMWARE 6.7 - ReadCache

Status Update - I added a new disk group to Pool A.

Pool A already holds the two esxi DataStores - I rebooted one of my ESXI hosts - Bang!  the DataStores will no longer mount.

Looking in vmkernel.log I see the following message


2019-03-21T16:09:32.361Z cpu7:2097364)WARNING: Vol3: 3102: XXXXXX1/5c91215c-80529b43-df3a-5cb901cf9580: Invalid physDiskBlockSize 512

2019-03-21T16:09:22.301Z cpu2:2097364)FSS: 6092: No FS driver claimed device '5c91218e-9ca78e9c-4f5d-5cb901cf9580': No filesystem on the device

 

Is this problem caused by an incompatibility between the MSA Firmware GL225R003 and ESXi 6.7 ?

fresh

Re: MSA 2040 - VMWARE 6.7 - ReadCache

@TigerRool10-1 

This is nothing to do with MSA I think. I just searched in Google and found many links where I see after reboot of ESX6.7 Datastore missing or got corrupted. Looks like some bug in ESX6.7

https://communities.vmware.com/thread/597817

https://communities.vmware.com/thread/597513

https://www.reddit.com/r/vmware/comments/9j8k6o/esxi_vmfs6_datastore_corruption_after_host_reboot/

 

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

***********************************************************************************

TigerRool10-1
Occasional Advisor

Re: MSA 2040 - VMWARE 6.7 - ReadCache

Ta,

I'll raise a support call and see where it goes,.

fresh