[T-Mobile Samsung Galaxy Note II] vebulous:
If i were to guess, some startup script got messed up some how. I haven't looked at the code, but what little experience i have with *nix distroes tells me that a bind command in what would be the the android fstab-like file got borked. I use this kind of trick on my ubuntu install. I bind my home folder from a separate partition on a different drive. I'll have to dig in to the zip and see exactly how it works, but maybe something you did messed up the startup script to make the mod.

OR

Your install of Jedi Master is evolving on its own inside your phone. If that's the case, skynet has become self-aware :D

UPDATE: I looked at the two script files. Identical except for the exfat and vfat part (exfat vs fat32 of external sd card)

sleep 10
mount -o remount,rw /
mount -t (sdcard file system type) -o umask=0000 /dev/block/vold/179:49 /storage/sdcard0
sleep 30
mount -o bind /data/media /storage/extSdCard
chmod 777 /mnt/extSdCard
sleep 10
chown 1023:1023 /storage/extSdCard
chown 1000:1000 /storage/sdcard0

Thats exactly what it is.

Here's a breakdown. after being executed by the ordered number (i'm guessing this bash script is put in an init.d folder), it waits 10 seconds.

Second, it remounts the root tree as read-write.

Thirdly, it mounts the external sd card to /storage/sdcard0.

Fourthly, it waits another 30 seconds, giving it time to execute the command. This may be where you can get fudged, because if the mount takes longer than 30 seconds, it can screw up with the command. Although its unheard of for a max 64gb mount to take longer than 30 seconds....anything is possible. Of course that's not the only thing that could have gone wrong.

THEN, it binds your "internal storage" (/data/media) to the external SD's mount point. This is where your script fails. So, it's my educated guess that it takes longer than 30 seconds to complete the previous mount command.

And then, it makes sure you can read, write and execute commands from your newly binded "external storage" partition (originally, internal storage).

Then we wait another 10 seconds.

Finally it changes ownership of the newly created "external storage" (originally, internal storage) to the userID:groupID of user:usergroup. And "internal storage" (originally, external SD) to userID:groupID of android_system:android_systemgroup.

Thats the rundown.

If you can get a log of the failure, either in dmesg or something, then you can pinpoint the exact problem. But the way you're describing your issue, with extSdCard on both external and internal partitions, it leaves me to believe that the script is not given enough time to execute properly OR something else is interfering with the script.

Wow, that took longer than i expected and its much more detailed than i wanted it to be. Sorry guys.

---------- Post added at 03:48 AM ---------- Previous post was at 03:37 AM ----------

This is the perfect example of a 'chown' or 'chmod' gone wrong. Or maybe even "mount -o umask=0000" getting fudged.

Isolated, these scripts are heavenly. But when other scripts are running left and right, one tries to modify a file that's already been modified and all hell breaks loose. It's hard to help if i don't have logs of the failure. And i don't even know which logs android stores (or where for that matter). I wish i could help.