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.

Corrupted SD Card

I'm running CM 4.1.11.1 I think and just recently new apps wouldn't install, so I rebooted and all of a sudden all of the apps just turned into the standard icon and none of them said they were installed except for like 3 or 4 of them. I think the SD card is alright, but must have some kind of error in the ext filesystem as I can see all of the files on the FAT32 portion just fine. Do you guys know of any way to just fix the errors on the ext portion without reformatting it? Or do I have to kill all of the partitions and redo them?

You could use the repair ext filesystem option if you are running a recovery image that has it (Cyanogen 1.4 or RA 1.2.3) or just reformat the ext partition using gparted under linux.

Yeah, the repair ext thing didn't work. I think I may just have to clear off the entire card and start from scratch.

I got the same problem
then I backup all the apps up with: tar cvf /sdcard/backup.tar /data/app/*
then copy backup.tar to your desktop pc
then reformat your tf card and repart the partitions
when it's done,move it to your tf card FAT32 partition again
insert to your Phone
the install CM ROM
when it's done
enter the terminal or adb shell
cd /data/app
tar xvf /sdcard/backup.tar
(if it says read only filesystem something you can try reboot )
then check to make sure all the .apk files are under the /data/app directory
then type
fix_permissions
when it's all done reboot
if some apps' error
reinstall them
that's all I did
good luck to you ;-)

oh,I suggest that the size of your ext3 partition should under 400MB
that't the key to solve the problem I thought

Move data to SD card in CM7

I had repartition my SD card for a while, and I never checked my 512M ext3 partiton since I rarely do anything with it. Recently I mounted it and check, nothing store in it, all app go to .android_secure in my Fat32 partition.
I'm using CM7, is there any extra step to get app install goes to ext3 partition, or I should delete the ext3 and resize fat32 partition ?
Edit: as I search around, CM7 using Froyo App2SD ? Maybe I should install Darktremor App2SD or not ? Is there any extra step to install it on Wildfire

You are right. Flash DTApps2SD.

when I install darktremor, will it move all app to ext3 or I have to do something with it ?
Thanks for your answer, maybe I'll install darktremor app2sd now

I installed DTApp2SD anh successfully moved dalvik-cache to ext partition, but .android_secure still there.
When I run a2sd reinstall, next time the phone will never load, stuck at HBOOT boot screen.

[Q] HD2 & App2SD

Hello everyone,
I've an issue and I am looking for your advise & support. I've bought HTC HD2 512 EU with the following NAND specification:
Android ver: 2.2.1
Baseband ver: 15.42.50.11U_2.15.50.14
Kernel ver: 2.6.32.15-saint.J_Rev.005-g009fade-dirty [email protected] #8
Build no: Desire HD Rev.10.XU
Software no: 1.72.405.3
aMAGLDR V1.13
The Issue: I wanted to install App2SD to be able to install apps in SD Card.. I followed this thread => http://forum.xda-developers.com/showthread.php?t=926015 & followed Darktremor instructions here.. However, When I entered the MAGLDR menu /AD Recovery I found no CWM recovery mode "no boot source".. So what should I do next as Darktremor approach assumed that there is a CWM recovery mode to be able to format, partition and flash the App2SD, while I haven't!.. What should I do to make it work?
Thank you,

unzip attached file.put the folder you get to your sd card.in mgldr menu: services-boot settings-ad sd dir-find the folder and choose it. now you'll go to mgldr menu automatically now take the second choice:ad sd. so you'll go to ad recovery.(by this method you have to do all these steps each time in order to go ad recovery.so it is recommended to flash a recovery using daf and usb flasher.but this will erase your installed android rom.) and in ad recovery menu backup your current rom.because darktremors method doesn't go well with som roms.and know that it leads 2 extra reboots after you flash it.

mutil, thanks for the reply. I did as you mentioned.. got into the CWM successfully but failed to partition the SD correctly. After it said=> "Done..! partition SD successfully!" I got the screen full of errors like=>
E: Can't mount /cache/recovery/log
E: Falid to find "cache" partition to mount at "/cache".
E: Can't open /cache/recovery/last_log
E: Can't find misc
P.S: I choose partition size of 1024mb & swap of 256mb..
Update: I ignored those errors & installed the App2SD & rebooted but didn't notice any change! The available space on the internal storage still 201mb!.. SD card now reads 14gb, previously 15gb..

download a2sdgui from market. move dalvik cache to sd.this gives you some more space.i think a2sd will work for applications you install from now on.therefore i install it just after i installed a new rom.btw 256mb swap is high. you must know that it may harm your sd (but i also use 128mb swap in spite of its risk)

mutil said:
download a2sdgui from market. move dalvik cache to sd.this gives you some more space.i think a2sd will work for applications you install from now on.therefore i install it just after i installed a new rom.btw 256mb swap is high. you must know that it may harm your sd (but i also use 128mb swap in spite of its risk)
Click to expand...
Click to collapse
Done!..
Thank you mutil...
About the swap, do you suggest me to redo the whole process again and limit the swap to maybe 128mb?.. I remember that swap partition is always double the mem size..
What is the max recommended ext partition size for the App2SD? because on the CWM you can make the partition up to 2048mb..

no just for that, it doesn't worth to redo everything.next time when you change rom you arrange it.i dont have much knowledge but the swap is said to harm sd-card.but as my experience it also improves speed.

Ext
If u want to install apps on EXT partition don't use App2SD,or A2ext use Data2ext.
Similar to a2ext, where data/app were stored inside your ext partition of the SD card, data2ext stores the whole /data inside your ext partition.
That means your internal storage will barely be used, and because nowadays some SD cards runs faster than your internal memory.
Instructions:
*This is a CyannogenMod version!Not tested on DHD Roms!
1.Make a Ext3 Partition via CWR
2. Flash data2ext_for_CM via CWR (attached) (DON'T FLASH IT ON THE FIRST BOOT OF ANY ROM!)
3. Go to your terminal emulator/adb shell to type data2ext --enable
4. Reboot
5. Go check your Ext storage via Titanium Backup(Your internal storage [220 mb~] will not be increased you must check the ext space from the Overview page of your Titanium Backup [SD card(a2sd):....mb(...mb free)])!

antonymilo said:
If u want to install apps on EXT partition don't use App2SD,or A2ext use Data2ext.
Similar to a2ext, where data/app were stored inside your ext partition of the SD card, data2ext stores the whole /data inside your ext partition.
That means your internal storage will barely be used, and because nowadays some SD cards runs faster than your internal memory.
Instructions:
*This is a CyannogenMod version!Not tested on DHD Roms!
1.Make a Ext3 Partition via CWR
2. Flash data2ext_for_CM via CWR (attached) (DON'T FLASH IT ON THE FIRST BOOT OF ANY ROM!)
3. Go to your terminal emulator/adb shell to type data2ext --enable
4. Reboot
5. Go check your Ext storage via Titanium Backup(Your internal storage [220 mb~] will not be increased you must check the ext space from the Overview page of your Titanium Backup [SD card(a2sd):....mb(...mb free)])!
Click to expand...
Click to collapse
mmmm, will give it a try
Does it has a GUI?

[Q] 0.00b free on /system after rooting

Dear all,
I tried to use link2sd on my S6102, so first I rooted it using this tutorial (which is linked in the link2sd tutorial):
http://forum.xda-developers.com/showthread.php?t=1611830
After applying update.zip, link2sd reports 0.00b on /system, thus the error message when starting link2sd:
"Mount script cannot be created. write: No space left on device.
Before applying update.zip, it was 1.4Mb in /system.
What does it mean? Did I do anything wrong?
BTW in this state, I tried to install the 15toggles package, which resulted in boot loop - had to restore nandroid backup via cwm. Maybe the same reason?
Thanks a lot!

To create a mount script you need a 2nd ext partition on your sd card - nothing to do with /system although you do need space there to place the script which I think is your problem
if you have got /system problems wipe Dalvik cache in cwm
if you still have problems You will have to wipe system & data and install a custom rom that is pre rooted

Yes 2nd partition is there and yes I think it is the script itself which doesn't fit in /system
Wiping dalvik cache did not change anything...
Maybe I can find another root "package" and try with that...