2V0-622 · Question #144
A vSphere Web Client task fails while creating a VMFS datastore on a disk with these characteristics: -The disk was formatted with an Master Boot Record (MBR) partition table -The disk was not erased
The correct answer is A. Delete the partitions manually with partedUtil.. A disk with an existing MBR partition table prevents ESXi from creating a new VMFS datastore, and the partedUtil command must be used to delete the existing partitions so ESXi can write a new GPT partition table and VMFS file system.
Question
A vSphere Web Client task fails while creating a VMFS datastore on a disk with these characteristics:
-The disk was formatted with an Master Boot Record (MBR) partition table -The disk was not erased -The disk is visible in the vSphere Web Client What action needs to be performed to resolve the issue?
Options
- ADelete the partitions manually with partedUtil.
- BCreate a VMFS3 file system first, then upgrade it.
- CCreate a VMFS5 file system with the command esxcli storage filesystem add.
- DDelete the data with the vmkfstools command.
How the community answered
(16 responses)- A75% (12)
- B6% (1)
- C13% (2)
- D6% (1)
Why each option
A disk with an existing MBR partition table prevents ESXi from creating a new VMFS datastore, and the partedUtil command must be used to delete the existing partitions so ESXi can write a new GPT partition table and VMFS file system.
ESXi requires a clean disk or one with a recognized GPT partition layout when creating a new VMFS datastore. An MBR-partitioned disk has a conflicting partition structure that the vSphere Web Client wizard cannot automatically overwrite. Using partedUtil on the ESXi host allows the administrator to explicitly remove all existing MBR partitions, after which the datastore creation task can write a fresh GPT label and VMFS volume successfully.
Creating a VMFS3 file system first is not possible for the same reason - the existing MBR partition table blocks any new VMFS creation, and this two-step approach does not resolve the root cause.
The esxcli storage filesystem add command adds an existing formatted device to the list of known datastores; it does not create or format a new VMFS file system on a disk that still has a conflicting partition table.
The vmkfstools command operates on VMDK files and existing VMFS volumes and has no capability to wipe or repartition a raw disk containing an MBR partition table.
Concept tested: partedUtil clearing MBR partition table for VMFS datastore
Source: https://knowledge.broadcom.com/external/article/308361/using-partedutil-on-esxi.html
Topics
Community Discussion
No community discussion yet for this question.