S2E not picking up ext partition [SOLVED]

segphault

Senior Member
Jan 20, 2011
122
10
0
twitter.com
I'm currently on a CM7 nightly (see my signature) and I want to get data2ext working using S2E, though it flat out refuses to pick up my ext partition.

I have run e2sfck which reports the partition as clean, though I know that the partition doesn't mount (may be flagged as a read-only filesystem?). I will attach a logcat of my boot process to this post as soon as possible, but I'll leave this thread here in the meantime if anyone's had similar issues.

Any solutions?

EDIT: Logcat attached, not a full log but probably enough
 

Attachments

Last edited:

segphault

Senior Member
Jan 20, 2011
122
10
0
twitter.com
No worries, problem solved! I simply backed up the data on my SD card, blanked the card's previous partitions and then re-partitioned the SD card using blay0's partitioning function inside his modified version of CWM. The partititon has been picked up and works just fine.

Thanks go to TheGrammarFreak for his suggestions and assistance.

I've a couple of additional questions, however. CWM asked me to define a swap size when I created the ext partition. I chose 64MB, as it seems like a decent middle ground. What would you recommend, and why?
 
Last edited:

segphault

Senior Member
Jan 20, 2011
122
10
0
twitter.com
Okay, scrap that. The partition is being mounted and picked up by s2e but not the android system. To clarify, the system is only displaying a maximum of 185MB of memory as opposed to the 768MB it should be. I'll grab another logcat when I can for your perusal. I'll also post the output of df -h soon.

EDIT: Attached is an edited version of the logcat which includes the first section of the boot process (first 1500 lines or so). The other logcat is what occurs when I launch S2E.

EDIT: df -h attached.

Sent from my Legend using XDA App
 

Attachments

Last edited:

TheGrammarFreak

Senior Member
Jul 29, 2010
2,820
678
0
twitter.com
s2e moves specific directories over to the ext partition, so android isn't fooled into seeing it as internal memory. You do, however, have the space available for apps. Install a large app, and the internal memory usage will barely change. The logcat indicates that everything is working as it should be

As for swap: you don't need it