Broken Linux

When Linux breaks—and it always does—this is the book you reach for. A practical, crisis-first guide to diagnosing, repairing, and recovering broken systems: GRUB and boot failures, filesystems, RAID and LVM, networking, SSH, sudo, packages, performance, containers, security, and full-system rescue.

Broken Linux: A Practical Guide to Diagnosing, Repairing, and Recovering Linux Systems exists because breakage is not the exception in a system administrator's career—it's the rule. Every Linux system, no matter how carefully built, eventually fails. A kernel refuses to boot. A disk fills up at 3 a.m. A service crashes silently, leaving nothing but a cryptic log entry. This book meets that reality head-on, transforming the panic of a failed system into a methodical, confident process of diagnosis and recovery.

This is not a book about how Linux is supposed to work—plenty of excellent books already cover that ground. This is a book about what happens when it doesn't: when GRUB won't load, when systemd hangs, when RAID arrays fail, when sudo itself is broken and you can't even fix the problem the normal way. "Broken" is the thread that ties every chapter together and the lens through which the entire book is written.

Broad by Design, Because Breakage Doesn't Respect Boundaries

The scope here is deliberately wide. You'll find dedicated chapters on broken boot processes, broken filesystems, broken networking, broken permissions, broken package managers, broken performance, and broken containers. The book examines servers under active attack, broken cloud VMs, and VPS instances stripped of console access. It even devotes an entire chapter to 25 broken Linux scenarios, because sometimes the fastest way to learn is to see a problem you recognize immediately.

Relentlessly Practical

Throughout, the emphasis stays on the practical: what commands to run, what output to expect, and what that output actually means. Each chapter assumes your system is already broken and walks you forward from there. This is the opposite of theory—it's the calm, ordered process you wish you had the last time everything went sideways at midnight.

What You'll Be Able to Handle

The book moves from a foundational troubleshooting mindset and emergency toolkit through every major category of failure:

• Boot failures — the Linux boot process, broken GRUB, kernels that won't boot, and systemd boot failures
• Storage failures — filesystem corruption, full disks, disappeared partitions, broken LVM, and RAID failures
• Networking failures — "the network is down," IP and routing problems, broken DNS, and firewall problems
• Access and permissions — SSH that doesn't work, broken SSH keys, users who can't log in, permission problems, and broken sudo
• Packages and services — package management failures, updates that broke the server, services that won't start, and downed web servers and databases
• Performance — "Linux is slow," CPU, memory, and disk I/O problems, and processes gone wrong
• Logging and debugging — reading logs that tell the story, and what to do when logging itself breaks
• Containers and security — Docker and Podman troubleshooting, SELinux and AppArmor problems, and answering "has the server been compromised?"
• Rescue and recovery — rescuing a completely broken system, recovering lost data, backup and disaster recovery, and broken VPS and cloud VMs

Turning Recovery Into Discipline

By the time you finish, you won't just know how to fix a broken Linux system—you'll understand why it broke, how to prevent it from happening again, and how to stay calm while doing it. The final chapters, including Troubleshooting Under Pressure and Preventing the Next Failure, are built specifically to turn hard-won recovery experience into lasting operational discipline.

Reference Material for the Broken Terminal

The extensive appendices are designed to sit open next to a broken terminal, not just on a shelf: a Linux emergency command cheat sheet, a boot recovery cheat sheet, a networking troubleshooting flowchart, storage and SSH recovery checklists, a performance troubleshooting checklist, a systemd troubleshooting reference, a log locations reference, distribution-specific recovery commands for Debian/Ubuntu and RHEL/Fedora/Rocky/AlmaLinux, an incident response checklist, and 100 Linux troubleshooting commands.

Written for the Real World, at Real Hours

This book is direct, unglamorous, and occasionally a little dark-humored—because anyone who has stared at a kernel panic at midnight knows gallows humor is part of the job. The goal is clarity under stress, not academic completeness. Whether you're a junior sysadmin facing your first broken production server, a DevOps engineer maintaining fleets of half-broken cloud instances, or a seasoned engineer who just wants a faster reference when things go sideways, this book meets you exactly where the system has already failed.

Why This Book

Read it cover to cover, or jump straight to the chapter matching your current crisis. Either way, when something breaks, this book is meant to be the first thing you reach for.