On 2013-03-13, Johnny Hughes <johnny@xxxxxxxxxx> wrote:
(...)
> On 03/13/2013 05:17 PM, Johnny Hughes wrote:
>> On 03/13/2013 04:19 PM, Liam O'Toole wrote:
>>> On 2013-03-13, Emmett Culley <emmett@xxxxxxxxxxxxxxx> 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=3Depel on two of five machines, one of=
> which is the host for the three VM's that succeeded and the one that fai=
> led, 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 fail=
> s 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 t=
> o 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=3D6304
>>>
>>> Just today kernel 2.6.32-358.2.1 became available. The problem is stil=
> l
>>> present, but only on the same one machine.
>>>
>> This file exists in the kernel:
>> /lib/modules/2.6.32-358.2.1.el6.x86_64/kernel/drivers/md/dm-mod.ko
>>
>> Somehow it seems that in some machines it is not making it into the ini=
> trd.
>
> Try this command where the kernel is installed and not booting (when
> booted into a kernel that works):
>
> lsinitrd /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img | grep dm-mod
>
> (if you have one of the other 358 kernels installed, use that version
> instead of2.6.32-358.2.1.el6.x86_64 )
>
Here you go:
$ uname -r && lsinitrd /boot/initramfs-2.6.32-358.2.1.el6.i686.img |
grep dm-mod
2.6.32-279.22.1.el6.i686
-rwxr--r-- 1 root root 106212 Mar 13 17:11
lib/modules/2.6.32-358.2.1.el6.i686/kernel/drivers/md/dm-mod.ko
So the module appears to be present in the initrd.
The only distinguishing feature I can think of in the machine that is
failing is that it has a solid-state drive. Relevant?
--
Liam
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
