Monthly Archives: October 2014

Failing/Failed Disk And Detailed Information From HPACUCLI

Today I was alerted by vCenter with a yellow, “Host Storage Status” alarm.
diskalert

Clicking the ESXi host in the alert I find from the description that I can check the Hardware Status tab of the host for more details
diskalertdetail

I see that the disk is failing and that RAID is in “Interim Recovery”.  This doesn’t give me much information about the failing disk though.  Maybe in HP ILO I can find more information?  Nope, ILO doesn’t seem to have any information about the disks in the host.  According to the ILO System Information, everything looks just fine.
nodiskilo

I called to open a ticket with HP and while on the phone the support technician mentioned a diagnostic tool called HPACUCLI.  If you installed your host a HP customized ESXi image, then this should be there for you.

SSH into your host then type cd opt\hp\hpacucli\bin.  If you type ls you should see the script called “hpacucli”.  Type ./hpacucli and then press “Enter”.  You should see something about detecting controllers and you should be at a new prompt.
hpacucli1

Type controller all diag file=/tmp/adu1.zip and then press “Enter”.
hpacucli2

Now you will need a program like WinSCP that will get the newly created zip file off the host.  Connect to the host with WinSCP and then navigate to the /tmp folder.  Click on the adu1.zip file and the click “Download”.
tmpadu

Looking into the zip file we see four files; double click on “ADUReport.htm”.  The report should open into your browser and should have a lot of information.  Towards the top of my report I see that the drive has failed and if I scroll down I can actually get some in depth information about the drive.  Things like the model and Serial.
Drivefaileddrivefailed2

Can’t power on VM in Workstation 10 after Windows 8.1 October Rollup KB2995388

This issue has been fixed with the release of VMware Workstation 10.0.4.  VMware recommends that if you made changes to the config.ini that you remove the entry or change the value to “FALSE”.  The Workstation download can be found here.

When powering on a VM in Workstation 10 after rollup KB2995388 I see the following.

workstationerror

VMware is aware of the issue it would seem and there are three workarounds so far.  VMware official blog has this about it.

1.  Uninstall KB2995388 (This is an optional update).
2.  Edit the config.ini found in C:\ProgramData\VMware\VMware Workstation         and add the line:  vmmon.disableHostParameters = “TRUE”
3.  This is untested by me but it is reported that if you open Workstation in                   administrative mode (with admin rights), that it won’t have the problem.

Reboot your computer and your VMs should work again.

I did notice after making the change that the first time I start my VMs I get:
devicenotavailable notrespondingdevice

I chose “No” on both and the VMs now boot without issue.