jgalexan
Enthusiast
Enthusiast

Guest Event log Errors "\Device\Scsi\vmscsi1, is not ready"

I currenlty have: VC 2.5, ESX 3.5.0 (patched but not update 1) and connected to an IBM SAN through multiple SVCs.

Guest OS = Win2K3 service pack1

We are running MOM and SMS as well.

I am starting to see more and more servers generating the following error:

Any one else see this issue.

___________________________________________________

Event Type: Error

Event Source: vmscsi

Event Category: None

Event ID: 15

Date: 4/24/2008

Time: 7:43:23 AM

User: N/A

Computer: USATL01MM214

Description:

The device, \Device\Scsi\vmscsi1, is not ready for access yet.

___________________________________________________

then the next event is:

___________________________________________________

Event Type: Error

Event Source: Disk

Event Category: None

Event ID: 11

Date: 4/24/2008

Time: 7:43:23 AM

User: N/A

Computer: USATL01MM214

Description:

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

__________________________________________________

0 Kudos
9 Replies
davidhaase
Enthusiast
Enthusiast

Hi,

take a look at this http://communities.vmware.com/message/845950#845950?

Maybe it's a similar problem.

What kind of SCSI controller do you use (LSI, Buslogic)?

Cheers,

David

„What's Up, Doc?“

-- Pedo mellon a minno --
0 Kudos
jgalexan
Enthusiast
Enthusiast

Thank you for the thread link, but my situation does seam to be a little different.

My environment was 2.5. We have since built a new 3.5 environment using new HP Blades in a c7000 chassis.

Old environment = ESX 2.5 on Stand alone servers, IBM SAN connected through 2 IBM SVCs (devices A and B) to IBM DS4800 storage

New environment = ESX 3.5 + VI3 on HP Blade c7000, IBM SAN connected through 2 IBM SVCs (devices C and D) to IBM 8100 Storage

All VMs that were in the 2.5 env. have been migrated to the new env. using VM-Converter. My errors did occur in the old environment and are still occuring now. I found that the errors were happening ervery 3 months until late last month. Now the errors have not stopped. I have a mix of LSI and Bus logic controllers.I have an open case with VMware. I am sure that VMware support will find a solution, but at the moment they are struggling to try and resolve.

I have my storage team looking into any connectivity problems on their side as well.

0 Kudos
jgalexan
Enthusiast
Enthusiast

Problem still exists, but I do have an open case with support. Closing thread.

0 Kudos
pboguszewski
Enthusiast
Enthusiast

Hello,

I am also seeing this issue. We have 3 ESX 3.5 update 2 servers in a HA cluster with VC 2.5 update 2. Have you figured out what the problem is? More details on our Guest system:

Windows 2003 R2 x64 with SP2

4 vCPUs

20tb of disks attached in a spanned drive on Windows

Thanks for any information.

Pete

0 Kudos
jgalexan
Enthusiast
Enthusiast

I am still getting these errors.

Lets compare infrastructure.

Mine = 18 Host Cluster ESX 3.5 Update1

Hardware = HP c7000 Blade Chassis

BL460c Blades

2 quad core CPUs per blade with 16Gig of RAM

Qlogic 2432 HBA cards

IBM SAN - DS8100 using 2 SVC (Array controllers)

Virtual Machines are a mix of Windows XP, Server 2000, and Server 2003 (some are R2)

Do you have any of the same hardware?

0 Kudos
pboguszewski
Enthusiast
Enthusiast

A bit more information on our SAN and these issues.

We run 3 Sun 4600 M2s servers each with:

4 dual core processors

32 Gig ram

Emulex HBAs

Sun 6140 San controllers

The interesting part (maybe not related but worth a mention) is that the errors are only showing up on the virtual machines that have massive storage on the SAN trays that run SATA disks (each of these have 2 to 20 tb of disks mapped to local drives in the guest OS). All our other guests run on trays that have FC disks and are not seeing these issues. For full disclosure, I will mention that the the guest on the FC disks do not have massive numbers of disks attached to them and do not see as much traffic.

0 Kudos
jgalexan
Enthusiast
Enthusiast

I see that we are running on completely different setups.

I want to make sure I undersatnd you, You have Guest VMs that have vmdks from 2 to 20tb in size. I did not realize that a windows server could have a single mounted volume that size.

All of my VMs have somewhat standard size disks (16Gb to 50Gb). I am having the problem with all VMs regardless of vmdk size.

All of my LUNs are 500Gb in size. I have approx. 7-9 VMs per LUN.

I will post if I am able to find anything.

0 Kudos
Langly
Contributor
Contributor

Any updates? Don't leave us hanging!

0 Kudos
KeithWil
Contributor
Contributor

Any updates on this. I am also having the same problem.

0 Kudos