Hi please let me know how to make use of initrd for rebuilding. I have not done that before. I am using fc15 live dvd for linux rescue. Let me know if any further information is required. TIA.

It's not clear exactly what your meaning of "rescue mode" is. If you mean you boot Fedora 15, then chroot into Fedora Core 9, then you should be able to do the following:This should confirm the syntax required to regenerate your FC9 initrd. It may differ. I pasted the above from Fedora 14. I don't have FC9 on a disk in a working PC to confirm.

You'll need to check in /lib/modules/ and /boot/ to get the required kernel version to use. Also it's possible you may find the new initrd located in your current directory and need to move it to /boot/. I would backup the original initrd before proceeding.

I expect the command to run will resemble the following:

Yes please let me know how to use initrd commands for that. I am using fc15 for linux rescue. I have not done before. If you need any further information kindly let me know.

I mean linux rescue and changing to chroot /mnt/sys image. My /boot have two images: initrd-2.6.25-14.fc9.i686 & initrd-2.6.27.25-78.2.25.fc9.i686.img.but no initramfs image. /lib/modules have 2.6.25-14.fc9.i686 & 2.6.27.25-78.2.25.fc9.i686.img. Let me know further actions. Thanks in advance

Even though you booted F15 for rescue purposes, once you've chrooted into FC9, you are running the installed FC9 system, so it's the FC9 commands you are running, and the FC9 man pages you have access to:Once upon a time many many moons ago a term was coined for a boot assistant to the kernel, called an INITialization Ram Disk, or initrd. Some years later, apparently after FC9 release, someone in silliness decided it needed a longer, more technically appropriate, but functionally no more than change for the sake of change, name: INITialization RAM FileSystem, or initramfs. Both initrd and initramfs are functional equivalents.

That was a pretty good explanation. Learned it. Meanwhile will run the code tmrw and let you know. Thanks again.

Command says image already exists in /boot. Rebooted. Same error.

That's to be expected. It doesn't want to run except by someone who knows what he's doing, a safety feature. You're intending to recreate what you already have, but with some required different content. That's why I pointed you to the man page instruction to read. There should be a force it option, or you can rename or remove the existing one first before running mkinitrd. Rebooting before successfully running mkinitrd won't do anything but waste time.

Well i have left that project. Very tiring. Was doing it so that I could learn. I am installing fc38. I will follow up from there. Thanks a lot to ALL who helped me out and reach up a bit higher in my conquest. Thanks again.