long way is a better learning exercise
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 05:07 PM.