Recover from system failures — AI Prompts for Linux

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

Production node atlas failed to boot this morning. Recover it: boot into rescue, repair the root…

Production node atlas failed to boot this morning. Recover it: boot into rescue, repair the root filesystem, restore GRUB if needed, mount the latest backup from the offsite repository, and bring the node back online with services started in their normal order. Confirm database accepts connections and the app reports healthy before declaring recovery complete.

Improve — make it easier to accept

Before I start the full recovery, make the plan easy to approve: list the one-line rescue-boot…

Before I start the full recovery, make the plan easy to approve: list the one-line rescue-boot command, the filesystem check and repair commands, the exact backup snapshot to restore, and the two highest-risk steps where an approver might veto (customer data restore and time-of-day-dependent cron jobs).

Decide — diagnose the stuck moment

I attempted to boot atlas into the rescue kernel but the LVM volumes don't appear. Could this be…

Server won't boot and rescue kernel doesn't see the LVM volumes.

I attempted to boot atlas into the rescue kernel but the LVM volumes don't appear. Could this be missing device-mapper modules, corrupted metadata, or a failed disk? What quick diagnostics identify which it is, and what is the single next move that preserves data while giving me access to restore?

Become — change the pattern

We keep ending up in full restores after system updates or maintenance windows. The pattern is…

Repeated emergency restores after untested updates.

We keep ending up in full restores after system updates or maintenance windows. The pattern is reactive restores, slow verification, and repeated data-restore mistakes. Which habit is costing us most — lack of pre-update snapshots, insufficient recovery runbooks, or no staged restores — and what one operational habit would most reduce emergency restores?

Next to this one

Other operating system work people do in Linux.

Perform security scans Perform system upgrades Provision infrastructure as code Provision storage volumes Provision virtual machines Resolve permission errors Restore from backups Rotate and manage logs Schedule recurring jobs Script repetitive tasks

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.

The rest of the map

Same library, five ways in.

Work Atlasthe whole map, interactive Careers1,949 jobs and their real tasks Soft skillsthe human part of the work Activities500 things people do Prompt Librarybrowse every prompt