Hi; I think the subject says it all. After rebuilding my kernel (and modules) I run mk_initrd and after a small think it ends with the line, failed to mount image. I've tried several different kernel sources and they all come up with the same message. ------------------------------------------------------------------ Here is the total output from mk_initrd. using "/dev/hda6" as root device (mounted on "/" as "reiserfs") creating initrd "//boot/initrd" for kernel "//boot/vmlinuz" (2.4.18) failed to mount image --------------------------------------------------------- This is how I build a kernel (as per the reference book p 234). cd /usr/src/linux make xconfig (choose a known working configuration with SuSE 8.0) make dep make clean make bzImage make modules cp /usr/src/linux-2.4.18/arch/i386/boot/bzImage /boot/vmlinuz make modules_install mk_initrd lilo Thanks for any help (I cannot turn off my computer until I have this fixed:-) -- --------- Darren Harmon http://www.darrenharmon1.uklinux.net
On Tuesday 30 July 2002 16.30, Darren Harmon wrote:
Hi;
I think the subject says it all.
After rebuilding my kernel (and modules) I run mk_initrd and after a small think it ends with the line, failed to mount image. I've tried several different kernel sources and they all come up with the same message.
Two thoughts: are you running this as root? Do you have enough disk space free on the partition that houses /tmp? //Anders
Hi; On Tuesday 30 July 2002 21:52, Anders Johansson wrote:
Two thoughts: are you running this as root? Do you have enough disk space free on the partition that houses /tmp?
Both. I only fiddle with the kernel in root (so I can do more damage:-) I have over a gig of disk space in /tmp. -- --------- Darren Harmon http://www.darrenharmon1.uklinux.net
On Tuesday 30 July 2002 23.00, Darren Harmon wrote:
Hi;
On Tuesday 30 July 2002 21:52, Anders Johansson wrote:
Two thoughts: are you running this as root? Do you have enough disk space free on the partition that houses /tmp?
Both. I only fiddle with the kernel in root (so I can do more damage:-)
:) ok, it was just a thought, since I tried running mk_initrd as regular user and got the exact same error message, since only root is allowed to mount things that aren't in fstab.
I have over a gig of disk space in /tmp.
OK, one more thought that occurred to me after I posted the other message: are you running a home grown kernel when you run mk_initrd? If you are, do you have loopback support built into it? //Anders
Darren Harmon <darrenharmon1@uklinux.net> writes:
After rebuilding my kernel (and modules) I run mk_initrd and after a small think it ends with the line, failed to mount image. I've tried several different kernel sources and they all come up with the same message.
Have you enabled 'loop' either built-in or as a module? mk_initrd will not work without it.
Hi; On Tuesday 30 July 2002 22:07, Graham Murray wrote:
Have you enabled 'loop' either built-in or as a module? mk_initrd will not work without it.
I've tried this but no luck. Note. Running mkinitrd fails even on the default SuSE kernel. -- --------- Darren Harmon http://www.darrenharmon1.uklinux.net
On Wednesday 31 July 2002 00.23, Darren Harmon wrote:
Hi;
On Tuesday 30 July 2002 22:07, Graham Murray wrote:
Have you enabled 'loop' either built-in or as a module? mk_initrd will not work without it.
I've tried this but no luck.
Note. Running mkinitrd fails even on the default SuSE kernel.
The simplest way to find out what goes wrong is to edit /sbin/mk_initrd, find the mount command (in 8.0 it's on lines 416 and 419) and remove the "2>/dev/null" bit at the end. This will enable the error messages to be printed. //Anders
Hi :) Please ~ am getting the SAME error message ~ Did you find a Solution ? Thanks best wishes ____________ sent on Linux ____________
participants (4)
-
Anders Johansson -
Darren Harmon -
Graham Murray -
tabanna