If I correctly understand how far along you've come ... that you now have access to all your file-systems, have verified that they are ok (or at least good enough for now), the ability to boot the system is all that is lacking. This means you are ready to repair and/or rebuildi the boot system. I can only INFER that the "sleeping forever" problem stems from a messed up boot configuration, but I DO NOT KNOW with complete certainty as I am not familiar with this specific problem. That said ... it's highly probable that constructing a solid boot system will eliminate that issue.
advance apology if I bore you with detail you already know ... I'd rather err on the side of being boring and long winded than on the side of cut and confusing ... especially with the bootloader, which is one of the trickier bits of any gnu/linux system.
Everything needed to boot your system must reside in a directory, "/boot" (I just LOVE the simplicity of *nix). Sometimes, "/boot" is simply a directory under "/", aka "THE ROOT FILE SYSTEM". It might be a separate file-system that is mounted on "/boot". Underneath the boot directory, you should find a kernel, such as "vmlinuz-220.127.116.11-147.fc13.i686", a bootstrap-er/kernel-helper/ramfs (don't really know the correct term) such as "initramfs-18.104.22.168-147.fc13.i686.img", and other files following the same naming pattern, obviously associated with a specific kernel. Underneath "/boot/grub", you will find all the files needed by the grub bootloader. The one file file we really care about, besides the kernel stuff, is "/boot/grub/grub.conf", which controls the boot process.
The first step, make sure you actually have a kernel ... I know I do because it's running ...
... so mine looks like this:
[root@dolphin]# uname -r #because I have a bad memory
[root@dolphin]# cd /boot #look in the right place
[root@dolphin]# find . -regex ".*147\.2\.4.*" -ls #list the files associated with my running kernel
33 110 -rw-r--r-- 1 root root 111193 Jul 23 12:32 ./config-22.214.171.124-147.2.4.fc13.i686
35 11328 -rw-r--r-- 1 root root 11598381 Aug 3 08:38 ./initramfs-126.96.36.199-147.2.4.fc13.i686.img
32 1545 -rw-r--r-- 1 root root 1580717 Jul 23 12:32 ./System.map-188.8.131.52-147.2.4.fc13.i686
34 3357 -rwxr-xr-x 1 root root 3436128 Jul 23 12:32 ./vmlinuz-184.108.40.206-147.2.4.fc13.i686
The second step: collect a little info about your particular system
From your original post, you seem to have 2 hard drives with boot as a separate file-system on /dev/sda1 and /dev/sdb1 and a root file-system in the lvm "/dev/VolGroup/lv_root". It looks like a raid 1 configuration to me. This is not super important to know in order to access root ... and lvm does a great job of abstracting from the hardware. Grub, the actual boot loader program does not really know how to speak either raid nor lvm. The "/boot" partition may live happily on a raid device, NOT in an lvm container (Volume Group to show off my lingo), provided that the device is raid level 1
From your post ... it is also possible that you have 2 disks with 2 completely separated oses, in which case you need to know the order in which these disks are accessed by the bios at boot time. This is usually under a menu named something like "disk order" or "boot priority" in the system bios.
Unless /boot sits on a raid 1 device, you REALLY need to know the order the disks so you can tell grub what he's supposed to do for you. And if /boot sits on a raid 1 device, you REALLY need to know, because you must install a subset of grub code the the mbr (Master Boot Record) of at least the first device in the array.
Your existing (or I should say the one you posted) /boot/grub/grub.conf has the line "root (hd0,0)". English translation: look for more grub stuff and a kernel in the first partition of the first disk as defined by the system BIOS".
Whew! I think we're finally ready to put humdy dumpty back together .....
Make sure that /boot/grub/grub.conf looks along these lines:
title Fedora (220.127.116.11-147.2.4.fc13.i686)
kernel /vmlinuz-18.104.22.168-147.2.4.fc13.i686 ro root=/dev/mapper/dolphin-root2 rd_LVM_LV=dolphin/root2 rd_MD_UUID=224aa24a:8d2b2d73:4fa6bae4:438fc5b1 rd_LVM_LV=dolphin/swap rd_NO_LUKS rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
making sure that the kernel files you need actually exist and that (hdX,Y) is correct for YOUR system. The line "default=0" simply says that the first os listed in this file will be the default os, what will get booted if nothing else is choosen after the number of seconds specified by timeout=<an interger value>.
Notice also that "#hiddenmenu" and "#splashimage....." have the # in front ... which tells grub "ignore this line". Don't worry about this stuff right now ... get a good boot first
Now the potentially confusing part:
1. IF /boot is NOT on a raid device ... you are about done ... make sure that the boot parrtion is active, reboot, have fun!
2. IF /boot is on a raid 1 device, then a little grub must get shoved into the mbr of the first drive in the array ...
a. As root user, type "grub". This will put you into a "grub" shell signified by the command prompt "grub> "
b. Type "root(hdX,Y)" where X and Y are the values you determined for /boot/grub/grub.conf
c. Type "setup (hdX)"
You may get some errors like "1_5stage file not found ... non-fatal" ... don't worry about it now ... we just want to get some junk in mbr .... and if grub says "non-fatal", it's probably jammed some code into mbr and you are ready to reboot ...
At this point, double cross your fingers (VERY IMPORTANT ... DO NOT SKIP) and reboot