I can change redhat-release of course but how can ESX or anything else be reading /etc/redhat-release when the root volume is not even mounted yet?The kernel panic is right when root is... [by freethinker]
Relatively new to Linux, so please bear with me. Recently installed Fedora 19, updated, and installed a number of development packages preparatory to installing Oracle XE, which went well. Downloaded VMWare (version 10) and it installed fine.
Problem - when I tried to run it, it complained out missing kernel-headers. Output from uname -r is: 3.10.10-200.fc19.x86_64.
just upgraded to kernel 3.4.3-1.fc17.x86_64 and it went panic after 2 minutes.
Now I get a kernel panic message when booting the machine:
Kernel panic - not syncing: VFS: Unable to mount root fs n unknown-block(0,0)
Pid: 1, comm: swapper/0 Not tainted 3.4.3-1.fc17.x84_64 #1
and the call trace which I'm not reporting.
Using old kernels gives me a filesystem error, requiring to ex
Updated recently to kernel 3.4 and getting kernel panic on boot.
Loading Fedora (3.4.2-1.fc16.x86_64)
Loading initial ramdisk...
[ 9.224897] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
3.3.x works fine, so I don't think it's a filesystem problem.