Can't boot - lack of ext4 support?

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Boot the "Test build 20110101" cd

What is the expected output? What do you see instead?
Android will boot. But instead, if I start in any 3 normal mode, I see:

Loading /kernel...
Loading /initrd.img...
Ready.
[    0.030000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
[    0.475844] microcode: no support for this CPU vendor
[    1.460048] ata1: softreset failed (device not ready)
Detecting Android-x86...   (add points indefinitely)

If I start it in debug mode, I see a lot of things but these following lines 
will be added indefinitely while my hdd's led activity blinks.

 attempt to access beyond end of device
sda1: rw=0, want=4, limit=2
EXT3-fs (sda1): error: unable to read superblock
attempt to access beyond end of device
sda1: rw=0, want=4, limit=2
EXT2-fs (sda1): error: unable to read superblock
attempt to access beyond end of device
sda1: rw=0, want=66, limit=2
isofs_fill_super: bread failed, dev=sda1, iso_blknum=16, block=32
EXT3-fs (sda3): error: couldn't mount because of unsupported optional features 
(240)
EXT2-fs (sda3): error: couldn't mount because of unsupported optional features 
(240)
EXT3-fs (sda6): error: couldn't mount because of unsupported optional features 
(240)
EXT2-fs (sda6): error: couldn't mount because of unsupported optional features 
(240)

What version of the product are you using? On what operating system?
I'm using the "Test build 20110101" cd on my Dell Inspiron 1501.

Please provide any additional information below.
sda3 is my data partition while sda6 is my Archlinux's system partition, both 
are in ext4. I searched this error on google and I tried to add 
"rootfstype=ext4" on the debug's boot line but it doesn't changed anything.

Original issue reported on code.google.com by ghostana...@gmail.com on 10 Jan 2011 at 11:01

[GoogleCodeExporter]

Ext4 is not officially supported by android-x86,
though you can just enabled it in your kernel config.
(currently ext4 is compiled as a module)

Original comment by cwhuang%...@gtempaccount.com on 12 Jan 2011 at 1:59

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

while I  use mount  commands
# mount /dev/sda1 /mnt
attempt to access beyond end of device
sda1: rw=0, want=4, limit=2
EXT3-fs (sda1): error: unable to read superblock
attempt to access beyond end of device
sda1: rw=0, want=4, limit=2
EXT2-fs (sda1): error: unable to read superblock
yaffs: dev is 8388609 name is "sda1" rw
yaffs: passed flags ""
yaffs: dev is 8388609 name is "sda1" rw
yaffs: passed flags ""
ufsd: default nls iso8859-1
attempt to access beyond end of device
sda1: rw=0, want=8, limit=2
mount: mounting /dev/sda1 on /mnt failed: Invalid argument 

Original comment by Chenling...@gmail.com on 30 Nov 2011 at 9:40

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have the same issue, Android-x86 is installed on partition 7, partition 5 is 
Ubuntu in EXT4. It hangs on 'uanable to read superblock' and 'couldn't mount 
because of unsupported optinal features (240)'. These messages are always 
repeated.

Original comment by retro.et...@gmail.com on 1 Nov 2012 at 11:52