[HD2 Android NAND Development] joeatx:
why the directory "/sys/block/mtdblock4/queue/scheduler" can not be created?

===============================
DL DesireZ v4.2
===============================

vdd_mode=+50
nand_data=0
ram_data=1
sd_boost=1
format_ext4=0
gps_zone=de

Sun Mar 6 18:28:40 UTC 2011
***********************************************
****** SuperInit ******
** **
** IMG/EXT4/RAM,SD/MAGLDR/NAND,EU/TMOUS **
** **
*** by dandiest & freak ***
***********************************************
--- Loading sdcard
Looking for image files in
--- System loaded from Nand ---
--- Define system config
--- Read config file
mknod: /dev/block/mtdblock0: File exists
mknod: /dev/block/mtdblock1: File exists
mknod: /dev/block/mtdblock2: File exists
mknod: /dev/block/mtdblock3: File exists
mknod: /dev/block/mtdblock4: File exists
mknod: /dev/block/mtdblock5: File exists
--- HD2 NAND version in use
--- Modify scheduler
cannot create /sys/block/mtdblock2/queue/scheduler: directory nonexistent
cannot create /sys/block/mtdblock3/queue/scheduler: directory nonexistent
cannot create /sys/block/mtdblock4/queue/scheduler: directory nonexistent
cannot create /sys/block/mtdblock5/queue/scheduler: directory nonexistent
--- Over/Under volting mode
--- 2nd partition found,start loading---
--- sd_boost mod active - mounting as loop device
/system/xbin/tune2fs: Filesystem has unsupported feature(s) while trying to open /dev/block/mmcblk0p2
Couldn't find valid filesystem superblock.
tune2fs 1.40.8 (13-Mar-2008)
--- Checking system image /dev/block/mmcblk0p2
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p2: recovering journal
/dev/block/mmcblk0p2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached inode 52
Connect to /lost+found? yes

Inode 52 ref count is 2, should be 1. Fix? yes

Inode 1405 ref count is 1, should be 2. Fix? yes

Pass 5: Checking group summary information

/dev/block/mmcblk0p2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p2: 1674/65536 files (8.6% non-contiguous), 56379/262144 blocks
--- Mounting fs at /data
--- EXT4 data loaded
--- to start move data - dandiest
**************************************
*** 3rd partition detected ***
*** Last boot - just for checking ***
**************************************
e2fsck 1.41.6 (30-May-2009)
extdata: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

12 inodes used (0.04%)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2
123537 blocks used (93.16%)
0 bad blocks
1 large file

1 regular file
2 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
3 files
/system/xbin/tune2fs: Filesystem has unsupported feature(s) while trying to open /dev/block/mmcblk0p3
Couldn't find valid filesystem superblock.
tune2fs 1.40.8 (13-Mar-2008)
--- ext4 swap mounted in /mnt/tmpdata
/dev/block/mmcblk0p3 on /mnt/extdata type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=60,barrier=1,data=ordered,noauto_da_alloc)
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

11 inodes used (0.01%)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 1
7864 blocks used (6.71%)
0 bad blocks
1 large file

0 regular files
2 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
2 files
--- Checking system image /mnt/extdata/ext4
e2fsck 1.41.6 (30-May-2009)
tmpdata: clean, 11/117248 files, 7864/117248 blocks
losetup: /dev/block/loop6
--- Mounting fs at /data/data
--- ext4 swap mounted in /mnt/tmpdata
/dev/block/loop6 on /data/data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered)
mount: mounting /mnt/extdata on /mnt/extdata failed: Invalid argument
--- last check
/dev/block/loop8 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=0,data=ordered) /dev/block/mmcblk0p3 on /mnt/extdata type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=60,barrier=1,data=ordered,noauto_da_alloc) /dev/block/loop6 on /data/data type ext4 (rw,relatime,barrier=0,data=ordered)
-- Swap partition mounted successfully --
--- Normally all is ok
--- the last fourth lines of the logs are mmcblk0p1-mmcblk0p2-mmcblk0p3-loop6
+++ Data-to-SD/EXT4 successfully enabled.
-- Not use Nand optimization --
--- Use RAM Optimization for dalvik-cache
--- Use RAM Optimization for Cache
--- create initial ramdisk of 16m
chown: unknown user/group system:system
+++ Data-to-SD/EXT4 completed, with the mount status:
rootfs on / type rootfs (rw,relatime)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p1 on /bootsdcard type vfat (rw,noatime,nodiratime,fmask=0111,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/mtdblock0 on /system type yaffs2 (rw,relatime)
/dev/block/loop1 on /system/squashed type squashfs (ro,relatime)
/dev/block/loop8 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=0,data=ordered)
/dev/block/mmcblk0p3 on /mnt/extdata type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=60,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/loop6 on /data/data type ext4 (rw,relatime,barrier=0,data=ordered)
tmpfs on /app-cache type tmpfs (rw,relatime,size=16384k)
+++ All done, let's goooo!!! :D +++