Host fails to mount SD card on otoro when UMS is enabled




DOM: Device Interfaces
5 years ago
5 years ago


(Reporter: cjones, Assigned: dhylands)


Gonk (Firefox OS)

Firefox Tracking Flags



I get the error

E/Vold    (   99): Unable to open ums lunfile (No such file or directory)
E/AutoMounter(  116): Command 'volume share sdcard ums' failed: 406 'volume operation failed (No such file or directory)'

Comment 1

5 years ago
I'll take a look at this as soon as my otoro arrives (expected Tuesday)
Assignee: nobody → dhylands

Comment 2

5 years ago
This is caused by a mismatch between vold (built for ICS) and the kernel (built for GB).

I've filed an issue in github:

and one possible solution:


5 years ago
blocking-basecamp: --- → ?

Comment 3

5 years ago
The solution of grabbing vold from the phone has been implemented.

If you've already run ./ otoro, you'll need to do it again to cause the correct vold to be updated.
Last Resolved: 5 years ago
Resolution: --- → FIXED
Do you mind posting a note about this to dev-b2g?  Thanks for fixing!

Comment 5

5 years ago
I posted the following to dev-b2g:

Fundamentally, the phone is running a GB kernel, but we're building an ICS userspace.

You need to update the phone to use the GB based vold that came with it, rather than the ICS based vold that we build.

1 - If you have a build environment setup, you need to update the vold that is in your build tree.
    There are 3 ways that you can do this:
    - ANDROIDFS_DIR=parent-of-place-you-saved-your-system-backup ./ otoro
    - cp parent-of-place-you-saved-your-system-backup/system/bin/vold ./vendor/qcom/common/proprietary/vold
    - I stashed a copy at

2 - You can then do ./ && ./
    Or you can do: adb push vold /system/bin

If you don't have a build environment, just grab the vold that I stashed (see above) and adb push it to the phone (see 2 above)

Reboot the phone, and USB mass storage should be working.
blocking-basecamp: ? → +
You need to log in before you can comment on or make changes to this bug.