{"id":450,"date":"2023-01-04T23:11:27","date_gmt":"2023-01-04T22:11:27","guid":{"rendered":"http:\/\/192.168.10.3:8585\/?p=450"},"modified":"2023-01-05T15:54:51","modified_gmt":"2023-01-05T14:54:51","slug":"how-to-replace-a-disk-in-vsan-with-the-error-general-vsan-error","status":"publish","type":"post","link":"https:\/\/thecloudarchitects.es\/?p=450&lang=en","title":{"rendered":"How to replace a disk in vSAN with the error: \u00abGeneral vSAN error\u00bb"},"content":{"rendered":"\n<p>During holdays a disk broke in our lab, thats a great opportunity to review what we need to do when a disk fails in vSAN and how to fix an error when we try to remove the diskgroup.<br><br>Our platform:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Version: vSphere 8.0<\/li>\n\n\n\n<li>Hosts: x3<\/li>\n\n\n\n<li>Diskgroups: 1 x host<\/li>\n\n\n\n<li>Disks: 1 NVMe disk for cache and 2 NVMe capacity disk<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-pullquote\"><blockquote><p>Some of the details covered in this articule only apply to traditional vSAN OSA architecture <\/p><\/blockquote><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<p>First we have to check if we can replace only the faulty disk or if we need to recreate the diskgroup completly. To decide what to do remember:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>If we need to replace a cache disk we have to recreate the complete diskgroup always.<\/li>\n\n\n\n<li>If encryption or deduplication is enabled we also need to recreate the diskgroup, there is no difference if the faulty disk is a cache disk or a capacity disk.<\/li>\n\n\n\n<li>In other cases where the faulty disk is a capacity disk we could replace only the faulty one without recreating the diskgroup.<\/li>\n<\/ul>\n\n\n\n<p>Let&#8217;s review some pre-requirements and requisites:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>We need to be extra careful when changing a disk in RAID 0, its recommended to check vendor instructions before replacing the disk physically. Don&#8217;t forget its recoomended to configure disk in the controller as passthrough.<\/li>\n\n\n\n<li>When replacing capacity disk it&#8217;s recommended to use the same model and size. If we cannot get the same size its recommended to use the same model with the next bigger size available. We need to be carefult with the balancing when using different disk sizes.<\/li>\n\n\n\n<li>When we change any kind of disks (capacity or cache) its recommended to use disks with the same or better factor of \u00abendurance\u00bb and performance\u00bb<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Diskgroup rebuild<\/h2>\n\n\n\n<p>First we need to do is finding the faulty disk. To do that we enter in the cluster configuration and then into the vSAN disk administrator, here we can check which host has has the disk with errors.<\/p>\n\n\n\n<p>Now we click on \u00abDisks\u00bb in the host with the alarm.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large is-resized\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/192.168.10.3:8585\/wp-content\/uploads\/2023\/01\/image-1-1024x660.png\" alt=\"\" class=\"wp-image-430\" width=\"1026\" height=\"661\" srcset=\"https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-1-1024x660.png 1024w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-1-300x193.png 300w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-1-768x495.png 768w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-1.png 1369w\" sizes=\"(max-width: 1026px) 100vw, 1026px\" \/><\/figure>\n\n\n\n<p>In our case the missing disk is the cache, in means we need to remove the diskgroup and recreate it.<\/p>\n\n\n\n<p>Click on the line of dots next to the diskgroup label to open options.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1014\" height=\"568\" src=\"http:\/\/192.168.10.3:8585\/wp-content\/uploads\/2023\/01\/image-2.png\" alt=\"\" class=\"wp-image-431\" srcset=\"https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-2.png 1014w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-2-300x168.png 300w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-2-768x430.png 768w\" sizes=\"(max-width: 1014px) 100vw, 1014px\" \/><\/figure>\n\n\n\n<p>Click on \u00abRemove\u00bb<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"788\" height=\"564\" src=\"http:\/\/192.168.10.3:8585\/wp-content\/uploads\/2023\/01\/image-3.png\" alt=\"\" class=\"wp-image-432\" srcset=\"https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-3.png 788w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-3-300x215.png 300w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-3-768x550.png 768w\" sizes=\"(max-width: 788px) 100vw, 788px\" \/><\/figure>\n\n\n\n<p>If the diskgroup is removed without alarms we can proceed to the following point where we create the new diskgroup again. In our case we got an error \u00abGeneral vSAN Error\u00bb<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"773\" height=\"134\" src=\"http:\/\/192.168.10.3:8585\/wp-content\/uploads\/2023\/01\/image-4.png\" alt=\"\" class=\"wp-image-433\" srcset=\"https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-4.png 773w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-4-300x52.png 300w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-4-768x133.png 768w\" sizes=\"(max-width: 773px) 100vw, 773px\" \/><\/figure>\n\n\n\n<p>Log in the host with the faulty disk by SSH, we can double check which disk is missing and the UUID of the diskgroup.<\/p>\n\n\n\n<p>Here we can see we only have capacity disks in the list, its the same info we got from the GUI. Write down the UUID for the next step.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#91;root@ast-esxi01:~] esxcli vsan storage list\nt10.NVMe____WDC_WDS200T2B0C2D00PXH0__________________D97806418B441B00\n   Device: t10.NVMe____WDC_WDS200T2B0C2D00PXH0__________________D97806418B441B00\n   Display Name: t10.NVMe____WDC_WDS200T2B0C2D00PXH0__________________D97806418B\n   Is SSD: true\n   VSAN UUID: 52389c3f-fa52-6905-39a7-c5adbfabcd9d\n   <strong><mark style=\"background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-red-color\">VSAN Disk Group UUID: 52adc0bc-6971-fe30-4490-c89de109565e<\/mark><\/strong>\n   VSAN Disk Group Name:\n   Used by this host: true\n   In CMMDS: false\n   On-disk format version: 17\n   Deduplication: false\n   Compression: false\n   Checksum: 8683338899751340819\n   Checksum OK: true\n   Is Capacity Tier: true\n   Encryption Metadata Checksum OK: true\n   Encryption: false\n   DiskKeyLoaded: false\n   Is Mounted: true\n   Creation Time: Mon Feb  7 13:20:14 2022\n\nt10.NVMe____WDC_WDS200T2B0C2D00PXH0__________________53D306418B441B00\n   Device: t10.NVMe____WDC_WDS200T2B0C2D00PXH0__________________53D306418B441B00\n   Display Name: t10.NVMe____WDC_WDS200T2B0C2D00PXH0__________________53D306418B\n   Is SSD: true\n   VSAN UUID: 52e1b7f0-74c6-3ccb-c441-09d7faed25bf\n   <strong><mark style=\"background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-red-color\">VSAN Disk Group UUID: 52adc0bc-6971-fe30-4490-c89de109565e<\/mark><\/strong>\n   VSAN Disk Group Name:\n   Used by this host: true\n   In CMMDS: false\n   On-disk format version: 17\n   Deduplication: false\n   Compression: false\n   Checksum: 3520512375592328882\n   Checksum OK: true\n   Is Capacity Tier: true\n   Encryption Metadata Checksum OK: true\n   Encryption: false\n   DiskKeyLoaded: false\n   Is Mounted: true\n   Creation Time: Mon Feb  7 13:20:14 2022\n<\/code><\/pre>\n\n\n\n<p>Remove the diskgroup using the UUID from the last step.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#91;root@ast-esxi01:~] esxcli vsan storage remove -u <strong><mark style=\"background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-red-color\">52adc0bc-6971-fe30-4490-c89de109565e<\/mark><\/strong><\/code><\/pre>\n\n\n\n<p>Using the GUI check the diskgroup has been removed. We should see that there are no disks in use.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"351\" src=\"http:\/\/192.168.10.3:8585\/wp-content\/uploads\/2023\/01\/image-5-1024x351.png\" alt=\"\" class=\"wp-image-435\" srcset=\"https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-5-1024x351.png 1024w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-5-300x103.png 300w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-5-768x263.png 768w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-5.png 1075w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>We need to create a new diskgroup. Click on \u00abDisks\u00bb and \u00abCreate diskgroup\u00bb<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"666\" height=\"231\" src=\"http:\/\/192.168.10.3:8585\/wp-content\/uploads\/2023\/01\/image-6.png\" alt=\"\" class=\"wp-image-436\" srcset=\"https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-6.png 666w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-6-300x104.png 300w\" sizes=\"(max-width: 666px) 100vw, 666px\" \/><\/figure>\n\n\n\n<p>Doublecheck the diskgroup has been created OK and its healthy.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"798\" height=\"268\" src=\"http:\/\/192.168.10.3:8585\/wp-content\/uploads\/2023\/01\/image-8.png\" alt=\"\" class=\"wp-image-438\" srcset=\"https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-8.png 798w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-8-300x101.png 300w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-8-768x258.png 768w\" sizes=\"(max-width: 798px) 100vw, 798px\" \/><\/figure>\n\n\n\n<p>Now we should have 3 disks in use in green.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/192.168.10.3:8585\/wp-content\/uploads\/2023\/01\/image-9.png\" alt=\"\" class=\"wp-image-439\" width=\"1011\" height=\"417\" srcset=\"https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-9.png 1011w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-9-300x124.png 300w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-9-768x317.png 768w\" sizes=\"(max-width: 1011px) 100vw, 1011px\" \/><\/figure>\n\n\n\n<p>Last step is to take out the host from maintenance mode. Objects with broken components should start repairing automatically (60 min counter probably is already expired)<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Object rebuild<\/h2>\n\n\n\n<p>We have a new working diskgroup, we should check all objects are now \u00abhealthy\u00bb<\/p>\n\n\n\n<p>Click on the virtual object manager in the \u00abMonitor\u00bb section of the cluster. If we have broken objects still to be repeared they will appear in red.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"650\" src=\"http:\/\/192.168.10.3:8585\/wp-content\/uploads\/2023\/01\/image-10-1024x650.png\" alt=\"\" class=\"wp-image-440\" srcset=\"https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-10-1024x650.png 1024w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-10-300x190.png 300w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-10-768x487.png 768w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-10.png 1370w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>It&#8217;s recommended to wait until all objets are rebuilt automatically. This can be checked in the section \u00abResyncing objects\u00bb. If we have rebuilding tasks to complete you will see there how many GBs and the time to complete all tasks.<\/p>\n\n\n\n<p>In the case not all objetcs are automatically rebuilt or if we want to force the resync immediately task we can do it in \u00abShyline Health\u00bb section. Do a test first to have updated information and select \u00abvSAN objects status\u00bb, there you can click \u00abRepair Objects Immediately\u00bb<br><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"881\" height=\"262\" src=\"http:\/\/192.168.10.3:8585\/wp-content\/uploads\/2023\/01\/image-12.png\" alt=\"\" class=\"wp-image-442\" srcset=\"https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-12.png 881w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-12-300x89.png 300w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-12-768x228.png 768w\" sizes=\"(max-width: 881px) 100vw, 881px\" \/><\/figure>\n\n\n\n<p>We should have all components in green now<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"447\" src=\"http:\/\/192.168.10.3:8585\/wp-content\/uploads\/2023\/01\/image-13-1024x447.png\" alt=\"\" class=\"wp-image-443\" srcset=\"https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-13-1024x447.png 1024w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-13-300x131.png 300w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-13-768x335.png 768w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-13.png 1043w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Extra: Recreate performance service<\/h2>\n\n\n\n<p>Sometimes if we wait too long to recover the performance service we cannot recover the missing components even if we force to repair the objects using Skyline Health. In this case the only thing we need to do is to deactivate the service and activate it again to rebuild the database,<\/p>\n\n\n\n<p>Inside the configuration of the cluster go to vSAN Services and edit the performance service to do it. We can deactivate it or change the storage policy there.<br><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"914\" height=\"890\" src=\"http:\/\/192.168.10.3:8585\/wp-content\/uploads\/2023\/01\/image-14.png\" alt=\"\" class=\"wp-image-444\" srcset=\"https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-14.png 914w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-14-300x292.png 300w, https:\/\/thecloudarchitects.es\/wp-content\/uploads\/2023\/01\/image-14-768x748.png 768w\" sizes=\"(max-width: 914px) 100vw, 914px\" \/><\/figure>\n\n\n\n<figure class=\"wp-block-pullquote\"><blockquote><p>There are version where we cannot deactivate it using the GUI, in these cases we need to do it using RVC<\/p><\/blockquote><\/figure>\n\n\n\n<p> <\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>During holdays a disk broke in our lab, thats a great opportunity to review what we need to do when a disk fails in vSAN and how to fix an error when we try to remove the diskgroup. Our platform: Some of the details covered in this articule only apply to traditional vSAN OSA architecture &hellip;<br \/><a href=\"https:\/\/thecloudarchitects.es\/?p=450&#038;lang=en\" class=\"more-link pen_element_default pen_icon_none\">Seguir leyendo <span class=\"screen-reader-text\">How to replace a disk in vSAN with the error: \u00abGeneral vSAN error\u00bb<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":430,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[41],"tags":[31],"class_list":["post-450","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vsan_english","tag-vsan"],"_links":{"self":[{"href":"https:\/\/thecloudarchitects.es\/index.php?rest_route=\/wp\/v2\/posts\/450"}],"collection":[{"href":"https:\/\/thecloudarchitects.es\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thecloudarchitects.es\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thecloudarchitects.es\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/thecloudarchitects.es\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=450"}],"version-history":[{"count":3,"href":"https:\/\/thecloudarchitects.es\/index.php?rest_route=\/wp\/v2\/posts\/450\/revisions"}],"predecessor-version":[{"id":454,"href":"https:\/\/thecloudarchitects.es\/index.php?rest_route=\/wp\/v2\/posts\/450\/revisions\/454"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/thecloudarchitects.es\/index.php?rest_route=\/wp\/v2\/media\/430"}],"wp:attachment":[{"href":"https:\/\/thecloudarchitects.es\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=450"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thecloudarchitects.es\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=450"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thecloudarchitects.es\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=450"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}