Issue:
Several virtual machines report the various errors relating to disk access and may crash and/or require a reboot.
Common Windows OS error messages and event logs that appear on multiple Virtual Machines
{Delayed Write Failed} Windows was unable to save all the data for the file. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
The device, \Device\Harddisk1, has a bad block.
Hard Error
Cannot write to C:\$Mft
Delayed write failed for file C:\$Mft
An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry.
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:
Stop 0x00000077 KERNEL_STACK_INPAGE_ERROR
Netware Servers that experience this issue may drop their LUNs and/or have the following errors.
Error writing to the directory on Server/Vol#
Device “[V358-A2-D1:0] VMware Virtual disk f/w:1.0” deactivated by driver due to device failure.
Error Messages that appear in the VMKernel log file
StorageMonitor: 196: vmhba1:2:4:0 status = D:0x2/H:0x0 0x2 0x4 0x2
WARNING: FS3: 2504: Couldn't verify lost lock: Transient storage condition, suggest retry
WARNING: VSCSI: 4485: Can't translate bad00bf/Transient storage condition, suggest retry
to SCSI: using MEDIUM ERROR
Cause:
While configuring a VMWare Consolidated Backup (VCB) Server, the VMFS LUNS are presented to the VCB Proxy server without first installing the VCB software. When this happens, Windows 2003 partition manager may inadvertently (usually during reboots of the VCB server) lock the VMFS volumes periodically and cause all ESX I/O to halt for short periods of time. The time of day when the error occurs will correspond with the following event on the VCB Proxy Server.
Event ID: 59
Source: PartMgr
Description: Disk XX will not be used because it is a redundant path for disk YY
Solution:
1) Disconnect the Fiber Channel or iSCSI cables
2) Install the VCB Software to manage the VMFS LUNs properly
3) Disable Automount
4) Install Storport.sys Hotfixes
5) Reconnect the cables