SD-EXT not mounting

Discussion in 'Bugless' started by jaytime, Oct 18, 2010.

  1. jaytime
    Offline

    jaytime New Member

    Joined:
    Aug 21, 2010
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    0
    Even though I still have a class 2 card, I wanted to begin using Apps2SD. I used ROM Manager to create a 512 partition with 0 MB swap (bc of class 2). After rebooting, SD-EXT isn't visible in Root Explorer (nor is there a /system/sd folder).

    I used the "move to sd card" feature, and it seemed to work, but later determined that these are getting mounted in /mnt/asec.

    I loaded the SD card in Ubuntu and copied a few files to the ext3 partition. I then rebooted the phone and searched in root explorer for the files I copied and they aren't found.

    Running BBv5 with Chevy's LV1100 kernel.

    I'm not sure if Firerat's fix is appropriate for BB.

    I've tried "mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p2 /sd-ext" in terminal emulator but get 'no such file or directory' response.

    Can anyone help me get /sd-ext to mount correctly and visible in root explorer??

    Thanks!
  2. ZeroBarrier
    Offline

    ZeroBarrier New Member

    Joined:
    Apr 23, 2010
    Messages:
    991
    Likes Received:
    0
    Trophy Points:
    0
    Try

    mount -o rw /dev/block/mmcblk0p2 /sd-ext

    If that works, you can get Firerat's Apps2EXT script to work on BB v0.5.

    And just a heads up, moving apps to SD in Froyo through Manage Apps in the settings will always move them to the FAT partition. That's why Firerat's script also creates a APKMAnager.sh script to move them from internal to external (sd-ext) memory.

    If the above command works to get your sd-ext partition mounted, try Firerat's script and let me know how it goes.
  3. jaytime
    Offline

    jaytime New Member

    Joined:
    Aug 21, 2010
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    0
    When I did that in Terminal Emulator on the phone, it responds with: 'Usage: mount [-r] [-w] [-0 options] [-t type] device directory' (presumably indicating incorrect syntax).

    I tried running the a2sd and sdext scripts from Firerat anyway to see if it would do better than I. Here is the relevant output:

    /system/etc/init.d/*userinit*: No such file or directory
    ========================
    grep: /system/etc/init.d/mountsd: no such file or directory
    e2fsck not found, assuming fs ok..
    ========================
    /sd-ext mount failed exiting


    Does that help? The only files i see in my /system/etc/init.d/ directory are:
    01cpuod
    02vm
    03backup
    04vending
  4. ZeroBarrier
    Offline

    ZeroBarrier New Member

    Joined:
    Apr 23, 2010
    Messages:
    991
    Likes Received:
    0
    Trophy Points:
    0
    Ok, let's try something here.

    Grab the attached file, unzip it and place it in /system/etc/init.d/, then set the permissions to "rwxr-x---" (if you aren't sure about this, look at the other files permissions with root explorer. It will be User - Read, Write, Execute; Group - Read, Execute).

    After you do that, reboot your phone and check to see if your sd-ext partition was mounted correctly. You can do this by going to sd-ext with root explorer and checking if you see a "used/free" at the top of your screen.

    Once you do that, let me know if it works and we'll go from there.

    Attached Files:

  5. jaytime
    Offline

    jaytime New Member

    Joined:
    Aug 21, 2010
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    0
    We're getting closer!

    It didn't seem to mount immediately, but after a moment, the SD-EXT directory did appear. However, it didn't have a file that I previously copied to that partition. Nor did it show a used/free at the top of root explorer. Nor does it appear in my SD card & Phone storage settings page.

    I ran 'sh /sdcard/fr-patch140.txt sdext a2sd' again to see if it could complete the rest. The first time I did, it seemed to have mounted SD-EXT as read only. So, I mounted as r/w in root explorer and ran again, but there still seem to be problems (besides the initial mounting as r/o). Here is the updated output:

    /system/etc/init.d/*userinit*: No such file or directory
    ========================
    /system/etc/init.d/05mountsd already exists (to be expected)
    ========================
    /sd-ext not mounted.. skipping a2sd

    Then a bunch of stuff about moving data/data to sd-ext, which I skipped because SD-EXT still doesn't seem to be mounting quite right.
  6. ZeroBarrier
    Offline

    ZeroBarrier New Member

    Joined:
    Apr 23, 2010
    Messages:
    991
    Likes Received:
    0
    Trophy Points:
    0
    Ok, one step at a time; first of all, I think you have an old script. You should be running "fr-a2sd_1-34c.sh.txt" which is the most recent script file from Firerat, get it from here.

    Ok, a few things straight, the sd-ext partition will not appear in your SD Card & Phone Storage under settings. Since this isn't an official function in a ROM (it's more like a work-around to use the old apps2sd that used the sd-ext partition instead of Froyo's native apps2sd using the FAT partition).

    Now, you say no used/free info was provided for /sd-ext/ in root explorer, that means it wasn't mounted, but did you have that folder before, or no? If it just appeared after placing the 05mountsd file in /system/etc/init.d/ folder, then try another reboot to see if your EXT partition finally get's mounted to the /sd-ext/ folder.

    No need to run any scripts just yet; first we need to try to mount your EXT partition manually before we can even think about running the script.

    OMG, I just remembered. What kernel are you using? Certain kernels do not support mounting external EXT partitions. I recommend you try slayher's kernel as I know this one to work 100% with mounting an external EXT partition. Find them here. Make sure it's one of the ones that say NEW Version 1.6.

    Get back to me, we will definitely get your phone working with Apps2EXT.
  7. jaytime
    Offline

    jaytime New Member

    Joined:
    Aug 21, 2010
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    0
    The one I got uses the 1.3.4 script. I got it here:
    [PATCH] Firerat 'all in one' patch file [ v1.4.0 - 2010-09-06 ] - xda-developers

    I don't really care if it appears here because I check several places. However, I have seen scren captures in other forums that it does appear here (they weren't Droids, and I've closed those tabs since we were making better progress). If it doesn't then oh well. Thanks for the info.

    It appeared for a hot second, but seemed to disappear after running Firerat's script the first time. I know the disappearing doesn't make sense, but I can't explain it. After I put your 05mountsd there, the dir remained. I tried rebooting several times after that, running Firerat's script in between to see, but still doesn't seem to be mounting correctly.

    I had read that somewhere too. I was originally on a Chevy kernel. After reading that it mattered, I flashed a jdlfg kernel. Then, reading on the CM page, I flashed a bekit kernel (which resulted in the boot freezing on M). So, I flashed back to a Chevy. I've now put a Slayher on (I actually looked for slayher in Rom Manager and swear I didn't see it yesterday, but its there today. Thanks for the link). I tend to stick to 1.1 GHz.
  8. jaytime
    Offline

    jaytime New Member

    Joined:
    Aug 21, 2010
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    0
    UPDATE: The Slayher kernel seems to have done the trick!!
    (along with your fine help, and file that you sent!)

    YAY Slayher!!

    THANK YOU! THANK YOU!
  9. ZeroBarrier
    Offline

    ZeroBarrier New Member

    Joined:
    Apr 23, 2010
    Messages:
    991
    Likes Received:
    0
    Trophy Points:
    0
    Awesome! I'm so glad to hear it worked!
  10. ZeroBarrier
    Offline

    ZeroBarrier New Member

    Joined:
    Apr 23, 2010
    Messages:
    991
    Likes Received:
    0
    Trophy Points:
    0
    Now, a few points you should know. You should run Firerat's script even though your sd-ext partition is already being mounted by the 05mountsd file; this is so it will create the APKManager.sh and bind mounting files. When you run it, it'll ask you if you want to bind /data/data/ to /sd-ext/data/, this is your choice to make depending on how much space you wish to save, how many apps you want to install without running out of space, or how much performance you are willing to sacrifice.

    I personally did bind /data/data/ to /sd-ext/data/ with the stock 16GB class 2 card and notice little to no performance sacrificed, so I recommend going that route since it will give you the best space saving per installed app.

    The other thing to remember is that /data/dalvik-cache/ will keep growing the more you install apps, so your internal /data/ partition will still shrink with every installed app, but at an incredibly low rate.

    After getting everything set up, you should keep in mind that any app that auto-installs to internal memory will now be automatically installed in /sd-ext/app/ (since this workaround actually tricks the device into thinking /sd-ext/app/ is actually /data/app/), but every app that auto installs into your SD (Apps2FAT in Froyo) should be moved into "internal" memory for best performance/space saving. You can do this through the normal Settings > Applications > Manage Applications > SD > Move to Phone, or you can use APKManager.sh through ADB/Terminal Emulator to batch move them.

    Also, you can choose certain apps to install in real internal memory through the APKManager.sh file (if you have an app you want to make sure doesn't lag on your and such). Firerat's script makes 2 new folders in your /data/ partition called /data/app-i/ and /data/app-private-i/; now the way these work is that APKManager.sh makes a symlink file in /sd-ext/app/ pointing to /data/app-i/ or /sd-ext/app-private/ to /data/app-private-i/, so your phone actually reads and executes the app from real internal memory.

    If you have any questions, let me know, and enjoy!!!
  11. jaytime
    Offline

    jaytime New Member

    Joined:
    Aug 21, 2010
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    0
    I just tried running the script again and received 'failed on /data/apps/all_my_apps - Cross device link'

    I think there are a few apps I'd like to move to /data/app-i/. I should be able to use Root Explorer and just copy the apk, right??

    With the symlink, Titanium Backup shouldn't have any problems, right? Do you know if 'move to SD' in Titanium sends to Apps2FAT or Apps2EXT? I assume that 'move to phone' would move to the EXT as you described with APKManager.sh. Is that right?
  12. jaytime
    Offline

    jaytime New Member

    Joined:
    Aug 21, 2010
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    0
    After receiving the above when running the fr-patch140.txt script without success, I tried flashing FR-a2sd_1-34b_S.zip. It froze during this process. I rebooted. When it loaded, my launcher was gone and none of my apps were in the dock. Hmmm... perhaps the symlink didn't get setup?

    Unfortunately, everything is on the ext partition and inaccessible to me through the phone. I'll have to ADB later, I think.

    Do you think that the symlink isn't working properly?
    Any thoughts on the 'cross device link' error (and how it could be affecting my current situation)?
  13. ZeroBarrier
    Offline

    ZeroBarrier New Member

    Joined:
    Apr 23, 2010
    Messages:
    991
    Likes Received:
    0
    Trophy Points:
    0
    No idea what this actually means, sorry.

    No, you should only do this with APKManager.sh. The phone does not naturally read apps from /data/app-i/, only from /data/app/; so you need to use APKManager.sh to move the app to internal memory and create the symlink for you.

    TiBu shouldn't have a problem, but I'm not 100% certain of that (I don't actually use TiBu for anything at all). TiBu's Move to SD would probably move them to Apps2FAT, as it's designed to work that way by default; and not to mention Move to Internal will actually move them to the EXT partition (because your phone thinks /sd-ext/app/ is actually /data/app/)

    You should really be using the most recent script (fr-a2sd_1-34c.sh.txt), I'll attach a copy that you can download (I've modified it to create the 05mountsd file with an included line at the beginning to run "mount -o rw /dev/block/mmcblk0p2 /sd-ext", for those ROMs that just won't play nice). With this script, you won't need the 05mountsd file you got from my previous posts. I would also start the whole process from a fresh ROM install (just to make sure that previous attempts didn't leave any messed up files/scripts/etc.

    Again, I really recommend starting from a fresh ROM install. Here's how I do it:

    Wipe boot, system, data, cache (in this case I'll recommend you wipe sd-ext too)
    Install ROM
    Install Kernel
    Install Compcache Fix (optional)
    Boot up phone
    Run "adb remount"
    Run "adb shell mount -o rw /dev/block/mmcblk0p2 /sd-ext
    Run "adb shell fr-a2sd_1-34c.sh.txt"
    Choose yes to bind /data/data/
    Reboot phone when script finishes

    You'll notice I run "mount -o rw /dev/block/mmcblk0p2 /sd-ext" before the script, and that's because on a couple of ROMs Firerat's script doesn't work 100%. He did make the script for CM, so any ROM based on CM or to at least use the /system/etc/init.d folder should work; and the way I found to get around it not working is by mounting the sd-ext partition before running the script.

    If I had to guess, it has to be because your sd-ext partition didn't mount properly (hence why none of your apps appeared). The symlinks are only for apps moved to real internal memory, it's the bindmounts that failed (and this would happen if sd-ext didn't properly mount, since the bindmounts are on "/sd-ext/userinit.d/10data2sdext-binds".

    Attached Files:

  14. jaytime
    Offline

    jaytime New Member

    Joined:
    Aug 21, 2010
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    0
    I flashed as suggested.

    "mount -o rw /dev/block/mmcblk0p2 /sd-ext" returns
    "usage: mount [-r] [-w] [-o options] [-t type] device directory"

    This was the same message that I received before flashing. I've tried in both Terminal Emulator and ADB.

    Is there another possible syntax? -t yaffs2 wouldn't hurt, right?
  15. ZeroBarrier
    Offline

    ZeroBarrier New Member

    Joined:
    Apr 23, 2010
    Messages:
    991
    Likes Received:
    0
    Trophy Points:
    0
    You flashed the ROM and a supported Kernel, right?
  16. jaytime
    Offline

    jaytime New Member

    Joined:
    Aug 21, 2010
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    0
    Yeah- BBv5 & Slayher 1100 (same as before).

    I haven't tried the script yet because that command wouldn't run.
  17. ZeroBarrier
    Offline

    ZeroBarrier New Member

    Joined:
    Apr 23, 2010
    Messages:
    991
    Likes Received:
    0
    Trophy Points:
    0
    Do you have an /sd-ext/ folder in the root of your phone?
  18. jaytime
    Offline

    jaytime New Member

    Joined:
    Aug 21, 2010
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    0
    Nope. I wiped, flashed ROM and kernal again this morning. no problem with remount, but it still doesn't like the mount syntax (only tried adb today). I haven't tried running the script yet since that command doesn't seem to work.

    I'm back to my thought that it may need -t yaffs2 included in it. What do you think?
  19. jaytime
    Offline

    jaytime New Member

    Joined:
    Aug 21, 2010
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    0
    I went ahead and tried with '-t yaffs2' in the command. It tells me 'No such file or directory'. I then mounted as r/w and did a 'mkdir /sd-ext'. The folder created. I then tried your original command and got the same 'usage...' error. I tried again with yaffs2 and it told me 'mount: invalid argument'.

    I used ROM Manager to create the partition. I'm going to delete the partition and re-create directly in Ubuntu.
  20. jaytime
    Offline

    jaytime New Member

    Joined:
    Aug 21, 2010
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    0
    Problem remains after re-creating the EXT3 partition.
Search tags for this page
android mount sd-ext
,

error mounting sd ext

,

error mounting sd-ext

,
how to fix error mounting emmc and sd-ext
,
how to fix sd ext not mount
,
how to mount sd-ext partition android
,
mount sd android terminal
,
mount sd ext
,

mount sd-ext

,
mount sd-ext android
,
mount sd-ext terminal
,

mounts2sd external not mounted

,
mounts2sd not mounted
,
sd-ext not mounted
,
sd-ext not mounting