Database Users

[Q] How to use ext3-sdcard?

Hi all,
i formatted my sdcard with ext3, but CM7 doesn't mount it. I changed the 'vfat' in the fstab to 'ext3', but it still dosn't mount the card. I can manually mount it with 'mount /dev/block/mmcblk0p1 /sdcard', but then I can only access /sdcard via Terminal Emulator or the adb shell. Root explorer says that it is not mounted although it is mounted. Does anybody know how to fix that?

Mister Ypsilon said:
Hi all,
i formatted my sdcard with ext3, but CM7 doesn't mount it. I changed the 'vfat' in the fstab to 'ext3', but it still dosn't mount the card. I can manually mount it with 'mount /dev/block/mmcblk0p1 /sdcard', but then I can only access /sdcard via Terminal Emulator or the adb shell. Root explorer says that it is not mounted although it is mounted. Does anybody know how to fix that?
Click to expand...
Click to collapse
Hey dude, I feel ya. I wanted to ext3 all the way, but google thought Android users would rather use fat for their sdcards so we're bound to trying to work around it. You might want to look at your sdcard permissions, check that you have "X" permissions for user, group and other, or just go crazy and do "chmod -R 777 /sdcard".
You could look into what this guy did: http://android.modaco.com/topic/308568-how-can-i-bind-mount-eg-systemsdxxx-sdcardxxx/#entry1511967
but I backed out mainly because it looks too much like more trouble than its worth.
Good luck!

[Q] Nook Simple Touch Bricked?

Hello. While I was copying the .pgm files out of the boot directory, (with hopes of editing and replacing) I accidentally rebooted my NT. The boot partition was mounted at via :
Code:
mount -o rw /dev/block/mmcblk0p1 /sdcard/mnt
My NT now shows no signs of life except for the power LED glowing while charging. It still shows the screen of the app where the reboot was initiated from. I have tried to boot it using a SD card with a fresh touchnooter image, but there has been no change in my NT. Could anyone suggest what I should do next?
Kind regards.

I will try out n2T-Recover_0.2.img . TY for the good info and tools. Time for sleep.

Worked like a charm

Format & Use MicroSD W/ ext4?

Hey guys, for a couple reasons I'd like to be able to format my micro SD card with the ext4 file system.
I can format my card using a computer running Ubuntu, but the card will not mount.
I'm running CM10 on my P3113.
Is there any simple way to do this?
It seems like it'd be best to use vold to mount the sdcard, but that doesn't support ext4 I guess?
Just wondering...

Ext4 support has to come from kernel.

???
Literally every other mounted filesystem on the CM10 ROM I use is ext4...
I'm gonna try mounting via an init.d script.
We'll see if that works...

Solved this one, it was easier than I expected.
You need to format the card, and then mount it at boot via a script.
CM9 and 10 support init.d scripts, so I have a script file at /system/etc/init.d/95sdcardext4
with this contents:
Code:
#!/system/xbin/sh
# Mount SD Card Ext4 Script
mount -rw -t ext4 /dev/block/mmcblk1p1 /storage/sdcard1
This runs very early in the boot up process, and ext4 partitions mount basically instantly, so everything is working as expected so far.
More tests need to be done, but I'm fairly certain I can package this up in a flashable ZIP package.

Brilliant !
ext4 is anyways far better than fat32 except Windows/Mac compatibility.
Awaiting your stable work

It will work on a s5670 running cm10 jb4.1.1?
I just have to create a file with that lines and put it in /system/etc/init.d/95sdcardext4 ?????????
I cannot get link2sd to mount the ext4 partition.
Thx
DivinityCycle said:
Solved this one, it was easier than I expected.
You need to format the card, and then mount it at boot via a script.
CM9 and 10 support init.d scripts, so I have a script file at /system/etc/init.d/95sdcardext4
with this contents:
Code:
#!/system/xbin/sh
# Mount SD Card Ext4 Script
mount -rw -t ext4 /dev/block/mmcblk1p1 /storage/sdcard1
This runs very early in the boot up process, and ext4 partitions mount basically instantly, so everything is working as expected so far.
More tests need to be done, but I'm fairly certain I can package this up in a flashable ZIP package.
Click to expand...
Click to collapse

Sorry about that, I don't have one of these anymore. I had a P3113, but switched to a T869, which is a very similar device but has 4G and some different stuff going on under the hood.
My brief ext4 experiment was honestly not that big of a deal. I ended up going back to FAT32 because the benefits didn't outweigh the annoyances.
The biggest issue I had was I couldn't figure out how to make the file system permissions behave in the same highly permissive way that FAT32 does. I ran into several force closes and other things that resulted from apps not being to read / write stuff on the card that they should have been able to. I know you can CHMOD stuff, and a boot script could chmod everything on the card, but that seems like a bandaid.
Maybe there's a way to make the permissions behave a specific way via the mount parameters? I didn't investigate deeply enough because my life got busy, and during the changeover to the new tab it was just easier to go back to FAT32. Also my new tab has 16GB of internal storage, so I've been much less stressed about storage.

Ok folks.. ...reviving an ancient thread....from good ol days when it 'KISS' was common for Android.
What about android 7+ onward . All this stuff is deprecated. My 128gb is cut into 3 Ext4's.
(I need a journaled FS - that story a lil later )
I can mount easily but problem is apps cant see it and its all got to do with mount space concept.
I am Su'ed via Magisk
Can someone post a step by step guide to mount ext4 on 7+

[Q] system partition corrupted (can't umount)

Just now after a reboot, I found that Google Play Service stops working. It happened quiet a few times before, so I decided to do what I always do - remove the Google Play Service and flash it again.
So I rebooted into recovery, removed gapps backup script under /system/addon.d using Aromafm, and tried to flash the latest CM nightly - and the flash failed with status 7.
Then I found that I can no longer boot into system, but I still have access to boot loader (fastboot) and recovery. So I begin to check what's wrong with my /system partition and found that once it's mounted, I can not umount it. At first I thought it's a file system problem so I tried to fix it with e2fsck - but I can't umount it so e2fsck won't work!
So I rebooted my phone again, executed e2fsck -cfy /dev/block/platform/msm_sdcc.1/by-name/system but it didn't show any error - it's like the file system is file but I just can't umount it for some reason I can not understand (If I try umount it, I'll get "invalid arguments")
Lucky enough there's nothing wrong with the secondary system partition (I have TDB enabled before and always been using system1) so I managed to flash the latest nightly to system2 and get my phone booted, but I still can't get access to system1
Anyone, help :crying:

Update
This is becoming weirder and weirder...
After a few days of usage, I did a lot modification to 2nd /system partition, I noticed that sometimes I got boot loop - if I connect the phone to my laptop and use adb logcat I can see the logcat loops forever. Using adb reboot can make my phone reboot and get into Android system.
So I powered off my phone, booted to recovery, and as I expected, the same thing happens to 2nd /system partition - it can be mounted with no problem, but I can not unmount it (except for power off the phone, of course)
I thought maybe there's something wrong with that partition, maybe bad block or whatever, so I copied the entire 2nd /system to 1st /system partition using dd - Then the 1st /system partition can't be unmounted as well.
Now I'm f_cked, so I decided to format 1st /system partition once again and start fresh, after format I went and try mount then unmount 2nd /system partition - now it can be successfully unmounted. I was shocked at the time that I thought something went wrong I acturally formatted both partitions, but turns out all data in 2nd /system partition is fine and the "can't unmount" issue is gone.
Now boot loop doesn't happen anymore, but I'm too afraid to do any more modifications to /system partition, therefore I have skipped a few nightly updates. I won't risk brick my phone until I can get my hands on a new one (It's just too hard to find a phone that has a great performance and not that freaking huge! Seriously, I would buy another Mi 2S if they still sell it.)
Does anyone know what could possibly happening here... I'm so confused...

/system stuck on VFAT file system

So I've been trying to do a lot of things and I must have messed up something along the way. I followed a video that tells you to change /system to vfat and then back to ext4 to fix it but now I cannot change it back to ext4 and I can't boot flash my phone since roms need system to be ext4.