[CentOS] Kernel panic after update to 6.4
Johnny Hughes
johnny at centos.org
Wed Mar 13 21:43:55 UTC 2013
On 03/13/2013 04:19 PM, Liam O'Toole wrote:
> On 2013-03-13, Emmett Culley <emmett at webengineer.com> wrote:
>
> (...)
>
>> So let's start again.
>>
>> Kernel panic - Not syncing: Attempted to kill init!
>> Pid: 1, comm: init not tainted: 2.6.32-358.0.1.el6.x86_64 #1
>>
>> After yum upgrade --enablerepo=epel on two of five machines, one of which is the host for the three VM's that succeeded and the one that failed, just as the host.
>>
>> I have a screen shot of that VM's boot failure, but I don't know the proper way to include it in a post.
>>
>> I've uninstalled that kernel and ran yum upgrade again, it still fails on that kernel, on both the host and the VM. I suppose the good thing is that it happened on a VM guest that is not critical, so I don't have to experiment with the host that has four important guests running on it.
>>
>> Any ideas?
>>
>> Emmett
> I saw this problem on one machine I upgraded from 6.3 to 6.4 recently.
> When I boot it in verbose mode I see the following messages:
>
> dracut: /proc/misc: No entry for device-mapper found
> dracut: Failure to communicate with kernel device-mapper driver
>
> which led me to the following bug report:
>
> http://bugs.centos.org/view.php?id=6304
>
> Just today kernel 2.6.32-358.2.1 became available. The problem is still
> present, but only on the same one machine.
>
What does this command say:
rpm -q device-mapper
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.centos.org/pipermail/centos/attachments/20130313/eecd3103/attachment.sig>
More information about the CentOS
mailing list