After increasing the Lun on a SAN a simple rescan will not work within Virtual Center. The process to make the new extended size show up in Virtual Center starts by logging directly into a ESX host that connects to the LUN. To increase the capacity of a VMFS datastore: 1. In vCenter Server, select

Recommended disk or LUN sizes for VMware ESX 3.x / 4.x and ESXi 3.x / 4.x / 5.x installations (1026500) Details This article provides information on: Required default storage space for a VMware ESX or ESXi installation. LUN size for a boot-from-SAN configuration. Solution VMware recommends provisioning enough space to satisfy the partitioning requirements outlined

Using the partedUtil command line utility on ESXi and ESX (1036609) Symptoms If you specify an incorrect GUID size using the partedUtil command, you may see errors similar to: error: “Invalid guid (0xfb). Contains non-hexadecimal digits Invalid guid (fb). Length should be 32 Invalid guid (251). Length should be 32 Purpose This article provides information

Recreating a missing VMFS datastore partition in VMware vSphere 5.0/5.1/5.5 (2046610) Symptoms A datastore has become inaccessible. A VMFS partition table is missing. Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the

 (1002281) Details A VMFS datastore is missing or inaccessible The missing VMFS datastore’s LUN is still presented and detected under the host’s Configuration and Storage Adapters view in the VMware vSphere Client or VMware Infrastructure Client. In the /var/log/vmkernel log file, you see one of these messages: cpu0)WARNING: SCSI: 6011: SCSI IO to non-existent partition 1,