cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
804
Views
0
Helpful
1
Replies

HyperFlex HX Data Platform 4.5(2a) Matrix: SD card issue

Nilay Patel
Level 1
Level 1

Issue: After upgraded HX to matrix 4.5(2a), ESXi loose access to storage but HX storage connected & ruining VMs working normal beside HX stCtlVM vm on that host. stCtlVM goes down for that host

 

Setup: All flash M4 nodes - upgraded from matrix 4.0(2d) | Connected Partition Over USB To Host | SC Card

 

https://www.cisco.com/c/en/us/td/docs/hyperconverged_systems/HyperFlex_HX_DataPlatformSoftware/release-guidelines-and-support-timeline/b-recommended-hx-data-platform-sw-releases/m-software-requirements-4-5.html

Upgrades to ESXi 7.0 U1 and U2 are not recommended on servers booting from SD cards. For more information

we are running ESXi 7U2A

Tried but work around is not working(SD card access issue with 7U2A fixed in 7U2C) https://kb.vmware.com/s/article/83376

 

Ones ESXi loose access to own storage where os running following symptoms coming up

Running command df -h from CLI will get stuck, or fail, for the LOCKER mount (VMFS-L partition)
Checking the hosts logfile /var/log/vmkernel.log, you’ll notice entries similair to this

 

from ESXi VMKernel Logs
2021-10-30T11:48:05.813Z cpu13:2097218)ScsiDeviceIO: 4315: Cmd(0x45b94248b6c0) 0x28, cmdId.initiator=0x4305fdccb8c0 CmdSN 0x1 from world 2374903 to dev "mpx.vmhba32:C0:T0:L0" failed H:0x5 D:0x0 P:0x0 Cancelled from device layer. Cmd count Active:1

2021-10-30T11:48:05.813Z cpu13:2097218)Queued:1

2021-10-30T11:48:05.813Z cpu7:2374903)VFAT: 5144: Failed to get object 36 type 2 uuid 61658d94-3795c530-dc04-0025b5f0a103 cnum 0 dindex fffffffecdate 0 ctime 0 MS 0 :Timeout

2021-10-30T11:48:05.868Z cpu45:2375242)ALERT: Bootbank cannot be found at path '/bootbank'

1 Accepted Solution

Accepted Solutions

Nilay Patel
Level 1
Level 1

Temporary fix is scan storage using this command & put affected host in maintenance mode & reboot it

1. run this 1st
#esxcfg-rescan -d vmhba32

2. put affected host in maintenance

3. reboot the host

View solution in original post

1 Reply 1

Nilay Patel
Level 1
Level 1

Temporary fix is scan storage using this command & put affected host in maintenance mode & reboot it

1. run this 1st
#esxcfg-rescan -d vmhba32

2. put affected host in maintenance

3. reboot the host

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: