Event ID 55 Windows 2003 Machines with RDM

[zenariga]

Hello,

I have a problem, every virtual machine Windows 2003 with RDM devices show an error "Event ID 55"

Event ID: 55

The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume.

The RDM device works how physical device.

Anybody knows what happens??? How to fix this problem?

Thanks!

[zenariga]

Hello,

I already check the HBA configuration and everything is OK. I don't know where is the problem!

Thanks!

[Texiwill]

Hello,

Moved to VI: VIrtual Machine and Guest OS forum.

Which version of ESX are you using? Also, look in /var/log/vmkernel of the ESX host while investigating failures within the VM.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

SearchVMware Blog: http://itknowledgeexchange.techtarget.com/virtualization-pro/

Blue Gears Blogs - http://www.itworld.com/ and http://www.networkworld.com/community/haletky

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

[zenariga]

I update today to ESX 3.5.3.

Thanks!

[SuryaVMware]

And the issue still persists? what about the /var/log/vmkernel? do you see any errors in that too?

Win2003, what level is it at? i mean the SP. Are all these VMs deployed from a template/clone?

-surya

[zenariga]

Hello,

The issue still persistis.

In /var/log/vmkernel have this errors:

Nov 25 08:06:50 sbisaesx02 vmkernel: 0:17:33:46.093 cpu3:1039)WARNING: SCSI: 119: Failing I/O due to too many reservation conflicts

Nov 25 08:06:50 sbisaesx02 vmkernel: 0:17:33:46.093 cpu3:1039)WARNING: SCSI: 255: status SCSI reservation conflict for vml.02000b00006006016032602100ba3a4fef07a4dd11524149442035. residual R 919, CR 0, ER 3

Nov 25 08:06:50 sbisaesx02 vmkernel: 0:17:33:46.093 cpu1:1261)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

Nov 25 08:06:51 sbisaesx02 vmkernel: 0:17:33:46.139 cpu1:1264)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

Nov 25 08:06:51 sbisaesx02 vmkernel: 0:17:33:46.204 cpu1:1262)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

Nov 25 08:06:51 sbisaesx02 vmkernel: 0:17:33:46.256 cpu1:1198)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

Nov 25 08:06:51 sbisaesx02 vmkernel: 0:17:33:46.304 cpu1:1259)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

Nov 25 08:06:51 sbisaesx02 vmkernel: 0:17:33:46.358 cpu1:1297)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

Nov 25 08:06:51 sbisaesx02 vmkernel: 0:17:33:46.422 cpu1:1299)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

Nov 25 08:06:51 sbisaesx02 vmkernel: 0:17:33:46.475 cpu1:1203)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

Nov 25 08:06:51 sbisaesx02 vmkernel: 0:17:33:46.537 cpu1:1198)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

Nov 25 08:06:51 sbisaesx02 vmkernel: 0:17:33:46.591 cpu1:1164)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

Nov 25 08:06:51 sbisaesx02 vmkernel: 0:17:33:46.659 cpu1:1203)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

Nov 25 08:06:51 sbisaesx02 vmkernel: 0:17:33:46.707 cpu1:1263)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

Nov 25 08:06:51 sbisaesx02 vmkernel: 0:17:33:46.778 cpu1:1300)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

Nov 25 08:06:51 sbisaesx02 vmkernel: 0:17:33:46.830 cpu1:1297)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

Nov 25 08:06:51 sbisaesx02 vmkernel: 0:17:33:46.886 cpu1:1125)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

Nov 25 08:06:51 sbisaesx02 vmkernel: 0:17:33:46.948 cpu1:1125)StorageMonitor: 196: vmhba1:0:11:0 status = 24/0 0x0 0x0 0x0

This error repeat and repeat many times.

The windows is a Windows 2003 SP2 R2, Any machines is installed another is template.

Thanks!

[JonRoderick]

I had a similar issue with my RDM - I needed to use SAN-based snapshots so RDM was my only option but I kept getting corrupt volumes after removing and adding the volume in Windows.

Jon

[SuryaVMware]

That is a SCSI reservation conflict. Is it reporting on only vmhba1:0:11:0 or other LUNs too?

NowI have few more questions for you.

1) What is the storage array?

2) Is it Active/Active or Active/Passive?

3) vmhba1:0:11:0 is a RDM LUN presented to a VM or a VMFS volume?

4) What is the multipathing policy you are using?

5) Any vendor agents installed inside the console OS? like HP openview.

Please try and answer all the above questions and any additions information you could collect will be useful like the version of the firmware on the storage array and the version of the monitoring agents.

-Surya

[zenariga]

Answer your questions:

That is a SCSI reservation conflict. Is it reporting on only vmhba1:0:11:0 or other LUNs too?

Happens with another LUNs too.

1) What is the storage array?

EMC Clariion CX3-20C

2) Is it Active/Active or Active/Passive?

Active/Active

3) vmhba1:0:11:0 is a RDM LUN presented to a VM or a VMFS volume?

RDM

4) What is the multipathing policy you are using?

MRU

5) Any vendor agents installed inside the console OS? like HP openview.

No. All physical machines converted using VMWare Converter don't have more any agent. And have many machines created from begenning.

We have here a SAN specialist and all Firmwares and HBA parameters are OK.

Thanks!

[SuryaVMware]

Isn't it active/passive? Anyhow that dosen't matter now since you have MRU as multipathing policy.

I was asking about the agents on the ESX server? like HP openview running on the service console or navispher agent running on the service console.

-Surya

[SuryaVMware]

not sure if it is applicable to Windows 2003 R2 SP2 but you might want to check this.

http://support.microsoft.com/kb/932578

-Surya

[zenariga]

OK, sorry is a active/passive.

Have only navisphere running in the service console.

Thanks!

[zenariga]

Thanks for this article, I try to install this hotfix and wait because this issue intermittent.

Thanks!

[dyee7]

Hi, i also having the same issue with the assign RDM LUN corrupted with one of my customer.. it mentioned the file or drive is corrupted. asking to perform the checkdisk. Anyone have the solution to solve it.

[JonRoderick]

I don't think that's a SCSI reservation conflict - it's a Windows failing - probably related to the drive being removed or disconnected whilst being accessed (that was my problem anyway).

jon

[zenariga]

Sorry but I don't have a resolution to his issue.

Two order was oppened one in Dell and another in VMWare.Dell made a environment arquiteture.

A short answer from Dell speaking about a bad sizing of environment, because the clariion have only one enclouser and have so many I/O's. But looking the Clariion analyser didn't have so many I/O's.

Dell and VMWare is looking this problem. I don't have idea what is the real issue of this environment.

Thanks,

[zenariga]

Hello JonRoderick,

This issue happens without remove or disconect the RDM disk.

This environment with this RDM disks have two problems:

1 - SCSI reservation conflict;

2 - Event ID 55 on Windows Virtual machines.

Nobody knows if the problem 2 is related with problem 1 (I believe that yes), a Case is open but I didn't received a official answer of VMWare.

Thanks

[JasonSchelpp]

zenariga,

Does the vmx file for the guest have the correct scsi entries for the raw mapped disk? I am getting the same error (event id 55) in a windows guest that has a raw mapped disk. I happened to check the vmx file and found that the scsi entires were missing. Tonight I am planning to add them back in to see if this resolves the appearance of the error in the windows event viewer.

[zenariga]

Hello JasonSchelpp,

I see that too. In my environment have 3 our 4 machines using RDM. Any machines have the wrong scsi entires our missing. I put this information but the problem (ID 55) continue.

Thanks,

[JasonSchelpp]

I am still getting the error as well after ensuring the scsi entries are present in the vmx file.