Link2SD and Read-only file system Error
I have been using Link2SD for few days now (on my Rooted NexusOne) and I simply loves this application. It solves all the issues of low internal memory for the custom applications.
However from time to time, the SD-Ext partition used by Link2SD gets corrupt. Now I’m not very sure whom to blame for this i.e. Android Kernal, Link2SD or anything application which writes files here. But anyway, I found a simple fix for any such problems, and that’s if you get the read-only file system error when installing or updating the SD-Ext in the Link2SD, you can quickly repair this from the ADB Shell. If you have never used this before, here is quick reference and guide:
http://developer.android.com/tools/help/adb.html
Once you have this tool. But the phone into recovery mode, and then run the ADB shell from your command prompt:
adb Shell |
adb Shell
Once you see the shell prompt, you can check and fix your sd-ext partition by typing following command:
e2fsck -fpDC0 /dev/block/mmcblk0p2 |
e2fsck -fpDC0 /dev/block/mmcblk0p2
If fixing is successful, re boot back into phone and try using the Link2SD again.
Update: A quick tip on this (based on my personal experience). If you are using Link2SD and your frequently get the file system error on your SD-Ext partition, then one trick which worked well for me is to change the SD-Ext partition format from the Ext3 or Ext4 to FAT32. This should get rid of most of the file system errors happen during transfer of files.
Tags: Android, Link2SD, Permissions
This entry was posted
on Monday, February 11th, 2013 at 1:51 pm and is filed under Android.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
I think what is happening is people are reading the instructions as a step-by-step guide. For example my internal device is mmcblk0p1 and the emulated sdcard contained thereon is mmcblk0p2. My actual EXTERNAL SD card is mmcblk1p1 and mmcblk1p2. You can see this using ls -al in the /dev/block directory.
Hi there. I tried replying a while back and the site stopped loading and then comments wouldn’t post.
The device in question is a Samsung Sprint Galaxy S1 Epic 4G. I was on CM11 at the time.
I tried this method. Only I made a fatal mistake. I tried to do it from TWRP which could have been fine if I did int from the proper directory. Maybe.
However I misread what the directory and believe I wrote the command for the internal memory.
Since then the device will not read from memory cards. I thought a newer recovery build was causing issues and ha to go through a lot of fun to fix that to end with the same problem.
And then I even did countless full ODIN restores. Even with repartitions and full device wipes of internal memory.
Same thing. And since the internal storage is low and reserved for system and apps only the phone is stuck on the old restore firmware.
Brother it says E2fsck not found,what can I do?,, please help
Himanshu,
Can you please verify that you are typing the command in all lower case i.e. it should be “e2fsck” and not “E2fsck”. Also, not very sure, but if it still gives you problem, can you try to install Busy Box, and see if it works this time?
What error is it?
I have to use EXT because I buied it and moved the apps data to sdext2.
It appears nearly every time after I shut the phone down or it crashes.
i just try to help about it…after get partition from your pc, reboot your device, open link2sd and this partition can read it but you have to format with fat32 for get device support. then reboot again…trataratarata…you have done. hope usefull
e2fsck: Invalid argument passed to ext2 library while rewriting block and inode
bitmaps for /dev/block/mmcblk0p2
this is the error i am getting at 70 percent
My solution:
Use “Root explorer” app or any other like that, go to /data/sdext2, then verify if the permission r/w is ON.
SOLVED!
dude plz reply
i connect my phone to usb then enable usb debugging.den i open command prompt and i go to the folder where i have adb.when i run adb shell it shows device not found.wat to do?
I got all the errors fixed but when i pasted the code it says device/mount is busy and used by another program.Please help
If you have mounted the Card in Windows, please un-mount this first. That’s just connect the Phone using USB, don’t do anything on the Phone, launch the ADB shell and try executing the command.
Hii akbar….i am also having the same problem…..can u plz explain it in more detail.waiting for ur reply 🙂
Abhinaba,
The instructions are pretty clear, I think. Have you any experience of using the ADB tool? If no, here is one good tutorial on this:
http://forum.xda-developers.com/showthread.php?t=1474956
Once you see the command prompt, simply paste and run the following command (on ADB connection shell):
e2fsck -fpDC0 /dev/block/mmcblk0p2
This should fix your problem.