docs(kb): stuck vSAN repair after a node's storage controller fails#485
Open
CarlRodabaugh wants to merge 1 commit into
Open
docs(kb): stuck vSAN repair after a node's storage controller fails#485CarlRodabaugh wants to merge 1 commit into
CarlRodabaugh wants to merge 1 commit into
Conversation
When a node's HBA/RAID controller hits a firmware fault, all of that node's vSAN drives drop offline at once; the tier goes non-redundant and the repair cannot complete until the drives rejoin (it will not rebuild onto surviving nodes, and free space is irrelevant). Covers recognizing it and recovering with a cold power-cycle, plus the non-redundant safety caution. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
New KB article for a vSAN condition where vSAN Repair Stuck alarms never clear and the tier stays non-redundant because a single node's storage HBA/RAID controller faulted and dropped all of that node's drives at once.
Key point: the repair does not self-heal onto the surviving nodes, and free space is irrelevant — the offline drives have to rejoin first. That distinguishes it from bad-block and out-of-space stuck repairs. Recovery is a cold power-cycle of the affected node (a warm reboot often won't clear a controller firmware fault), with a prominent caution not to take any other node in the tier offline while it's running non-redundant.
Type
Troubleshooting
Source
Recurring support pattern — two customer cases. Promoted from internal support KB.
Checks
validate_frontmatter.pypasses locallyidentifying-a-failed-disk-drive,removing-a-node-from-cluster)🤖 Generated with Claude Code