Database Develop

[Q] app2SD - can't mount ext2 partition

Hi, I have an unlocked, rooted Milestone running 2.1-update1.
I am having some issues getting App2SD up and running.
Everything seems to be working fine except for one piece:
I can't mount the ext2 partition of my SDCard.
I have a 16gb sdcard, formatted with two primary partitions, 14.5gb for FAT32 and 1.5gb for ext2.
busybox was installed ok, all the shell scripts seem to have installed fine as well, however, in order for it to work, the "mount_sd.sh" script has to be able to mount the second partition in order to link /data/app to it - but the damn thing won't mount.
I have tried re-partitioning the SD card multiple times, using multiple different partitioners (gparted in Ubuntu, Minitool in XP, even fdisk in the Android shell itself...) but nothing seems to work - I always get the same error:
Code:
# mount -t ext2 /dev/block//vold/179:2 /system/sd
mount -t ext2 /dev/block//vold/179:2 /system/sd
mount: No such device
The device however, most certainly DOES exist:
Code:
# ls /dev/block//vold
ls /dev/block//vold
179:2
179:1
179:0
I have seen that some people use the /dev/block/mmcblk0 instead of /dev/block//vold/179 - I am unsure as to why (anyone know which one I should be using on the Milestone???) but I tried that as well:
Code:
# mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount: No such device
Again, it tells me the device doesn't exist, when it clearly DOES:
Code:
# ls /dev/block/mmc*
ls /dev/block/mmc*
/dev/block/mmcblk0
/dev/block/mmcblk0p1
/dev/block/mmcblk0p2
When I try to verify the partitions are there in the ADB shell, it looks like /dev/block//vold/179 doesn't exist or is some kind of special device (incidentally, does anyone know wtf the double slashes "//" are for?):
Code:
# fdisk /dev/block//vold/179
fdisk /dev/block//vold/179
fdisk: can't open '/dev/block//vold/179'
However, I CAN fdisk /dev/block/mmcblk0, and it gives me the following partition table:
Code:
# fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
...snip...
Disk /dev/block/mmcblk0: 16.0 GB, 16039018496 bytes
255 heads, 63 sectors/track, 1949 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1762 14153233+ b Win95 FAT32
/dev/block/mmcblk0p2 1763 1949 1502077+ 83 Linux
So, it looks like /dev/mmcblk0 is the correct block device, however, mount tells me this:
Code:
# mount
mount
...snip...
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=101
020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
So, mount is telling me that the first partition is mounted onto /sdcard from /dev/block//vold/179:1
I am confused. The only thing left I need to do in order to get App2SD working on my Milestone, is to mount the bloody second partition of my SD card and link it to the file system, yet the damn thing refuses to mount.
Does anyone know where I am going wrong here?
Which is the correct block device I should even be trying to mount /dev/block/mmcblk0 or /dev/block//vold/179:2?
I don't want to flash to an unofficial 2.2 and I have everything else working just the way I want it, so I'd rather not reset either.
There MUST be a solution somewhere, but I am getting frustrated.
Thanks for any help you can give me!

Hello!
I'm having exactly the same problem... I've been trying to find a solution for this problem for the last 3 hours, but I can't figure out a way...
Can anyody give us a light??
Thanks!

Same question here. Partitioned more than a month ago, but then I reached a dead end. I don't know a reliable way to mount the ext2 partition. I'm familiar with Linux, and I have tried all kinds of crazy shell scripts, but the Android filesystem is still a bit alien to me.
By the way, what is this App2SD that you speak of? It's something different from the Apps2SD app on Froyo, right?

JoeDuncan said:
Code:
# mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount: No such device
Click to expand...
Click to collapse
A shot in the dark would be ext2.ko is not insmodded ... ?

got this problem to on stock US froyo kernel for Samsung Galaxy 5. I also suspected ext2 was missing but it seems compiled into kernel.
Code:
# cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev rpc_pipefs
nodev inotifyfs
nodev devpts
ext2
nodev ramfs
vfat
nodev nfs
rfs

For the MS, you have to insert a ext2 Kernel module, look around here on the forums..
Depending on which module-version you're using try "-t auto" instead of "-t ext2"
Also you should use "/dev/block/mmcblk0p2" if this is your ext2 partition
Besides, there should be some packages available which contain the necessary scripts and files to install this automatically and at boot, applicable as OR-updates

It was my understanding that Apps2SD could not be used on 2.1, you needed 2.2 to use that app. Although I have the same issue with Links2SD which is suppose to work with 2.1. I can't get anything to see an ext2 or 3 or Fat partition.

My amator tries
Hy,
I've got the same problem on Cyanogen and Goapk roms:
mount -t auto /dev/block/mmcblk0p2 /sd-ext
doesn't work
I verified sd-ext was present
mkdir /sd-ext
Nothing changed.
My mount description is somethime using vold instead of mmcblk0p... I don't really understand.
However I succeeded to mount sdext by using busybox (on goapk rom)
busybox mount -r -w -t auto /dev/block/mmcblk0p2 /sd-ext
result mount:
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /mnt/asec tmpfs rw,mode=755,gid=1000 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,g
id=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-
1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,uid=1
000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso
8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,size=0k,mode=000 0 0
/dev/block/mmcblk0p2 /sd-ext ext2 rw,errors=continue 0 0
Just in case, If somebody can help me:
*I have a symlink /data/drm =>/data/local :how to unsymlink it? (unbind isn't present and replacement doesn't work:" Invalid cross-device link")
*perl script are unable to decompresse boot.img, how to change init.rc in this case?
thanks

symlinks
lamidesbetes said:
*I have a symlink /data/drm =>/data/local :how to unsymlink it? (unbind isn't present and replacement doesn't work:" Invalid cross-device link")
Click to expand...
Click to collapse
Symlinks can be removed with the rm command.
The "cross device link" error happens when one uses the ln command without the "-s" option (so attempting a hard link instead of symlink).

system dump

Hey guys,
Here's a dump of /system from the Google I/O GT10.1. Let me know if there's anything else you're interested in.
http://www.mediafire.com/?hmjy4w04u9cb4j4

smaskell said:
Hey guys,
Here's a dump of /system from the Google I/O GT10.1. Let me know if there's anything else you're interested in.
http://www.mediafire.com/?hmjy4w04u9cb4j4
Click to expand...
Click to collapse
EDIT: Haha fail wasn't even thinking.....

Thanks mate. Can you dump boot and recovery as well? Not even sure if you can, but...

I could if I knew where they were. Someone more knowledgeable than I would probably know where they usually are. Unfortunately, I cannot search the device because most standard commands are not available(find, grep, etc.)

smaskell said:
I could if I knew where they were. Someone more knowledgeable than I would probably know where they usually are. Unfortunately, I cannot search the device because most standard commands are not available(find, grep, etc.)
Click to expand...
Click to collapse
Cool. Thanks.
Have you tried adding busybox? Im surprised that the root 'package' didn't include them. I think Titanium Backup will add it for you but not the symlinks AFAIK so you need to prefix each command with busybox. eg:
Code:
busybox chmod +x <file>

it won't let me create a link to /system/bin/ because it's stuck at read only. I created a thread about this already, but does anyone know how to remount /system? I've tried the standard ways and they don't seem to work

This worked for me:
mount -o remount,rw /system

If all else fails, use Root Explorer to remount /system

Just thinking "out loud" here, but would it be fair to say that if someone could extract the boot and recovery images from these google 10.1's that they could be flashed onto a 10.1v with Odin or fastboot and allow the 10.1v to be rooted in the same way as the 10.1g?

That's what I'm hoping
Sent from my GT-P7100 using XDA Premium App

ObsidianX said:
This worked for me:
mount -o remount,rw /system
Click to expand...
Click to collapse
wow, that was stupid of me. I was trying
mount -o remount,rw /dev/block/mmcblk0p4 /system
but obviously that isn't needed.
Thanks

alright, so I have busybox working
but all the tutorials I've found have said to use
cat /proc/mtd
to find out what to pull but for me, it just returns
dev: size erasesize name
also, they say to use
cat /dev/mtd/mtdX > /sdcard/mtdX.img
but /dev/mtd doesn't exist on this device
any ideas what I could be doing wrong?

smaskell said:
alright, so I have busybox working
but all the tutorials I've found have said to use
cat /proc/mtd
to find out what to pull but for me, it just returns
dev: size erasesize name
also, they say to use
cat /dev/mtd/mtdX > /sdcard/mtdX.img
but /dev/mtd doesn't exist on this device
any ideas what I could be doing wrong?
Click to expand...
Click to collapse
Stupid question, but you did do a
Code:
su
before running these commands?
Sometimes it's the simple things

it certainly wouldn't be the first time I'd missed something as blatantly obvious as that, but no I did remember this time. That's not to say that I'm not missing something else that should be completely obvious, but I did at least remember to run it as root.

smaskell said:
it certainly wouldn't be the first time I'd missed something as blatantly obvious as that, but no I did remember this time.
Click to expand...
Click to collapse
Haha - yeah, Ive certainly been stumped by simpler things than that. Usually success if followed by a facepalm
Really appreciate your persistence with this!
Could you possibly post the output of:
Code:
adb shell mount
and
Code:
adb shell su ls -l /cache
You should see from this output which device is mounted as /cache and how the /cache/recovery is mounted/linked.

certainly
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p4 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Code:
drwxrwx--- root root 1969-12-31 16:00 lost+found
drwxrwx--- system cache 2011-05-11 23:38 recovery
in /cache/recovery/last_log, I see this(among other things)
Code:
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) '(null)' 0000 '(null)' 0
1 /efs ext4 /dev/block/mmcblk0p1 (null) '(null)' 0000 '(null)' 0
2 /recovery emmc /dev/block/mmcblk0p2 (null) '(null)' 0000 '(null)' 0
3 /boot emmc /dev/block/mmcblk0p3 (null) '(null)' 0000 '(null)' 0
4 /system ext4 /dev/block/mmcblk0p4 (null) '(null)' 0000 '(null)' 0
5 /cache ext4 /dev/block/mmcblk0p5 (null) '(null)' 0000 '(null)' 0
6 /data ext4 /dev/block/mmcblk0p8 (null) '(null)' 0000 '(null)' -16384
I'll try pulling mmcblk0p2 and 3
Edit: here they are. Hopefully this is what you were looking for

or not.. I tried uploading twice and both times it appeared to succeed but they're not showing up. let's try again.
still not working. let's try mediafire
http://www.mediafire.com/file/r37q8vluzshkdu8/boot.img
http://www.mediafire.com/file/bhi4q2wrqgl2ms5/recovery.img

Fantastic! Thanks again.
Downloading now although I just discovered I have blown my 120Gb/month allowance in 14 days so it may take a while to download at 256k
EDIT: smaskell, you are truly a champ! Recovery works on the 10.1v so I now have root!
Will be posting a guide here and asking all to thank smaskell
http://forum.xda-developers.com/showthread.php?t=1079781

smaskell said:
or not.. I tried uploading twice and both times it appeared to succeed but they're not showing up. let's try again.
still not working. let's try mediafire
http://www.mediafire.com/file/r37q8vluzshkdu8/boot.img
http://www.mediafire.com/file/bhi4q2wrqgl2ms5/recovery.img
Click to expand...
Click to collapse
You need to zip them. XDA only accepts ZIPs and media files for upload. Only discovered this myself yesterday

excellent! just glad I could help =]

[SOLVED]"Not enough disk space" problem.

Ok.. so I was having issues with not being able to install apps after I did a factory reset on my phone and reinstalled v20q rebuild and a custom kernel.
Some things from the market automatically downloaded, but others failed saying "Not enough disk space".
So I attached my phone to the PC, and deleted some unimportant files (Like soutcraft demo I never used, I removed the spiderman/gameloft stuff.. and other stuff that I knew was not important. I DID NOT remove system files.
So in the end.. I had about a gig spare space on my internal SD card. BUT after rebooting it still says "not enough disk space".
So I tried to boot into CWM... but it no longer boots in. I can't install Astro as not enough disk space. how the heck can I find out what's going on?
Which partition is it referring to not enough space? (And why won't CWM work?)
If i goto settings > applications > Manage Applications > Storage > It tells me I am only using 302MB of 1.2GB .. so defo plenty. It must be a different partition?

The /system partition is probably full, not the entire internal SD-card. I ran across the same problem when I installed adaway and tried to install the hosts file. So I deleted a couple of .apk's from /system/app. Why the system partition is so small I don't know.

Might that explain why CWM isn't starting as well?

Just a quick thought: on my old phone, when this error occurred, I had to wipe cache partition. It wouldn't hurt to try - as you cannot access CWM, maybe there's a way to do this using ADB.

wiredback said:
Just a quick thought: on my old phone, when this error occurred, I had to wipe cache partition. It wouldn't hurt to try - as you cannot access CWM, maybe there's a way to do this using ADB.
Click to expand...
Click to collapse
I've tried a factory reset. It wouldn't do the reset.
I've tried formatting the internal SD Card. It did that, but made no difference.
As you say, I am unable to get into CWM, so I would need some help with ADB if I'm to sort this :-(

I had that once too.
Did you change to EXT4 ?

Hmm.. not that I remember. I remember it saying that it was 'converting to ext3' when I put flashed "V20Q rebuild" on again, but I thought it was ext3 anyway. I'm not sure anything I have put on has ext4...
Only other thing I put on was the V20Q tweak pack, followed by spica's HP RC12 kernel (was trying it out).
Only thing I can do at present is seemingly to get in Android, and hook it up to the PC. It's useable, but without apps I'm a bit screwed, and even more screwed without access to CWM.
Can I reflash CWM perhaps?
(Side Note: I have flashed V20Q rebuild, gueste kernel, flik123's tweak pack and spica's HP kernel before without issue... I think this might be relating to the internal partition space. How the hell do I get access to it).

It's a bit of a pain that you can't get in CWM else you could try the backtoext3 tool by Paul, and reflash
I did that and it worked.
But with my problem, CWM still worked... Strange.
try reflashing CWM, and then go in CWM and format your /system and do a full wipe.
And reflash the ROM.
Try the BackToExt3 tool too (if Reflashing CWM worked):
http://android.modaco.com/topic/336...3-for-converting-your-device-er-back-to-ext3/
IT WILL WIPE YOUR DATA
BTW : Only use the backtoext3.zip mod of course if you use a EXT3 ROM
If that all dind't work try to hard reset to factory settings with NVFlash:
http://android.modaco.com/topic/335...k-rom-release-v10b-dated-1300166062-15032011/
Flashing at your own risk of course.
Hope this helps you somewhat i'm just suggesting some things for you to try.

I would firstly try to flash CWM again using ROM Manager or (if this is not possible) manually (I think there is a thread in Development section how to do this).
Secondly, I would flash original ROM using Smartflash.

I'm unable to run that from work, so I'll give it a shot when I get home.

Restalling CWM did nothing. Still a blank screen after the 2nd LG logo (Where the CWM logo and options would normally be).
Hmm.. how can I get access to the system partition, and then how do I delete stuff? (I'm a newb at linux stuff)
In fact, interal and external CWM bat files seems to copy but doesn't work on reboot :-( ARGGHH.

Hmm.. seems I can do a 'pull' and managed to pull everything out of /system/ LOL!!!
Someone help me here.. I assume I need to delete something in /system/ (or another directory???) to make room on the partition?
As info I have been looking around and used the 'df' command to get this:
# df system
df system
Filesystem Size Used Free Blksize
system 338M 327M 11M 1024
# df root
df root
Filesystem Size Used Free Blksize
root 0K 0K 0K 4096
# df
df
Filesystem Size Used Free Blksize
/dev 185M 64K 185M 4096
/mnt/asec 185M 0K 185M 4096
/mnt/obb 185M 0K 185M 4096
/system 338M 327M 11M 1024 <---- is this the issue here 11M free ?
/data 1G 136M 1G 4096
/mnt/extasec 185M 0K 185M 4096
/lgdrm 2M 2M 398K 2048
/mnt/sdcard 5G 2M 5G 4096
/mnt/secure/asec 5G 2M 5G 4096
/mnt/sdcard/_ExternalSD 7G 2G 4G 32768
/mnt/extsecure/extasec 7G 2G 4G 32768

"Pulled" some files off as backups, and deleted a few apk's to try and make space on system, but CWM will still not boot.
I have tried deleting the dalvik-cache, and no difference. I've tried reinstalling CWM.. but no difference :-(
What is going on :-(
EDIT: Even after removing these APK's which must have given me at least 20mb extra.. I STILL cannot download anything else from the market. Something is wrong here. please help XDA

Have you tried the Smartflash or NVflash method
To hard reset your phone we recommended ?

Not yet. Spent all night trying to make space on the system area, but it still told me no space, and CWM wouldn't boot.
Which do you recommened I try first? Actually I will follow Rusty's post here and see what happens (with NVFlash) . http://forum.xda-developers.com/showthread.php?t=1229407&highlight=smart+flash
I am not worried about the data in the slightest, only recovering the phone.

@Scougar: the df output looks a bit strange for me. I was expecting to see something like this:
# df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 215564 32 215532 0% /dev
tmpfs 215564 0 215564 0% /mnt/asec
tmpfs 215564 0 215564 0% /mnt/obb
tmpfs 215564 0 215564 0% /mnt/asec
tmpfs 215564 0 215564 0% /mnt/extasec
/dev/block/mmcblk0p1 347067 198348 130799 60% /system
/dev/block/mmcblk0p8 1548144 271128 1198376 18% /data
/dev/block/mmcblk0p2 63461 4154 56031 7% /cache
/dev/block/mmcblk0p6 2472 2074 398 84% /lgdrm
(some other less relevant entries deleted to make the output more readable).
Please note that I can see actual devices (partitions) how much they are filled and where they are mounted. In your output I'm missing things like e.g. cache partition.
The above output I got on adb but the same thing appeared in terminal emulator on my phone (currently WIUI).
You can also use "mount" command to see what is mounted where.

mipr said:
@Scougar: the df output looks a bit strange for me. I was expecting to see something like this:
# df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 215564 32 215532 0% /dev
tmpfs 215564 0 215564 0% /mnt/asec
tmpfs 215564 0 215564 0% /mnt/obb
tmpfs 215564 0 215564 0% /mnt/asec
tmpfs 215564 0 215564 0% /mnt/extasec
/dev/block/mmcblk0p1 347067 198348 130799 60% /system
/dev/block/mmcblk0p8 1548144 271128 1198376 18% /data
/dev/block/mmcblk0p2 63461 4154 56031 7% /cache
/dev/block/mmcblk0p6 2472 2074 398 84% /lgdrm
(some other less relevant entries deleted to make the output more readable).
Please note that I can see actual devices (partitions) how much they are filled and where they are mounted. In your output I'm missing things like e.g. cache partition.
The above output I got on adb but the same thing appeared in terminal emulator on my phone (currently WIUI).
You can also use "mount" command to see what is mounted where.
Click to expand...
Click to collapse
OK, I'll redo the df tonight when I get in (I can't do it from work), and see what I get. Maybe you have a different version of ADB to me ? (I am using the version as supplied by Rusty in his CWM script thread - linked to from the Q&A).
I'm trying to go through the sequence of events that lead up to this:
1) Booted into CWM (I did all the below WITHOUT rebooting until I had finished installing ZIPS - fatal flaw?)
2) Wiped dalvik cache
3) wiped data/Factory reset
4) Installed the Rebuilt V20Q ROM
5) Installed the V20Q Tweak pack (From Flix123)
6) Installed Spica's latest HP kernel (RC12 a few days ago).
I then rebooted.
None of the above I believe would have changed to ext4, only ext3 (Although I really don't understand ext versions at present). Perhaps by me doing too much at once, and not rebooting after I installed the V20Q ROM is what did it?

I'm using the latest adb downloaded from google. But this should not matter because with adb you are running commands from your phone, not from your computer, i.e. after "adb shell" you are effectively on your phone and the "df" is one of the commands on your phone. You may try "df -a" which should list all your file systems. You may also try "df --help" to see all command options. Additionally the "mount" command (without any params) should list all your mounted devices/partitions along with their filesystems, e.g. on my phone I get following:
/dev/block/mmcblk0p1 on /system type ext4 (rw,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p8 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p6 on /lgdrm type ext3 (rw,nosuid,nodev,noatime,data=writeback)
As you can see my "system" partition is ext4, as well as "data" and "cache" partitions.

mipr said:
I'm using the latest adb downloaded from google. But this should not matter because with adb you are running commands from your phone, not from your computer, i.e. after "adb shell" you are effectively on your phone and the "df" is one of the commands on your phone. You may try "df -a" which should list all your file systems. You may also try "df --help" to see all command options. Additionally the "mount" command (without any params) should list all your mounted devices/partitions along with their filesystems, e.g. on my phone I get following:
/dev/block/mmcblk0p1 on /system type ext4 (rw,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p8 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p6 on /lgdrm type ext3 (rw,nosuid,nodev,noatime,data=writeback)
As you can see my "system" partition is ext4, as well as "data" and "cache" partitions.
Click to expand...
Click to collapse
Cool, thanks. I'll give those a go tonight

Here is the result of the mount command:- (I do not know how to interprete the output, advice here gladly received)
# mount
mount
rootfs / rootfs ro,noatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,noatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext3 ro,nodev,noatime,errors=continue,data=ordered
0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,noatime,errors=continue,data=ord
ered 0 0
tmpfs /mnt/extasec tmpfs rw,nodev,noatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p6 /lgdrm ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,ui
d=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noati
me,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocha
rset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:17 /mnt/sdcard/_ExternalSD vfat rw,dirsync,nosuid,nodev,noex
ec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp4
37,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/extsecure/extasec vfat rw,dirsync,nosuid,nodev,noexe
c,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp43
7,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/_ExternalSD/.android_secure tmpfs ro,relatime,size=0k,mode=000
0 0
#

[Help] Changing Around Mountpoints for sdcard and extSdCard?

Hey guys.
Some previous Samsung devices had no external storage at all but still mapped the biggest flash partition to /mnt/sdcard.
The Galaxy Tab 2 7.0 has a Micro SD card slot on it (one of the reasons I bought the thing!), but I guess for compatibility they still mount an internal flash storage partition to /sdcard. The actual micro SD card gets mounted to freaking /mnt/extSdCard.
Why does this matter?
Basically, tons of stuff in Android is setup to dump the large files to /sdcard by default. Things like games that require an extra download, the Camera app, etc. I've got a 32GB microSD card in there, and it makes me really frustrated that stuff won't just automatically use that.
So. What I'm looking to do is switch them around, so the internal fake flash partition ends up mounting to /mnt/extSdCard and the REAL microSD card mounts to /mnt/sdcard. That way my big huge card is where most data will end up automagically. Ultimately if I could just dump the internal "sdcard" partition and give that space to other parts of the system, that'd be sweet, but at this point I'm still kindof in la la land with Android, so I'll be happy just to get the mounts flipped around.
I do Linux stuff for work, and use a 5-disk file server at home running Ubuntu Server, so I approached this problem in a Linux way: why not mount via fstab??
Turns out Android doesn't actually directly have a /etc/fstab. Instead you've got /system/etc/vold.fstab.
From my brief research, this file appears to work pretty much the same way as fstab in Linux.
However, the stock one doesn't contain any mountpoint for the fake internal sdcard. vold.fstab seems to tell the vold executable what to do during boot-time.
My first problem: the vold.fstab file on my device doesn't contain any mount instructions for the /sdcard device.
Not a problem, I have SSH and WinSCP working, so I got a read on the mount points likeso:
Code:
127|[email protected]:/dev/block # cat /proc/mounts
rootfs / rootfs ro,noatime 0 0
tmpfs /dev tmpfs rw,nosuid,noatime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,mode=600 0 0
proc /proc proc rw,noatime 0 0
sysfs /sys sysfs rw,noatime 0 0
none /acct cgroup rw,noatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,noatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,noatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 rw,noatime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,noatime 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:25 /mnt/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
OK. so the vold.fstab file contains:
Code:
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# external sdcard
dev_mount sdcard /mnt/extSdCard auto /devices/platform/omap/omap_hsmmc.0/mmc_host/mmc1
#usb host device
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/omap/musb-omap2430/musb-hdrc/usb1
So, I have made a backup of my vold.fstab file, but I'm a little gun shy about making changes to it, particularly adding a new line for the "internal" sdcard. I know there are a couple of other ways to probably do this, like an init.d shell script that just executes the needed mount commands, and I'm honestly not sure if putting an entry for /mnt/sdcard into vold.fstab will override the mounts that are (I guess?) coming from the ramdisk init sequence. Any input, XDA devs?

Go for it :thumbup:
Sent from my GT-P3100 using xda app-developers app

I have the same Problem on my Galaxy Tab2 7.0 WIFI (GT-P3110 8 GB). I found a temporary Soloution for me. The App that i use is LINK2SD. You should have two partitions on SD card and both should be primary.
The first FAT partition is your standard sdcard (mountetd on extSdCard). The second partition /data/sdext2 is used for application files and can be ext2, ext3, ext4 or FAT32. Here are more informations about it: http://rootzwiki.com/topic/24500-if...move-apps-to-sd-card/page__st__10#entry701146
In this thread are the same Question: http://forum.xda-developers.com/showthread.php?t=1679037

I think it will read the changes. For example on the htc rezound the firmware update for ics changed the mount points from what was used in gb.So in order to run a gb Rom on ics firmware and vice versa the Fix was swaping vstab. Figure as long as u only mess with the sd mounts internal and ext. It will still boot and u can swap file as needed for testing.
Sent from my ADR6425LVW using xda premium

I'll try and figure it out.
Already found one thing: running the mount command with no switches will list all current mounts (can't believe I forgot that!).

DivinityCycle said:
I'll try and figure it out.
Already found one thing: running the mount command with no switches will list all current mounts (can't believe I forgot that!).
Click to expand...
Click to collapse
Im workin on it too. Im used to seeing them on separate lines. Ill let u know if i beat ya to it lol
Sent from my GT-P3113 using xda premium

Something else useful that I found:
Code:
[email protected]:/dev/block # cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 20480 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 716800 mmcblk0p7
259 0 20480 mmcblk0p8
259 1 1433600 mmcblk0p9
259 2 4886511 mmcblk0p10
259 3 524288 mmcblk0p11
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 30318592 mmcblk1
179 25 30314496 mmcblk1p1
and
Code:
[email protected]:/dev/block # df
Filesystem Size Used Free Blksize
/dev 347M 48K 347M 4096
/mnt/asec 347M 0K 347M 4096
/mnt/obb 347M 0K 347M 4096
/system 1G 259M 1G 4096
/data 4G 2G 2G 4096
/cache 688M 58M 630M 4096
/efs 19M 4M 15M 4096
/mnt/extSdCard 28G 13G 15G 32768
/mnt/sdcard 4G 2G 2G 4096
I'm pretty sure the partitions listed are found at /dev/block/mmcblk0pX, so maybe that's what needs to be mounted. I've not been successful yet in mounting anything manually but I just found this stuff, so hopefully will have it soon.

Hey DivinityCycle,
This post and tool in the S3 forum might be useful to you as it does the exact same thing in the GS3.
http://forum.xda-developers.com/showthread.php?t=1772234
If I recall correctly it needs a kernel with init.d support. But I think it will definitely help.
Rgrds
Sent from my GT-I9300

I have this in mine i didnt see it in yours
#storage_struct = series, "/mnt/sdcard/extStorages"
#storage_struct = parallel

Making progress, I was able to mount the "external" sdcard to my test mountpoint using:
mount -t vfat -o umask=0000 /dev/block/vold/179:25 /mnt/testing
So, that's part of the puzzle figured out. Now, just need to sort of out the internal "sdcard" device path and then I guess I can try throwing stuff into vold.fstab

OK I believe I have a solution will work, based on the init.d script inside the package Mattiadj made and Rostol linked me to (thanks!).
I modified his init.d script likeso:
Code:
sleep 2
mount -o remount,rw /
mkdir -p /data/internal_sd
mount -o bind /mnt/sdcard /data/internal_sd
mount -t vfat -o umask=0000 /dev/block/vold/179:25 /mnt/testing
mount -o bind /data/internal_sd /mnt/extSdCard
vold has to be used for external storage. The internal storage isn't very flexible, which is why that guy's script just binds it up during boot time rather than some other method of mounting it.
I have just run the commands in a terminal one by one and they all appear to do exactly what they "should", and I have verified that the result is the "real" sdcard being mounted to /mnt/sdcard, which ALSO makes it accessible at /sdcard (which I think is just a symlink). That's the default target for most apps, so after installing this init.d script I think everything should "just work".
Obviously you could adjust the mount point for the "internal" sdcard space as needed.
Working on the script and installation bit now.

/mnt/sdcard
/dev/fuse fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
Nice

OK I am having some problems getting the init.d script to work properly.
My working code is:
Code:
#!/system/bin/sh
LOG=/data/local/tmp/sdcard.txt
exec 3>&1 4>&2 >$LOG 2>&1
echo "Script start"
echo "Sleeping 2 seconds"
sleep 2
echo "Now attempting to remount root filesystem RW"
mount -o remount,rw /
echo "Make the internal_sd directory"
mkdir -p /data/internal_sd
echo "Bind the internal sdcard to the new folder"
mount -o bind /mnt/sdcard /data/internal_sd
echo "Mount the real sdcard"
mount -t vfat -o umask=0000 /dev/block/vold/179:25 /mnt/sdcard
echo "Bind the internal_sd directory to the extSdCard mountpoint"
mount -o bind /data/internal_sd /mnt/extSdCard
echo "Script done"
Basically I am logging the output to /data/local/tmp/sdcard.txt, so I can debug.
In that log, it gets as far as the first mount command, and then things go off the rails:
Code:
Script start
Sleeping 2 seconds
Now attempting to remount root filesystem RW
Make the internal_sd directory
Bind the internal sdcard to the new folder
mount: Invalid argument
Mount the real sdcard
mount: No such file or directory
Bind the internal_sd directory to the extSdCard mountpoint
Script done
What's messed up is, the same mount command (with the bind) works fine once the device is all the way booted up.
Its just during the "init" sequence that it has a problem. I have no idea why

We had a similar thing for my Droid x2. You my want to check out this thread http://forum.xda-developers.com/showthread.php?p=16875467 and contact the dev.
Sent from my GT-P3113 using xda premium

That guy did it via vold.fstab, which is interesting.
The relevant stuff:
Code:
# external sd card
dev_mount sdcard /mnt/sdcard:none:lun1 auto /devices/platform/tegra-sdhci.2/mmc_host/mmc2 /devices/platform/tegra-sdhci.2/mmc_host/mmc1
# internal eMMC
dev_mount sdcard_ext /mnt/sdcard-ext 18 /devices/platform/tegra-sdhci.3/mmc_host/mmc0
I am honestly not too sure what I'm looking at there, so I'm gonna try some stuff in vold.fstab next.

OK, I am too tired to keep messing around with this for tonight, so I am trying out a new method: I moved my init script over to /data and then used Script Manager to make it run as root as boot time.
This is obviously not a permanent fix, but should be OK for tonight.
Basically my big problem is I don't know the syntax for vold.fstab to mount the internal sdcard to a new mount point...

Ahh the joys of doing weird hacky stuff to your tablet... I pretty much gave up on the vold.fstab working in the short term, and instead just tried setting my init script up as just a regular "run at launch" script using Script Manager.
The version of my script that I posted had unforeseen consequences. For whatever reason, doing a "bind" of /mnt/sdcard like I was doing caused all sorts of things to stop working. Like, Script Manager was locking up, as was Root Explorer!
The best one was that when my alarm clock went to go off this morning it crashed, and I was late for work! LOL
Sooo yeah, that's pretty special. I had to use Terminal Emulator to fix my stuff on the bus on the way to work
I have revised my script and it now works perfectly with the caveat that I'm simply unmounting the internal "sdcard" partition and letting it sit there unused.
Code:
#!/system/bin/sh
LOG=/data/local/tmp/sdcard.txt
exec 3>&1 4>&2 >$LOG 2>&1
echo "Script start"
echo "Unmount internal sdcard"
umount /mnt/sdcard
echo "Mount the real sdcard"
mount -t vfat -o umask=0000 /dev/block/vold/179:25 /mnt/sdcard
echo "Script done"
I believe because of vold.fstab the microSD card still gets mounted to /mnt/extSdCard. My script puts it at /mnt/sdcard as well. This seems to work OK because then the few programs that are smart enough to access the card via /mnt/extSdCard still can get to it, but everything else that works on the regular sdcard also goes to the sdcard as well.
I have tested out the camera, music player, Root Explorer, Script Manager, etc. Everything I have tried works exactly as expected.
The next thing I'll need to test out is if this script can be used as an init.d script instead of needing Script Manager to set it up to run at boot.
I figure the only other things to do are:
1-figure out what's needed to be able to mount the internal "sdcard" partition to a different mount point
or
2-figure out how to delete the "sdcard" partition and then just give that extra space to one of the other flash partitions (probably /system?)

I really am hoping you get this figured out and it can be used by us common folk. (I'm no hacker) Lol :thumbup:
Sent from my GT-P3113 using xda premium

Wow, while working on my init.d script, I managed to make my system freeze at the bootup animation. I "unlocked" things by reflashing my ROM.
Good thing its a slow day at the office...

i really hope u can get this working, would love it

Cannot format /data using TWRP 3.0.2[Solved]

I have a problem ... i'm trying to install Android MM using TWRP 3.0.2 but i can't because i can't format.
When i'm trying to format it shows this error: E:Unable to wipe '/data' -- unknown file system 'auto'
Unable to format to remove encrytion
Do i need to use another recovery?
Can someone tell me how to solve this?

I had the same problem, for some reason TWRP is unable to format encrypted partitions.
It can be solved using adb shell or using the terminal in TWRP (it's under the advanced tab).
To format the partition you have to know which device it is, to find out type this inside the terminal:
Code:
cat /etc/fstab
In my case the output is:
~ # cat /etc/fstab
/dev/block/mmcblk0p13 /system ext4 rw 0 0
/dev/block/mmcblk0p14 /cache f2fs rw 0 0
/dev/block/mmcblk0p15 /data f2fs rw 0 0
Which means that my /data is on device /dev/block/mmcblk0p15 and uses the f2fs filesystem. If you're on f2fs then you can format the partition using
Code:
mkfs.f2fs /dev/block/mmcblkXXXX
if you're on ext4 then use
Code:
make_ext4fs /dev/block/mmcblkXXXX
Where XXXX is whatever is in your fstab. After this TWRP should be able to mount /data.

It worked,thank you!

Ok, now i have another problem ... every time i'm trying to install(flash) a zip with TWRP it's rebooting again in TWRP and can't install anything ... I had this problem in the past and i solved it but i forgot how i did that .. anyone knows?
Solved: i had to format my sd card.

penn.gwyn said:
I had the same problem, for some reason TWRP is unable to format encrypted partitions.
It can be solved using adb shell or using the terminal in TWRP (it's under the advanced tab).
To format the partition you have to know which device it is, to find out type this inside the terminal:
Code:
cat /etc/fstab
In my case the output is:
~ # cat /etc/fstab
/dev/block/mmcblk0p13 /system ext4 rw 0 0
/dev/block/mmcblk0p14 /cache f2fs rw 0 0
/dev/block/mmcblk0p15 /data f2fs rw 0 0
Which means that my /data is on device /dev/block/mmcblk0p15 and uses the f2fs filesystem. If you're on f2fs then you can format the partition using
Code:
mkfs.f2fs /dev/block/mmcblkXXXX
if you're on ext4 then use
Code:
make_ext4fs /dev/block/mmcblkXXXX
Where XXXX is whatever is in your fstab. After this TWRP should be able to mount /data.
Click to expand...
Click to collapse
I did that but I am getting only this
/3rdmodem ext4 rw 0 0
/cache ext4 rw 0 0
/data f2fs rw 0 0
and so on
/dev/block/mmcblkXXXX is missing My TWRP version is 3.1.1-1-frd any help would be greatly appreciated.

penn.gwyn said:
I had the same problem, for some reason TWRP is unable to format encrypted partitions.
It can be solved using adb shell or using the terminal in TWRP (it's under the advanced tab).
To format the partition you have to know which device it is, to find out type this inside the terminal:
Code:
cat /etc/fstab
In my case the output is:
~ # cat /etc/fstab
/dev/block/mmcblk0p13 /system ext4 rw 0 0
/dev/block/mmcblk0p14 /cache f2fs rw 0 0
/dev/block/mmcblk0p15 /data f2fs rw 0 0
Which means that my /data is on device /dev/block/mmcblk0p15 and uses the f2fs filesystem. If you're on f2fs then you can format the partition using
Code:
mkfs.f2fs /dev/block/mmcblkXXXX
if you're on ext4 then use
Code:
make_ext4fs /dev/block/mmcblkXXXX
Where XXXX is whatever is in your fstab. After this TWRP should be able to mount /data.
Click to expand...
Click to collapse
I tried this but now i cant fully install roms correctly. However i did this to more than just data

Hi, I tried this, but it's telling me : "need size of filesystem"
Do you have an idea of what's going wrong ? thanks
BTW : i have : /dev/block/dm-0 /data ext rw 0 0

hi I need help. Tell me "need size of filesystem"
Please help me.

help me /sbin/e2fsck -fp /dev/block/sda18 process ended with ERROR: 8
Cannot format /data using TWRP
and
make_ext4fs /dev/block/mmcblkXXXX
tell me "need size of filesystem"
help me please

dont know how i got into this. perhaps its the twrp 3.5.2_9 issue.
my parition names are long. ../soc.0/f9824900.sdhci/by-name/userdata
there is no data partition.
any way to get out of this? i dont have anything on the phone so i just want to get back to clean start.