F19 won't boot after swap's UUID was changed

The other day, I installed a new distro on my computer. This involved reformatting 3 partitions, one of which was swap. When partitions are reformatted, their UUIDs are changed.

I used the new distro to go into my Fedora 19's fstab and change the existing UUIDs to the new ones.

However, F19 now will not boot, and the last few lines of the "sosreport.txt" file that the emergency shell generated read as follows:

[ 2.159705] hatbox systemd[1]: Found device Hitachi_HDS722020ALA330.
[ 184.695497] hatbox dracut-initqueue[104]: Warning: Could not boot.
[ 184.710123] hatbox dracut-initqueue[104]: Warning: /dev/disk/by-uuid/3a9b0fe5-06b3-4897-a878-ced87d469da2 does not exist
[ 184.713173] hatbox systemd[1]: Starting Dracut Emergency Shell...

The UUID it can't find was that of my swap file, prior to the reformat. It now has a new UUID.

From this, I conclude 4 things:
1: The UUID of my swap file is written into the initramfs.
2. It takes forever to get to an "emergency shell" after this problem occurs (note the difference in the timestamps). One might think the computer's simply hung.
3. Fedora does not play well with others.
4. <redacted due to use of inappropriate language>

Can someone tell me how to regenerate the initramfs, or otherwise get around this problem?