To me, it is beginning to sound more and more as though your LFS system has never booted, and it is hanging somewhere very early during booting. Your repeated use of the phrase "standing at grub" makes me think it is stopping at a grub> or grub rescue> prompt (a common thing). That in turn suggests that the grub-install /dev/sda step worked. If you also ran that grub-mkconfig command on that page, then the problem could be in the config file generated by that command (the reason spiky0011 wants you to post it).

I never intended for you to actually use the Super Grub 2 Disk. Originally, you were talking about things in chapter 3 of the BLFS book (about creating an emergency boot disk with xorriso). You even installed xorriso but were having problems burning with it. Remember? The Super Grub 2 Disk is a utility to boot a system whose GRUB boot loader is broken. Therefore, it satisfies the intent chapter 3 of the BLFS book. I only intended to pry you loose from xorriso so you could continue on with BLFS. But unfortunately, that is not what you were doing. How you got to chapter 3 of BLFS before the LFS system ever booted remains a mystery to readers here. All I accomplished was to divert you away from what you should be doing (fixing your boot loader). I regret that very much and would like to divert you back to fixing your boot loader.

Here is what I think you should do...

Do what spiky0011 suggested and somehow copy and paste in your next post the contents of your grub.cfg file and the output of fdisk -l.


P.S.: You know, you are using a very old version of the LFS book (probably because of that live CD). Recent versions of the LFS book don't have that grub-mkconfig step. It's true. It has been dropped from the book, and the book now even recommends that we not use that command for LFS systems. It instead has steps to manually create a simple grub.cfg file. That is what I do. Of course you should do what you think is best. But if you never get anywhere with this matter, then look at chapter 8 of the v7.2 LFS book about creating a simple config file by hand. It might solve your problem and get the system booting.

I see that this is marked as solved
If it is can you post the fix to the problem for future ref
Thks