Amazon Web Services Blog

We built a custom Centos5-x86_64 instance and installed the 2.6.16.33 kernel source and kernel modules (for x86_64). It boots up fine if /dev/sda2,3 aren't in fstab but if we add them as outlined in the ec2 manual, we get the following output (from dmesg):

device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com
MC: drivers/edac/edac_mc.c version edac_mc  Ver: 2.0.0 Aug 15 2007
NET: Registered protocol family 2
Registering block device major 8
 sdb: unknown partition table
 sdc: unknown partition table

A little later in the boot process, there are other filesystem related errors (not sure if they're connected):

md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
EXT3 FS on sda1, internal journal
loop: loaded (max 8 devices)
kjournald starting.  Commit interval 5 seconds
EXT3 FS on loop0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Buffer I/O error on device loop0, logical block 206866
... (repeats multiple times) ...
Aborting journal on device loop0.
EXT3-fs error (device loop0) in ext3_dirty_inode: IO failure
EXT3-fs error (device loop0) in ext3_ordered_commit_write: IO failure
ext3_abort called.
EXT3-fs error (device loop0): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
... (more Buffer I/O errors) ...
__journal_remove_journal_head: freeing b_committed_data
.. repeats for the rest of the log except for a "journal commit I/O error"


Any ideas what we're doing wrong?

Thanks,
Colin