Dear all,
This is just to help anyone avoid a stupid mistake I did myself when trying to set up Link2SD on a 4G P780 with ROW S228.
The bottom line is - use ext4. Or in other words - use the file system your phone uses already. To find it out, you need some terminal emulator. Just run
Code:
mount
and examine the output.
More background for the curious (or, well, if you just want to laugh a bit...)
I searched the forum beforehand and saw some remarks about successfull usage of ext2. So I formatted the second partition to ext2. No success - Link2SD complained about "no mount point". Same story with ext3. So I gave up (it was late evening) and temporarily used VFAT. When I started to think about compiling ext3 support, I realised the phone must already use some non-FAT FS. And mount command gave me the answer...
Hope that helps someone.
Related
Hi.
I've rooted my A70s with chulri's kernel and it seems to work ok.
My next goal is to get more app room ... so I guess I need to resize the app/data partition.
I've thought that having my internal storage formatted on ext4, it would be possible to ln the /data folder to /storage/data without problems, but then I should create a boot script for that. The question is... can I do this with my current root status? What would be the way to do it? I'm don't know enough of linux os to make it on my own.
If the system can't be fooled with a ln, then is there any way to resize the data partition, even if I have to backup/restore my current data?
I don't want to use Urukdroid, since all the versions I tried were very unstable on my machine.
Cheers!!
search the forum: http://forum.xda-developers.com/showthread.php?p=14710945#post14710945
Follow chulri's method, or repartition your internal storage in Linux, mount it on the archos, and copy the data there. Then edit init.rc and change the data mount line. If it gets mounted in the kernel, you'll have to umount it first to remount it to the other partition.
Hey all I'm running CMD 7.1 (RC) on a Nexus One and I've followed the instructions to partition my sd card from here as ext3, installed link2sd, and get this error:
Mount script error
Mount script cannot be created.
mount: mounting/dev/block/
vold/179:2 on /data/sdext2
failed: Device or resource busy
Anyone have a solution for this? I have searched XDA and Google for a solution, a few posts showed up with the same problem, but the person that starts the thread with the same problem ends up not following their own thread, or finds a solution without explaining how.
I am having the exact same problem, Nexus One with CM7 nightly 214. Tried S2E but it kept screwing up and trashing my EXT partition so I wanted to try Link2SD.
Finally got it to work but I can only get EXT3 partition, tried updating using Amon-Ra and MiniTool Partition but neither updated to EXT4.
In Terminal you can check the type of EXT partition by typing: mount | grep sd-ext
Everything I tried kept giving me only an EXT2 partition, I tried converting to EXT4 using MiniTool Partition Manager which reported a successful conversion but when I checked in terminal it reported EXT2. I then used Amon-Ra recovery to convert from EXT2 to EXT3 and now Link2SD works. Lexar 32GB Class 10 SD. Hope this helps.
Possible solution
I might have just found a solution.
Do you guys use any kind of bk2sdext? (automated backup of app/data to sdext partition, which comes with some ROMs built in)
To find out, go to your build.prop file in /system and check, it's one of the last lines, if it says something like bkup2sdext.enable=1, then disable it (switch 1 to 0), save and restart.
After that either go to ClockworkMod Recovery or just unmount your SD card, in order to FORMAT the sd-ext partition again so that it doesn't contain any data (and doesn't get automatically filled back, because bkup2sdext is off now).
This way I was able to mount it finally.
I think it has something to do with the build.prop AND the sd-ext partition having some other data on it before first mounting with link2sd.
Cheers.
download titanium backup press menu select batch operation scroll down till u see move all user apps to sd(if supported) and also make sure that you have checked allow application moving(settings->applications)
I have segmentation fault all the time,donnu why
hello,
I'd ask the question in the dev UBUNTU testing thread, but I don't have enough posts yet.
I am following the lifeinarootshell.blogspot.com/ instructions and have been following the Ubuntu thread since its beginning. I'm a bit of a newbie with linux, so it's taking some time.
I can't mount the micro sd card... I'm trying with the command "mount /dev/block/mmcblk1p1 /data/mmc"
When I type "mount" from a terminal on the TF201, I don't see "/dev/block/mmcblk1p1" listed.
This micro sd has my roofs on it that I need to chroot into. I've tried reformatting like 10 times now using various methods. I've used an HP format tool at fat32, then used the Minitool partition wizzard and formatted as ext4. I've also tried the gparted tool in a ubuntu vm. It's set as a primary partition.
Can anybody point me in the right direction?
Okay, got it figured out....
nookusr said:
hello,
I'd ask the question in the dev UBUNTU testing thread, but I don't have enough posts yet.
I am following the lifeinarootshell.blogspot.com/ instructions and have been following the Ubuntu thread since its beginning. I'm a bit of a newbie with linux, so it's taking some time.
I can't mount the micro sd card... I'm trying with the command "mount /dev/block/mmcblk1p1 /data/mmc"
When I type "mount" from a terminal on the TF201, I don't see "/dev/block/mmcblk1p1" listed.
This micro sd has my roofs on it that I need to chroot into. I've tried reformatting like 10 times now using various methods. I've used an HP format tool at fat32, then used the Minitool partition wizzard and formatted as ext4. I've also tried the gparted tool in a ubuntu vm. It's set as a primary partition.
Can anybody point me in the right direction?
Click to expand...
Click to collapse
I needed to use the busybox, so the command to mount is "busybox mount /dev/block/mmcblk1p1 /data/mmc"
Hope it might help someone else if they have the same issue.
hope it's not a big deal to be in the question thread
nookusr said:
I needed to use the busybox, so the command to mount is "busybox mount /dev/block/mmcblk1p1 /data/mmc"
Hope it might help someone else if they have the same issue.
Click to expand...
Click to collapse
Being a noob, I hadn't realized what busybox was really. Now I see it adds more functionally to the terminal.
What was funny was that I could mount and browse the files in TWRP, but not within android....
Yes well, I can now proceed....
Figured it out....
nookusr said:
hello,
I'd ask the question in the dev UBUNTU testing thread, but I don't have enough posts yet.
I am following the lifeinarootshell.blogspot.com/ instructions and have been following the Ubuntu thread since its beginning. I'm a bit of a newbie with linux, so it's taking some time.
I can't mount the micro sd card... I'm trying with the command "mount /dev/block/mmcblk1p1 /data/mmc"
When I type "mount" from a terminal on the TF201, I don't see "/dev/block/mmcblk1p1" listed.
This micro sd has my roofs on it that I need to chroot into. I've tried reformatting like 10 times now using various methods. I've used an HP format tool at fat32, then used the Minitool partition wizzard and formatted as ext4. I've also tried the gparted tool in a ubuntu vm. It's set as a primary partition.
Can anybody point me in the right direction?
Click to expand...
Click to collapse
I thought I'd post my solution here just in case if anyone else had the smae problem.
I had busybox installed and did not know what it did. It looks like busybox allows a selection of terminal commands. Therefore, I needed to type "busybox mount /dev/block/mmcblk1p1 /data/mmc"
this mounted without errors.
Hello everyone, this is my very (noob) first thread, and is a question.
I've started reading xda forums like 3 days ago, for like 12 hours each day... and its an amazing comunity of knowledge. Osom.
Well... ive been trying to set a 2nd partition on my 32gb C10 SD for extend internal memory with link2sd on my OptimusOne... on the way i learned how to mod, terminal mount and modify, recover, and all the stuffs that could make this work... but i surrender.
I can make it work formating SD with mini-tool partition wizz, conecting device to PC, and seting into USB massive storage mode (yeap! Worked indeed!!) but if i reboot 2nd Part. lose format and link2sd report error on mounting 2nd partition (says its invalid, mini-tool says it's unformated)... for re-mount i have to re-format with mini-tool and wipe the data... so i've avoided linking any app.
Readed about NAND lock (my device is by default unlocked), /system permisions, and others... and i simply cant make 2nd partition stays at FAT32. (yes, i tried with the other formats too, formated with CWM on recovery mode too and nothing).
Tried this too http://forum.xda-developers.com/showthread.php?t=1971689, and didn't work for me.
Last discover was that via Root Browser app, /system file has no "Sticky" permision, if i modify it then busybox and other apps fail and run into recovery mode... (had to reinstal everything several times)
I know there is some kind of permision that i missed... but could be kernel config?
The most simply thing and i cant make it work... ideas?
Hi there!
I have been using the latest CM11 nightly for a while and decided to go for Link2SD, but I simply cannot mount my sd-ext partition from recovery. I have partitioned my SD-card of size 16GB with MiniTool Partition Wizard, and created an EXT3 partition of size 2GB. The partitions appear perfectly on the software, but whenever I try to mount /sd-ext from recovery, I get an error of "Error mounting /sd-ext!". Could anyone please help me out here? Quite a n00b here about sd-ext really.
I never tried mounting the sd-ext from recovery, but it works just fine after boot. What would you do with mounted sd-ext in recovery?
Well, I want to use Link2SD and have been always receiving an error message while creating the mount script, which goes something like:
"Mount script error
Mount script cannot be created.
mount: Invalid argument"
Also, upon looking into the Storage info, I find that SD Card 2nd Part. is not mounted. This is why I'm trying to mount my sd-ext from the CWM recovery, so that I can eradicate the error. Am I going in the wrong track?
I don't know, ext partition should work out of the box. What I did was partition sd card, boot, install link2sd, create mount script, reboot once again, done.
The only time link2sd won't create mount script for me is when the internal memory is full. Maybe your internal memory is full?
Not really, my internal memory is at least 50% free. Either way, I'll try reflashing the kernel and make a fresh install, and see if the problem persists. Thanks for responding and helping regardless!
psychoticdemon said:
Not really, my internal memory is at least 50% free. Either way, I'll try reflashing the kernel and make a fresh install, and see if the problem persists. Thanks for responding and helping regardless!
Click to expand...
Click to collapse
u say u created an ext3 partition?? so u must hav selected the same when creating mount scripts in link2sd right?? then it shud work...
it if did not work try with ext4 partition as i am using the same with ext4 partition for a year now...
psychoticdemon said:
Well, I want to use Link2SD and have been always receiving an error message while creating the mount script, which goes something like:
"Mount script error
Mount script cannot be created.
mount: Invalid argument"
Also, upon looking into the Storage info, I find that SD Card 2nd Part. is not mounted. This is why I'm trying to mount my sd-ext from the CWM recovery, so that I can eradicate the error. Am I going in the wrong track?
Click to expand...
Click to collapse
Reboot then, dude. recreate mount script again, reboot, let see what happen next
Alright, I finally got Link2SD working and apparently, as it turned out, it's more comfortable with ext4 than ext3. Creating a mount script always failed when I tried with ext3, but with ext4, it worked like a charm. Anyway, thanks for all the advice, guys. Gonna tag this as solved right away.