Boot
如果核心崩潰如何修復系統？
我剛剛更新了軟體包：
2013-05-23 11:15:34 startup archives unpack 2013-05-23 11:15:35 upgrade locales:all 2.13-38 2.17-3 2013-05-23 11:15:35 status half-configured locales:all 2.13-38 2013-05-23 11:15:35 status unpacked locales:all 2.13-38 2013-05-23 11:15:35 status half-installed locales:all 2.13-38 2013-05-23 11:15:35 status triggers-pending man-db:amd64 2.6.3-3 2013-05-23 11:15:35 status half-installed locales:all 2.13-38 2013-05-23 11:15:38 status half-installed locales:all 2.13-38 2013-05-23 11:15:38 status unpacked locales:all 2.17-3 2013-05-23 11:15:39 status unpacked locales:all 2.17-3 2013-05-23 11:15:39 upgrade libc6:i386 2.13-38 2.17-3 2013-05-23 11:15:39 status half-configured libc6:i386 2.13-38 2013-05-23 11:15:40 status unpacked libc6:i386 2.13-38 2013-05-23 11:15:40 status half-configured libc6:amd64 2.13-38 2013-05-23 11:15:40 status half-installed libc6:i386 2.13-38 2013-05-23 11:15:47 status half-installed libc6:i386 2.13-38 2013-05-23 11:15:47 status unpacked libc6:i386 2.17-3 2013-05-23 11:15:48 status unpacked libc6:i386 2.17-3 2013-05-23 11:15:48 upgrade libc6:amd64 2.13-38 2.17-3 2013-05-23 11:15:48 status half-configured libc6:amd64 2.13-38 2013-05-23 11:15:48 status unpacked libc6:amd64 2.13-38 2013-05-23 11:15:48 status half-installed libc6:amd64 2.13-38 2013-05-23 11:15:53 status half-installed libc6:amd64 2.13-38 2013-05-23 11:15:53 status unpacked libc6:amd64 2.17-3 2013-05-23 11:15:54 status unpacked libc6:amd64 2.17-3 2013-05-23 11:15:54 trigproc man-db:amd64 2.6.3-3 2.6.3-3 2013-05-23 11:15:54 status half-configured man-db:amd64 2.6.3-3 2013-05-23 11:16:00 status installed man-db:amd64 2.6.3-3 2013-05-23 11:16:01 startup packages configure 2013-05-23 11:16:01 configure libc6:amd64 2.17-3 <none> 2013-05-23 11:16:01 status unpacked libc6:amd64 2.17-3 2013-05-23 11:16:02 status unpacked libc6:amd64 2.17-3 2013-05-23 11:16:02 status half-configured libc6:amd64 2.17-3 2013-05-23 11:16:57 status installed libc6:amd64 2.17-3 2013-05-23 11:16:57 configure libc6:i386 2.17-3 <none> 2013-05-23 11:16:57 status unpacked libc6:i386 2.17-3 2013-05-23 11:16:57 status unpacked libc6:i386 2.17-3 2013-05-23 11:16:57 status half-configured libc6:i386 2.17-3 2013-05-23 11:16:57 configure locales:all 2.17-3 <none> 2013-05-23 11:16:57 status unpacked locales:all 2.17-3 2013-05-23 11:16:57 status unpacked locales:all 2.17-3 2013-05-23 11:16:57 status half-configured locales:all 2.17-3Debian GNU/Linux 傑西/sid \n \l
並且因為我的電腦給了我核心恐慌。：/
更確切地說是這樣的：
3f ip 處的init 1段錯誤 ..
$$ i don’t remeber rest of message $$ 核心恐慌不同步。試圖殺死init。
初始化未完成..
我該如何處理？
我發現了這樣的東西： http ://forums.debian.net/viewtopic.php?f=10&t= 96879 據我所知（或者我錯了）某種libc被更新了。我試過了根據評論 21解決，但我沒有：
/lib/libc.so.6文件。
啟動停止時添加圖片。
從 /var/log/apt/term.log 添加日誌：
Log started: 2013-05-23 09:57:05 Selecting previously unselected package less. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 320906 files and directories currently installed.) Unpacking less (from .../archives/less_458-1_amd64.deb) ... Processing triggers for mime-support ... Processing triggers for man-db ... Setting up less (458-1) ... Log ended: 2013-05-23 09:57:16 Log started: 2013-05-23 11:15:33 (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 320928 files and directories currently installed.) Preparing to replace locales 2.13-38 (using .../locales_2.17-3_all.deb) ... Unpacking replacement locales ... Preparing to replace libc6:i386 2.13-38 (using .../archives/libc6_2.17-3_i386.deb) ... De-configuring libc6:amd64 ... Checking for services that may need to be restarted... Checking init scripts... Unpacking replacement libc6:i386 ... Preparing to replace libc6:amd64 2.13-38 (using .../libc6_2.17-3_amd64.deb) ... Checking for services that may need to be restarted... Checking init scripts... Unpacking replacement libc6:amd64 ... Processing triggers for man-db ... Setting up libc6:amd64 (2.17-3) ... Checking for services that may need to be restarted... Checking init scripts... Restarting services possibly affected by the upgrade: samba: restarting...done. mysql: restarting...done. cron: restarting...done. atd: restarting...done. apache2: restarting...done. Services restarted successfully. Setting up libc6:i386 (2.17-3) ... dpkg: error processing libc6:i386 (--configure): subprocess installed post-installation script was killed by signal (Segmentation fault) Setting up locales (2.17-3) ... Installing new version of config file /etc/locale.alias ... dpkg: error processing locales (--configure): subprocess installed post-installation script was killed by signal (Segmentation fault) Errors were encountered while processing: libc6:i386 locales日誌結束：2013-05-23 11:16:59
我按照schaiba所說的做了，所以：
- 備份您的敏感內容（僅對我 /home 目錄）
- 重裝作業系統
所有發行版都會保留一些核心，以防（不太可能）核心安裝失敗或最後一次更新嚴重中斷的情況。啟動一個舊的。
大多數發行版的安裝媒體兼作應急媒體。用它啟動，然後修復系統。
這可能是由於某種硬體錯誤（發生在我身上……）。使用安裝媒體的診斷工具（或其他工具）檢查系統。損壞的文件系統也可能是原因（慷慨的幫助
fsck可能會解決此問題）。一個文件可能已經損壞（如果機器在錯誤的時間崩潰，一種流行的方法是用一個空文件替換），find /etc -empty或者這樣會把它們抽出來）。在已安裝的軟體包上執行診斷程序，在基於 RPM 的系統上rpm -Va會報告不一致的情況（但由於某種原因，即使在許多新安裝的軟體包上，RPM 也會抱怨，不要驚慌）。檢查重複的包和其他不一致的地方。重新安裝任何看起來可疑的軟體包。