[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


Force ESXi 6.0 to check / update status of Degraded Disk as presented by PERC

Posted on 2016-11-03
Medium Priority
Last Modified: 2016-11-23
Hello experts,

I have a Dell PowerEdge R530 running ESXi 6.0.0 Update 2 (Build 4192238).
It has 4 drives in a RAID10 on the PERC H730.
One drive went bad and of course the status switched to Degraded. I replaced the drive, the rebuild completed, and the DRAC now shows all 4 drives green and OK (not in rebuilding status, no predicted failures, all normal, etc), and the RAID10 itself is back to healthy (no longer showing degraded in the DRAC).
However, in ESXi it still shows as Degraded and I can't seem to find anything that will get it to go back to normal.
The array hasn't been in Degraded status (according to the DRAC itself) for well over 24 hours now.
I've tried rebooting the Host multiple times. I've even tried completely unplugging both PSU for about 10 minutes and doing a cold boot.

Is there some command you can enter in esxcli to force it to check/update the status of a disk that was previously reporting as degraded?

Screenshot of Degraded disk status in ESXi
Question by:EndTheFed
  • 5
  • 3
LVL 124
ID: 41872668
Restart vCenter Server service you are using the Dell OEM version of ESXi ?

Also reset the logs on the server. (at the Dell POST)

Author Comment

ID: 41872784
Thanks for the quick reply Andrew.
No vCenter, this is a standalone Host with Dell OEM version of ESXi.
I did clear the System Event Log (DRAC, Server, Logs, System Event Log, Clear Log)
However I noticed the SEL is separate from the Lifecycle Controller (LC) log.
When looking at the LC log the errors are still in there. I can't find a way to clear the LC log

Author Comment

ID: 41873046
Have you seen this issue before? Do you believe the problem is that the errors still exist (albeit in the past) in the Lifecycle Controller logs? I think I may have found how to clear them but you basically have to completely delete all config on the server and reset to factory defaults...
Let me know if you still think that's the route to go.

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

LVL 124
ID: 41873083
I have seen this before, but usually if you reset the logs from Client, e.g. reset sensors, it works.

BUT only if you have the Dell OEM ESXi version.

Author Comment

ID: 41887886
I did the full reset to factory defaults, cleared the lifecycle controller log and config, bios, system log, wiped all drives, deleted the raid from the perc, basically started over. Still showing as 'Normal, Degraded' in ESXi somehow, yet just as before PERC showing all green. At this point I'm thinking it may be a bug in the build I'm on.
LVL 124
ID: 41887917
Using the Dell OEM version ?

Accepted Solution

EndTheFed earned 0 total points
ID: 41893108
Yes, I had replied this is the Dell OEM version but I should have also mentioned that in the initial question.
I can now confirm this is an issue with this specific build from Dell.
This is not an issue when running: VMware-VMvisor-Installer-6.0.0.update02-3620759.x86_64-Dell_Customized-A02.iso
It does occur when running: VMware-VMvisor-Installer-6.0.0.update02-4192238.x86_64-Dell_Customized-A03.iso

Tested on two separate hosts to verify. Haven't witnessed any other bugs or issues with local storage other than the mis-reporting of being Degraded. Guess I'll just use DRAC to keep an eye on RAID status.

Thank you for your time Andrew

Author Closing Comment

ID: 41898870
able to confirm issue with this build of Dell customized version of ESXi

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
In this article we will learn how to backup a VMware farm using Nakivo Backup & Replication. In this tutorial we will install the software on a Windows 2012 R2 Server.
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …
Teach the user how to use create log bundles for vCenter Server or ESXi hosts Open vSphere Web Client: Generate vCenter Server and ESXi host log bundle:  Open vCenter Server Appliance Web Management interface and generate log bundle: Open vCenter Se…

834 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question