Glibc更新后CentOS进入内核恐慌 [英] CentOS booting into kernel panic after Glibc update

查看:81
本文介绍了Glibc更新后CentOS进入内核恐慌的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我愚蠢地尝试将Glibc更新到较新的版本,出现段错误并重新启动,只是为了面对这个错误:

I foolishly tried to update Glibc to a newer version, got segfaults and rebooted, only to face this error:

这是一台在内核PV 64位(4.4.27-x86_64-jb1)上运行CentOS 6.2 64位的VM,我只有远程访问权限.

It's a VM running CentOS 6.2 64bit on Kernel PV 64bit (4.4.27-x86_64-jb1) I only have remote access to.

我可以选择启动到不同的内核中,我可以简单地这样做以访问安装在不想启动到同一系统上的Web服务器和mysql db吗?

I have the option do boot into a different kernel, could I simply do that to access a webserver and mysql db that is installed on the same system it doesn't want to boot into?

我在其他地方读过我可以简单地为发行版重新安装正确的Glibc库,但是我不能这样做,因为我一开始无法启动它.

I've read elsewhere that I could simply re-install the correct Glibc libs for the distribution, however I can't since I can't boot into it in the first place.

推荐答案

我愚蠢地尝试更新Glibc

I foolishly tried to update Glibc

是的,错误升级GLIBC是使系统无法启动的简便方法.

Yes, incorrect upgrade of GLIBC is an easy way to render your system unbootable.

我可以选择启动到另一个内核

I have the option do boot into a different kernel

不同的内核将有完全相同的问题.您的问题不在于内核,而在于/sbin/init ,这是内核创建的第一个用户空间进程无法运行.

The different kernel will have exact same problem. Your problem is not with the kernel, it's that /sbin/init, which is the very first user space process the kernel creates, can't run.

恢复是可能的,但可能非常复杂(取决于您在MySQL数据库中有多少数据,这种努力可能值得也可能不值得).

Recovery is sill possible, but may be quite complicated (and may or may not be worth the effort, depending on how much data you have in the MySQL database).

您将需要访问要引导到的根文件系统,将其作为根文件系统挂载到其他VM中,进行修复(删除已安装的bottom的GLIBC部件)并重新安装原始软件包),然后将其卸载.之后,您将能够启动原始虚拟机.

You'll need to get access to the root file system you are booting into, mount it into some other VM as a non-root file system, repair it (remove your botched installed GLIBC parts and re-install the original package), and unmount it. After that you'll be able to boot your original VM.

您需要执行的操作的确切详细信息取决于您实际使用的虚拟机以及如何配置其磁盘.

The exact details of what you need to do depend on which VM you are actually using and how you've configured its disks.

这篇关于Glibc更新后CentOS进入内核恐慌的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆