[HD2 Android NAND Development] dorimanx:
checking!

This is my test phone, rom 3.1.7 kernel 6.8

# 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/mmcblk0p2 on /sd-ext type ext4 (rw,nodev,noatime,nodiratime,barrier=0,nobh,data=writeback,inode_readahead_blks=4,noauto_da_alloc,discard)

/dev/block/mmcblk0p2 on /data/dalvik-cache type ext4 (rw,nodev,noatime,nodiratime,barrier=0,nobh,data=writeback,inode_readahead_blks=4,noauto_da_alloc,discard)

/dev/block/mtdblock5 on /cache type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)

/dev/block/mmcblk0p2 on /data/app type ext4 (rw,nodev,noatime,nodiratime,barrier=0,nobh,data=writeback,inode_readahead_blks=4,noauto_da_alloc,discard)

/dev/block/mmcblk0p2 on /cache/dalvik-cache type ext4 (rw,nodev,noatime,nodiratime,barrier=0,nobh,data=writeback,inode_readahead_blks=4,noauto_da_alloc,discard)

/dev/block/mmcblk0p2 on /data/data type ext4 (rw,nodev,noatime,nodiratime,barrier=0,nobh,data=writeback,inode_readahead_blks=4,noauto_da_alloc,discard)

/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,short

name=mixed,utf8,errors=remount-ro)

tmpfs on /mnt/sdcard/.android_secure type tmpfs (rw,noatime,nodiratime,size=0k,mode=000)

tmpfs on /cache/download type tmpfs (rw,noatime,nodiratime,mode=755)

#

In red is my mounted sd-ext!

# df -h

df -h

Filesystem Size Used Available Use% Mounted on

tmpfs 202.2M 32.0K 202.2M 0% /dev

tmpfs 202.2M 0 202.2M 0% /mnt/asec

tmpfs 202.2M 0 202.2M 0% /mnt/obb

/dev/block/mtdblock3 170.0M 148.9M 21.1M 88% /system

/dev/block/mtdblock5 742.8M 2.7M 740.0M 0% /data

/dev/block/mtdblock4 742.8M 2.7M 740.0M 0% /cache

/dev/block/mmcblk0p2 963.0M 89.3M 871.8M 9% /sd-ext

/dev/block/mmcblk0p2 963.0M 89.3M 871.8M 9% /data/dalvik-cache

/dev/block/mtdblock5 742.8M 2.7M 740.0M 0% /cache

/dev/block/mmcblk0p2 963.0M 89.3M 871.8M 9% /data/app

/dev/block/mmcblk0p2 963.0M 89.3M 871.8M 9% /cache/dalvik-cache

/dev/block/mmcblk0p2 963.0M 89.3M 871.8M 9% /data/data

/dev/block/vold/179:1

2.4G 612.4M 1.8G 25% /mnt/sdcard

/dev/block/vold/179:1

2.4G 612.4M 1.8G 25% /mnt/secure/asec

tmpfs 202.2M 32.0K 202.2M 0% /cache/download

#

not much to do,

backup the ext, and format.

then all will be ok, you have errors in ext journal.

and it's cant be mounted till it's fixed.

you can try to fix it by running fix prog!

connect by adb

type:

e2fsck -pfv /dev/block/mmcblk0p2

If you get this!

e2fsck -pf /dev/block/mmcblk0p2

e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p2

Filesystem mounted or opened exclusively by another program?

Then it's mounted, but damaged!

if you see table with info and something about repair..

then type:

sync

reboot

and hope that it's will be ok after full boot :)