SCIENTIFIC-LINUX-USERS Archives

October 2013

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Steven J. Yellin" <[log in to unmask]>
Reply To:
Steven J. Yellin
Date:
Tue, 1 Oct 2013 13:27:45 -0700
Content-Type:
multipart/mixed
Parts/Attachments:
text/plain (2696 bytes)
     You said initrd lines were erased in grub.conf and the initrd* files 
in /boot/grub were renamed.  That's weird!  I assume you have already 
tried editing grub.conf to adapt it to the renamed initrd files, and since 
you didn't say so, I assume that vmlinuz-2.6.18-348.18.1.el5 was not 
renamed.  If I'm mistaken, grub.conf should be edited accordingly, or the 
files should be renamed back so as to be consistent with grub.conf.
     I've no experience with a problem like yours, so I'll just guess that 
something interfered with installation of the kernel rpm at an especially 
bad step in the process.  Check with rpm (within chroot to your normal 
root file system from, say, a Live USB) that it thinks 
kernel-2.6.18-348.18.1.el5.x86_64 is installed.  Verify that there's a 
directory /lib/modules/2.6.18-348.18.1.el5 with over 100 MB in it, and 
that in addition to the strangely renamed initrd file, /boot has files 
config-2.6.18-348.18.1.el5, symvers-2.6.18-348.18.1.el5.gz, 
System.map-2.6.18-348.18.1.el5, and vmlinuz-2.6.18-348.18.1.el5.  If the 
latest SL5 kernel rpm is not installed, or even if it already is, you 
could try installing or reinstalling it or an older one.

Steven Yellin

On Tue, 1 Oct 2013, Franchisseur Robert 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
>
> Thanks for your help.
>
> --
>                 Best regards,
>                               Robert FRANCHISSEUR
> ____ Apollo_gist :-)_______________________________________________
> | Robert FRANCHISSEUR                 Phone  : +33 (0)950  635  636 |
> | 30 rue René Hamon                   Phone  : +33 (0)1 46 78 37 29 |
> | F-94800 VILLEJUIF            e-mail : Robert at Franchisseur . fr |
> -------------------------------------------------------------------
>

ATOM RSS1 RSS2