Database Info

[Q] Tiamat 1.4.0, 3g/wifi, sdcard doesnt mount on boot.

i tried hijacking the other 1.4.0 thread but got ignored and didnt want to keep a something stale that was off-topic alive.
so, i have flashed 1.4.0, verified that the kernel is in fact running. i wiped before the update to get rid of other issues i was having with some apps.
now, with 1.4.0 running, it appears that the external sdcard is not mounting while the system is booted. in recovery, it shows up as it should with all of the files. i have an /mnt/sdcard/sdcard2 and i have an an external directory under /sdcard
ive tried with card in before boot and after. i can say that dmesg is in fact seeing the card being removed and pushed in; however it doesnt seem to 'automount' from vold.fstab properly, or something else is jacked.
that being said, i dont seem to have a /devices which is where these things are suppose to be mounting from, is it not?
/sys/devices/platform/sdhci-tegra.2/mmc_host/mmc1
should i add the prefix /sys to both the usbOTG and sdcard to fix this?
or is there something else that is missing? presumably i could also create a symbolic link /devices -> /sys/devices, or does the kernel chroot to /sys at some point so none of this is needed, and i am having a different problem?
thanks for the help,
~marion

ya i noticed mine sd card is doing the same thing wont mount but works in recovery and i know it did work bc i had sdcard access through root explorer on v1.4.0 and now it does not work like it died over night

mine has not worked since moving to 1.4.0.
i originally went from 1.3.2 to 1.4.0 but the update didnt work well through the clockworkmod steps was having problems mounting e: so i went back to 1.3.1 then -> 1.4.0 [after wiping cache/data, and readding an sdcard2] using kernelmanager.
the update worked well, i rebooted to recovery and say that i could mount e:, and files where on the sdcard as expected. when booting to OS external has no files and sdcard2 has no files. also using connectbot for a shell, df shows nothing mounted.
is this because vold.fstab isnt mounting from /sys as described in my earlier post?

still unable to mount external sdcard while xoom is boote in 1.4.0.
Am able to pc-mount, and back up to it via recovery... no one else is seeing anything similar?

In 1.4.0 the sdcard should be in /sdcard/external not sdcard2. The card has to be in before turning it on. They are not hot-swappable.
Sent from my Xoom

Guys this is why Mass Storage has been removed in 1.4.1. Here's basically what's going on. When the device boots, the Sdcard is mounted to data/media/external which is the same as Sdcard/external. The Sdcard mounts before data/media is "fused" to create a virtual internal Sdcard. This is the only reason why you can actually see the external Sdcard inside the internal Sdcard. And this is why gallery can see the external Sdcard. However, in order for the Sdcard to mount as mass storage, Vold.fstab MUST mount the Sdcard at mnt/Sdcard so that Vold service can see it. But, this is the same mount point the internal storage is "fused" to. So when mass storage is done, it attempts to remount the sdcard where it was previously mounted, sdcard/external. But because of the way "fuse" works, it does not let any devices be mounted inside it. This is why I need source to do it right. I can then tell Vold to look some other place for the sdcard mount point. Until then, it's borked and that's why I pulled it.

@bwcorvus: in my first post i said that it wasnt showing up in sdcard2 or external... maybe i wasnt clear enough but its there.
@bigrush: thats exactly what i was seeing, and what i was presuming. i figured the lack of response meant either people werent seeing the issue or noticing it.
that being said... dmesg shows the device showing up if inserted/removed while running. but its showing out of /sys/devices... instead of /devices... changing that in vold.fstab didnt do anything for me as im not sure i have a great grasp on the boot sequence.
~marion

That's odd, mine mounts to external with no issue with 1.4.0

[Q] About my Sdcard and External Sdcard (Removable Disk?)

Firstly, I am running Valhalla Final 2.3.6 ("Happy Holidays") and using the KI3 Kernel. I'm almost Positive my issue is not related to the ROM or kernel.
A couple of weeks ago I was attempting to get Link2SD app to work properly (it never has but I kept trying every few weeks thinking Link2SD app would get updated and it would work) on my EXTERNAL Sdcard's 2nd EXT4 patition. I ended up with a soft bricked phone.
And my Sdcard appeared to be wiped. I restored the backup of my EXTERNAL Sdcard to my Sdcard (Internal).
Prior to restoring the backup of my EXTERNAL to Internal I used to have a "Long" menu list in Recovery. That List included options like
external
external/sd
tapatalk
tapatalk/download
They aren't listed anymore.
This is what my Menu looks like in Recovery (CWM Voodoo Lagfix Recovery v3.0.2.8.) now;
Android/
CameraZOOM/
DCMI/
LOST.DIR/
Removable Disk/ Removable Disk/ Was NEVER an option for me.
SpeedSoftware/
SupertaskManager/
TunnyBrowser/
Voodoo/
albumthumbs/
bluetooth/
bugreports/
clockworkmod/
data/
gameloft/
handcent/iTagCache/
launcherpro_backup/
music/
openfeint/
tapatalkxdapre_download/
and then my ROMS and Kernels Boot Anamation ect.
My Sdcard NEVER looked like this before my restoring of EXTERNAL to internal.
HOW do I fix this?? I've been searching for 2 weeks and haven't found anyone with a problem like this or solution... my phone works properly but I know this is not the way it should be.. I NEVER had a Removable Disk option before.
Any Help/Insight on this issue will be Greatly Appreciated and Thanked.

Jerry D said:
Firstly, I am running Valhalla Final 2.3.6 ("Happy Holidays") and using the KI3 Kernel. I'm almost Positive my issue is not related to the ROM or kernel.
A couple of weeks ago I was attempting to get Link2SD app to work properly (it never has but I kept trying every few weeks thinking Link2SD app would get updated and it would work) on my EXTERNAL Sdcard's 2nd EXT4 patition. I ended up with a soft bricked phone.
And my Sdcard appeared to be wiped. I restored the backup of my EXTERNAL Sdcard to my Sdcard (Internal).
Prior to restoring the backup of my EXTERNAL to Internal I used to have a "Long" menu list in Recovery. That List included options like
external
external/sd
tapatalk
tapatalk/download
They aren't listed anymore.
This is what my Menu looks like in Recovery (CWM Voodoo Lagfix Recovery v3.0.2.8.) now;
Android/
CameraZOOM/
DCMI/
LOST.DIR/
Removable Disk/ Removable Disk/ Was NEVER an option for me.
SpeedSoftware/
SupertaskManager/
TunnyBrowser/
Voodoo/
albumthumbs/
bluetooth/
bugreports/
clockworkmod/
data/
gameloft/
handcent/iTagCache/
launcherpro_backup/
music/
openfeint/
tapatalkxdapre_download/
and then my ROMS and Kernels Boot Anamation ect.
My Sdcard NEVER looked like this before my restoring of EXTERNAL to internal.
HOW do I fix this?? I've been searching for 2 weeks and haven't found anyone with a problem like this or solution... my phone works properly but I know this is not the way it should be.. I NEVER had a Removable Disk option before.
Any Help/Insight on this issue will be Greatly Appreciated and Thanked.
Click to expand...
Click to collapse
I see nobody has responded to you... but I do not see a problem. Maybe more explanation of your concerns.
The after restore list looks similar to mine. It is showing you the contents of your sdcard (folders & files).
EDIT: Not sure if you are aware of this thread: [GUIDE] Link2sd setup and installation

Did you set both partitions to primary? Don't format to Ext4, just use FAT 32.

lumin30 said:
I see nobody has responded to you... but I do not see a problem. Maybe more explanation of your concerns.
The after restore list looks similar to mine. It is showing you the contents of your sdcard (folders & files).
EDIT: Not sure if you are aware of this thread: [GUIDE] Link2sd setup and installation
Click to expand...
Click to collapse
Thanks for your reply..
My major concern was that after I dragged, dropped and restored my sdcard backup my menu list in Voodoo Recovery looked much different than it had ever looked before.
Specifically The Removable Disk option (I had NEVER had that option before).
Also. I no longer had external/ or external sdcard/ in my options list.
I thought I had dropped my EXTERNAL SD backup into my INTERNAL sdcard. But you say mine looks similar to your's so I guess I'm ok.. it was very disconcerting to see a much different Recovery Menu than the one I had been seeing for a year.
I had used an Excellent Guide by desexton to get an EXT4 partition on my External sdcard and it worked Flawlessly on Froyo and was hoping to have it work the same way on Gingerbread.. Other members have also been having issues with an EXT4 Partition (External sdcard) on Gingerbread.
The Guide you posted says to make the Partition EXT3. I am going to look into the Guide you posted tonight after work.
Thank you for your reply. I feel much better now that someone has replied that their menu looks like mine.
Have a Great Day!

[Q] Has anyone found an App to SD solution?

I've looked through the big development thread and haven't found a clear answer but has anyone found an app to sd solution that works?
This stupid SdCard / ExtSdCard arrangement is making me pull my hair out. I just realized my titanium backups weren't really backups since they were being stored on my internal memory.
I managed to change my backup folder and free up some space by moving all my backups to the SD card, but for some reason I cannot move apps to SD through Titanium or any other app I've tried.
Does anyone know how to do this? Is there a setting in titanium I need to change or is this just something we have to deal with forever short of flashing a custom rom?

SDCARD binary
Galahad_Knight said:
I've looked through the big development thread and haven't found a clear answer but has anyone found an app to sd solution that works?
This stupid SdCard / ExtSdCard arrangement is making me pull my hair out. I just realized my titanium backups weren't really backups since they were being stored on my internal memory.
I managed to change my backup folder and free up some space by moving all my backups to the SD card, but for some reason I cannot move apps to SD through Titanium or any other app I've tried.
Does anyone know how to do this? Is there a setting in titanium I need to change or is this just something we have to deal with forever short of flashing a custom rom?
Click to expand...
Click to collapse
I've found the real problem, but not the solution.
My Relay runs ICS. It is rooted, and you have to root to even touch any of this. The phone has a binary, /system/bin/sdcard that controls the internal memory and your SDcard. now, I have found that if you are rooted, you can chmod this binary (or use rooted ES File explorer to remove all executable properties) so that it can no longer run, then reboot. then you can run, as superuser "mount -o rw,bind /mnt/extSdCard /mnt/sdcard"
Seems great... Except vfat doesn't like to be bound in such a fashion, and you quickly lose write access and it starts mangling your files.
vfat just doesn't seem to work for us in this case. I've changed mine back, and reformatted my SDcard to be NTFS and mounted with paragon NTFS/HFS, which has completely stabilized my filesystem. only problem is, I can't get this to mount -o bind worth a damn.
I'm toying with the idea of reformatting my SDCard part vfat and either part NTFS or EXT4. maybe I get get the phone to natively recognize ext4 for the sdcard (even if I have to create a script myself)
keypoints I've found in this process:
1. the sdcard binary only allows access to 1023 files at once on either the SDcard, or the memory block it is using as the SDcard. too many pictures in your gallery? so sorry... can't load them all.
2. the physical device for your sdcard is /dev/block/mmcblk1. the partitions are mmcblk1p* (starting with 1)
3. the phone will not allow the sdcard binary to be killed manually. removing the executable permission and then rebooting the phone seems to be the only way to get it to stop.
4. vfat is prone to errors, and android seems to love screwing with the card. getting off vfat seems to be crucial to this process.
As you've gotten no other replies, and this is a gigantic concern for me as well, I'm going to keep working on this myself, in the hopes that I can get the phone to actually use the SDcard the way we hope it can be used.

Problems with TWRP Backup - unable to mount sd/ext

I've been searching both this forum and the net generally and not found an answer to my specific problem so I'm hoping someone can help.
I'm trying to swap out my ROM, I'm currently running CM 11 nightly but I'm getting endless FCs with apps so thought I'd try something different.
When I try to run the nandroid backup with TWRP v2.7.0.1 the backup fails every time with the error E: unable to mount '/sd-ext'
Can anyone advise? Thanks

tht looks like external sd card.
Try changing location for your backup to internal memory or make sure you got SD card plugged in to SD slot.
you may also try command on terminal emulator (or via adb shell):
ln -s /storage/emulated/0/ /sd-ext/
it will create symbolic link named sd-ext in root of your system and it will point to internal storage (if I am not mistaken, from now on it should not matter if you select internal or external storage as target for your backup - it will end up as internal anyways)
Sent from my TF300T using XDA Free mobile app

Thanks, the backup was to be created on the internal SD card, but you are right it is almost certainly a problem with the external card. I'm unable to mount either the dock SD or micro SD cards in TWRP - the options are just greyed out and can't be selected.
I can't get either card to mount when I boot to system ether I have noticed. I've tried formatting them as FAT32, EXFAT and NTFS and no dice so I'm wondering if this is a KK issue - they both worked flawlessly when I was running PA and Omnirom JB ROMs.
I've managed to find a workaround - I've flashed CWM and have been able to do a nandroid backup with that - but I still can't mount either the micro SD or dock SD cards with CWM or in system when I flashed KatKISS ROM - and of course now I can't use any old TWRP nandroids I have from JB ROMs without reflashing TWRP. I'd also rather be running TWRP ultimately if I can so it would be good to get to the bottom of what is causing this issue.
Not quite sure what the command line you suggested does, but I'm guessing it won't be useful with the problem as it stands now?

sorry for late reply as I was out of internet lately.
that command creates /sd-ext/ folder that acts similar to shortcut to intertnal sdcard
any call for /sd-ext (for example: cd /sd-ext) will end up on internal sdcard.
That wont help with accessing your external sdcard (as this was main issue here) - it would merely fool installer to 'think' it is working on external sd while it was still on internal.
Sent from my TF300T using XDA Free mobile app

Thanks for your help. I've had endless troubles which ultimately ended in a hard brick during a failed flash of the stock ROM. I'm waiting for a replacement motherboard - something wasn't right with the old board anyway, it doesn't seem that it was just ROM issue. Hopefully when it comes I'll find that it wasn't a hardware issue associated with the SD cards as well.

[Completed] [Question] Writing to external sd card Specifically with ES File Manager!

I have a Sprint Galaxy Note $ Running Stock og5 Rom Rooted via Beast Mode TWRP then Play update, then flashed to Plazma Kernel. I have modified the /etc/permissions/platfom.xml file to include Group Id media_rw in the write to external storage permission and mounted the /mnt/media_rw/estSDcard as r/w in the root explorer portion of ES File Manager and it seemed to work fine for as long as I can remember but now if I try to copy or paste or send something to /storage/extSDcard it is created asychrously and ends up in the LOST.dir folder after a simple unmount remount or reboot or SDcard pull. Other apps are having the same problems like app backup restore and Btitorrent and others when trying to write directly to extSDcard I even went ass far as adding sdcard_all to the aforementioned gid permission set. It seems like such an obvious thing that has been overlooked by develpoers of the rom. I can create masting folders "no asychronously' if I do so buy navigating to /mnt/media_rw/extSDcard rather than /storage/extSDcard and they'll last but not all programs will allow that directory in their settings. Furthermore ES download Manager won't function with either directory and will not allow their app backup file to be saved the /mnt directory. only /0 or /storage/extSDcard.
I have exhausted my abilities with this and have no answer also It seems to be a new problem, and I haven't done anything I can think of to cause this. Partition table is 55000mb Fat32 17009mb ext4 journal partition on the extSDcard. Any Ideas?
Below you can see The before and after of unmounting and remounting my sd card resulting in Populated Lost.dir and loss of created folders also you can see the way that all nav methods resultu in same permission set when checked with a root explorer "total Commander"

wELL i DON'T KNOW WHY BUT REFORMATTING THE SD CARD TO A SINGLE FAT 32 VOLUME SOLVED THE LEAK. i FIRST TRIED AN ALTERNATE SD CARD WITH A SIMILAR PATITION TABLE (EXT2/FAT32) BUT HAD THE SAME PROBLEMS EXCEPT THE DATA WOULD SIMPLY BE GONE INSTEAD OF IN THE LOST.DIR FOLDER. i HAVE YET TO IMPLEMENT THIS TO MY PRIMARY USE SD CARD because of the fact that I have backups and files that I need on that card from before the leak. I anticipate the same results, fingers crossed.
If ANYONE has any incite into why the partition table set up as it was would affect the retention of data in this manner please let me know.
PLEASE PLEASE let me know

Hello,
Try posting your question/issue in the ROM/kernel thread where you got them or their dedicated Q&A thread(if it has one) or even PM the developer in case its something he isn't aware of, he may want to try and solve it so his ROM has no issues.
I hope this helps. Good luck.

Droidriven said:
Hello,
Try posting your question/issue in the ROM/kernel thread where you got them or their dedicated Q&A thread(if it has one) or even PM the developer in case its something he isn't aware of, he may want to try and solve it so his ROM has no issues.
I hope this helps. Good luck.
Click to expand...
Click to collapse
Thanks, I was using stock rom though. And the caps lock was an accident, at any rate i have changed roms and the issue appeared to be a faulty sd card to begin with. I wasn't able to retain data from my reader writer to phone on my primary sd ince reformatted but was when I used a different one. Anyway thanks for the advice and I will use it if I have different questions