On Tue, Oct 1, 2013 at 10:00 AM, Franchisseur Robert
<[log in to unmask]> wrote:
> Hello,
>
> after  kernel update I almost have trouble caused by dkms (I think
> it is  since the last mkinird package).
>
> After the update when rebooting there were many error messages
> but I can boot.
>
> But at next reboot I got a kernel panic.
> Kernel panic - not sncing VFS : Unable to mount root fs on unknown-block(0,0)
>
>
> This  is  often  due  to the fact that the file  grub.conf  has  been
> erased,  so  it is easy to repair whith a Live USB, but this time  it
> was because all the lines
>
>         initrd  /initrd-2.6.18-x.y.z.el5.img
>
> have been erased in grub.conf
>
> and all the
>
>  initrd-2.6.18-x.y.z.el5.img
>
> were renamed
>
>  initrd-2.6.18-x.y.z.el5.img.dup_orig
>
>
> Is  it  possible  to do an mkinitrd from a live rescue  USB  disk  as
> I cannot boot with any of my 4 previous initrd files :
>
> initrd-2.6.18-348.6.1.el5.img.dup_orig
> initrd-2.6.18-348.12.1.el5.img.dup_orig
> initrd-2.6.18-348.16.1.el5.img.dup_orig
> initrd-2.6.18-348.18.1.el5.img.dup_orig

What kernel module(s) is your dkms supposed to build?  This may depend
on what they are for but try renaming the initrd file by removing the
.dup_orig and see if that allows the system to boot.

An attempt to rebuild initrd will probably reveal what went wrong.
/sbin/weak-modules created those .dup_orig files. I suspect the
problem is related to the module(s) built by dkms.

Akemi