Skip to content

docs(kb): isolated vSAN "Error reading block" warning is a transient read - #495

Open
CarlRodabaugh wants to merge 2 commits into
mainfrom
docs/kb-vsan-fillpage-transient-read
Open

CarlRodabaugh wants to merge 2 commits into
mainfrom
docs/kb-vsan-fillpage-transient-read

Conversation

@CarlRodabaugh

Copy link
Copy Markdown
Collaborator

Summary

New KB article: knowledge-base/posts/vsan-fillpage-enoent-transient-read.md.

A VM drive I/O error that lands in the same second as a single vSAN FillPage error ... (2) No such file or directory / Error reading block ... from all sources warning keeps coming up in support, and nothing public explains it. The article covers:

  • the verbatim error strings (sanitized), so the page is findable by search
  • why the read is transient and not a media error
  • how to confirm no data was lost: Infrastructure → vSAN Tiers → tier → Repairs 0, Unavailable Drives 0, Redundant checked
  • when to contact support instead
  • a note that the similar-looking site-sync string is a different issue

Verification

  • UI path and field labels checked on a 26.1.8 system.
  • Rendered locally with mkdocs serve.
  • All Additional Resources links return 200 on docs.verge.io.

🤖 Generated with Claude Code

CarlRodabaugh and others added 2 commits September 23, 2026 16:34
… transient read

Troubleshooting article for the single vSAN FillPage ENOENT /
"Error reading block ... from all sources" warning that appears alongside a
VM drive I/O error. Explains that an empty repair queue, no unavailable
drives, and a redundant tier mean the read succeeded on retry and nothing
was lost, and lists when to contact support instead.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant