Virtual Machine Kernel Panic : Not Syncing : VFS : Unable To Mount Root FS On Unknown-Block (0,0)

Virtual Machine Kernel Panic : Not Syncing : VFS : Unable To Mount Root FS On Unknown-Block (0,0)

33192

Share on FacebookShare on Twitter

This issue appeared in the Linux virtual machines in the VMware environment after upgrading the guest os, Virtual machines were failing after the guest OS shutdown and it was throwing the ” Kernel Panic : Not Syncing : VFS : Unable To Mount Root FS On Unknown-Block (0,0) ” error on the screen.

This is not directly related to the VMware Virtual platform, but I thought it is worth to share this in my site for my Linux users who are working with the Virtual Machines. Upgrading the Operating system is not expected after the os and it’s package update, unfortunately it ended up with this error at the boot. If you reboot the Virtual Machine it might not appear in the screen but it might appear after shutting down the Virtual Machine and restart after a while. I was using a CentOS Linux machine and this is how I fixed the issue.

Kernel Panic : Not Syncing : VFS : Unable To Mount Root FS On Unknown-Block (0,0)

Try Old Kernel…

So, I tried to use my old kernel to load and it was successful and Operating System loaded without an issue.

I logged in as root and checked the available kernels and I removed my updated kernel from the Operating System ( use “rpm -qa kernel” to display the available kernels, and “yum remove <kernel_version>” to remove the kernel)

Let the Virtual Machine to remove the kernel and hit “Y” if it asks in the middle of the removal

Checked the kernel and verified

I performed the update again and Virtual Machine installed the removed latest kernel again on the Operating System (Used “yum -y update“)

Once it completed the Virtual Machine I powered of and started to confirm the kernel and newly installed kernel loaded without an issue.

Note: If You Are Cloning A Virtual Machine Make Sure To Adjust The MAC Address, Read My Previous Post To Find Out How To Do That.

If You Found This Post As Useful Please Rate The Post And Share It!

原文地址：https://www.cnblogs.com/mouseleo/p/10534500.html

时间： 2024-10-08 09:29:49

Virtual Machine Kernel Panic : Not Syncing : VFS : Unable To Mount Root FS On Unknown-Block (0,0)的相关文章

Linux内核升级导致无法启动，Kernel panic - not syncing Unable to mount root fs on unknown block(0,0)

问题原因:内核的某次升级,导致系统无法启动. 首先进入recovery模式:引导界面选择-->Ubuntu高级-->出现的选项中选择能够启动的recovery模式(几个内核版本分别试一下)-->确认后就能看到一个界面出现很多选项,选择第一个recovery模式-->OK.(大概步骤就是这样,自己摸索一下就出来了) 然后就进入系统了.在这里操作如下 1,查看/boot/下的文件 abi-4.4.0-31-generic memtest86+.binabi-4.4.0-98-gener

Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004

移植文件系统时,我们可能会遇到这个问题: VFS: Mounted root (cramfs filesystem) readonly on device 31:3. Freeing unused kernel memory: 176K (c0616000 - c0642000) Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 CPU: 0 PID: 1 Comm: sh Not tainted 3.

CentOS系统Kernel panic - not syncing: Attempted to kill init

结果启动虚拟机出现如下问题: Kernel panic - not syncing: Attempted to kill init     解决方法: 系统启动的时候,按下'e'键进入grub编辑界面,编辑grub菜单,选择"kernel /vmlinuz-2.6.23.1-42.fc8 ro root=/dev/vogroup00/logvol00 rhgb quiet" 一栏,按'e'键进入编辑,在末尾增加enforcing=0,即: kernel /vmlinuz-2.6.23.

Kernel panic - not syncing Attempted to kill init

将linux按单用户模式启动时, 出现如下错误: Kernel panic - not syncing: Attempted to kill init! ? 查了一下, 有两种可能: 一种情况是是grub的配置里面,root指向有问题, 还有一个可能是内核没有硬盘的驱动造成的 对于第一种情况,解决方法如下: 系统启动的时候,按下'e'键进入grub编辑界面,编辑grub菜单, 选择"kernel /vmlinuz-2.6.23.1-42.fc8 ro root=/dev/vogroup00/lo

linux 内核启动错误和selinux参数 Kernel panic -not syncing:Attempted to kill init

今天在装某个软件的时候,修改了selinux参数.修改selinux 的某个参数值为Disable.导致 linux系统不能启动.出现如下错误 Kernel panic -not syncing:Attempted to kill init! 后经过向群友请教和自己操作和互联网搜索,终于找到了解决办法. 在linux启动界面出现时,按f2进入如下界面: 按e进入如下界面 移动到第2个选项,再按e进入编辑 在后面输入 selinux=0 按回车. 返回到原来界面, 再按b,就可以启动了. 以下为转

Err &quot;Kernel panic - not syncing: Fatal exception&quot;

从Oracel delivery下载到的Oracle Linux 6.7,安装完后启动报错"Kernel panic - not syncing: Fatal exception" 实际上在这个画面出来前还有一个VMware的提示框: 重启,在以下画面按回车: 会出现内核选择菜单: 默认选择的是UEK,选择第二个登进去就可以了. 然后可以去开机启动配置文件里面将UEK选项注释掉: 关于OEL UEK,可以参考如下文档: https://www.cnblogs.com/kerrycode

Linux启动提示Kernel panic - not syncing: Attempted to kill init解决办法

一.问题截图: 二解决方法: 1.重启客户机2.在出现开机提示迅速按esc并按e3.选择第二项按e 4.在尾部加入enforcing=0 5.回车跳转界面后按B键重启 6.进入系统后vim /etc/grub.conf在quiet尾部加入enforcing=0,这一步是为了让它永久生效 不然重启之后又会出现同样的错误提示. 7.ok,接下来你可以开心的享受linux盛宴了.

Linux启动提示&quot;&quot;Kernel panic - not syncing: Attempted to kill init&quot;&quot;永久解决办法

昨天装在vmware10中安装centos6.5,安装完成后进入系统出现如下提示: 原以为是虚拟机系统设置问题,重装2次问题依旧. 1.重新引导系统:重启centos后按E 继续按E,然后选择第2项后按E 在末尾添加:enforcing=0 添加后按回车继续 按B重新引导系统成功进入系统 2.修改grub.conf文件,永久解决问题 此处按E进行编辑 按pagedown移动光标到quiet出,然后按A进行编辑文本,添加enforcing=0.按ESC退出编辑模式 保存退出 重启系统启动正常.

Kernel panic - not syncing: Requested init linuxrc failed (error -5)

在Powerpc mpc8247上移植Linux的时候,制作了ramdisk镜像文件放在RAM里,用bootm命令启动系统时,出现如下错误: 返回的错误代码是5,在Linux源码目录/include/uapi/asm-generic的errno-base.h中定义的是I/O错误.引起错误的原因是分配的ramdisk空间小于文件系统镜像文件的大小,解决方法是在U-boot 环境变量bootargs中设置ramdisk_size一个适当的值: setenv bootargs root=/dev/ra