Database Users

[REQUEST] Internal NAND partition setup

Can someone who has performed a temp root post the results of a "mount" and "busybox df -h"? I'd like to see how the internal NAND is partitioned. Thanks!

silow said:
Can someone who has performed a temp root post the results of a "mount" and "busybox df -h"? I'd like to see how the internal NAND is partitioned. Thanks!
Click to expand...
Click to collapse
I posted this in the rooting thread, but here it is again...
Code:
$ su
su
# mount
mount
rootfs / rootfs ro,relatime 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
/dev/block/mmcblk0p26 /system ext3 ro,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p27 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=o
rdered 0 0
/dev/block/mmcblk0p28 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=
ordered 0 0
/dev/block/mmcblk0p31 /devlog ext3 rw,nosuid,nodev,relatime,errors=continue,data
=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=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/dm-0 /mnt/asec/com.qualcomm.qx.neocore-1 vfat ro,dirsync,nosuid,nodev
,noexec,relatime,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/com.rovio.angrybirds-1 vfat ro,dirsync,nosuid,nodev,no
exec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/loop9 /system/bin ext2 rw,relatime,errors=continue 0 0
#
Code:
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 186.6M 0 186.6M 0% /dev
/dev/block/mmcblk0p26
391.4M 331.4M 59.9M 85% /system
/dev/block/mmcblk0p27
431.7M 259.3M 172.4M 60% /data
/dev/block/mmcblk0p28
142.2M 18.1M 124.1M 13% /cache
/dev/block/mmcblk0p31
19.9M 4.0M 15.8M 20% /devlog
tmpfs 186.6M 0 186.6M 0% /mnt/asec
tmpfs 8.0M 4.0K 8.0M 0% /app-cache
tmpfs 8.0M 4.0K 8.0M 0% /app-cache
/dev/block/vold/179:33
7.1G 5.7G 1.4G 80% /mnt/sdcard
/dev/block/vold/179:33
7.1G 5.7G 1.4G 80% /mnt/secure/asec
/dev/block/dm-0 7.1M 5.4M 1.7M 76% /mnt/asec/com.qualcomm.q
x.neocore-1
/dev/block/dm-1 16.2M 14.1M 2.1M 87% /mnt/asec/com.rovio.angr
ybirds-1
/dev/loop9 14.5M 10.2M 3.5M 74% /system/bin
#

[Q] [SOLVED] Original sdcard mount point

Hey everyone,
This is pretty embarrassing... I successfully ran the following:
Code:
mount -w -t vfat /dev/block/mmcblk0p12 /mnt/sdcard
But now I cannot revert back to the original mount point of "/sdcard"
I've even tried umount-ing with the force-flag and still no luck
I'd appreciate any help at all, thanks

It *might* revert when you reboot unless you overwrote something.
Why are you screwing with this anyways?

Thanks for the quick reply.
Rebooting didn't change it.
Edit: Below is fixed, no longer relevant
Except, now I'm noticing I have to root with SuperOneClick each time I reboot to get su access.
The only thing I did after running the mount command, was install BusyBox

Wait, what? Since when does Kindle Fire have an SD Card? I'm so confused

jasongw said:
Wait, what? Since when does Kindle Fire have an SD Card? I'm so confused
Click to expand...
Click to collapse
There's an "sdcard" partition. It's whats mounted when you attach your KF to your PC... But no, there's no removable SD Card

Not sure 100% what the correct command to remount the sdcard partition is so can't say much right now.
check under /proc/mounts and also under /proc/emmc (open them as a text file) and paste what it says.

Didn't see a /proc/emmc but here's what I found
Contents of /proc/mounts:
Code:
rootfs / rootfs ro,relatime 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,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
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/splash /dropbox ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/vold/179:12[B][COLOR="Red"] /mnt/sdcard[/COLOR][/B] 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:12 /mnt/secure/asec 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
tmpfs[B][COLOR="Red"] /mnt/sdcard/[/COLOR][/B].android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.angrymobgames.muffinknight3rdparty-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

I hope you can solve your problem,good luck

looks like you need to mount /dev/block/vold/179:12 so rerun the command you were doing with that instead.

I installed Astro File Manager, through which I can view the sdcard partition's contents in "/sdcard" as well as "/mnt/sdcard"
I only seem to have issues viewing contents of location "/sdcard" in adb shell.
At this point I'm not too terribly concerned about it. Maybe I'm making a deal out of nothing...
I do appreciate your help though.
And if anyone knows the exact solution, then please speak up
EDIT:
Returns nothing:
Code:
ls /sdcard
Returns contents:
Code:
cd /sdcard
ls
I guess nothing was ever wrong after all.. Now I feel extra-dumb

Need help with flashing device. Thanx!

First I want to thank all the devoted developers here, who all do a great job.
I am a proud owner of a GT-S5360 for 2 days now, and as I am a Sysadmin (although not into linux that much) I had to try to flash my device, of coursse. I am new to this, but I already had the honour to flash a Galaxy Tab at work once wich worked just fine.
But not quite with my GT-S5360.
Here is what I did:
I tried to flash the Jellyblast v3 according to this thread:
http://forum.xda-developers.com/showthread.php?t=1679563
Of course i rooted the divice:
http://www.galaxy4gaming.in/2012/07/root-unroot-samsung-galaxy-y.html
While in CWM trying to wipe data, clear cache and dalvik cache, I got error messages like these:
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
as stated already here:
http://forum.xda-developers.com/showthread.php?t=1150917
Thus I upgraded my linux skills and did some adb shell work and installed busybox on my device.
As the above thread is for the HTC Desire I'm now not sure what to make of my results. I don't think its the eMMC chip, thats faulty.
Code:
dmesg | grep mmc0
gave me
Code:
# dmesg | grep mmc0
dmesg | grep mmc0
<6>[ 2.058532] mmc0: SDHCI controller on [bcm_sdhc.1] using ADMA
<4>[ 2.063812] mmc0: mmc_rescan start
<4>[ 2.063842] mmc0: mmc_rescan rescann is out
<4>[ 22.212402] mmc0: mmc_rescan start
<6>[ 22.308227] mmc0: new high speed SDIO card at address 0001
<4>[ 22.815917] mmc0: mmc_rescan rescann is out
I googled the results, but with no result, at least none that i could understand.
It semms that the SD Card is working fine, as I can put all the .zip files and other stuff onto it, but the /cache and /data folders are inaccessible.
Is it possible, that the system is somehow secured?
I really did some deep reading in the forum but now I'm kinda stuck.
If anyone can help me, it would be really, really appreciated.
kind regards
Frank
here are some more adb shell results.
Code:
mount
rootfs / rootfs ro,relatime 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,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=cp
437 0 0
/dev/stl10 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,gid/uid/rwx,iocharset=cp
437 0 0
/dev/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/dev/stl11 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=cp437 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=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:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
mount
rootfs / rootfs ro,relatime 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,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=cp
437 0 0
/dev/stl10 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,gid/uid/rwx,iocharset=cp
437 0 0
/dev/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/dev/stl11 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=cp437 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=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:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
# df
df
Filesystem Size Used Free Blksize
/dev 144M 52K 144M 4096
/mnt/asec 144M 0K 144M 4096
/mnt/obb 144M 0K 144M 4096
/system 221M 214M 7M 4096
/cache 35M 20K 35M 4096
/data 189M 44M 145M 4096
/mnt/sdcard 1G 224M 1G 32768
/mnt/secure/asec 1G 224M 1G 32768

which cwm u using?
try to mount system/data

CALIBAN666 said:
which cwm u using?
try to mount system/data
Click to expand...
Click to collapse
I downloaded it via the link in this thrad, as told...
http://forum.xda-developers.com/showpost.php?p=26703127&postcount=8
....
error mounting /data
do not have option mount /system

frank_77 said:
I downloaded it via the link in this thrad, as told...
http://forum.xda-developers.com/showpost.php?p=26703127&postcount=8
....
error mounting /data
do not have option mount /system
Click to expand...
Click to collapse
use the temporary CWM by madteam
or get a permanent CWM via kernels like savie, merruk, white

deathnotice01 said:
use the temporary CWM by madteam
or get a permanent CWM via kernels like savie, merruk, white
Click to expand...
Click to collapse
thank you for your reply deathnotice and caliban.
it seems to work
so it was the CWM.
many thanks for your help.
kind regards
Frank

SWAP on /dev/block/stl6 ???

I used swap on /dev/block/mmcbl0p2 but I flashed Merruk lernel 2.5 (overclocked) I found that /dev/block/stl6 is being used as swap instead of mmcblk0p2......
$ mount | grep j4fs
/dev/stl6 /mnt/.lfs j4fs rw,relatime 0 0
$ free
total used free shared buffers
Mem: 296216 290604 5612 0 21052
Swap: 153596 3488 150108
Total: 449812 294092 155720
$
Click to expand...
Click to collapse
flashed DDLK2 with ODIN but it's all the same.... IS IT NORMAL???

See Here from Galaxy Tab
/data/local/tmp/busybox mount -o
rw,remount /system > /data/local/tmp/
output 2>&1
export TEMPRANDOM=34850
export PS1=END:$TEMPRANDOM;cat /
data/local/tmp/output
mount: permission denied (are you root?)
END:34850export PS1=""
/data/local/tmp/busybox mount > /data/
local/tmp/output 2>&1
export TEMPRANDOM=76781
export PS1=END:$TEMPRANDOM;cat /
data/local/tmp/output
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs
(rw,relatime,mode=755)
devpts on /dev/pts type devpts
(rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup
(rw,relatime,cpuacct)
/dev/block/stl6 on /mnt/.lfs type j4fs
(rw,relatime)
tmpfs on /mnt/asec type tmpfs
(rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs
(rw,relatime,mode=755,gid=1000)
tmpfs on /app-cache type tmpfs
(rw,relatime,size=12288k)
none on /dev/cpuctl type cgroup
(rw,relatime,cpu)
/dev/block/stl9 on /system type rfs
(ro,relatime,vfat,log_off,check=no,gid/
uid/rwx,iocharset=utf8)
/dev/block/mmcblk0p2 on /data type rfs
(rw,nosuid,nodev,relatime,vfat,llw,check=
no,gid/uid/rwx,iocharset=utf8)
/dev/block/mmcblk0p3 on /preinstall type
rfs
(rw,nosuid,nodev,relatime,vfat,llw,check=
no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl10 on /dbdata type rfs
(rw,nosuid,nodev,relatime,vfat,llw,check=
no,gid/uid/rwx,iocharset=utf8)
/dev/block/mmcblk0p1 on /cache type rfs
(rw,nosuid,nodev,relatime,vfat,llw,check=
no,gid/uid/rwx,iocharset=utf8)
/dev/block/vold/179:9 on /mnt/sdcard
type 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)
/dev/block/vold/179:9 on /mnt/secure/
asec type 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)
tmpfs on /mnt/sdcard/.android_secure
type tmpfs
(ro,relatime,size=0k,mode=000)
Click to expand...
Click to collapse

[Q] All of a sudden sdcard0 is read-only

Hello, since yesterday I can't write anything om my external memory-card (sdcard0) anymore. No idea what caused this
CM: nightly 24.11.2014 (happens also on older builds until 16.11.)
Mounts (recorded with the mount command via terminal):
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,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,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data_root ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/dm-0 /mnt/asec/com.quoord.tapatalkHD-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/ginlemon.flowerpro-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/vold/179:27 /mnt/media_rw/sdcard0 ext4 ro,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,data=ordered 0 0
/dev/block/vold/179:27 /mnt/secure/asec ext4 ro,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,data=ordered 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-2 /mnt/asec/com.sonny.lpi.frost2-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0

Hmmm - I hope I did provide enough information ...
I'm wondering whether it is possible to unmount /mnt/media_rw/sdcard0 in a terminal and mount it again with read-write enabled?
Not sure how to proceed and a bit anxious about it as well since I don't know enough about Android despite working with Linux since 20 years

I guess your filesystem is corrupted. Please post dmesg logs.

Here's the dmesg.log -> https://gist.github.com/wimstefan/7af22e19b6ff408a7c22
Thanks for looking into it!
If needed I also can provide the logcat I took this afternoon ...

yep ur filesystem is corrupted. The weird thing is, that errors should be fixed on each boot.
you could reboot to recovery and run "e2fsck -fy /dev/block/platform/msm_sdcc.1/by-name/system" from a shell.

m11kkaa said:
yep ur filesystem is corrupted. The weird thing is, that errors should be fixed on each boot.
you could reboot to recovery and run "e2fsck -fy /dev/block/platform/msm_sdcc.1/by-name/system" from a shell.
Click to expand...
Click to collapse
Oh I see
Well running the command above seems not to do that much:
Code:
# e2fsck -fy /dev/block/platform/msm_sdcc.1/by-name/system
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/msm_sdcc.1/by-name/system: 1944/32768 files (0.5% non-contiguous), 106443/131072 blocks
Same happens with system1 ... but that's not where the errors in dmesg are listed or am I completely wrong now? I see some fs errors passing dmesg regarding device mmcblk0p27 which is /dev/block/platform/msm_sdcc.1/by-name/storage. Running the e2fsck command on that device was a completely different story! A lot of errors and corrections ... the filesystem was modified at the end and after a reboot it is mounted writable again!
So THANK YOU VERY MUCH for pushing me in the right direction !!! :highfive: :victory:
Hopefully everything is alright again and I can continue to enjoy my MI2S

yeah sorry I meant storage. stupid copy&paste errors