Hello all: I am trying to build in initrd fail for a kernel that I compiled. I want to use my 3Ware ATA raidcard as a module. So I made sure the module was added to the /etc/sysconfig/kernel file and did the following: ==================================================================== falcon:/boot # mkinitrd -k linux-2.4.21-2 -i initrd-linux-2.4.21-2 using "/dev/sda1" as root device (mounted on "/" as "reiserfs") creating initrd "/boot/initrd-linux-2.4.21-2" for kernel "/boot/linux-2.4.21-2" (2.4.21) failed to mount image ==================================================================== The failure message is: failed to mount image. No /boot/initrd-linux-2.4.21-2 file was created. Any ideas what I am doing wrong? Thanks. JIm
On Wednesday, July 16, 2003, at 11:36 AM, Jim Norton wrote:
Hello all:
I am trying to build in initrd fail for a kernel that I compiled. I want to use my 3Ware ATA raidcard as a module. So I made sure the module was added to the /etc/sysconfig/kernel file and did the following:
==================================================================== falcon:/boot # mkinitrd -k linux-2.4.21-2 -i initrd-linux-2.4.21-2 using "/dev/sda1" as root device (mounted on "/" as "reiserfs")
creating initrd "/boot/initrd-linux-2.4.21-2" for kernel "/boot/linux-2.4.21-2" (2.4.21) failed to mount image ====================================================================
The failure message is: failed to mount image.
No /boot/initrd-linux-2.4.21-2 file was created.
Any ideas what I am doing wrong?
Using 3ware cards. ;-) Seriously. I have 3 of them in my SuSE linux and I had a lot of problems. If you browse back the list for a few days, you'll find a message (and an update) I sent regarding a freeze with 8.2. This could not be your problem, though. I tried to build the 2.4.20 kernel and I had problems. It booted, without having to build initrd, but the kernel crashed just in the 3ware module, while fsck-ing. It was months ago. I don't remember exectly. When you have troubles over troubles, you don't remeber all the things you did and what fixed things and what not. Eventually I was sick and tired to running after these idosyncracies. This is the origin of my decision of trying with 8.2 All I can say for sure, is the 3w-xxxx.o module that comes along with linux (at least 2.4.18 and 20) is older than the one you can download from the 3ware site. Good luck.
Thanks. JIm
Ciao, Ermanno Polli
Jim Norton wrote, On 07/16/2003 05:36 PM:
I am trying to build in initrd fail for a kernel that I compiled. I want to use my 3Ware ATA raidcard as a module. So I made sure the module was added to the /etc/sysconfig/kernel file and did the following:
==================================================================== falcon:/boot # mkinitrd -k linux-2.4.21-2 -i initrd-linux-2.4.21-2 using "/dev/sda1" as root device (mounted on "/" as "reiserfs")
creating initrd "/boot/initrd-linux-2.4.21-2" for kernel "/boot/linux-2.4.21-2" (2.4.21) failed to mount image ====================================================================
The failure message is: failed to mount image.
No /boot/initrd-linux-2.4.21-2 file was created.
Any ideas what I am doing wrong?
IIANM, the sysconfig file is only used for the defaults. Try adding -m <modules you want to put in the initrd.> -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Jim Norton wrote, On 07/16/2003 05:36 PM:
I am trying to build in initrd fail for a kernel that I compiled. I want to use my 3Ware ATA raidcard as a module. So I made sure the module was added to the /etc/sysconfig/kernel file and did the following:
==================================================================== falcon:/boot # mkinitrd -k linux-2.4.21-2 -i initrd-linux-2.4.21-2 using "/dev/sda1" as root device (mounted on "/" as "reiserfs")
creating initrd "/boot/initrd-linux-2.4.21-2" for kernel "/boot/linux-2.4.21-2" (2.4.21) failed to mount image ====================================================================
The failure message is: failed to mount image.
No /boot/initrd-linux-2.4.21-2 file was created.
Any ideas what I am doing wrong?
IIANM, the sysconfig file is only used for the defaults. Try adding -m <modules you want to put in the initrd.>
Thanks for the information. Somebody suggested that 3Ware cards/drivers are the problem. I guess he was having troubles with them. I on the other hand have nothing be great success with my 3Ware card ( 7500 - 4 port ). My issue is that I just want to load the 3Ware module from initrd and not compile it directly into the kernel. Thanks again, Jim
Jim Norton wrote, On 07/17/2003 12:56 AM:
Jim Norton wrote, On 07/16/2003 05:36 PM:
==================================================================== falcon:/boot # mkinitrd -k linux-2.4.21-2 -i initrd-linux-2.4.21-2 using "/dev/sda1" as root device (mounted on "/" as "reiserfs")
Stated a bit differently, try "mkinitrd -k linux-2.4.21-2 -i initrd-linux-2.4.21-3 -m "reiserfs,3w-xxxx" (or a comma separated list of your modules, this was just a guess)
creating initrd "/boot/initrd-linux-2.4.21-2" for kernel "/boot/linux-2.4.21-2" (2.4.21) failed to mount image ====================================================================
The failure message is: failed to mount image.
No /boot/initrd-linux-2.4.21-2 file was created.
The initrd you created had no modules, because you gave it none. Only vmlinuz and vmlinuz.shipped get their modules from /etc/sysconfig/kernel. Therefore, it could not load your /
Thanks for the information. Somebody suggested that 3Ware cards/drivers are the problem. I guess he was having troubles with them. I on the other hand have nothing be great success with my 3Ware card ( 7500 - 4 port ). My issue is that I just want to load the 3Ware module from initrd and not compile it directly into the kernel.
Try the above and let us know. :) -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Ok thanks again for the information. Now how do I tell GRUB to use the new initrd for a given kernel image?
Jim Norton wrote, On 07/17/2003 12:56 AM:
Jim Norton wrote, On 07/16/2003 05:36 PM:
==================================================================== falcon:/boot # mkinitrd -k linux-2.4.21-2 -i initrd-linux-2.4.21-2 using "/dev/sda1" as root device (mounted on "/" as "reiserfs")
Stated a bit differently, try "mkinitrd -k linux-2.4.21-2 -i initrd-linux-2.4.21-3 -m "reiserfs,3w-xxxx" (or a comma separated list of your modules, this was just a guess)
creating initrd "/boot/initrd-linux-2.4.21-2" for kernel "/boot/linux-2.4.21-2" (2.4.21) failed to mount image ====================================================================
The failure message is: failed to mount image.
No /boot/initrd-linux-2.4.21-2 file was created.
The initrd you created had no modules, because you gave it none. Only vmlinuz and vmlinuz.shipped get their modules from /etc/sysconfig/kernel. Therefore, it could not load your /
Thanks for the information. Somebody suggested that 3Ware cards/drivers are the problem. I guess he was having troubles with them. I on the other hand have nothing be great success with my 3Ware card ( 7500 - 4 port ). My issue is that I just want to load the 3Ware module from initrd and not compile it directly into the kernel.
Try the above and let us know. :)
-- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Jim Norton wrote, On 07/17/2003 10:03 AM:
Ok thanks again for the information. Now how do I tell GRUB to use the new initrd for a given kernel image?
Maybe edit /boot/grub/menu.lst and just add an entry for the new kernel, giving the same disk partition but different kernel image name and initrd name. Or, try the bootloader module of Yast. -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Ok got it to work. Thanks to Joe Morris for providing part of the missing pieces. However, once I supplied the list of modules on the command line, mkinitrd still failed to mount /. I had to build and load the LOOP module before running mkinitrd. thanks Joe. I am now running with my 3Ware ATA Raid driver as a module and not in the kernel. :-)
Jim Norton wrote, On 07/16/2003 05:36 PM:
I am trying to build in initrd fail for a kernel that I compiled. I want to use my 3Ware ATA raidcard as a module. So I made sure the module was added to the /etc/sysconfig/kernel file and did the following:
==================================================================== falcon:/boot # mkinitrd -k linux-2.4.21-2 -i initrd-linux-2.4.21-2 using "/dev/sda1" as root device (mounted on "/" as "reiserfs")
creating initrd "/boot/initrd-linux-2.4.21-2" for kernel "/boot/linux-2.4.21-2" (2.4.21) failed to mount image ====================================================================
The failure message is: failed to mount image.
No /boot/initrd-linux-2.4.21-2 file was created.
Any ideas what I am doing wrong?
IIANM, the sysconfig file is only used for the defaults. Try adding -m <modules you want to put in the initrd.>
-- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (3)
-
Ermanno Polli -
Joe Morris (NTM) -
jrn＠oregonhanggliding.com