Re: [tlug] Kernel panic

[Brian Chandler <brian@example.com>]

SL Baur wrote:
> On 4/22/08, Brian Chandler <brian@example.com> wrote:
>
> >    0 -rw-r--r--  1 root root       0 Apr 18 17:03
> > initrd.img-2.6.22-14-generic
> >  7064 -rw-r--r--  1 root root 7219550 Jan 27 18:24
> > initrd.img-2.6.22-14-generic.bak
> >  7064 -rw-r--r--  1 root root 7218967 Apr 18 17:01
> > initrd.img-2.6.22-14-generic.dpkg-bak
>
> What's wrong with this picture?  (Your initrd is empty).

Shiver my timbers! So it is...

> You are going to have to rebuild your initrd.  By the way, how much
> disk space do you have on that partition?
>
> The commands you need to run (as root) are:
> rm /boot/initrd.img-2.6.22-14-generic
> mkinitrd /boot/initrd.img-2.6.22-14-generic 2.6.22-14-generic

Plenty (gigabytes) of space, so I deleted the empty file. Then /bin/sh 
says it can't find mkinitrd.

I tried looking with find, and couldn't find it. I also googled a bit 
(mkinitrd and ubuntu in case there was something different), and found 
plenty of ubuntu references to mkinitrd, but no hint of where I might 
find it. Hmmm??

Thanks for your ongoing help.

I still don't understand why there isn't some sort of default procedure 
that simply reinstalls whatever bits are necessary to get the same 
vanilla system running. (I also wonder if I could just copy the .bak 
version of the file...?)

Brian Chandler