- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- MSA 2040 - VMWARE 6.7 - ReadCache
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-15-2019 09:25 AM
03-15-2019 09:25 AM
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-21-2019 07:06 AM
03-21-2019 07:06 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-21-2019 08:17 AM
03-21-2019 08:17 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-21-2019 09:47 AM
03-21-2019 09:47 AM
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 ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-21-2019 09:58 AM
03-21-2019 09:58 AM
Re: MSA 2040 - VMWARE 6.7 - ReadCache
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!
***********************************************************************************
I work for HPE

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-21-2019 10:21 AM
03-21-2019 10:21 AM
Re: MSA 2040 - VMWARE 6.7 - ReadCache
Ta,
I'll raise a support call and see where it goes,.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-27-2019 05:31 AM
03-27-2019 05:31 AM
Re: MSA 2040 - VMWARE 6.7 - ReadCache
Just an update on where I'm at with this!
I downgraded one of the ESXi hosts from 6.7 to 6.5 Build 5310538.
I then modified Pool A on the MSA 2040. I added a second Disk Group to it. I then rebooted the esxi 6.5 host. (The vmware datastores for my esxi environemtn are located on Pool A.)
On reboot the datastores loaded correctly in ESXi 6.5! Dang!
This means that the problem is ESXi 6.7. Its not compatible the MSA 2040 GL225R003 firmware. Downgrading the esxi hosts to 6.5 is going to create a huge load of problems for the existing VMs (all built in the 6.7 environment), VM hardware version, vmotion, EVC mode....a right headache!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-03-2019 04:45 AM
04-03-2019 04:45 AM
SolutionRight - this has been solved - Many thanks to Stephen Wagner and his brilliant site :
This is what I found.
ESXi 6.7 does not like it if you change the configuration of a virtual pool after it has been presented (presented and mounted by ESXi)
For example, if you are using Virtual Disk Pools which contain volumes that are presented to ESX 6.7 as Datastores and at a later date you change that pool by adding a disk group to it or a read cache to it - you will probably come across the problem that I have doucmented here (datastore will not mount on reboot of esxi 6.7 after virtual disk pool changes)
The only way you can avoid this problem is if all your disks have the same Sector Format. All the disks in the MSA should be 512n or 512e (is there any other format?)
Remember this only applies to ESXi 6.7 (In my testing 6.5 is not affected)
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP