CamdenITDept
asked on
W2k3 SP1 host on VMware
We have 4 ESX hosts, using an EMC AX4-5i.
On 1 W2k3 SP1 client we are getting the following errors:-
Fri Mar 06 07:32:58 +0000 2009 --- - |+ Found Event ID:11 Source: Disk at: Tue Mar 03 11:33:01 +0000 2009 - The driver detected a controller error on \Device\Harddisk0. - |+ Found Event ID:15 Source: vmscsi at: Tue Mar 03 11:33:01 +0000 2009 - The device, \Device\Scsi\vmscsi1, is not ready for access yet.
Fri Mar 06 07:32:58 +0000 2009 Event: 15 Source: vmscsi - The device, \Device\Scsi\vmscsi1, is not ready for access yet.
Fri Mar 06 07:32:58 +0000 2009 Event: 11 Source: Disk - The driver detected a controller error on \Device\Harddisk0.
Any ideas? This started on Wednesday (had similar issues but was originally caused by a Disk Failure on the SAN, we have since moved the VM to the 2nd LUN on the SAN)
On 1 W2k3 SP1 client we are getting the following errors:-
Fri Mar 06 07:32:58 +0000 2009 --- - |+ Found Event ID:11 Source: Disk at: Tue Mar 03 11:33:01 +0000 2009 - The driver detected a controller error on \Device\Harddisk0. - |+ Found Event ID:15 Source: vmscsi at: Tue Mar 03 11:33:01 +0000 2009 - The device, \Device\Scsi\vmscsi1, is not ready for access yet.
Fri Mar 06 07:32:58 +0000 2009 Event: 15 Source: vmscsi - The device, \Device\Scsi\vmscsi1, is not ready for access yet.
Fri Mar 06 07:32:58 +0000 2009 Event: 11 Source: Disk - The driver detected a controller error on \Device\Harddisk0.
Any ideas? This started on Wednesday (had similar issues but was originally caused by a Disk Failure on the SAN, we have since moved the VM to the 2nd LUN on the SAN)
ASKER
Just to advice - OS is W2k3 SP1 - I updated the original question...
Forced CHKDSK at reboot, No errors found...
Forced CHKDSK at reboot, No errors found...
Take a look at this thread. It talks about potential HCL issues and updates that may have been performed on the ESX host. Does it help any?
http://communities.vmware.com/message/845950#845950
http://communities.vmware.com/message/845950#845950
ASKER
We havent touched the build of ESX on any host. Since the reboot and subsequent CHKDSK the error has gone - but for how long?
The SAN says its working normally (no HD errors). The VM is on LUN2 now - we had HD1 (LUN1) go faulty twice!
I have determined that it showed in Event Log roughly every 3 hours...
Will wait for a while yet to ensure this time has passed before passing further judgement.
The SAN says its working normally (no HD errors). The VM is on LUN2 now - we had HD1 (LUN1) go faulty twice!
I have determined that it showed in Event Log roughly every 3 hours...
Will wait for a while yet to ensure this time has passed before passing further judgement.
ASKER
That was short lived... And again Event 11 & Event 15 Errors...
Any suggestions?
Fri Mar 06 13:32:57 +0000 2009 Event: 15 Source: vmscsi - The device, \Device\Scsi\vmscsi1, is not ready for access yet.
Fri Mar 06 13:32:57 +0000 2009 Event: 11 Source: Disk - The driver detected a controller error on \Device\Harddisk0.
Fri Mar 06 13:32:57 +0000 2009 Event: 15 Source: vmscsi - The device, \Device\Scsi\vmscsi1, is not ready for access yet.
Fri Mar 06 13:32:57 +0000 2009 Event: 11 Source: Disk - The driver detected a controller error on \Device\Harddisk0.
Fri Mar 06 13:32:57 +0000 2009 Event: 15 Source: vmscsi - The device, \Device\Scsi\vmscsi1, is not ready for access yet.
Fri Mar 06 13:32:57 +0000 2009 Event: 11 Source: Disk - The driver detected a controller error on \Device\Harddisk0.
Any suggestions?
Fri Mar 06 13:32:57 +0000 2009 Event: 15 Source: vmscsi - The device, \Device\Scsi\vmscsi1, is not ready for access yet.
Fri Mar 06 13:32:57 +0000 2009 Event: 11 Source: Disk - The driver detected a controller error on \Device\Harddisk0.
Fri Mar 06 13:32:57 +0000 2009 Event: 15 Source: vmscsi - The device, \Device\Scsi\vmscsi1, is not ready for access yet.
Fri Mar 06 13:32:57 +0000 2009 Event: 11 Source: Disk - The driver detected a controller error on \Device\Harddisk0.
Fri Mar 06 13:32:57 +0000 2009 Event: 15 Source: vmscsi - The device, \Device\Scsi\vmscsi1, is not ready for access yet.
Fri Mar 06 13:32:57 +0000 2009 Event: 11 Source: Disk - The driver detected a controller error on \Device\Harddisk0.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have uninstalled VMWare Tools & Re-Installed... Just to wait to see if error re-appears...
ASKER
So far so good...
There could be there was corruption in the virtual disk due to the san hiccupping...
What type of SCSI adaptor does your XP host have?