[Defy General] MauroSZ:
I really don't know if it is a glitch because the CWM builder has worked well to build defy mini CWM Image to mount / unmount / backup SD-EXT using a custom recovery.fstab.

After reply you I submitted to CWM builder XT682 stock recovery.img that you extracted. I was hope it was worked well because It is more similar to XT687 than Motoluxe XT615, but Motoluxe has a CWM recovery that works reasonable on XT687.

XT682 and XT687 are different (hardware) only in the amount of SIM card, single and dual SIM, but the CWM image built by me with your img extracted, didn't work at all.

I've not tried the permanent CWM yet, because I would need to do it using Motoluxe CWM recovery.img. Do i have to replace only ?

update after [MENTION=4880538]rootdefyxt320[/MENTION] update

The result of ADB SHELL SU MOUNT you suggested.

C:\ADB>adb shell
* daemon not running. starting it now *
* daemon started successfully *
shell@android:/ $ su
su
root@android:/ # mount
mount
rootfs on / type rootfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
/dev/block/mtdblock1 on /misc type yaffs2 (rw,nosuid,nodev,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock6 on /hidden type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock7 on /hidden/data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock9 on /system type yaffs2 (rw,relatime)
/dev/block/mtdblock11 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock10 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mmcblk0p2 on /data/sdext2 type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
root@android:/ #

Maybe this also helps:

cat /proc/mtd
dev: size erasesize name
mtd0: 00700000 00020000 "boot"
mtd1: 00300000 00020000 "misc"
mtd2: 00300000 00020000 "misc2"
mtd3: 00200000 00020000 "splash"
mtd4: 00700000 00020000 "recovery"
mtd5: 00d00000 00020000 "ftm"
mtd6: 00d00000 00020000 "hidden"
mtd7: 01500000 00020000 "cda"
mtd8: 00060000 00020000 "dbgmsk"
mtd9: 19500000 00020000 "system"
mtd10: 06e00000 00020000 "cache"
mtd11: 183e0000 00020000 "userdata"
root@android:/ #

Bellow the custom recovery.fstab I submitted with the CWM recovery.img by enox for Motoluxe XT615 adding the last line (thanks [MENTION=4745666]Guitwo2[/MENTION]) to CWM builder to customize it. The bad blocks that were before go on but works well to make backup, mount and unmount everything including sd-ext etc. "Issues" are these bad blocks which apparently do not disturb and the touch functionality doesn't work. The screen is OK.

/boot	mtd	boot
/cache	yaffs2	cache
/data	yaffs2	userdata
/misc	mtd	misc
/recovery	mtd	recovery
/sdcard	vfat	/dev/block/mmcblk0p1	/dev/block/mmcblk0
/system	yaffs2	system
/misc	mtd	misc
/misc2	mtd	misc2
/splash	mtd	splash
/ftm	mtd	ftm
/hidden	yaffs2	hidden
/hidden/data	yaffs2	cda
/sd-ext	ext4	/dev/block/mmcblk0p2

Now I don't know what else i can do. I would prefer a proper CWM for my device but all times I tried, I got severed issues, like the weird split ( I attached a picture ) and not functioning ADB. The only thing that works is the touch functionality.