<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>启动排错 on PlumePHP</title><link>https://plumephp.com/tags/%E5%90%AF%E5%8A%A8%E6%8E%92%E9%94%99/</link><description>Recent content in 启动排错 on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Mon, 28 Sep 2026 10:00:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/%E5%90%AF%E5%8A%A8%E6%8E%92%E9%94%99/index.xml" rel="self" type="application/rss+xml"/><item><title>Linux 启动排错实战：引导失败、救援模式与内核崩溃诊断</title><link>https://plumephp.com/linux-boot-troubleshooting/</link><pubDate>Mon, 28 Sep 2026 10:00:00 +0800</pubDate><guid>https://plumephp.com/linux-boot-troubleshooting/</guid><description>&lt;h2 id="引言"&gt;引言&lt;/h2&gt;
&lt;p&gt;开机黑屏/卡住/报错，是最让人慌的场景——但&lt;strong&gt;启动失败有清晰的定位路径&lt;/strong&gt;。Linux 启动是一条接力链：固件 → GRUB → 内核 + initramfs → systemd。排错就是「定位卡在哪一段」。本文给一套框架：从启动日志（journalctl -b / console）、GRUB 故障修复、initramfs 重建、内核参数与单用户模式、文件系统挂载失败、systemd 救援目标，到 Live 系统救援与内核 panic/kdump 诊断。&lt;/p&gt;</description></item></channel></rss>