Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Host PSODs on Boot after removing a SSD Drive from the host (66996)

Last Updated: 7/2/2023Categories: TroubleshootingTotal Views: 7623Language:
Chinese (Simplified)JapaneseSpanishEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

ESXi host PSOD after removing a failed SSD cache or capacity drive in a vSAN disk group.

Purpose

Provide steps to correct the host's disk group configuration so that the host will be able to boot and re-join the vSAN cluster.

Cause

Drive physically removed/replaced without first removing it logically from the vSAN disk group.

Impact / Risks

Potential Data Unavailability or Data Loss. When a drive is removed improperly, the disk groups data itself, in an all flash dedupe configuration, is lost.

Resolution

To resolve the issue:

1. Disable vSAN at host boot.

Reboot the ESXi host.
During the pre-boot splash screen, press SHIFT+O to modify the boot options.
In the resulting screen, move to the end of the boot line.
To disable the vSAN kernel modules, add a space at the end of the boot line and then add the following line:

jumpstart.disable=vsan,lsom,plog,virsto,cmmds,,

Press the enter key to resume booting.

2. Boot host up

3. Remove Partitions from Disks in the failed disk group.

In vCenter Hosts and Clusters > Select the problem Host > Configure > Storage > Storage Devices

Using All Actions > Erase Partitions of each of the disks of the disk groups.

Be absolutely certain which disks to erase, as with multiple disk groups, there is potential for mistakenly erasing the wrong disk.

4. Reboot Host - vSAN service will be restored on reboot. Keep the host in maintenance mode.

5. Disks will now be eligible to join vSAN as part of a new Disk group.

6. Ensure the Logical vSAN Disk group is removed.

Hosts and Clusters > Select vSAN Cluster Inventory Object > Configure > vSAN > Disk Management.
Locate the host and disk group identified as failed. Remove the disk group with the No Data Migration option.

7. If the new replacement disk has already been slotted into the host, proceed to creating the disk group. If the disk has not been replaced, proceed to installing the new disk.

8. Recreate the Disk Group and take the host out of maintenance mode.

9. Check that the vSAN datastore capacity has increased to reflect the re-created disk group.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseSpanishEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 6.x

VMware vSAN 6.7.x

VMware vSAN 6.5.x

VMware vSAN 6.1.x

VMware vSAN 6.0.x

Take Our Survey

Support Assistant