[HD2 Android NAND Development] :
after new test same issue.....:eek:

task29 / radio / magldr

sd with 3 partition (fat32 / ext4 1024 / linux swap 150mo)

mod system.img with new initrd fix included directly

base config with just format_ext4=1

flash rom, boot ok / all is good and speed (axt4 detected ok see with space in phone)

reboot....and loose all widgets in my home and settings...:confused:

dandiest here you have my init.log

+++ Start the Nand Loading +++
- system mounted
- mmc&mtd scheduler changed
userdata: 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

userdata: ***** FILE SYSTEM WAS MODIFIED *****

816 inodes used (1.25%)
72 non-contiguous files (8.8%)
2 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 803/1
36730 blocks used (14.01%)
0 bad blocks
1 large file

354 regular files
451 directories
0 character device files
0 block device files
0 fifos
0 links
2 symbolic links (2 fast symbolic links)
0 sockets
--------
807 files
-- EXT4 data loaded --
-- Loaded Nand userdata --
-- Swap partition started --
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

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

514 inodes used (1.34%)
42 non-contiguous files (8.2%)
1 non-contiguous directory (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 493/10
6509 blocks used (16.95%)
0 bad blocks
1 large file

96 regular files
408 directories
0 character device files
0 block device files
0 fifos
0 links
1 symbolic link (1 fast symbolic link)
0 sockets
--------
505 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/mmcblk0p2 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=0,data=writeback,noauto_da_alloc)
/dev/block/loop6 on /data/data type ext4 (rw,sync,nosuid,nodev,noatime,nodiratime,commit=3,barrier=1,data=ordered)

is the probleme is my 3rd partition linux swap?? (i test it with EXT4...and report my result)

now i make another test with same procedure and i have mod my partition

fat32

est4 1024

ext4 150

base config with just format_ext4=1 and new full flash (task29 etc)

same problem...all is ok at first boot, and my widgets loose after reboot, but after 2 new reboot my config is now save and if y put a widget and restart it's now ok (but all settings of first boot is loose, i can re configure all but i think if it's ok after first boot it's bettter)

here my new init.log

+++ Start the Nand Loading +++
- system mounted
- mmc&mtd scheduler changed
userdata: 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

userdata: ***** FILE SYSTEM WAS MODIFIED *****

835 inodes used (1.27%)
70 non-contiguous files (8.4%)
2 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 822/1
36762 blocks used (14.02%)
0 bad blocks
1 large file

367 regular files
457 directories
0 character device files
0 block device files
0 fifos
0 links
2 symbolic links (2 fast symbolic links)
0 sockets
--------
826 files
-- EXT4 data loaded --
-- Loaded Nand userdata --
-- Swap partition started --
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

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

518 inodes used (1.34%)
43 non-contiguous files (8.3%)
1 non-contiguous directory (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 494/13
6603 blocks used (17.08%)
0 bad blocks
1 large file

98 regular files
410 directories
0 character device files
0 block device files
0 fifos
0 links
1 symbolic link (1 fast symbolic link)
0 sockets
--------
509 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/mmcblk0p2 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=0,data=writeback,noauto_da_alloc)
/dev/block/loop6 on /data/data type ext4 (rw,sync,nosuid,nodev,noatime,nodiratime,commit=3,barrier=1,data=ordered)