obsidian-incident-runbook

# Obsidian Incident Runbook ## Overview Systematic procedures for diagnosing and resolving Obsidian failures: plugin crashes, vault corruption, sync conflicts, performance degradation, and broken CSS/themes. Each section is a self-contained runbook -- jump to the relevant one. ## Prerequisites - Access to the affected Obsidian vault directory - Developer Console access (Ctrl+Shift+I / Cmd+Option+I) - Terminal access for filesystem operations - Backup awareness (know where your backups are before making changes) ## Instructions ### Step 1: Quick Triage Determine the category before diving in: | Symptom | Category | Go to | |---------|----------|-------| | Obsidian crashes on open or plugin enable | Plugin crash | Step 2 | | Notes missing, corrupted, or garbled | Vault corruption | Step 3 | | Duplicate files, conflicting edits | Sync conflicts | Step 4 | | Obsidian slow, high CPU/memory, lag while typing | Performance | Step 5 | | UI elements missing, wrong colors, broken layout | CSS/Theme | Step 6 | ### Step 2: Plugin Crash Recovery **Immediate: Enter Safe Mode** If Obsidian crashes on startup, force safe mode: ```bash VAULT_PATH=~/path/to/vault # Option A: Disable all community plugins echo '[]' > "$VAULT_PATH/.obsidian/community-plugins.json" # Option B: Disable a specific suspect plugin python3 -c " import json plugins = json.load(open('$VAULT_PATH/.obsidian/community-plugins.json')) suspect = 'plugin-id-here' if suspect in plugins: plugins.remove(suspect) ...