Host server:
HP Compaq 8200 Elite Convertible Minitower PC
Intel Core i7-2600 CPU @ 3.40 GHz.
16.0 GB RAM
Windows 7 Enterprise N Operating system
Oracle VirtualBox 4.3.10 r93012
VM Instance has 4096MB RAM, 80 GB on a single partition.
CentOS 6.5 has been installed and running flawlessly for 4 months.
Last working kernel was kernel-2.6.32-431.5.1.el6.x86_64
Last yum update installed kernel-2.6.32-431.11.2.el6.x86_64
Following yum update, the following message appeared after boot:
Code: Select all
Kernel panic — not syncing: VFS: Unable to mount root fs on unknown—block(0,0)
Pid: 1, comm: swapper Not tainted 2.6.32-431.11.2.el6.x86_64 #1
Call Trace:
[ <ffffffff81527823> ] ? panic+0xa7/0x16f
[ <ffffffff81c27432> ] ? mount_block_root+0x2160x2cb
[ <ffffffff81002930> ] ? bstat+0x2b0/0x980
[ <ffffffff81c2753d> ] ? mount_root+0x56/0x5a
[ <ffffffff81c276b1> ] ? prepare_namespace+0x170/0x1a9
[ <ffffffff81c2692a> ] ? kernel_init+0x2e1/0x2f7
[ <ffffffff8100c20a> ] ? child_rip+0xa/0x20
[ <ffffffff81c26649> ] ? kernel_init+0x0/0x2f7
[ <ffffffff8100c200> ] ? child_rip+0x0/0x2O
Other posts on the subject of similar kernel panics have usually attributed this to a glitch in the install process. People have rolled back to the previous kernel, reinstalled the new kernel, and life is good.
I have successfully rolled back the previous kernel, so I am able to boot the CentOS instance. Unfortunately, I have run 'yum update' to reinstall the kernel about 3 times now, and post-reboot we always wind up with a similar crash screen.
Does anyone have any ideas as to how to work around this without avoiding 'yum update' for the next six months?