The driver detected a controller error on \Device\Harddisk0.

Hi

I have an ESXI server with 3 virtual host on it...

1 host gives a lot of errors in the event viewer mentioning the following:

Error; event ID:11, The driver detected a controller error on \Device\Harddisk0.

in combination with that error i get

Error; Event ID: 15, The device, \Device\Scsi\symmpi1, is not ready for access yet.

This error gets thrown a lot a lot of times within a minute (like 100 errors within a minute), and then the errors stop. This happens 1 time a day...

My other virtual servers don't throw errors like this, so it can't be an hardware failure i think...

VMwaretools is installed succesfully on this server and is up to date.

What could be the reason and how can i prevent this errors from be thrown...

thanks in advance

kind regards
techneitsolutionsAsked:
Who is Participating?
 
Netman66Connect With a Mentor Commented:
The Host with the Harddisk error is suggesting you may have a local drive going bad.

The timeout thing could be as simple as requiring a new driver or perhaps a firmware update.

0
 
btassureCommented:
Sounds like bus timeouts.

What is your datastore architecture? What kind of disks are you using for storage?
0
 
techneitsolutionsAuthor Commented:
Hi

@btassure: my datastore contains of a RAID 5 Configuration with 3 HP 146GB 6G SAS 15K rpm SFF (2.5-inch) disks. (http://h30094.www3.hp.com/product.asp?sku=4018730&mfg_part=512547-B21&pagemode=ca)

So i have 373Gb on storage.

But isn't it strange that my other servers don't give me the error, if it would be an hardware issue?

@netman66 -> I thought that vmware tools provided all the drivers i needed...

thanks for the answers

kind regards
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Netman66Commented:
Is it the ESX itself giving you these errors or the VMs residing on it?

ESX still requires drivers and their may be updated ones for your server from VMWare - you'll need to check.

What Proliant is this?  Does it have a CD or DVD player (which one)?

You can (and should) download the Firmware Maintenance CD and boot from it to update the firmware on your server.

The last CD version of Firmware Maintenance is 8.70, from there up is DVD.

This is the closest I have to getting all the versions in the same place, but you'll still need to page through to find each one.  
http://h20000.www2.hp.com/bizsupport/site/search/r4_0/jsp/search.jsp?lang=en&cc=ca&prodTypeId=15351&prodSeriesId=316529&tx=firmware+maintenance&sc=1&nh=10&rf=0&lkc=1&lk=1&sts=1
0
 
techneitsolutionsAuthor Commented:
Hi Netman

It ain't the esx server itself that throws the error, but one of the virtual machines (one of the 3) that gives me the errors in the event viewer.

Do you still think that i need to update my esx server. I find it very strange that my 2 other vm's don't seem to experience any problems ...

thanks for the answer
0
 
Netman66Commented:
No, in this case I would think drivers for ESX may be fine.  It never hurts to update the firmware on the server though.

If you have a lot of I/O activity from these VMs, then it's possible that you have some contention at the disk level.

You should make sure your RAID controller is not configured to use write-cache (turn that off) or it may create this issue too.

0
 
techneitsolutionsAuthor Commented:
Well, the VM receives data 24/7 that he needs to manipulate (it's a server from a truckcompany that gets the truckinformation 24/7, so there's a lot of I/O activity on that VM

This could be solved by turning write-cache off on the raid-controller? How is it possible that my other servers (one is a citrix server) aren't suffering from this?
0
 
Netman66Commented:
It might, yes.

I can't say why other VMs aren't throwing this error - perhaps it's just dumb luck?  It might be an idea to add two more disks (mirrored) and move this VM to that storage to isolate it from the others.

We use a high performance fibre-channel SAN for our VMs and when we hit about 8 VMs in a LUN we start seeing drive contention.  So we have limited our VMs to 7 per LUN to avoid this issue.  With local storage (since it isn't as robust as a fibre SAN) you may be reaching the limit of I/O for this array given the load on this one server.

You should be able to look at performance metrics within ESX (using vSphere) to see if there is any merit to the I/O issue.

0
 
techneitsolutionsAuthor Commented:
Actually, we already added some extra storage to the server, made another LUN and Moved that server to the new LUN. It's the only server on that datastore. But after the move the errors still showed up ...
0
 
Netman66Commented:
Update the firmware on that server.
Clear the logs.
When / if the errors come back, post the Event here.

We have to start eliminating things one at a time.  You have isolated the VM to new drives (I think they are separate based on what you are stating), now let's update the firmware to eliminate that as a cause so we can continue troubleshooting.

0
 
techneitsolutionsAuthor Commented:
I am checking this asap

thx netman
0
 
S00007359Cloud Engineering OfficerCommented:
0
 
techneitsolutionsAuthor Commented:
We changed the drive that was causing errors and it works now
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.