Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

Upgrading to ESX 3.5 Update 3 Causes Local VMFS Volume to be Unrecognized

Details

After upgrading to ESX 3.5 Update 3, the ESX host may not be able to recognize local VMFS volumes.  Virtual machines located on the local VMFS volumes will be inaccessible.

Solution

This occurs on server hardware ICH-7 SATA Controllers configured in ATA mode.  If the controller’s BIOS setting is changed to SATA/AHCI mode, the ESX host may be able to re-recognize the local VMFS volumes.  Once this change is made, the ESX host will need to be booted to see a new hardware configuration.  Another additional reboot will be required to see the VMFS volumes.

Note: This controller is supported with SATA CD/DVD drives in IDE/ATA mode only. SATA CD/DVD drives connected in SATA/AHCI mode will not be available to virtual machines.
 
Please note:  The ICH-7 SATA Controller does not support storing VMFS datastores.  The above steps is provided to help recover and migrate the virtual machine onto a supported configuration.  For complete list of supported I/O devices please see our compatibility guide at:  http://www.vmware.com/pdf/vi35_io_guide.pdf

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (2 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (2 Ratings)   
Actions
  • KB Article: 1007724
  • Updated: Nov 17, 2008
  • Products:
    VMware ESX
  • Product Versions:
    VMware ESX 3.5.x
    VMware ESXi 3.5.x Embedded
    VMware ESXi 3.5.x Installable