Comment 14 for bug 82314

I could be wrong, but I think my problem may also be related. I attempted a very standard install of Feisty Herd 5 alongside my Edgy install. Here's my fdisk output:

[CODE]
$ sudo fdisk -l /dev/hda

Disk /dev/hda: 40.0 GB, 40007761920 bytes
255 heads, 63 sectors/track, 4864 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/hda1 1 2980 23936818+ 83 Linux #Edgy
/dev/hda2 4737 4864 1028160 82 Linux swap / Solaris
/dev/hda3 2981 4736 14105070 83 Linux #Feisty

Partition table entries are not in disk order
[/CODE]

Feisty's boot hangs very early in the boot process. When in recovery mode, here's my final output:
[CODE]
Begin: Running /script/local-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
Done.
[ 5.640000] attempt to access beyond end of device
[ 5.640000] sda:rw=32, want=71990972, limit=70501362
[ 5.640000] EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode block - inode=1733313, block=3473410
init: Unable to execute "/bin/sh" for rcS: Permission denied
init: rcS process (2342) terminated with status 255
init: Unable to execute "/bin/sh" for rc-default: Permission denied
init: rc-default process (2343) terminated with status 255
[/CODE]

Thanks, and sorry if in missinterpreted something, this is my first time on launchpad.