Cannot boot into Arch using Gummiboot and Intel fake RAID

Question

This is my first time installing Arch Linux in a few years. The installation seemed to go fine, but I can't boot into it. At this point, when I try to boot into it this is my console output: http://pastie.org/9389435
First of all, what confuses me about this output are the RAID lines. My system currently has two RAID arrays: My RAID0 array where Windows 7 is installed and my RAID1 array where I'm attempting to install Arch Linux. My fstab nor Gummiboot entry files refer to the RAID0 array at all. Why does it activate the partitions on the RAID0 array but not the RAID1 array?
Second of all, lines 10, 11, 14, and 16 refer to /dev/sdd3. When I mount the partitions on my RAID array using the Arch live CD, I have to refer to them as either /dev/md/RAID1_0p1-4 or /dev/md124p1-4. The /dev/sda-sdd seem to refer to the individual drives. Why is it different when I try to boot into the system?
Here is my current fstab: http://sprunge.us/bQCT
The reason fstab is using labels is because the genfstab command generated an fstab that mounted the partitions on the RAID array with their /dev/md124p1-4 names. I noticed these names sometimes changed if I booted back into the live cd, so at one point I changed those names to the /dev/md/RAID1_0p1-4 names. Then in another attempt to fix the problem I'm currently having, I gave each of the partitions labels and I'm now referring to them by their labels in fstab. I also removed the commented UUID's since a few of them had changed since this fstab was generated. Everything to the right of the labels was kept from the original genfstab command.
Here is my gummiboot arch.conf entry file: http://sprunge.us/HPVb
I'm also referring to my root partition by label in this file, rather than the UUID which seems to be the norm. The reason for this is because I was previously getting an error saying that it couldn't even find the root partition based on that UUID. As you can see, I left the UUID line commented in case I have to use it again later.
Here is my mkinitcpio.conf file, which I'm thinking the problem has something to do with this since it's the part I understand the least: http://sprunge.us/IFDL
The modifications I made to this file were based on what I read in the fake raid article on the Arch wiki. All I did was make sure dm_mod and dm_mirror were added to the MODULES line and dmraid was added to the HOOKS line. At first I also had chipset_module_driver in MODULES, but it just generated warnings when I ran `mkinicpio -p linux` so I took it out. I don't know what that module would be for, since it only says "if necessary" on the wiki.
As for the emergency shell it puts me in when it fails to boot, there's not really much I can do from there. The filesystem it puts me in looks entirely different from the root filesystem I can mount from the live cd.
At this point, I'm stumped and I'm not sure where to go from here.

Answer 1

x:5:respawn:/opt/kde/bin/kdm -nodaemon
This is the line that's causing it.  It's probably not because of this line, but because kdm isn't starting properly (possibly erroring) and being re-run because of the respawn option.
Try booting into single user mode, changing the default run level to 3, and debugging it from there (figure out why kdm doesn't want to start right).