Database Users

SD card lost with message "Removed SD card" after update to cyanogenmod

Did not get any help in cyanogenmod thread, so creating a separate thread here.
I am in trouble. After I updated my ROM to cyanogenmod 3.6.7.2 (with his recovery image 1.3.1 and latest radio) I get a message saying: "Removed SD Card" in the notification and I am getting force closes in apps which access sd card.
Why did it remove my sd card? I have the following partition structure"
c (formatted fat32) 2GB - this is what used for upgrading the radio and rom.
83 (formatted ext4) 6GB
c (formatted fat32) 7GB
82 (mkswapped) whatever left off from 16GB card.
Is this structure causing the issues? I used Linux 2.6.30 and e2fsprogs 1.41.7 to format ext4 and dosfstools 3.0.2 to format fat32 FSs.
I ran fix_permissions from recovery console because I was getting FCs in powermanager (which logs files on SD card).
Also, if I boot into the recovery console, I can mount /sdcard and it automatically mounts the first fat32 partition on /sdcard. I can 'fdisk -l' and see all my partitions are there. So, its not a hardware issue. Some sort of chicken&egg because of apps2sd.
I just mounted the partition2 (which is ext4) in recovery console and I can see there are "app app-private dalvik-cache lost+found" folders on it. So, it looks like normally initialized.
Does anybody know what's going on here? Appreciate your help!

It's the same response you've been getting in the other section.
Try backing up your data on your computer, and completely formatting your card to fat32.
From there, instead of making the partitions on the computer, use the Recovery Console (accessed from Cyano's Recovery) and re-create the partitions as you like.

Ok, I delete the 3rd and 4th partitions, and it seems to be working fine now. So, it seems like there is an assumption about the partition structure in the code somewhere.

devsk said:
Ok, I delete the 3rd and 4th partitions, and it seems to be working fine now. So, it seems like there is an assumption about the partition structure in the code somewhere.
Click to expand...
Click to collapse
So you are all good now?
What exactly did you do? Just remove the 3rd & 4th partition, without formatting?

akapoor said:
So you are all good now?
What exactly did you do? Just remove the 3rd & 4th partition, without formatting?
Click to expand...
Click to collapse
Yeah, I just removed the 3rd and 4th partitions from recovery console and the card is recognized and working fine. Now, I need to find out why is it hard coded like that.

It seems like something doesn't like more than 3 partitions on the SD card. I now have 3 partitions with 'c' (fat32), '83' (ext4) and 'c' (fat32) codes and it seems to work fine.

An ext partition of more than 1.5gb can cause problems
Most roms will not work with the way you had it set up (at least not well)
They follow a 3 partition scheme as such
FAT32 > EXT > SWAP

B-man007 said:
An ext partition of more than 1.5gb can cause problems
Most roms will not work with the way you had it set up (at least not well)
They follow a 3 partition scheme as such
FAT32 > EXT > SWAP
Click to expand...
Click to collapse
I've heard this repeated elsewhere but nobody ever actually says what the problem is with partitions greater than 1.5gb. I'm very curious to know, because I haven't noticed anything wrong.
Except that /sdcard won't automount if my sd card has 4 partitions defined on it. As soon as I mark the 4th one empty and reboot, it's fine again. But that has nothing to do with the size of the ext fs on partition 2. Something with vold is funky, because I can mount /sdcard manually from adb.

[Q] How can I tell if my partitioned SD is being used properly?

Thank you to anyone who can assist with this. I have tried searching the other threads for an answer, but have been unsuccessful.
My configuration is as follows...I partitioned my SD as follows:
1st - PRIMARY - FAT32 (Approx 10GB)
2nd - PRIMARY - EXT2 (2GB)
3rd - PRIMARY - SWAP (2GB)
I extracted and copied the Desire_DL folder (new v4.0) to the newly created FAT32 partition.
I then extracted and copied the Desire_DL and Update_DL folders (from the bugfix.DLZ4.0 patch). I also changed the config.txt.sd to config.txt (though I made no edits).
I rebooted the phone, and once in WM 6.5 I loaded booted Android. Everything booted OK, but I am not sure if it is utilizing the 2nd & 3rd partitions, or if it is just running on the FAT32 partition only. I'd like to ensure I am getting the best performance I can out of the build, so how do I check to see if everything is configured properly and using these partitions?

open MiniTool and see if it uses them.. It says how much it uses. As long as you don't have data_img=1 then it can't remember anything if it doesn't use them.

Thanks for the repsonse.
I used mintool to partition the SD card originally, but how do I use it to see if the partitions are being utilized?
Also, the default settings of the config.txt includes a line that reads: data_img=1
Should I delete that line to force it to utilize the other partitions?

ccrobin said:
Thanks for the repsonse.
I used mintool to partition the SD card originally, but how do I use it to see if the partitions are being utilized?
Also, the default settings of the config.txt includes a line that reads: data_img=1
Should I delete that line to force it to utilize the other partitions?
Click to expand...
Click to collapse
plz see http://forum.xda-developers.com/showpost.php?p=11398763&postcount=3602
set the data_img=0 to use the ext4 ! no need for data.img anymore

what is A2S for and how to use it???

I've just installed the Paranoid-Jellybean 1.99
http://forum.xda-developers.com/showthread.php?t=1793180
on my EU HTC HD2
I can't anderstand what sd the idea behind program S2E, it seems its purpose is to move apps to SD but when used it this way then all newly installed Widgets disappeared What's more even without launching S2E in Settings thare are options to move individual apps to SD (not for all in fact)

it isn't talking about the normal fat partition on the sd card, you must have an EXT partition created before using the app.
What it does, is take the ext partition on the sd card and makes the system think that it is internal memory, thus giving you more 'internal' memory for apps and data and such like.
This isn't the same as choosing 'move to sd ' in the settings - apps options, as this moves the app to the FAT (windows) partition of the sd card. Some apps wont work when 'moved to sd', however they WILL work from the ext partition, because android thinks its internal.
So, if you haven't already got an ext partition, back up the contents of your current sd card (it will get wiped) then reboot into cwm, choose 'advanced - partition sd card' and choose a partition size. (512 or 1024 is usually plenty) then restart android and try the app again.
Any apps that you have already 'moved to sd', go move them back to internal, and the system should automatically move them from the FAT partition to the EXT partition.

Tahnk you for your explanation. Also I must apologize I confused the names of the programs - in fact its S2E rather than A2S (the previous post have written from memory). However probabely this s2e serves the same purpose, as it has such relevant commands:
Applications - Location: /data/app
Private apps - Location: /data/app-private
...
and so on, until:
Dalvik cache - Moving from /data to /sd-ext
So, I've chosen the first option and got displayed:
Application
Moving from /data to /sd-ext
Reboot is required!
and rebooted the phone, but the result was disappointing - several apps dissappeared including all Widgets!
Of course I've had ext3 partition previously set.
What was wrong?
Other question please: exactly WHAT is worth moving to SD Ext partition, Dalvik cache too?

yea they do the same/similar things - namely move parts of the system to the ext partition, and create symbolic links so that the system doesnt notice they've moved.
You seem to be moving your entire data folder to the ext, which i believe has an impact on boot performance, since the data partition wont be mounted straight away, and android needs it during boot.
I don't know a great deal about the various app2sd scripts, but the ones i've used normally only move the /data/app/ (your user installed apps folder) and the dalvik cache to the sd-ext partition.

samsamuel said:
yea they do the same/similar things - namely move parts of the system to the ext partition, and create symbolic links so that the system doesnt notice they've moved.
You seem to be moving your entire data folder to the ext, which i believe has an impact on boot performance, since the data partition wont be mounted straight away, and android needs it during boot.
I don't know a great deal about the various app2sd scripts, but the ones i've used normally only move the /data/app/ (your user installed apps folder) and the dalvik cache to the sd-ext partition.
Click to expand...
Click to collapse
So won't it exert excessive load on SD card which could lead to some sort of instability or other issues?

ioy said:
So won't it exert excessive load on SD card which could lead to some sort of instability or other issues?
Click to expand...
Click to collapse
better than exerting load on the nand and increasing the chances of bad blocks, right?

samsamuel said:
better than exerting load on the nand and increasing the chances of bad blocks, right?
Click to expand...
Click to collapse
theoretically YES but then does it also apply for the whole Android ROM itself (please compare the neighbouring discussion "is NAND Android better than SD and why?")

ioy said:
(please compare
Click to expand...
Click to collapse
no thanks, i have far more interesting things to do. i couldn't care less if there's excess load, though i'm pretty sure there isn't, since i've been running an ext partition for several months and no problems.

Have you understood me well? I've asked about the problem probably NAND ROMs themselves wear NAND memory too so would it be safer (for the device) to use SD ROMs (which write only on SD memory all the time)? How do you think, could it be the case?

i think if it were of any real benefit, people would be talking about it, but no one does. I guess its down to you, if YOU think it will help, then do it. If you don't, don't!
I guess battery drain would be teh real deal maker/breaker. I havent used sd android, but i believe it to be (in general terms) a little less stable, more prone to slowdowns, and harder on teh battery. But thats all anecdotal evidence, as i said, ive never booted sd android.
(edit - i must say, in humour, not meaning offence, that between this thread and your other thread, you sound like a guy who just bought a sports car and wants to cycle to work to save wear and tear on teh car )

Copying from one partitioned SD card to another

I'm trying to understand the most convenient way to make a copy of an SD card that has an EXT partition on it. This would need to be done anytime you upgrade from a smaller to a larger SD card, so I have to believe a number of people on these forums have dealt with it.
This is what I'm expecting to be done... please confirm if it's correct:
Make a nandroid backup, stored on the old SD card
Copy the nandroid backup to PC
Install new SD card and partition it accordingly
Copy nandroid backup to new SD card
Perform a nandroid restore
At this point, everything should be as it was, with the larger SD card. Correct? I've also noticed an alternative that would probably work, that being a partition management program like EaseUS.

My 32Gb SD card arrived so I downloaded Mini-Partition to set it up. Then when I went to copy the EXT3 partition from my 8Gb SD card, the option wasn't possible. Apparently I can't copy it into a larger EXT3 space, only unallocated space. So, I removed the target EXT3 partition, making it unallocated, and then tried to copy and resize. Apparently the tool won't let you resize an existing EXT3 partition. I installed EaseUS to try this operation and encountered the same thing.
From what I've just experienced, I'm now thinking that if I try to restore a nandroid backup onto my new card, it will override the newly minted EXT3 partition with the smaller EXT3 partition.
Searching around turned up a lot of Ubuntu/Linux information, requiring one to boot up in those operating systems and execute a long series of commands to enlarge the EXT3 partition. I'd rather not go down that path right now. Is there some easier way of doing this? If not... then I'm thinking what I need to do is move as many apps having data I need to my phone, then just opt not to restore the EXT3 partition and go back to manually move apps to the EXT3 partition again.

* bump * .... anyone?

cytherian said:
* bump * .... anyone?
Click to expand...
Click to collapse
What rom are you running?

Shelnutt2 said:
What rom are you running?
Click to expand...
Click to collapse
Presently running CM7.2, which supports EXT3. I'm just not getting how I can manage the EXT3 partition. When I switch to a new ROM and wipe the system, then all apps installed on the EXT3 partition would be deleted, correct?

So, what this ultimately means is that each and every time I switch ROMs, the EXT3 partition must be wiped and applications manually moved back there. It's annoying, but I haven't found any other way around this.

Set-up micdoSD for Android Partition ext3 - Help Pleease.

Hi,
how are you today? For me good, thanks for asking, ha ha ha hanb
It's alredy my second thread for today, all problems, wow.
So I will try to explain, like in the thread before, I got HTC HD2 and I have Mdeejay eVo on my sd card and I launch Android from WM6.5.
The Android which I use have already the data_1024 folder, inside data.IMG file which it use for storage the Androids apps, but from my research I find the news to some how edit my microsd card and set-up a Partition which be the sobstitute of the data_1024.
I will be glad to know HOW?
Like I said, I got my Android on sd and I try for a week to find the solution with no success, I try to make a ext3 partition on sd of 2048mb but the android do not see that partition. I can't flash anything because on my ROM is WM 6.5.
I also will be glad to make another data_2048 folder with inside data.IMG file, if the Partition can't be done.
Please guys let me know how do I have set-up the partition for the Android?
Thanks.

hmmm not really sure here, but you can make a back up of your SD card then use minitool partition to partition & create EXt3/ Ext 4 / Fat 32 partitions, try the links below they might help

mengfei said:
hmmm not really sure here, but you can make a back up of your SD card then use minitool partition to partition & create EXt3/ Ext 4 / Fat 32 partitions, try the links below they might help
Click to expand...
Click to collapse
before post here I already saw your thread and like I said I do not have MALGDR on my phone or CWM, also I don't know which type of partition need my Android but I am sure is not the last type of Androids which they have the folders; kernel, META-INF, sdcard (inside NativeSD) and system folder. My Android is whit rootfs.img with external data_1024 folder for storage system.
I used Gparted live and I made a partition of 2048mb of ext3 partition but the Android do not see the partition because somehow I can't make a link to it.
I want more storage for my Android and delete data_1024 folder so I try to figure out, with some help, how to do that?
Any ideas?

Use toporesize app on pc to expand your present data img size without losing present data. . To get more space. .No need for ext 3 and all
Search for topo resize
If youwant to use apps 2 sd or link 2sd app from market to use ext 3.. Then you can move apps to sd ... That is for nand installs. . You don't need that on sd builds. ...
You try native sd builds. . Fastest ever.sd builds. . You can boot from wm also . You need ext4 partition for it. ..
sent from my galaxy note 2 (7100)

pakure said:
Use toporesize app on pc to expand your present data img size without losing present data. . To get more space. .No need for ext 3 and all
Search for topo resize
If youwant to use apps 2 sd or link 2sd app from market to use ext 3.. Then you can move apps to sd ... That is for nand installs. . You don't need that on sd builds. ...
You try native sd builds. . Fastest ever.sd builds. . You can boot from wm also . You need ext4 partition for it. ..
sent from my galaxy note 2 (7100)
Click to expand...
Click to collapse
Thanks mate, this is something great!
So I do not need a special partition for my android, good to know.
I know the last Nand Androids are good but I have old phone with old Android and he work fine, I try to put Native SD Android on my sd but too complicated and I do not have so much time. At the moment I find Mdeejay very fast and good, I tryed AmeriCan Android, CM7 and 10 and really I am not comfortable with them like with Mdeejay, so it's ok like that. ! problem solver, I just try to update my kernel - http://forum.xda-developers.com/showthread.php?t=1976835 - and I am ok.
Thanks.

pakure said:
Use toporesize app on pc to expand your present data img size without losing present data. ....
Click to expand...
Click to collapse
End of the Party, Guys, I was happy to soon!
I used toposize to made data.img for my android but I got problems.
If I resize data.img system partition, first of all, I got the error on e2fsck (see the pic) and i have to click ok to compleate the operation and after that I put the data.img into Anrdoid forlder and I replace the original (backups before) but the Android do not turn on, he stuck in HTC Logo.
If I made a clean data.img with ext3 system partition and I replace the data.img into the Android folder, he do not turn on and he stuck in Android logo.
If I use the original data.img from the package the Android turn on normally.
Do I forgot to do something? Do I missing something?

sorry, I forgot the pic.... here we go...

eclyptos said:
sorry, I forgot the pic.... here we go...
Click to expand...
Click to collapse
you are keeping data .img in a folder?...data.img should be in android folder..no further subfolders...and delete that stupid ext3 partition..you dont need it.
try native sd..it is very simple (for you to dual boot with windows mobile):
you need ext4 partition..use minitool partition manager to create it
then put selected rom zip (like pacman hd2 rom..."the best rom") on sd card
put 4ext recovery folder on sd card..open it , click clcrad and haret inside...follow screen instructions to install rom
Reboot and boot the ROM by executing the usual clcrad and haret stuff inside the NativeSD folder.
thats it.

pakure said:
you are keeping data .img in a folder?...data.img should be in android folder..no further subfolders...and delete that stupid ext3 partition..you dont need it.
Click to expand...
Click to collapse
ohh, well, yes, the data.img is in Android folder, not subfolders or external folders, I said so because in my package of Mdeejay are 2 folders, Android and data_1024. The data_1024 is all ready done to make a fast boot instantly but if I do not use it Android make the clean data into his root folder.
About the partition you get confused a little bit because when I used toporesize to made a clean data.img file to use it in android folder, the app ask me in which system the file have to be, ext2, ext3 or NONE. So no 1 of this data.img worked.
I hope I clarifide, I do not have ext3 partition on sd, is the data.img. that's all.
pakure said:
try native sd..it is very simple (for you to dual boot with windows mobile):
you need ext4 partition..use minitool partition manager to create it
then put selected rom zip (like pacman hd2 rom..."the best rom") on sd card
put 4ext recovery folder on sd card..open it , click clcrad and haret inside...follow screen instructions to install rom
Reboot and boot the ROM by executing the usual clcrad and haret stuff inside the NativeSD folder.
thats it.
Click to expand...
Click to collapse
I don't know about that, currently I have a working Android (not jet set-up like I want too) but I will see if I sholud do all this stuff. I am not so deep in this stuuf and just reach when I reach now, get me tired. So I take in the consideration you advice but now I have to have 1 android working well.

Ok, some bad news:
I did in different way to set-up my storage image, I let Android to made a clean data.img into his folder, after he finished installation and start running well I take the data.img of 1GB and with toposize I resize the image to 3GB. Like I said before, he give me this crap error but I really do not understand why? If Android made a clean data.img in his folder which errors can be made?
So I click ok anyway and made this file and I replaced the 1GB with 3GB with unclarifide done error fix.
He works for feew hours, smooth and fast, I start installing appps and games. Like many games they ask for downloading some updated files so I start downloading 450mb for 1 game and after 20 minuts Android crashed and he do not turn on anymore, he stuck in Android logo.
Are you sure this crap "TOPOSIZE" working? or it's just ME?

Guys, please help, I get confused and I don't know how to do it.
Today I also try install on my android Chainfire and i can't install plugins for low storage so after few hours of serching I find this thread http://forum.xda-developers.com/showpost.php?p=16457164&postcount=14723 but after read what they saying I do not understand anymore which system file I have to resize to get more space AND to make working chainfire which I really need right now for few games!
Someone can tell me which files I have to resize? How? or Post the right thread? please.