Database Info

[Q] how to tell android to detect my sd card storage as external storage

Hello xda hackers,first off I'd like to say this is my first post here but your forums (and forum members work) has helped a lot.
I've recently been experimenting with xfs for my "sd card" on my nexus s.
(just to see the performance difference between xfs,fat32 and ext4 on my nexus s)
I've successfully compiled mkfs.xfs for arm and I’ve successfully formatted my sdcard storage with xfs. I’ve even gotten it to mount fine in android (btw, i use a custom kernel based on netarchy's git repo). i can verify it's mounted(i've even gotten it to mount at boot because vold.fstab just wasn't working). and i can even access files on it using some file browser apps.
the problem I'm having is that all of my apps think i don't have "external storage".
I've even done setprop EXTERNAL_STORAGE_STATE mounted
camera,music,etc.... all the apps say i don't have usb/external storage.
so i just wanted your help in finding out how exactly android tells if a mount-point is external storage or not.
FYI: my nexus s doesn't really have an sd card it's an internal storage (i think nand).
here is the output of some commands in case you need it:
adb shell mount:
Code:
rootfs / rootfs ro,noatime 0 0
tmpfs /dev tmpfs rw,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,relatime,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,relatime,cpu 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/mtdblock6 /efs yaffs2 rw,nosuid,nodev,noatime 0 0
/dev/block/platform/s3c-sdhci.0/by-name/system /system ext4 rw,noatime,barrier=0,nobh,data=ordered 0 0
/dev/block/platform/s3c-sdhci.0/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,barrier=0,nobh,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p3 /mnt/sdcard xfs rw,noatime,attr2,noquota 0 0
none /sys/kernel/debug debugfs rw,noatime 0 0
adb echo $EXTERNAL STORAGE :
# echo $EXTERNAL_STORAGE
/mnt/sdcard
feel free to ask me for more info. and yes I’ve googled it all over and plenty of people have tried helping me on irc. all the topics that come up is about people having their sd cards not detected.

mkfs.xfs in case anyone wants it.
oh, and I’ve attached mkfs.xfs for those of you who want to run it from your phones but don't want to compile it from the source(it took me a few hours to get around some of the compilation/cross-compilation issues).
it's 1.8Mb because it's statically linked.

nvm, i got is solved by hacking around vold. thanks for all the help...Not.

i cant mount sdcard storage
hi i have samsung galaxy 3 i5800
end i instaled on my phone kyrilos v9.4 rom
end now i want to mount sdard storage bat wen i go to the recovery
i choice mount sdcard storage,mount sdcard ext end reboot nothing hapen
i go back to recovery end i have agen option mount sdcard that mean my card is not mounted
pleace i need som healp this is my first android phone
sory for my english

[Q] Midnight Commander on ICS

A brand-new Galaxy Nexus, rooted, installed many apps w.o. problems. (e.g. sshd, Total Commander, ConnectBot, OpenVPN, ...) Tried to install Midnight Commander as seen here:
http://forum.xda-developers.com/showthread.php?t=1243699&page=6
No success, so I tried from scratch, copied files into /system dir and subdirs. It works. But in some subdirs the mc has no read-permission, e.g. /system, /data... I'm wondering, able to listing contents of these directories directly from console. Also able to copy files into /system or /etc with F5.
Any Hints?
Thanks, Charmin.

.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.

Same problem on ICS (cm-9.0.0-RC1-maguro.zip)...
I do not have the solution but I may have a clue. When mc attempts to access /system, strace shows:
Code:
chdir("/system") = 0
getcwd("/system", 4096) = 8
stat64("/system", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/system", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
open("/system", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = 3
fstat(3, 0xbe98d868) = -1 EOVERFLOW (Value too large for defined data type)
close(3) = 0
Hopefully someone will find that info to be helpful...

Similar problem, cannot access sdcard, Resurrection Remix 2.6.1 on SGS2
strace:
ioctl(0, TIOCLINUX, 0xbecc07c7) = -1 EINVAL (Invalid argument)
chdir("/mnt/sdcard") = 0
getcwd("/mnt/sdcard", 4096) = 12
stat64("/mnt/sdcard", {st_mode=S_IFDIR|075, st_size=32768, ...}) = 0
stat64("/mnt/sdcard", {st_mode=S_IFDIR|075, st_size=32768, ...}) = 0
stat64("/mnt", {st_mode=S_IFDIR|0775, st_size=0, ...}) = 0
open("/mnt/sdcard", O_RDONLY|O_NONBLOCK|O_DIRECTORY|0x80000) = 3
fstat(3, 0xbecbf6f8) = -1 EOVERFLOW (Value too large for defined data type)
close(3) = 0
select(1, [0], NULL, NULL, {0, 0}) = 0 (Timeout)
Thank you,

An additional data point...
I tried midnight commander on the standard AOSP ICS via the emulator that comes with the SDK (platform 4.1). No problem! Access to any directory (i.e. /system) is error free...
This issue appears to be specific to Cyanogenmod (at least with my version cm-9.0.0-RC1-maguro.zip).

Is the source code (w/ android specific configure options and patches) for this version of Midnight Commander available somewhere?

I decided to build my own version of Midnight Commander so I could fix this bug for myself. You can find it here (in n00b URL syntax):
www dot noid dot net slash mc-android

Why not use Ghost Commander? Free and works well, it's available from Google Playstore.

demonoflust said:
Why not use Ghost Commander? Free and works well, it's available from Google Playstore.
Click to expand...
Click to collapse
Ghost Commander looks great and I'll probably use that too... It's great to have both!
The Ghost Commander is a GUI app that runs on your device's screen as a normal Android application does.
This version of Midnight Commander that I've made is a console app. It runs in a terminal. So, to use it on your device's screen, you would first need to start a "terminal emulator" application. But that's not where it really shines because (on a phone at least) it's very small and the default soft-keyboard does not have function keys, etc..
This version of Midnight Commander is ideal if you are using your home PC (with a full keyboard) and you SSH into your device. For example, if you are running DroidSSHd on your device and you use PuTTY from you home PC to connect. Now you're really cooking!
So they're both good (but different)...

charminbear said:
A brand-new Galaxy Nexus, rooted, installed many apps w.o. problems. (e.g. sshd, Total Commander, ConnectBot, OpenVPN, ...) Tried to install Midnight Commander as seen here:
http://forum.xda-developers.com/showthread.php?t=1243699&page=6
No success, so I tried from scratch, copied files into /system dir and subdirs. It works. But in some subdirs the mc has no read-permission, e.g. /system, /data... I'm wondering, able to listing contents of these directories directly from console. Also able to copy files into /system or /etc with F5.
Any Hints?
Thanks, Charmin.
Click to expand...
Click to collapse
The same for a brand-new Samsung Galaxy S2 ( ICS 4.0.4) , rooted
Dont list /system, /data a its subfolder...
---------- Post added at 04:37 PM ---------- Previous post was at 04:23 PM ----------
a.human said:
Same problem on ICS (cm-9.0.0-RC1-maguro.zip)...
I do not have the solution but I may have a clue. When mc attempts to access /system, strace shows:
Code:
chdir("/system") = 0
getcwd("/system", 4096) = 8
stat64("/system", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/system", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
open("/system", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = 3
fstat(3, 0xbe98d868) = -1 EOVERFLOW (Value too large for defined data type)
close(3) = 0
Hopefully someone will find that info to be helpful...
Click to expand...
Click to collapse
I have one idea =
looks like that listing doesnt work, because both mounts /system and /data larger then 500GB
# df
Filesystem Size Used Free Blksize
/dev 413M 76K 413M 4096
/mnt/asec 413M 0K 413M 4096
/mnt/obb 413M 0K 413M 4096
/system 503M 498M 5M 4096
/cache 98M 4M 94M 4096
/efs 19M 8M 11M 4096
/data 1G 426M 1G 4096
---------- Post added at 04:43 PM ---------- Previous post was at 04:37 PM ----------
yariks7 said:
The same for a brand-new Samsung Galaxy S2 ( ICS 4.0.4) , rooted
Dont list /system, /data a its subfolder...
I have one idea =
looks like that listing doesnt work, because both mounts /system and /data larger then 500GB
# df
Filesystem Size Used Free Blksize
/dev 413M 76K 413M 4096
/mnt/asec 413M 0K 413M 4096
/mnt/obb 413M 0K 413M 4096
/system 503M 498M 5M 4096
/cache 98M 4M 94M 4096
/efs 19M 8M 11M 4096
/data 1G 426M 1G 4096
Click to expand...
Click to collapse
correct large /mnt/sdcard also not listable by mc!
Filesystem Size Used Free Blksize
/system 503M 498M 5M 4096
/data 1G 442M 1G 4096
/mnt/sdcard 11G 305M 11G 32768
---------- Post added at 04:50 PM ---------- Previous post was at 04:43 PM ----------
yariks7 said:
The same for a brand-new Samsung Galaxy S2 ( ICS 4.0.4) , rooted
Dont list /system, /data a its subfolder...
---------- Post added at 04:37 PM ---------- Previous post was at 04:23 PM ----------
I have one idea =
looks like that listing doesnt work, because both mounts /system and /data larger then 500GB
# df
Filesystem Size Used Free Blksize
/dev 413M 76K 413M 4096
/mnt/asec 413M 0K 413M 4096
/mnt/obb 413M 0K 413M 4096
/system 503M 498M 5M 4096
/cache 98M 4M 94M 4096
/efs 19M 8M 11M 4096
/data 1G 426M 1G 4096
---------- Post added at 04:43 PM ---------- Previous post was at 04:37 PM ----------
correct large /mnt/sdcard also not listable by mc!
Filesystem Size Used Free Blksize
/system 503M 498M 5M 4096
/data 1G 442M 1G 4096
/mnt/sdcard 11G 305M 11G 32768
Click to expand...
Click to collapse
strange but large submounts accessible and listable
/dev/block/vold/259:3 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
tmpfs /mnt/sdcard/external_sd tmpfs rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000 0 0
tmpfs /mnt/sdcard/usbStorage tmpfs rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,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,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/mnt/sdcard/Alarms # df
Filesystem Size Used Free Blksize
/dev 413M 76K 413M 4096
/mnt/asec 413M 0K 413M 4096
/mnt/obb 413M 0K 413M 4096
/system 503M 498M 5M 4096
/mnt/sdcard 11G 305M 11G 32768
/mnt/sdcard/external_sd 7G 6G 1G 32768
/mnt/sdcard/external_sd 7G 6G 1G 32768
/mnt/secure/asec 7G 6G 1G 32768
so /mnt/sdcard not listable ,
but large /mnt/secure/asec and /mnt/sdcard/external_sd is listable too.

Hello guys,
I've double checked MC and everything seems ok, on my phone it works (it has 16Gb internal memory from which about 10Gb are assigned to /storage/sdcard, and I added 16gb external SDCARD which it mounts under /storage/extSdCard).
Code:
[[email protected]]/sdcard# busybox df -k
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 426612 84 426528 0% /dev
tmpfs 426612 0 426612 0% /mnt/asec
tmpfs 426612 0 426612 0% /mnt/obb
/dev/block/mmcblk0p3 20144 8372 11772 42% /efs
/dev/block/mmcblk0p9 1548144 863612 684532 56% /system
/dev/block/mmcblk0p8 1007896 17280 990616 2% /cache
/dev/block/mmcblk0p12
11901576 8123632 3777944 68% /data
/dev/fuse 11799176 8123632 3675544 69% /storage/sdcard0
/dev/block/vold/179:17
15613952 14060896 1553056 90% /storage/extSdCard
I'm using an S3 with rooted stock firmware and stock kernel and I can navigate everywhere without incidents.
The only question that now comes to mind is if you somehow formatted the the /mnt/sdcard with ext2/3 filesystem ? Or is it FAT32 single partition ?

Hello viulian,
thank your reply .
I think you are right - it depends on filesystem type (and it size also) .
Large /mnt/sdcard/external_sd (vfat) is listable,
but large ext4 partition /system and /data is NOT listable.
here is my
#busybox df -k
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 423444 76 423368 0% /dev
...[skipped]...
/dev/block/mmcblk0p9 516040 510032 6008 99% /system
/dev/block/mmcblk0p10 2064192 720956 1343236 35% /data
/dev/block/vold/259:3 12063840 2676224 9387616 22% /mnt/sdcard
tmpfs 31154688 2222432 28932256 7% /mnt/sdcard/external_sd
/dev/block/vold/179:9
31154688 2222432 28932256 7% /mnt/sdcard/external_sd
...[skipped]...
1|[email protected]:/sdcard #
1|[email protected]:/sdcard # mount
/dev/block/mmcblk0p9 /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/259:3 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
tmpfs /mnt/sdcard/external_sd tmpfs rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
viulian said:
Hello guys,
I've double checked MC and everything seems ok, on my phone it works (it has 16Gb internal memory from which about 10Gb are assigned to /storage/sdcard, and I added 16gb external SDCARD which it mounts under /storage/extSdCard).
Code:
[[email protected]]/sdcard# busybox df -k
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 426612 84 426528 0% /dev
tmpfs 426612 0 426612 0% /mnt/asec
tmpfs 426612 0 426612 0% /mnt/obb
/dev/block/mmcblk0p3 20144 8372 11772 42% /efs
/dev/block/mmcblk0p9 1548144 863612 684532 56% /system
/dev/block/mmcblk0p8 1007896 17280 990616 2% /cache
/dev/block/mmcblk0p12
11901576 8123632 3777944 68% /data
/dev/fuse 11799176 8123632 3675544 69% /storage/sdcard0
/dev/block/vold/179:17
15613952 14060896 1553056 90% /storage/extSdCard
I'm using an S3 with rooted stock firmware and stock kernel and I can navigate everywhere without incidents.
The only question that now comes to mind is if you somehow formatted the the /mnt/sdcard with ext2/3 filesystem ? Or is it FAT32 single partition ?
Click to expand...
Click to collapse

symlinks and /mnt/sdcard

What filesystem format is the internal memory that's presented as /mnt/sdcard? If it's EXT4 can you link from it to /mnt/external1 that's formatted FAT32?
The reason I ask is I have an RSS client that will only save its cache to /sdcard but I have more saved content from my old phone than will fit in the internal memory (by about 2x) and I was thinking of rooting to be able to do a symlink between the directory on /sdcard and the external card.

afidel said:
What filesystem format is the internal memory that's presented as /mnt/sdcard? If it's EXT4 can you link from it to /mnt/external1 that's formatted FAT32?
The reason I ask is I have an RSS client that will only save its cache to /sdcard but I have more saved content from my old phone than will fit in the internal memory (by about 2x) and I was thinking of rooting to be able to do a symlink between the directory on /sdcard and the external card.
Click to expand...
Click to collapse
This sounds interesting, I've got an app or two that default to sdcard even when I change their preferences to external1, would be a good way to make them use the right location without having to navigate to it each time.

Code:
rootfs / rootfs ro,relatime 0 0tmpfs /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
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/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=0,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/carriercust /carrier ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/tombstones /tombstones ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/pds /pds ext3 rw,nosuid,noexec,relatime,barrier=0,data=writeback 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:97 /mnt/external1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=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:97 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepag
e=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/external1/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Here's what it says on mine from the output of 'mount'

Well, it turns out symlinks don't work on the locally hosted /sdcard due to Fuse. However there IS a solution. I ended up using this tool to do a directory to directory mount. It's quite a hack, and when combined with the chroot Debian install I did on my phone makes my mount table a million lines long, but it does work =)

[Q] Cache partition seems to have disappeared

LG Optimus 2x (P990), Stock ROM, Android 2.3.4, rooted, ROM Manager and CWM Recovery installed.
My phone seemed to be getting rather slow so I decided to clear the cache and the Dalvik cache, from the recovery menu, to see if it would speed up the phone a little. Both processes completed without errors and I rebooted the phone.
The phone now works faster and is completely normal except for one thing. I find that I cannot now download any apps from Google Play as I get an error 498. If I look at a DF listing in a terminal there is no /cache listed. If I look at the results of 'mount' in the terminal I cannot see a cache partition either.
I have tried clearing the cache 3 times now with no success. I have also tried Cache Fixer but that gives errors if I try to move the cache 'Cache has NOT been moved'. I assume that may be because there isn't a cache partition now. I also tried restoring the cache using a partial restore from a nandroid backup which completed successfully but hasn't cured the problem - I still don't seem to have a cache.
EDIT: I've just had a look at the partition using fdisk and this is what I see:
Disk /dev/block/mmcblk0p2: 4 heads, 16 sectors, 2048 cylinders
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 00 0 0 0 0 0 0 0 0 00
2 00 0 0 0 0 0 0 0 0 00
3 00 0 0 0 0 0 0 0 0 00
4 00 0 0 0 0 0 0 0 0 00
Doesn't look good!
FURTHER EDIT: That bit about fdisk above is wrong. I thought that I was looking at a device but it was a partition.
Using fdisk on the proper device I get:
Disk /dev/block/mmcblk0: 7996 MB, 7996440576 bytes
1 heads, 16 sectors/track, 976128 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 129 44928 358400 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 44929 53120 65536 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 53121 53376 2048 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 53377 946432 7144448 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 53441 54464 8192 83 Linux
/dev/block/mmcblk0p6 54529 54848 2560 83 Linux
/dev/block/mmcblk0p7 54913 57472 20480 83 Linux
/dev/block/mmcblk0p8 57537 254144 1572864 83 Linux
/dev/block/mmcblk0p9 254209 946432 5537792 83 Linux
So the cache partition is still there (/dev/block/mmcblk0p2) but it doesn't appear in the mount list:
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
none /acct cgroup rw,relatime,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,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext3 ro,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,noatime,data=ordered 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,uid=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,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=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,noexec,noatime,uid=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:17 /mnt/extsecure/extasec vfat rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,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
/dev/block/dm-0 /mnt/asec/com.MultitaskingDrawer-2 vfat ro,dirsync,nosuid,nodev,noatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/org.englishheritage.app-2 vfat ro,dirsync,nosuid,nodev,noatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/uk.agiletech.forestcomm-2 vfat ro,dirsync,nosuid,nodev,noatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.mxdata.tube.Market-1 vfat ro,dirsync,nosuid,nodev,noatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
If I try and unmount, mount or remount the cache partition I get 'Invalid argument'.
I have run a file system check on that partition and it shows 'clean'. So, to summarise, the cache partition is there, the file system is clean but it isn't being mounted and I can't mount it either. I'm baffled.
I would be really grateful for some suggestions.

I've made a correction and added some extra information under 'FURTHER EDIT' so I've bumped it.

I have the same problem on motorola defy (jordan)
BarrySamuels said:
I've made a correction and added some extra information under 'FURTHER EDIT' so I've bumped it.
Click to expand...
Click to collapse
Did you manage to solve it?

KfirSolomon said:
Did you manage to solve it?
Click to expand...
Click to collapse
Sorry for the very late reply but I've only just seen your post.
Yes I did solve it. It was because the partition had been formatted ext4 which my current OS didn't recognise. It used ext3 so I reformatted it manually via a terminal and all was well.

[DISCUSSION] Sensation internal memory partition info

Hello Fellow Sensation Owners!
A couple of days ago someone asked about the Sensation's internal storage layout, which got me curious, as we get 1GB of storage to data partition, about 700MB for system, and where does all the rest go? boot is just a couple of megabytes, and firmware (combined), is 400MB.
When I searched google for it, I couldn't find any mention of the Sensation's partition layout, and barely found how to get it by myself. So here I am, creating this mention/guide (for future people who like me want to know what the partition layout is).
To get the layout and sizes, I used the df command in the shell, which gives a nice table with all (mounted) partitions, with information about them.
The results I got were:
Code:
Filesystem Size Used Free Blksize
/dev 271.7M 52K 271.6M 4096
/storage 271.7M 0K 271.7M 4096
/vendor/firmware/misc 199.8M 21.5M 178.3M 4096
/vendor/firmware/adsp 199.8M 5.7M 194.1M 4096
/mnt/secure 271.7M 0K 271.7M 4096
/mnt/asec 271.7M 0K 271.7M 4096
/mnt/obb 271.7M 0K 271.7M 4096
/mnt/fuse 271.7M 0K 271.7M 4096
/system 787.4M 388.8M 398.6M 4096
/data 1.1G 482.1M 693.9M 4096
/cache 118.1M 98M 20.1M 4096
/devlog 19.7M 14.8M 4.9M 4096
/storage/sdcard0 14.8G 13G 1.8G 32768
/mnt/secure/asec: Permission denied
/mnt/asec/com.quoord.tapatalkxda.activity-1 5M 3.2M 1.8M 4096
Note: I got this list on Cyanogenmod 10.1, a different ROM might bring
different results.
There are a few points of interest here:
1) There are 5 empty partitions, 271.7MB each.
2) Apps stored on the SD card are listed as individual partitions - in my case - XDA app (also tested on Sony Ericsson Live With Walkman - same result).
3) /mnt/secure/asec needs root access to be read, and after enabling, it seems to be mounted to the same space as the sdcard. this partition is actually the Android_secure foldier on the SD Card. This makes me suspect that some of the empty partitions are also mounts of the same partition from different directories inside it.
4) My suspition is most probably wrong, as the sum of all partition sizes amounts to about 4GB, which is what listed on the spec sheet.
5) /boot partition is not listed, which makes me believe some more are not actually mounted.
To know if there are double-mounted partitions, I checked the mount list on /proc/mounts by using this command:
Code:
[B]CAT /proc/mounts[/B]
I will post points of interest I found as It's quite long and mostly messy:
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
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
/dev/block/mmcblk0p17 /vendor/firmware/misc vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p19 /vendor/firmware/adsp vfat ro,relatime,fmask=0000,dmask=00
00,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=re
mount-ro 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 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
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p22 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p23 /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p24 /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p28 /devlog ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
We can see something interesting - /mnt/secure, /mnt/asec, /mnt/obb, /mnt/fuse, /storage and /dev are all mounted from tmpfs, which is not an adress on the mmc. I have no Idea what this means, but it explains all those partitions seen before - They are the same space (probably like /mnt/secure/asec - folders inside a bigger partition).
This thread is meant for me (and probably other curious users) to understand how the sensation is formatted.
Also, to keep a clean explanation of what each partition actually is (for begginers and to have it organized), here is a list of partitions with explanations about them (all those I know are included, some are basic knowledge, list will be updated).
/data - where your apps and basically all your data that is stored on the device is
/system - where system apps, frameworks, and the rest of the OS is (excluding kernel)
/boot (not listed) - kernel
/storage/sdcard - no need to be imaginative here - the SD card
/mnt/secure/asec - the android_secure folder on sdcard
/cache - app cache - where temporary data is stored to speed up apps
What I'm trying to do here is to create a clear and comprehensive explanation of the Sensation's NAND layout, so anyone looking for it could find it. For non-devs it's of not much use, but nice to know. Also to keep a clear way to check it on other devices (had to dive to linux websites to find some stuff here).
Would be glad if someone more knowledgeable than I am would add/correct me here, to make this helpfull.
To your Enjoyment/feeding your interest.

astar26 said:
Hello Fellow Sensation Owners!
A couple of days ago someone asked about the Sensation's internal storage layout, which got me curious, as we get 1GB of storage to data partition, about 700MB for system, and where does all the rest go? boot is just a couple of megabytes, and firmware (combined), is 400MB.
When I searched google for it, I couldn't find any mention of the Sensation's partition layout, and barely found how to get it by myself. So here I am, creating this mention/guide (for future people who like me want to know what the partition layout is).
To get the layout and sizes, I used the df command in the shell, which gives a nice table with all (mounted) partitions, with information about them.
The results I got were:
Code:
Filesystem Size Used Free Blksize
/dev 271.7M 52K 271.6M 4096
/storage 271.7M 0K 271.7M 4096
/vendor/firmware/misc 199.8M 21.5M 178.3M 4096
/vendor/firmware/adsp 199.8M 5.7M 194.1M 4096
/mnt/secure 271.7M 0K 271.7M 4096
/mnt/asec 271.7M 0K 271.7M 4096
/mnt/obb 271.7M 0K 271.7M 4096
/mnt/fuse 271.7M 0K 271.7M 4096
/system 787.4M 388.8M 398.6M 4096
/data 1.1G 482.1M 693.9M 4096
/cache 118.1M 98M 20.1M 4096
/devlog 19.7M 14.8M 4.9M 4096
/storage/sdcard0 14.8G 13G 1.8G 32768
/mnt/secure/asec: Permission denied
/mnt/asec/com.quoord.tapatalkxda.activity-1 5M 3.2M 1.8M 4096
Note: I got this list on Cyanogenmod 10.1, a different ROM might bring
different results.
There are a few points of interest here:
1) There are 5 empty partitions, 271.7MB each.
2) Apps stored on the SD card are listed as individual partitions - in my case - XDA app (also tested on Sony Ericsson Live With Walkman - same result).
3) /mnt/secure/asec needs root access to be read, and after enabling, it seems to be mounted to the same space as the sdcard. this partition is actually the Android_secure foldier on the SD Card. This makes me suspect that some of the empty partitions are also mounts of the same partition from different directories inside it.
4) My suspition is most probably wrong, as the sum of all partition sizes amounts to about 4GB, which is what listed on the spec sheet.
5) /boot partition is not listed, which makes me believe some more are not actually mounted.
To know if there are double-mounted partitions, I checked the mount list on /proc/mounts by using this command:
Code:
[B]CAT /proc/mounts[/B]
I will post points of interest I found as It's quite long and mostly messy:
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
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
/dev/block/mmcblk0p17 /vendor/firmware/misc vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p19 /vendor/firmware/adsp vfat ro,relatime,fmask=0000,dmask=00
00,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=re
mount-ro 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 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
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p22 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p23 /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p24 /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p28 /devlog ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
We can see something interesting - /mnt/secure, /mnt/asec, /mnt/obb, /mnt/fuse, /storage and /dev are all mounted from tmpfs, which is not an adress on the mmc. I have no Idea what this means, but it explains all those partitions seen before - They are the same space (probably like /mnt/secure/asec - folders inside a bigger partition).
This thread is meant for me (and probably other curious users) to understand how the sensation is formatted.
Also, to keep a clean explanation of what each partition actually is (for begginers and to have it organized), here is a list of partitions with explanations about them (all those I know are included, some are basic knowledge, list will be updated).
/data - where your apps and basically all your data that is stored on the device is
/system - where system apps, frameworks, and the rest of the OS is (excluding kernel)
/boot (not listed) - kernel
/storage/sdcard - no need to be imaginative here - the SD card
/mnt/secure/asec - the android_secure folder on sdcard
/cache - app cache - where temporary data is stored to speed up apps
What I'm trying to do here is to create a clear and comprehensive explanation of the Sensation's NAND layout, so anyone looking for it could find it. For non-devs it's of not much use, but nice to know. Also to keep a clear way to check it on other devices (had to dive to linux websites to find some stuff here).
Would be glad if someone more knowledgeable than I am would add/correct me here, to make this helpfull.
To your Enjoyment/feeding your interest.
Click to expand...
Click to collapse
i have serious bootloops, ppl are saying my nand is faulted, how do i repair it, as what ever ruu or rom i install i end up with bootloop

dxbboy said:
i have serious bootloops, ppl are saying my nand is faulted, how do i repair it, as what ever ruu or rom i install i end up with bootloop
Click to expand...
Click to collapse
Nobody can repair Nand memory's, probably your entire motherboard needs to be replaced.

All the tmpfs filesystem mounts are temporary ones and are on ram..
Sent from my HTC Sensation using XDA Premium 4 mobile app

I remember the HTC Desire, you could actually change the partition sizes to however you see fit using thalmus HBOOT patcher. It's a shame nobody managed to do it on here as I use AOSP which hardly uses any internal memory

Filesystem Size Used Free Blksize
/dev 271.7M 52K 271.6M 4096
/storage 271.7M 0K 271.7M 4096
/vendor/firmware/misc 199.8M 21.5M 178.3M 4096
/vendor/firmware/adsp 199.8M 5.7M 194.1M 4096
/mnt/secure 271.7M 0K 271.7M 4096
/mnt/asec 271.7M 0K 271.7M 4096
/mnt/obb 271.7M 0K 271.7M 4096
/mnt/fuse 271.7M 0K 271.7M 4096
/system 787.4M 388.8M 398.6M 4096
/data 1.1G 482.1M 693.9M 4096
/cache 118.1M 98M 20.1M 4096
/devlog 19.7M 14.8M 4.9M 4096
/storage/sdcard0 14.8G 13G 1.8G 32768
/mnt/secure 271.7M 0K 271.7M 4096
/mnt/asec 271.7M 0K 271.7M 4096
/mnt/obb 271.7M 0K 271.7M 4096
/mnt/fuse 271.7M 0K 271.7M 4096
THIS IS ONLY ONE 271Ç7M AND IT IS SHARED BY secure, asec, obb, fuse.
I can not find /storage 271.7M 0K 271.7M 4096 in sensation. it is missing.
I sum up and find 3GB.
somhow still missing 0.8gb

sokomind said:
Filesystem Size Used Free Blksize
/dev 271.7M 52K 271.6M 4096
/storage 271.7M 0K 271.7M 4096
/vendor/firmware/misc 199.8M 21.5M 178.3M 4096
/vendor/firmware/adsp 199.8M 5.7M 194.1M 4096
/mnt/secure 271.7M 0K 271.7M 4096
/mnt/asec 271.7M 0K 271.7M 4096
/mnt/obb 271.7M 0K 271.7M 4096
/mnt/fuse 271.7M 0K 271.7M 4096
/system 787.4M 388.8M 398.6M 4096
/data 1.1G 482.1M 693.9M 4096
/cache 118.1M 98M 20.1M 4096
/devlog 19.7M 14.8M 4.9M 4096
/storage/sdcard0 14.8G 13G 1.8G 32768
/mnt/secure 271.7M 0K 271.7M 4096
/mnt/asec 271.7M 0K 271.7M 4096
/mnt/obb 271.7M 0K 271.7M 4096
/mnt/fuse 271.7M 0K 271.7M 4096
THIS IS ONLY ONE 271Ç7M AND IT IS SHARED BY secure, asec, obb, fuse.
I can not find /storage 271.7M 0K 271.7M 4096 in sensation. it is missing.
I sum up and find 3GB.
somhow still missing 0.8gb
Click to expand...
Click to collapse
MMC
Manufacturer: Samsung Electronics
Model: MLL00M
Size: 2416 MB
Manufacture Date: Jun 2011
SDIO
Manufacturer: Broadcom
Model: BCM4329
Whoever said this device is 4GB was drunk.

can you tell me please witch mmcblk is hboot?