Hi Jeff,

Thanks for your valuable information.

My configuration is similar to the one that is there in the link.
"It sounds like you're building a "Emulated primary, physical secondary" 
device" => Yes I am building Emualated primary and physical secondary.

Can you please let me know how to check whether FUSE daemon is started and 
running.
I used "ps" command. I am not able to see any FUSE daemon process running.

Regards,
Anand.

On Wednesday, March 12, 2014 10:37:18 PM UTC+5:30, Jeff Sharkey wrote:
>
> That error is happening when Zygote is trying to prepare the 
> multiuser mount namespace.
>
> It looks like primary external storage is emulated on your device; is that 
> FUSE daemon started and running?  (The mkdir might be failing against the 
> read-only rootfs if the daemon isn't present.)
>
> It might also be helpful to compare your configuration against a known 
> working example:
>
> http://source.android.com/devices/tech/storage/config-example.html
>
> It sounds like you're building a "Emulated primary, physical secondary" 
> device.  Hope this helps.
>
> j
>
>
> On Tue, Mar 11, 2014 at 5:16 PM, Anand R <[email protected] <javascript:>
> > wrote:
>
>> Hi All,
>>
>> I am facing a issue when i try to mount a external sdcard in a custom 
>> device which is running on Kitkat 4.4.2.
>> Below is the error which i am getting whenever sdcard mount happens.
>>
>> 03-11 23:25:32.229: E/cutils(553): Failed to 
>> mkdir(/mnt/shell/emulated/0): Read-only file system
>> 03-11 23:25:32.229: E/dalvikvm(553): cannot mountExternalStorage(): 
>> Read-only file system
>>
>> My init.device.rc is as follows:
>>
>> # no emmc file systems mounted at this point (system, data, pds, etc.)
>> # runs after "on early-init" and before "on early-fs"
>> # runs in charge-only-mode
>> on init
>>     export PATH /system/sbin:/system/bin:/system/xbin:/sbin:/vendor/bin
>>
>>     write /sys/class/graphics/fbcon/cursor_blink 0
>>
>>     mkdir /mnt/shell 0777 shell shell
>>     mkdir /mnt/shell/emulated 0700 shell shell
>>
>>     #mkdir /storage 0550 system sdcard_r
>>     mkdir /storage/emulated 0555 root root
>>
>>     mkdir /mnt/media_rw 0777 media_rw media_rw
>>     mkdir /mnt/media_rw/sdcard1 0700 media_rw media_rw
>>     mkdir /storage/sdcard1 0775 root root
>>
>>     export EXTERNAL_STORAGE /storage/emulated/legacy
>>     export SECONDARY_STORAGE /storage/sdcard1
>>     export EMULATED_STORAGE_SOURCE /mnt/shell/emulated
>>     export EMULATED_STORAGE_TARGET /storage/emulated
>>
>>     #symlink /storage/emulated/legacy /sdcard
>>     #symlink /storage/emulated/legacy /mnt/sdcard
>>     #symlink /storage/emulated/legacy /storage/sdcard0
>>     #symlink /mnt/shell/emulated/0 /storage/emulated/legacy
>>     #symlink /storage/sdcard1 /extSdCard
>>     #symlink /storage/sdcard1 /mnt/extSdCard
>>
>> fstab.device is as follows
>>
>> # Android fstab file.
>> #<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
>> # The filesystem that contains the filesystem checker binary (typically 
>> /system) cannot
>> # specify MF_CHECK, and must come before any filesystems that do specify 
>> MF_CHECK
>> /dev/block/system /system ext4 ro,noatime wait
>> /dev/block/cache /cache ext4 
>> nosuid,nodev,noatime,nodelalloc,barrier=1,data=ordered wait,check
>> #/dev/block/panic /panic raw defaults wait
>> /dev/block/userdata /data ext4 
>> nosuid,nodev,noatime,nodelalloc,barrier=1,data=ordered 
>> wait,check,encryptable=footer
>> /dev/block/pds /pds ext4 
>> nosuid,nodev,noatime,nodelalloc,barrier=1,data=ordered wait,check
>> /devices/pci0000:00/0000:00:04.0/mmc_host/mmc1 auto vfat defaults 
>> voldmanaged=sdcard1:auto
>>
>> Whether i comment or uncomment the creation of symlinks to "/sdcard", 
>> "/mnt/sdcard/", the behavior is the same.
>>
>> When i explicitly mount sdcard from shell prompt using "mount" commnd, it 
>> is able to mount.
>> Please help me to resolve this issue.
>>
>>
>> Thanks in Advance,
>> Anand.
>>
>> -- 
>> -- 
>> unsubscribe: [email protected] <javascript:>
>> website: http://groups.google.com/group/android-porting
>>
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "android-porting" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Jeff Sharkey
> [email protected] <javascript:>
>
>
>
> j
>
>
> On Tue, Mar 11, 2014 at 5:16 PM, Anand R <[email protected] <javascript:>
> > wrote:
>
>> Hi All,
>>
>> I am facing a issue when i try to mount a external sdcard in a custom 
>> device which is running on Kitkat 4.4.2.
>> Below is the error which i am getting whenever sdcard mount happens.
>>
>> 03-11 23:25:32.229: E/cutils(553): Failed to 
>> mkdir(/mnt/shell/emulated/0): Read-only file system
>> 03-11 23:25:32.229: E/dalvikvm(553): cannot mountExternalStorage(): 
>> Read-only file system
>>
>> My init.device.rc is as follows:
>>
>> # no emmc file systems mounted at this point (system, data, pds, etc.)
>> # runs after "on early-init" and before "on early-fs"
>> # runs in charge-only-mode
>> on init
>>     export PATH /system/sbin:/system/bin:/system/xbin:/sbin:/vendor/bin
>>
>>     write /sys/class/graphics/fbcon/cursor_blink 0
>>
>>     mkdir /mnt/shell 0777 shell shell
>>     mkdir /mnt/shell/emulated 0700 shell shell
>>
>>     #mkdir /storage 0550 system sdcard_r
>>     mkdir /storage/emulated 0555 root root
>>
>>     mkdir /mnt/media_rw 0777 media_rw media_rw
>>     mkdir /mnt/media_rw/sdcard1 0700 media_rw media_rw
>>     mkdir /storage/sdcard1 0775 root root
>>
>>     export EXTERNAL_STORAGE /storage/emulated/legacy
>>     export SECONDARY_STORAGE /storage/sdcard1
>>     export EMULATED_STORAGE_SOURCE /mnt/shell/emulated
>>     export EMULATED_STORAGE_TARGET /storage/emulated
>>
>>     #symlink /storage/emulated/legacy /sdcard
>>     #symlink /storage/emulated/legacy /mnt/sdcard
>>     #symlink /storage/emulated/legacy /storage/sdcard0
>>     #symlink /mnt/shell/emulated/0 /storage/emulated/legacy
>>     #symlink /storage/sdcard1 /extSdCard
>>     #symlink /storage/sdcard1 /mnt/extSdCard
>>
>> fstab.device is as follows
>>
>> # Android fstab file.
>> #<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
>> # The filesystem that contains the filesystem checker binary (typically 
>> /system) cannot
>> # specify MF_CHECK, and must come before any filesystems that do specify 
>> MF_CHECK
>> /dev/block/system /system ext4 ro,noatime wait
>> /dev/block/cache /cache ext4 
>> nosuid,nodev,noatime,nodelalloc,barrier=1,data=ordered wait,check
>> #/dev/block/panic /panic raw defaults wait
>> /dev/block/userdata /data ext4 
>> nosuid,nodev,noatime,nodelalloc,barrier=1,data=ordered 
>> wait,check,encryptable=footer
>> /dev/block/pds /pds ext4 
>> nosuid,nodev,noatime,nodelalloc,barrier=1,data=ordered wait,check
>> /devices/pci0000:00/0000:00:04.0/mmc_host/mmc1 auto vfat defaults 
>> voldmanaged=sdcard1:auto
>>
>> Whether i comment or uncomment the creation of symlinks to "/sdcard", 
>> "/mnt/sdcard/", the behavior is the same.
>>
>> When i explicitly mount sdcard from shell prompt using "mount" commnd, it 
>> is able to mount.
>> Please help me to resolve this issue.
>>
>>
>> Thanks in Advance,
>> Anand.
>>
>> -- 
>> -- 
>> unsubscribe: [email protected] <javascript:>
>> website: http://groups.google.com/group/android-porting
>>
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "android-porting" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Jeff Sharkey
> [email protected] <javascript:> 
>

-- 
-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to