Several errors starting EC2 instance - EBS-backed

Question

A little background: We converted our S3-backed (instance-store) AMI to an EBS-backed AMI recently. The process basically equated to:

1. Stop the server
2. Image the filesystem using ec2-bundle-image
3. rsync that image onto a new EBS volume (excluding several directories: --exclude=/root/.bash_history --exclude=/home/*/.bash_history --exclude=/etc/ssh/ssh_host_* --exclude=/etc/ssh/moduli --exclude=/etc/udev/rules.d/*persistent-net.rules --exclude=/mnt/* --exclude=/proc/* --exclude=/tmp/* --exclude=/sys/* --exclude=/dev/*
4. cd to the EBS volume's /dev
5. run for i in console null zero pty; do MAKEDEV $i; done
6. create a snapshot of that EBS volume in the AWS management console
7. create an AMI from the EBS snapshot
8. launch this new AMI

The new AMI I created does boot, correctly serves our websites, and is reachable by ssh. However, I've recently tried to mount an EBS volume with some MP3s on this new instance, and I'm getting errors -- namely:

# mount -t ext3 /dev/sdp /production
mount: /dev/sdp is not a valid block device

I have since run MAKEDEV sd in /dev and tried again to mount it, with no luck.

EDIT: Wow, I made a dumb mistake. the correct command to mount this volume is mount -t ext3 /dev/sdp1 /production. That said, I would still like information about these errors in the startup log, as they worry me.

There's a full paste of the log I copy-pasted from Amazon's AWS management console here: http://pastebin.com/NCvzQyum

The lines that concern me are the following:

139-143:

Mount failed for selinuxfs on /selinux: No such file or directory

modprobe: FATAL: Could not load /lib/modules/2.6.16-xenU/modules.dep: No such file or directory

modprobe: FATAL: Could not load /lib/modules/2.6.16-xenU/modules.dep: No such file or directory

149-159:

/proc is empty (not mounted ?)

hostname: the specified hostname is invalid udev requires a kernel >= 2.6.18, not started.

[31mfailed!
[39;49m

[31mfailed!
[39;49m

Mount point '/dev/shm' does not exist. Skipping mount.
[33m(warning).
[39;49m

171-177:

Mounting local filesystems...mount: special device /dev/sda2 does not exist
mount: mount point /production does not exist
mount: none already mounted or /sys busy
mount: according to mtab, sysfs is already mounted on /sys

[31mfailed.
[39;49m

The last one, at 204-206, is familiar. We're using Amazon RDS so we don't need a local mysql daemon, and I'm aware that the root device is too full -- and I'll be fixing that anyway.

Thanks in advance to anyone who tries to help out!