Android file system is not mounting "binder: 147:147 transaction failed 29189, size 0-0 "

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Android file system is not mounting "binder: 147:147 transaction failed 29189, size 0-0 "

6,066 Views
pushpachennuru
Contributor I

Hi,

         I am porting android lollipop 5.0 to sabre sd board. My android file system is not mounting i am facing the binder issue. even i tried with both 4GB and 8GB sd card also  facing the same issue. Tried with prebuilt images also getting the same problem. Please guide me to resolve this issue.

I am getting the below log

EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: barrier=1

fs_mgr: __mount(source=/dev/block/dm-0,target=/system,type=ext4)=0

fs_mgr: __mount(source=/dev/block/mmcblk2p4,target=/data,type=ext4)=-1

fs_mgr: fs_mgr_mount_all(): possibly an encryptable blkdev /dev/block/mmcblk2p4 for mount /data type ext4 )

fs_mgr: __mount(source=/dev/block/mmcblk2p6,target=/cache,type=ext4)=-1

fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/mmcblk2p6 at /cache options: nomblk_io_submit error: Read-only file system

EXT4-fs (mmcblk2p7): INFO: recovery required on readonly filesystem

EXT4-fs (mmcblk2p7): write access unavailable, cannot proceed

fs_mgr: __mount(source=/dev/block/mmcblk2p7,target=/device,type=ext4)=-1

fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/mmcblk2p7 at /device options: (null) error: Invalid argument

init: fs_mgr_mount_all returned an error

init: fs_mgr_mount_all returned unexpected error 255

SELinux: Could not set context for /cache: Read-only file system

rfkill: BT RF going to : off

binder: 154:154 transaction failed 29189, size 0-0

init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead

init: using deprecated syntax for specifying property 'ro.product.manufacturer', use ${name} instead

init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead

android_usb: already disabled

mtp_bind_config

healthd: BatteryTemperaturePath not found

healthd: BatteryTechnologyPath not found

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

Thanks & Regards,

pushpa teja.c

0 Kudos
5 Replies

2,102 Views
manjunathjoshi
Contributor V

Hi Pushpa,

Hoping you have not solved the issue,

Please check the partitioning of your SD card. That should solve binder issue. If you have solved then you may ignore or post your solution. It will help others.

Regards,

Manju

0 Kudos

2,102 Views
jasonl
Contributor II

Hi Pushpa,

Have you solved the issue yet? I am facing the similar error as you posted. So far I am still not yet found the solution.

Thanks

Jason

0 Kudos

2,102 Views
tftu
Contributor III

Hi Pushpa,

 

    Have you solved this "binder..." issue? We are facing the exact same situation when flashing the Android 5.1 image to sd card. Appreciate any advise or comment!

TF

0 Kudos

2,102 Views
SergioSolis
NXP Employee
NXP Employee

Hello Pushpa,

Do you still get this error when using the demo image from our website?.

Did you do any changes to the android porting you are developing?

0 Kudos

2,102 Views
pushpachennuru
Contributor I

Hi SergioSolis,

                   

Yes still i am facing the same issue with the demo images also. I did changes in  fstab.freescale file to build the images for SD card booting rather than that i dint did any thing the fallowing change i did .

/devices/soc0/soc.1/2100000.aips-bus/2198000.usdhc/mmc_host /mnt/media_rw/extsd vfat defaults voldmanaged=sdcard:auto
/devices/soc0/soc.1/2100000.aips-bus/2184000.usb/ci_hdrc.0  /mnt/media_rw/udisk vfat defaults voldmanaged=sdcard:auto
/dev/block/mmcblk3p5    /system      ext4    rw,barrier=1                                                                               wait,verify
/dev/block/mmcblk3p4    /data        ext4    nosuid,nodev,nodiratime,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic    wait,encryptable=/dev/block/mmcblk3p9
/dev/block/mmcblk3p6    /cache       ext4    rw,nosuid,nodev,nomblk_io_submit                                                    wait
/dev/block/mmcblk3p7    /device      ext4    rw,nosuid,nodev                                                                  wait
/dev/block/mmcblk3p1    /boot        emmc    defaults                                                                         defaults
/dev/block/mmcblk3p2    /recovery    emmc    defaults                                                                         defaults
/dev/block/mmcblk3p8    /misc        emmc    defaults                                                                         defaults

                         But with out doing this change first i fallowed below procedure to build images for SD card booting i faced same issue.

remove  out/target/product/sabresd_6dq/root directory and boot*.img
remove  /out/target/product/sabresd_6dq/recovery directory and recovery*.img
remove  /out/target/product/sabresd_6dq/system directory and system*.img

$ make BUILD_TARGET_DEVICE=sd

Thanks & Regards,

pushpa teja

0 Kudos