VMware Cloud Community
neildumoran
Contributor
Contributor

ESX 6.7 purple screen

3 host running ESX 6.7 update 2 for 4 months

Suddenly in VM Ware hypervisor have error message "The ramdisk 'tmp' is full. As a result, the file /tmp/ams-sas.txt could not be written"

and

At least one corrupt resource metadata region was detected

on volume 5d2d2f93-0c25b2d0-879c-ecebb898aa64 (MSA-VM_STORAGE). Other regions of the volume

might be damaged too.

ramdisk error fix by clearing logs (or reboot host)

3 hosts no physical indication of hardware failure.

All application are running normally (we refer to vendor)

Then VM Ware ESX crash, purple screen.

1) Try update ESX to Update 3 - still ha prob

2) Try update server hardware firmware version to (Sep-2019) - still have prob.

Check HPE storage for any abnormal message - no; host server still no indication of H/W failure.

Try google and check recommendation - still no good.

VMware service request no reply for 5 hours already.

Contact HP suppport, still checking

Any idea is acceptable. Thanks

10 Replies
neildumoran
Contributor
Contributor

HP found no problem in HPE storage. Refer to VM Ware support

0 Kudos
a_p_
Leadership
Leadership

0 Kudos
Ardaneh
Enthusiast
Enthusiast

Hi

I want to share my experience.

we had 3 HPE G8 DL380 with Qlogic HBA cards. we face the same problem whenever we attempted to storage motion some VMs. we upgraded to the newer version (by that time it was ESXi U2) but the problem resisted. After lots of searches, we found out that there are some problems with drivers and upgrading the ESXi hosts cannot solve it. so we reinstalled our ESXi from scratch and the problem was gone.

0 Kudos
neildumoran
Contributor
Contributor

Hi,

Thanks for the advice.

/tmp was now not filling.

0 Kudos
neildumoran
Contributor
Contributor

Hi,

It seems our problem is similar as I notice this issue when VM was move to other location.

We also reinstall esxi with latest version, and try open and start VMs. Others OK, most will result to purple screen.

Tried to copy VMs to other location but still inside Storage as we have no available backup storage.

Start of copied  VMs OK, but not all was copied as storage disconnect during last copy.

Now storage datastore cannot be seen in esxi, but device still present --another problem

0 Kudos
daphnissov
Immortal
Immortal

Sounds like you should open a case with GSS.

0 Kudos
oneilv
Enthusiast
Enthusiast

Hi neildumoran

Did you check this link from HPE

https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00073323en_us&docLocale=en_US

Also can you please share a screenshot of the PSOD?

Also send through a list of HBA's and network cards installed on the server along with the driver and firmware versions.

Cheers,

Onil Varghese

0 Kudos
blazilla
Enthusiast
Enthusiast

Hi,

I really recommend to update the drivers, firmware and agents offered by HPE. Do you used a HPE ESXi Image, or a plain vanilla ESXi Image from VMware?

How is your MSA connected to the hosts?

Best regards Patrick https://www.vcloudnine.de
0 Kudos
vietnguyen2304
Contributor
Contributor

Hi @neildumoran,

Have you found the root cause yet? Because I have met the same problem.

Tags (2)
0 Kudos
pkvmw
VMware Employee
VMware Employee

Hi @vietnguyen2304,

please open a new discussion, explain your issue in detail there and don't hijack a thread from nearly 2 years ago.

Thanks,
Patrik

0 Kudos