ESX 3.5 update to 4.0 vSphere VMFS error

[David01]

After an upgrade to ESX Server 4.0, two VMFS volumes were no longer recognized as valid datastore. In ESX Server 3.5 has not yet updated, the VMFS appears but only as read-only, virtual machines can not be cloned, disconnected or migrated because the VMFS does not allow this operation.

How can I return this datastore for normal operation?

Thanks

[Texiwill · Accepted solution]

Hello,

Moved to the vSphere Upgrade and Install Forum.

After an upgrade to ESX Server 4.0, two VMFS volumes were no longer recognized as valid datastore. In ESX Server 3.5 has not yet updated, the VMFS appears but only as read-only, virtual machines can not be cloned, disconnected or migrated because the VMFS does not allow this operation.

It looks like the 2 VMFS are for ESX v2.x not 3.x. VMFS 2.x are R/O in ESX v3.

The easiest thing to do is to offload your VMs from the VMFS using ESX v3.5 and then recreate the VMFS on ESX v4, then transfer the VMs back. You can also recreate on v3.x but I am not sure that is required.

Best regards,
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, 2010

Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security'[/url]

Also available 'VMWare ESX Server in the Enterprise'[/url]

Blogging: The Virtualization Practice[/url]|Blue Gears[/url]|TechTarget[/url]|Network World[/url]

Podcast: Virtualization Security Round Table Podcast[/url]|Twitter: Texiwll[/url]

[David01]

Thanks Texiwill,

I'll move virtual machines from datastore and format the same in v4 as you said ..