[HD2 Android NAND Development] Tiller:
Well, the sd-ext is not mounted =/

Here is a log :

# mount
mount
rootfs on / type rootfs (rw,noatime,nodiratime)
tmpfs on /dev type tmpfs (rw,noatime,nodiratime,mode=755)
devpts on /dev/pts type devpts (rw,noatime,nodiratime,mode=600)
proc on /proc type proc (rw,noatime,nodiratime)
sysfs on /sys type sysfs (rw,noatime,nodiratime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,noatime,nodiratime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,nodiratime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (rw,noatime,nodiratime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,noatime,nodiratime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (rw,noatime,nodiratime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.natenai.glowhockey2-2 type vfat (rw,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/com.robotinvader.knightmare-1 type vfat (rw,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /cache/download type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-2 on /mnt/asec/com.forthblue.pool-1 type vfat (rw,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-3 on /mnt/asec/com.fullfat.android.flickgolf-2 type vfat (rw,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-4 on /mnt/asec/com.ovh.android.mom-2 type vfat (rw,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-5 on /mnt/asec/com.polarbit.tokitori-1 type vfat (rw,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-6 on /mnt/asec/com.mojang.minecraftpe-2 type vfat (rw,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-7 on /mnt/asec/com.eamobile.tetris_eu-2 type vfat (rw,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

# e2fsck -pfv /dev/block/mmcblk0p2
e2fsck -pfv /dev/block/mmcblk0p2

2805 inodes used (0.56%)
102 non-contiguous files (3.6%)
7 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 474/137/0
Extent depth histogram: 661/5
902316 blocks used (90.23%)
0 bad blocks
0 large files

1799 regular files
962 directories
0 character device files
0 block device files
0 fifos
0 links
35 symbolic links (32 fast symbolic links)
0 sockets
--------
2796 files

I already tried, last night, to format my SD-Card and to re-partition it. But i've got the same issue.

Your last kernel do not change anything except a weird display bug on boot.

On boot, the screen is divided into 4 parts :

On the TOP-LEFT and TOP-RIGHT : The Dorimanx.Kernel logo

On the BOTTOM-LEFT and BOTTOM-RIGHT : The CMW Recovery Logo

But it boots without any problem.

But sd-ext is still unmounted =/

But I can mount sd-ext via CMW Recovery and access by adb shell without any problems. In your ROM the problem is here since the release after the 3.5.1

Edit : I check the logcat, and that's not beautiful =D

Look at the first lines :

http://stooit.com/pub/logcat.txt

Edit2 : Oh, I forgot the "sync + reboot" command after e2fsck. I did it again and it works !

Great ! Thanks Dori :)

So, for others ppls :

e2fsck -pfv /dev/block/mmcblk0p2
sync
reboot

That worked for me.

Edit3: It doesn't work anymore :(