Follow-up Comment #3, bug #25008 (project grub): Thanks for the reply. I realized what was wrong. I was creating the core.img using grub-mkimage but when I ran grub-install it overwrote the image I created previously.
So the correct command should be: grub-install --root-directory=/media/sdg2 --modules="linux raid ext2 gpt pc biosdisk" /dev/sdg2 I still wonder why the "pc" and "linux" modules are not put in core.img when I ran grub-install and modules like "pxe" and "bsd" were there? The second reason I was confused was not understanding the function of grub-install from the documentation. I now see that the grub-install manual page has the crucial information in one sentence at the very end. I would expect to see that sentence at the very top of the DESCRIPTION section, not hidden after listing all the options. If the user could see the steps that grub-install executes it would have helped, too. grub-install should accept the '-v' option to pass to its subordinate processes to verbosely display the steps it's executing to be able to properly debug problems (mkimage, setup, etc.). I saw several examples on the internet where grub-install is followed by grub-setup, which is unnecessary since install does setup. So I probably am not the only one confused. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?25008> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/ _______________________________________________ Bug-grub mailing list Bug-grub@gnu.org http://lists.gnu.org/mailman/listinfo/bug-grub