Complete procedures with a way back.

Terraform Error: Provider configuration not present means state still associates one or more managed resource instances with a provider configuration address that the current root module can no longer supply. The missing object may be a deleted child-module provider block, a removed alias, an absent module call, or a changed provider source. Repair the execution context before planning any infrastructure change.

Terraform Error acquiring the state lock means the configured backend refused a potentially state-writing operation because another lock exists or the lock service is unavailable. The safe response is to identify the exact backend, workspace, lock owner, and active run before considering force-unlock.

Sub-process /usr/bin/dpkg returned an error code (1) is a final summary, not the root cause. The decisive message normally appears earlier in the transaction. This guide preserves that first failure, checks package-manager ownership, locks, disk and filesystem health, audits dpkg state, then completes configuration or performs a targeted rollback without deleting lock files or forcing unrelated removals.

Use Codex to investigate an unfamiliar repository, freeze scope and acceptance criteria, implement a focused change, run proportional tests, review the complete diff, commit intentionally, and recover without erasing unrelated work.

Build a complete Claude Code hook suite that blocks protected edits before execution, formats only reviewed source files after successful edits, emits privacy-safe local notifications, records sanitized configuration-change evidence, survives cwd changes, and has deterministic tests plus an emergency disable path.

Create a mirrored OpenZFS data pool from stable device identities, separate data into policy-aware datasets, recover individual files from snapshots, verify every block with scheduled scrubs, replace a failed member without confusing device names, and rehearse a read-only import path before an incident.

Recover a non-booting Ubuntu Server by choosing the least invasive systemd target, preserving console evidence, identifying the failed boot dependency, applying a reversible correction, and proving a clean normal boot.

Correlate kernel I/O symptoms, SMART or NVMe health data, self-test history, stable device identity, storage-stack membership, and application evidence before replacing a Linux data drive through the layer that actually owns redundancy.

Build a two-member data RAID 1 array, persist assembly and mounting, monitor synchronization and consistency, rehearse a controlled member failure, and rebuild onto a positively identified replacement.

Copy an Ubuntu root filesystem to a larger ext4 disk, preserve Linux metadata, rebuild UUID-based boot artifacts, perform a controlled cutover, and retain the original disk as a tested rollback.

Create a consistent logical backup with routines, events, triggers, metadata, compression, encryption, checksums, retention, and an isolated restore test.

Define recovery objectives, create a least-privilege backup identity, capture schemas and objects consistently, encrypt offsite, and run an isolated restore test.