[Samsung Galaxy Gio GT-S5660] dreuzel:
ERATIC-CORRUPTION CWM 5.0.2.7 CM7.1/cm7.2.....

Seemingly i seem to piss off people.... Claiming corruption asking/claiming you only need a few hours to write simple script.....

or only I have the problem.....

Well there is more:

A) using ext4 on sd-ext

1) You need to partition is (seems like this is done by CWM difficult for statistics since fully distructive)

2) You need to format it:

A) by PC (makes no sense since WIPE/Hardware reset required on install will overwrite all formatting.....)

B) using CWM is not reliable :

using Fdisk after reformatting it sometimes reformats to some ???? formatting : EXT4 ==> EXT2 ===>????= or does NOT reformat at all

And this is very ERRATIC.......(independently of key directories not yet present!!!!! contradictory to success message and elapsed time .....)

As mentioned in the linked mail , it hardly takes 10 minutes with many reboots to find that out....

The behaviour is different every time. IT is NOT relayable

Sometimes it was auto done in the inital start of cm7.1 later withdrawn.....
​

3) you need to mount the device at boot time ......

Since jan2011 there are reports of problems using CM7.xxx

There are timing problems during the initial mount causing the sd-ext device not tot be mounted.... its relation to ext4 formatting is unclear...

The same problem causes BOOTLOOPS (ringing any bells)

Only if you are lucky and get formatted ext4 S2E /A2SD will work otherwize you are in trouble..... BUT you will never KNOW since there are hardly tools to see what CWM did.... I did some test using Fdisk and the result is depending on the direction the wind blows.

If you are stuck with an ext2 partition You would not know..... and any program gets aborted .... reboot (normal CM7.x behavior will corrupt you sd-ext, No recovery executed .....so in a reasonable amount of time all is corrupted enough to not to be able to use the phone...(see 90% of forum 7.1/7.2 so you re install....But then it's erratic again .... format or not ... mount or not and the **** increases..... People get more and more into trouble ....

getting advice from the forum to move to S2E, the next day to A2DT the net day ,link2SD, and so on and so on.... never risking to solve the real problem.

Users do'n't you feel insulted...... especially after hitting the CWM75.0.2.7 format sd-ext button for the 10é time and stating it is NOT formatted.....(you would not see that... of coarse....

Some people just do not like you to say such things .....

As I was brutally asked :::: "DO IT YOURSELF...", I did , at least get the info from the mobile ..... and I find CWM 7.0.2.7 does NOT reliably do what it claims... Causing a lot of unnecessary talk on the forum.

It's not my intention only to make noise or scare people......

With little effort, but I need help ; I'm not used to write Linux/android batches

for me it seems only to work after manually entering the data ......(ps: i personally do not care about ownership of problem or solution...)

If this formatting/mounting problem could be solved? , or patched (Command line FORMAT sd-ext:/ext4) and potentially a generic MOUNT SD-EXT: for any EXT2/3/4 to be included in the initd.

We Could have a working long time stable CM7.2, little effort my guess....

THERE ARE IssueS reported in CM7.xx main code (Did not find a solved confirm)

exactly showing the seen behaviour (an intd script with timing problems ignoring the mount of sd-ext)

The Mount timing can conflict and is not executed then causing DTa2SD and S2e TO BEHAVE even more erraticaly [device NOT or badly mounted])

This causes BOOTLOOPS and other related problems ....

Writing the asked Command line modules;

we will not have really solved the problem... CWM needs to be addapted and CM7.xxx needs to be corrected, but we would have a survivable seemingly correct working CM7.2 RC1 without the erratic behavior, Problems in this and related threads reduced by 90 % and concentrated on real remaining issues....

potential we will need to slow down the Boot Processing view of the timing problems) just to ensure a correct double mount of sd-ext and potential warning it is not ext4 or not a recoverable file system..... in conflict with the android abort architecture ....

Is this not the goal of every GIO CM7.xx user ?????

There is evolution in this Thing.(wind SW for the moment)