Why am I getting these errors?

[esnmb]

My VM is getting these errors. In fact it filled the event log!

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

and

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

and

The driver detected a controller error on \Device\Harddisk0

After booting in to safe mode and then restarting again normally the error isn't showing up any more.

Thoughts?

[kryichek]

Good question. I am receiving the same errors on a few VM's. Any Ideas?

[conyards]

http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;Q314093

deals with the error that you are seeing, the article leans towards this being a hardware fault rather then WinOS error. Can you list anything more about your SAN/LUN/VMDK configuration, also please post any errors listed on the ESX hosts themselves.

Simon

[admin · Accepted solution]

Sounds like a storage timeout problem.

[Texiwill]

Hello,

Look at your /var/log/vmkernel and /var/log/vmkwarning files for SCSI errors.

Best regards,

Edward

[mschipper]

I am also seeing these errors in our environment.

Our config is as follows:

IBM HS21-XM's (7995-C2U) (6 in one cluster), IBM HS21 (8853-C3U) (5 in two additional clusters)

• 32 GB RAM (16 GB in 8853s)

• 2x Quad Core 2.33 GHz CPUs

• ESX 3.5 Update 3

Fiber-Channel connected via dual port QLogic 4G/s HBAs to independant fabrics to dual IBM SVCs front ending IBM DS4800 Disk System, all at 4G/s.

We are not seeing these errors on non-VM systems connected to the same SAN.

This has occured with the LUNs being set to MRU and most recently Fixed manually load balanced across fabrics and SVC ports.

[mitchellm3]

We had the same problem but now have been error free for 3 weeks. We were running SVC code 4.2.1.1. I believe the fix for this was made in 4.2.1.9 but we ended up upgrading to 4.3.0.2. BTW, the fix isn't documented as a "fix vmware scsi issues" fix.