LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 08-14-2004, 05:26 PM   #1
jjorloff1
Member
 
Registered: Nov 2003
Distribution: Gentoo (I've tried everything twice+)
Posts: 48

Rep: Reputation: 15
Kernel 2.6.7 install error, initrd-2.6.7.img error


I am installing my kernel and i got all the way up to the very last step but it give me and error. the step i mean is: /sbin/mkinitrd /boot/initrd-2.6.7.img 2.6.7

when i type that in it gives the error:

/boot/initrd-2.6.7.img/var/tmp is not a directory

and i tried some other things, and i may possibly have it up, but im afraid to shut down my computer for fear of not booting up again. What i did was. I manually deleted the symlink to my old initrd file (not a .img, something to do with gzip according to konquerer) and i made a new symlink to the initrd-2.6.7 (konquerer says gzip file) file and my /boot/grub/menu.lst file seems to be right if what i did is not wrong, but i really have no idea. can someone tell me if it will work, or if ive messed it up.

oh and also when i run the /sbin/mkinitrd alone i get this (may have some consequence to the help i recieve)



Root device: /dev/hda3 (mounted on / as reiserfs)
Module list: reiserfs

Kernel image: /boot/vmlinuz-2.6.5-7.104-default
Initrd image: /boot/initrd-2.6.5-7.104-default
Shared libs: lib/ld-2.3.3.so lib/libc.so.6 lib/libselinux.so.1
Modules: kernel/fs/reiserfs/reiserfs.ko

Kernel image: /boot/vmlinuz-2.6.7
Initrd image: /boot/initrd-2.6.7
Shared libs: lib/ld-2.3.3.so lib/libc.so.6 lib/libselinux.so.1
Cannot determine dependencies of module reiserfs. Is modules.dep up to date?
Modules:
none


And when i run this command (/sbin/mkinitrd -t /var/tmp -m /lib/modules/2.6.7) to specify the modules and bypass the */var/tmp error i get this:


Root device: /dev/hda3 (mounted on / as reiserfs)
Module list: /lib/modules/2.6.7

Kernel image: /boot/vmlinuz-2.6.5-7.104-default
Initrd image: /boot/initrd-2.6.5-7.104-default
Shared libs: lib/ld-2.3.3.so lib/libc.so.6 lib/libselinux.so.1
Cannot determine dependencies of module /lib/modules/2.6.7. Is modules.dep up to date?
Modules:
none

Kernel image: /boot/vmlinuz-2.6.7
Initrd image: /boot/initrd-2.6.7
Shared libs: lib/ld-2.3.3.so lib/libc.so.6 lib/libselinux.so.1
Cannot determine dependencies of module /lib/modules/2.6.7. Is modules.dep up to date?
Modules:
none



is it safe to reboot my comp, or will i not be able to boot it up with the new kernel?
 
Old 08-14-2004, 05:39 PM   #2
jjorloff1
Member
 
Registered: Nov 2003
Distribution: Gentoo (I've tried everything twice+)
Posts: 48

Original Poster
Rep: Reputation: 15
???
 
Old 09-14-2004, 10:18 PM   #3
jrobicha
LQ Newbie
 
Registered: Sep 2004
Posts: 1

Rep: Reputation: 0
You may have selected the reiserfs as builtin instead of a module (make menuconfig -> File Systems -> Reiser FS ) while the /etc/sysconfig/kernel file contains INITRD_MODULES = "reiserfs". Either you remove reiserfs from the INITRD_MODULES variable or you set ReiserFS as a module <M> instead of being built-in <*>...

I just had the same problem stucking me for the last 2 hours ....

Good Luck...

Jp

P.S. Yes it is safe to reboot since the old kernel will still be accessible, but trying to boot from the new one will certainly crash.... unless you solve that "reiserfs" problem

P.P.S. BTW, just "mkinitrd" alone will do ... unless you have dozen of kernels in /boot (and are concerned about time taken by mkinitrd), you don't need to specify the one for which you want to built the initrd

Last edited by jrobicha; 09-14-2004 at 10:23 PM.
 
Old 09-15-2004, 12:15 AM   #4
amosf
Senior Member
 
Registered: Jun 2004
Location: Australia
Distribution: Mandriva/Slack - KDE
Posts: 1,672

Rep: Reputation: 46
Why not just compile the root filesystems and such into the kernel and skip the initrd?

But mkinitrd should do the job anyway... eg on my system I just bullt 2.6.9-rc2 kernel, so the following:

mkinitrd initrd-2.6.9-rc2.img 2.6.9-rc2

would make the initrd if I wanted to use one...

Last edited by amosf; 09-15-2004 at 12:24 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel initrd.img? microsoft/linux Debian 15 10-29-2004 12:35 PM
initrd.img GONE after kernel instal?!?! denniz Debian 5 08-17-2004 03:55 PM
no initrd.img after install of new kernel? denniz Linux - General 1 08-17-2004 09:25 AM
Initrd.img Error...Isolinux: Disk Error 80 bohh Slackware - Installation 1 07-29-2004 11:20 AM
no initrd.img after upgrading kernel buknoy Linux - General 1 10-10-2003 04:22 AM


All times are GMT -5. The time now is 11:49 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration