diagnose-dirty-ntfs-mount-errors
Troubleshoot NTFS mount failures by identifying dirty volume flags and driver type
Best use case
diagnose-dirty-ntfs-mount-errors is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Troubleshoot NTFS mount failures by identifying dirty volume flags and driver type
Teams using diagnose-dirty-ntfs-mount-errors should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/diagnose-dirty-ntfs-mount-errors/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How diagnose-dirty-ntfs-mount-errors Compares
| Feature / Agent | diagnose-dirty-ntfs-mount-errors | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Troubleshoot NTFS mount failures by identifying dirty volume flags and driver type
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Diagnose Dirty NTFS Mount Errors When an external NTFS drive fails to mount with 'wrong fs type, bad option, bad superblock', first verify the filesystem type and installed drivers using `blkid` and `ntfs-3g --version`. Check kernel logs (`dmesg`) to identify if ntfs3 kernel driver is refusing a dirty volume. Modern Linux (Ubuntu 24.04+) uses the ntfs3 kernel driver by default, which rejects volumes with dirty flags set after unsafe ejection. Mount with `sudo mount -o force /dev/device /mountpoint` to override the safety check, or clean the volume on Windows first.
Related Skills
diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
diagnose-venv-shebang-mismatch
Diagnose and fix ModuleNotFoundError caused by entry point shebang pointing outside virtual environment
diagnose-venv-shebang-import-errors
Debugging pattern for ModuleNotFoundError when CLI entry points use wrong Python interpreter
diagnose-venv-shebang-conflicts
Debugging pattern for resolving ModuleNotFoundError when CLI entry points use wrong Python interpreter
diagnose-symlink-shebang-persistence
Fix persistent shebang issues in symlinked CLI entry points that revert after git operations
diagnose-shebang-virtualenv-import-errors
Debugging pattern for ModuleNotFoundError when CLI entry points use wrong Python interpreter
diagnose-shebang-venv-mismatch
Identify and fix shebang mismatches when CLI tools resolve to system Python instead of their virtual environment
diagnose-shebang-venv-import-errors
Troubleshoot ModuleNotFoundError in CLI tools by identifying shebang-venv mismatches
diagnose-and-mount-dirty-ntfs-drives
Troubleshoot and mount NTFS external drives blocked by dirty filesystem flags
debug-toml-section-scoping-errors
Diagnose and fix TOML configuration errors caused by misplaced key-value pairs in named sections
batch-syntax-repair-from-injection-errors
Detect and fix systematic syntax errors caused by line-injection scripts that split multiline constructs
clean-worktree-integration-from-dirty-main
Land validated issue work from isolated worktrees when the main checkout is dirty by creating a fresh integration worktree, cherry-picking only implementation commits, re-running combined validation, and preparing push/closeout artifacts.