[HD2 Android NAND Development] B-Man2005:
oh dandy come on ... dont make me wanna cry

another update yet ???

i downloaded my init i think two hours ago ...

and here are the log files from first and second start

and all my widgets are gone again :(:(:(

+++ Start the Nand Loading +++

- system mounted

- mmc&mtd scheduler changed

Filesystem label=userdata

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

Stride=0 blocks, Stripe width=0 blocks

65536 inodes, 262144 blocks

0 blocks (0.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=268435456

8 block groups

32768 blocks per group, 32768 fragments per group

8192 inodes per group

Superblock backups stored on blocks:

32768, 98304, 163840, 229376

Writing inode tables: 0/81/82/83/84/85/86/87/8done

Creating journal (8192 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 25 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override.

tune2fs 1.41.6 (30-May-2009)

-- reformat Partition2 --

-- EXT4 data loaded --

-- Loaded Nand userdata --

-- Swap partition initiate started --

Filesystem label=extdata

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

Stride=0 blocks, Stripe width=0 blocks

76800 inodes, 76800 blocks

0 blocks (0.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=79691776

3 block groups

32768 blocks per group, 32768 fragments per group

25600 inodes per group

Superblock backups stored on blocks:

32768

Writing inode tables: 0/31/32/3done

Creating journal (4096 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 21 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override.

tune2fs 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

6548 blocks used (8.53%)

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

tune2fs 1.41.6 (30-May-2009)

+++Create ext4 loop file with 90% disk space, 10% left for lost+found

tune2fs 1.41.6 (30-May-2009)

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

tune2fs 1.41.6 (30-May-2009)

-- Swap partition reset successful --

-- Swap partition started --

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

6548 blocks used (8.53%)

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

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

-- Swap partition mounted successfully --

-- no /cache find, create a default one --

-- Init Nand successfully --

+++ Data-to-SD/EXT4 completed, with the mount status:

rootfs on / type rootfs (rw)

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/loop8 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=writeback)

+++ Start the Nand Loading +++

- system mounted

- mmc&mtd scheduler changed

-- EXT4 data loaded --

-- Loaded Nand userdata --

-- Swap partition started --

Superblock last write time is in the future. Fix? yes

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

extdata: ***** FILE SYSTEM WAS MODIFIED *****

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

6548 blocks used (8.53%)

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

The superblock could not be read or does not describe a correct ext2

filesystem. If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

-- Swap partition mounted successfully --

-- no /cache find, create a default one --

-- Init Nand successfully --

+++ Data-to-SD/EXT4 completed, with the mount status:

rootfs on / type rootfs (rw)

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/loop8 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=writeback)

/dev/block/loop6 on /data/data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=writeback)