{"id":62324,"date":"2024-05-21T09:00:59","date_gmt":"2024-05-21T07:00:59","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=62324"},"modified":"2024-05-21T12:25:39","modified_gmt":"2024-05-21T10:25:39","slug":"vmware-vsan-unable-to-erase-partitions","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vmware-vsan-unable-to-erase-partitions\/","title":{"rendered":"VMware vSAN: unable to erase partitions"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-62325 size-full\" title=\"vsan-unable-to-erase-partitions-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/05\/vsan-unable-to-erase-partitions-01.jpg\" alt=\"vsan-unable-to-erase-partitions-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>During the configuration of a new <a href=\"https:\/\/nolabnoparty.com\/en\/vsan-8-esa-on-minisforum-ms-01\/\">VMware vSAN<\/a> cluster, disks are <strong>unavailable for claiming<\/strong> and the erase partitions procedure fails.<\/p>\n<p>If you are using disks previously used in another vSAN cluster, this is an expected behavior since disks are still retaining the <strong>previous configured vSAN partitions<\/strong> then disks are not available for another vSAN cluster.<!--more--><\/p>\n<p>&nbsp;<\/p>\n<h2>Erase partitions<\/h2>\n<p>To fix this matter, the partitions removal is the solution. To remove the configured partitions is a simple task. Select the host with the disk partitions to remove and select <strong>Storage Devices<\/strong> under the <strong>Configure<\/strong> tab.<\/p>\n<p>Select the disk to erase (<em>Samsung EVO 970 Plus SSD<\/em> in the example) and select <strong>Partition Details<\/strong> to see the current configuration. You should see the following partitions:<\/p>\n<ul>\n<li>vSAN metada<\/li>\n<li>vSAN File System<\/li>\n<\/ul>\n<p>Click <strong>Erase Partitions<\/strong> to remove the configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-62327 size-large\" title=\"vsan-unable-to-erase-partitions-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/05\/vsan-unable-to-erase-partitions-02-600x288.jpg\" alt=\"vsan-unable-to-erase-partitions-02\" width=\"600\" height=\"288\" \/><\/p>\n<p>It may happen the <strong>system fails<\/strong> to delete the partitions displaying the following error message:<\/p>\n<blockquote><p><em>Cannot change the host configuration. Failed to update disk partitions for \/vmfs\/devices\/disks\/...<\/em><\/p><\/blockquote>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-62329 size-full\" title=\"vsan-unable-to-erase-partitions-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/05\/vsan-unable-to-erase-partitions-03.jpg\" alt=\"vsan-unable-to-erase-partitions-03\" width=\"556\" height=\"364\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Fix<\/h2>\n<p>Before trying tricky solutions, the <strong>old school trick<\/strong> always worth to be attempted.... put the host in <strong>Maintenance Mode<\/strong>, right click the host and select <strong>Power &gt; Reboot<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-62331 size-large\" title=\"vsan-unable-to-erase-partitions-04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/05\/vsan-unable-to-erase-partitions-04-600x356.jpg\" alt=\"vsan-unable-to-erase-partitions-04\" width=\"600\" height=\"356\" \/><\/p>\n<p>After rebooting the host, select the host and go to <strong>Configure<\/strong> tab. Access the <strong>Storage Devices<\/strong> section under the <strong>Configure<\/strong> tab and select the disk to erase. Click <strong>Erase Partitions<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-62333 size-large\" title=\"vsan-unable-to-erase-partitions-05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/05\/vsan-unable-to-erase-partitions-05-600x358.jpg\" alt=\"vsan-unable-to-erase-partitions-05\" width=\"600\" height=\"358\" \/><\/p>\n<p>A confirmation window is displayed. Click <strong>OK<\/strong> to proceed.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-62335 size-large\" title=\"vsan-unable-to-erase-partitions-06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/05\/vsan-unable-to-erase-partitions-06-600x369.jpg\" alt=\"vsan-unable-to-erase-partitions-06\" width=\"600\" height=\"369\" \/><\/p>\n<p>This time partitions have been <strong>deleted successfully<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-62337 size-large\" title=\"vsan-unable-to-erase-partitions-07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/05\/vsan-unable-to-erase-partitions-07-600x405.jpg\" alt=\"vsan-unable-to-erase-partitions-07\" width=\"600\" height=\"405\" \/><\/p>\n<p>Attempting the <a href=\"https:\/\/www.vmware.com\/products\/vsan.html\" target=\"_blank\" rel=\"noopener\">VMware vSAN<\/a> configuration once again, <strong>disks can now be claimed<\/strong> and used in the new cluster. If you experience this issue, as first troubleshooting step <strong>give the host a reboot<\/strong>.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>During the configuration of a new VMware vSAN cluster, disks are unavailable for claiming and the erase partitions procedure fails. If you are using disks previously used in another vSAN cluster, this is an expected behavior since disks are still retaining the previous configured vSAN partitions then disks are not available for another vSAN cluster.<\/p>\n","protected":false},"author":3,"featured_media":62325,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,1853],"tags":[2857,2858,2039],"class_list":["post-62324","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsan-en","tag-erase","tag-partition","tag-vsan-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/62324","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=62324"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/62324\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/62325"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=62324"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=62324"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=62324"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}