Linux - GeneralThis 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.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
The reason I didn't mention simply regenerating the initrd from a live CD is that you wouldn't know it was necessary to do so unless you understood what the problem was in the first place.
It is a much better learning exercise to actually have a look inside your initial filesystem especially if you never have before. If you don't know what an initial fs does or what an init script does you need to do this. There are macho users that build initramfs' by hand without a script. There are other cases where at least it is necessary to hand edit the init script such as creating a boot CD for a firewire root drive.
Your problem began as you didn't realize there could be references to your old volume group names inside the initrd filsystem after you had changed fstab and grub.conf. This was most likely as you had never looked inside your initial fs. By doing so you will understand the boot process better and avoid similar problems in the future. I had done this long ago out of curiosity and instantly recognized your problem. Next time you will know immediately.
A hybrid approach is possible. I strongly recommend at least looking at the contents with
cd temp_dir && gzip -dc /boot/initrd-2.6...img | cpio -i -c
and then if you want use the mkinitrd script to fix the references. You should then verify that the corrections were made by looking inside the new initrd.
Sometimes the long way provides more understanding.
Last edited by tofino_surfer; 08-28-2007 at 04:07 PM.
Just a note to say I agree with tofino_surfer. Looking at what initrd contains is very interesting and much fun. I also advise you look at it if you don't know what's inside. Look at the init script which is launched by the kernel with nash. You can customize it to your own needs. You can also have a look at the mkinitrd script and see how it is generated