My S7 failed to mount some of my SDCards for some reason. I am not sure if it is because I have a corrupted file system, but I used the fsck_msdos from CM7 Nexus One and it seems to work fine now.
fsck_msdos was seg faulting every time it tried to scan my 8GB SDHC card. I tried a different 8GB card, and it produced the same result.
I just pushed the newer fsck_msdos to /system/bin, and experienced no more issues after that.
It might be related to the patch on fsck_msdos fixed in Gingerbread:
https://android.googlesource.com/platform/external/fsck_msdos/+/gingerbread-mr4-release
Related
First off thanks for all the wonderfull help. I finally managed to flash jf1.51 and get the phone running again. Kinda hard 2 do without a sdcard and when fastboot didnt work!!!!!
Now that the phone is running again I STILL have no sdcard slot!! The phone just says...
Removed SD card
The SD has been removed. Insert a new SD card to increase your device
No one has had this problem....
********Original********
We will start with what happened up till that point.
I originally was using haykuro hero with apps2sd (Original Tmobile 1gb sdcard) It worked but slow and crashing on just about everything.
Did the multiple speedups / optimizations for hero.
Switched too Superheros beta v1 hero rom. (No problems other than slow/app crashing)
Ordered a new Transcend 4gb class 6 sdcard.
Waited until I received the new card before switching too Superheros beta v2.
Setup the partitions on the new 4gb just like I had done with the 1gb (and the 1gb had no problems except 4 being slow)
Updated to superheros beta v2 rom. Everything went fine, had like 9mb free (I used the full Rom) After the phone was setup and rom was booted. Used the app2sd app built into the rom. Moved the apps/cache 2 sdcard. Rebooted phone and had a bootloop (kept replaying the htc boot animation)
So remembering reading when hero first came out. I assumed that some of the files for hero did not transfer too the sdcard (Remember when people had problems with app_s.zip)
So I go into the bootloader mode (home + power) to reflash the rom and receive this error (Now during this time I still have the 4gb in)
Installing from sdcard...
Finding update package...
E:Can't mount /dev/black/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
--------------------------------
I have tried 4 different sdcards with 3 different sdcard readers and every one of them has this error. I have tried wiping but didnt change anything.
It is like the phone cannot see any sdcard anymore. I can adb but I dont know anything that could help.
Thanks
-Matt
**Edit**
Have tried partitioning to only fat16 and fat32 on sdcards.
Have tried fastboot with dreaimg.nbh and still does not detect sdcard.
Have tried putting app_s.zip into ext2 partition.
Have tried Downloading different roms and rom types.
Have tried "mount /sdcard" *error mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory*
Have tried Pushing app and app_s to /data from update.zip
Have tried copying app and app_s to /mmcblk0p2 from a linux os "Phone will not detect either partitions" (/mmcblk0p1 is fat32. /mmcblk0p2 is ext2)
Have tried editing mountd.conf and init.rc
Everytime I try and apply update.zip I get these weird files on the sdcard. (http://www.pcxpressrepair.com/android/qxdm_20080904_032341_1.dm , http://www.pcxpressrepair.com/android/qxdm_20080904_032607_1.dm There are just 2 that I uploaded.
Also here is a Logcat of when the phone is trying to boot (bootloop)
http://www.pcxpressrepair.com/android/logcat1.txt
During bootloop here are the mounts
--------------------------------------------
Filesystem Size Used Available Use% Mounted on
tmpfs 48.2M 0 48.2M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 90.0M 76.7M 13.3M 85% /system
/dev/block/mtdblock5 89.8M 14.7M 75.1M 16% /data
/dev/block/mtdblock4 30.0M 1.1M 28.9M 4% /cache
I have had similar problems but it was because of a bad download. Or I disconnected the phone to quickly from the USB before selecting remove.
Wrong forum. Mods, lock this thread pronto!
Also I received a letter from tmobile saying that they are going to drop me because of roaming too much. I would be nice to get this worthless phone running again. I have until July 7th 2 switch carriers. Because my G1 is basically a paperweight now I was thinking of getting the HTC lancaster with AT&T but it will not be on the market in time.
By the way the phone is acting and no one else having this problem. I am lead 2 believe that this is a hardware issue with the G1. But, every time I try and flash the rom I get that weird file on my fat32 partition. So I would assume that the phone can still write to the sdcard, even though it cannot mount it. So don’t know if it is hardware or not. But, tonight I will disassemble the phone. (Because I’m not getting 2 much help here)
Also if apps2sd or cache failed when the rom was running for a moment what would be a way to restore it back (If the phone worked and no apps2sd is still fine 4 me!). Every time I try and link back 2 the phone it cannot find the directories that are on the sdcard (obvious cuz the sdcard is not mounted) I had this problem before but, the sdcard was mountable so there was no problem.
Would there be a configuration file that I can pull, modify, and then push back with the app2sd/cache info on it. I am moments away from pushing the entire update.zip 2 the phone. I am running out of options on what 2 do or how 2 fix.
-Matt
phone wont even turn on now.
Will it blend? Post results.
As soon as I get a blender
Same Prob
I'm having the exact same problem, has anyone found a solution yet?
Same issue here! Reformatted, wiped the works and nothing. And I have searched everywhere and like you it seems hardly anyone has this same issue. If I can't get it resolved soon I am getting the phone replaced.
I have got the same problem on my vodafone HTC Magic. Can boot to spl, fastboot to recovery rom but cannot mount SD Cards. Anyone found a solution?
Hi .
Main issue which is shared I encountered with 0.5 once installed is that /cache was read only due to it behing a sub directory of / . ie I installed from archos 2.1.X here 2.1.4 where mmblk0p3 is swap and not ext3 thus mount of mmblk0p3 as ext3 to /cache was not working.
I commented:
mount ext3 /dev/block/mmcblk0p3 /cache noatime nosuid noexec
and added:
mount ext4 /data/cache /cache bind noatime nosuid noexec
instead. It fixes download/install from android market once it was automatically updated by the UpdateMarket process. and probably other issues as well.
Otherwise:
- install seemed to work with easy installer until the send the uruk install file via usb where the usb was seen by my linux station but nothing to mount was available. Using the sdcard in the station showed up that no partition table existed and that there was a "label" issue. This was fixed by applying the partition and formating scheme by hand (I uncompressed the uruk initramfs.cpio.gs and used the commands from the /init dedicated to that and they worked ).
I guessed something was wrong with the partitionning and fs as this step was near instantaneous for a 16G sdcard class 6. After parititionning and formating by hand and redoing the partitioning in easy installer it indeed took a few moments and afterwards the mmcblk2p1 was indeed available via usb for the last "copy installation files" steps.
- one question : I used UrukDroid-GoogleMarket_1.0.tgz should I have used gAppsInstaller - Froyo for archos instead ? Ie I see nowhere google maps in the market. While it as available in stock archos firmware with the external google apps installer. I will attempt the upgrade to 0.6RC2 of uruk in a few minutes. I wonder if it could help in this regards.
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+
I've given up on reformatting the internal memory as EXT4 (my last post). However now, I want to mount an external SD card that is EXT4 (or any file format that has UNIX permissions). I can't get my device to mount the card, it says the filesystem is unsupported. Now, that's bull**** since Android has built in support for EXT. After searching threads here on XDA and Google, and even purchasing EzyMount as recommended, I can't get it to mount. I've tried BusyBox and mount commands (as root), with various errors such as "mount operation not supported on transport endpoint". I'm at my wit's end by now, trying to get some filesystem which has support for symlinks and UNIX permissions... any ideas?
kcattakcaz said:
I've given up on reformatting the internal memory as EXT4 (my last post). However now, I want to mount an external SD card that is EXT4 (or any file format that has UNIX permissions). I can't get my device to mount the card, it says the filesystem is unsupported. Now, that's bull**** since Android has built in support for EXT. After searching threads here on XDA and Google, and even purchasing EzyMount as recommended, I can't get it to mount. I've tried BusyBox and mount commands (as root), with various errors such as "mount operation not supported on transport endpoint". I'm at my wit's end by now, trying to get some filesystem which has support for symlinks and UNIX permissions... any ideas?
Click to expand...
Click to collapse
you fully rooted with custom kernel or only with rdlv etc?
First you gotta figure out how to mount this damn thing, gotta be possible.
Then you need to get this done on bootup, either in init.rc or init.d or smth.
You probably just use wrong commands? But I could be wrong, didnt try that yet but would also be interested. Having the file permissions also on SD would be nice, but it could cause trouble with mtp maybe?
zroice said:
you fully rooted with custom kernel or only with rdlv etc?
First you gotta figure out how to mount this damn thing, gotta be possible.
Then you need to get this done on bootup, either in init.rc or init.d or smth.
You probably just use wrong commands? But I could be wrong, didnt try that yet but would also be interested. Having the file permissions also on SD would be nice, but it could cause trouble with mtp maybe?
Click to expand...
Click to collapse
I am rooted, but stock ROM and kernel. MTP is for connecting to a computer? If it is, I don't need that. I have tried
mount -rw -t ext4 /dev/block/mmcblk1p1 /storage/extStorageCard
and variants switching the flags and options.
Interesting... I just typed that command in to make sure I didn't make any typos.... and my phone crashed and rebooted. I typed it again to see if it would cause another crash and it appears to have mounted the card! Whwn I type "df" at the prompt it now shows a 28.6 GB filesystem at that location, which has to be my sd card.
Why, how, I don't know. It works, it's all I can say.
Like the title above; I was wondering how come I get the 64GB SD card I formatted with Linux EXT2 to even appear in the stock camera app and some specific apps in Jelly Beans ROM just fine, but not 100% on Kit Kat OS (no file size indicator in Storage tab in the setting panel). However, I can still access the files on it via ES File Explorer. Still not satisfactory because the vold in Kit Kat is so stubborn (hence the battery life also gets penalized).
The content of the mounter script (ext2_sd.sh file) I wrote from trials and errors (which works PERFECTLY in Jelly Beans - I use SManager to run this script):
e2fsck /dev/block/mmcblk1p1
mount -o rw -t ext2 /dev/block/mmcblk1p1 /storage/sdcard1
chown root:sdcard_rw /storage/sdcard1
busybox chmod -R 777 /storage/sdcard1
vold
Now, this is probably not the best but it worked for me on Jelly Beans, due to the frustration of the stupid FAT32 4 GB file limitations, and exFAT being a no-go.
I want some opinions on this and why Kit Kat still behave funnily even with the SD card mount fixes already applied (CyanogenMod 11 being the main subject of this discussion). And, of course you can also try this on Lollipop and report back. The only requirements are root, busybox and of course the script manager you usually use.