Android Oreo 8.0.0 file-system error during usermode build

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

Android Oreo 8.0.0 file-system error during usermode build

Jump to solution
2,953 Views
prasannakulkarni
Contributor IV

Hi,

We are using Android Oreo 8.0.0 OS on imx6dl EVK.  When we build Android in eng mode everything works fine. but there is a issue in mounting file system during usermode build. We need to build usermode images for production release. following are the errors 

1. log_not_booting_userdebug mode  build

ueventd: Coldboot took 0.366633 seconds
keychord: using input dev gpio-keys for fevent
Console: switching to colour dummy device 80x30
watchdogd: watchdogd started (interval 10, margin 20)!
EXT4-fs (mmcblk3p10): Ignoring removed nomblk_io_submit option
EXT4-fs (mmcblk3p10): recovery complete
EXT4-fs (mmcblk3p10): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,noauto_da_alloc,errors=panic
EXT4-fs (mmcblk3p4): Ignoring removed nomblk_io_submit option
EXT4-fs (mmcblk3p4): recovery complete
EXT4-fs (mmcblk3p4): mounted filesystem with ordered data mode. Opts: nomblk_io_submit
EXT4-fs (mmcblk3p9): recovery complete
EXT4-fs (mmcblk3p9): mounted filesystem with ordered data mode. Opts: barrier=1
file system registered
using random self ethernet address
using random host ethernet address
zram0: detected capacity change from 0 to 314572800
mkswap: executing /system/bin/mkswap failed: No such file or directory
mkswap: mkswap terminated by exit(255)

Unable to find swap-space signature
rfkill: BT RF going to : off
audit: type=1400 audit(25218.360:3): avc:  granted  { read } for  pid=1 comm="init" name="ttymxc0" dev="tmpfs" ino=10410 scontext=u:r:init:s0 tcontext=u:object_r:tty_device:s0 tclass=chr_file
audit: type=1400 audit(25218.370:4): avc:  granted  { read open } for  pid=1 comm="init" path="/dev/ttymxc0" dev="tmpfs" ino=10410 scontext=u:r:init:s0 tcontext=u:object_r:tty_device:s0 tclass=chr_file
read descriptors
read strings
android_work: sent uevent USB_STATE=CONNECTED
android_work: sent uevent USB_STATE=DISCONNECTED
android_work: sent uevent USB_STATE=CONNECTED
configfs-gadget gadget: high-speed config #1: b
android_work: sent uevent USB_STATE=CONFIGURED
init: starting service 'bluetooth-1-0'...
init: property_set("ro.boottime.bluetooth-1-0", "22790170002") failed: property already set
init: cannot execve('/vendor/bin/hw/android.hardware.bluetooth@1.0-service'): No such file or directory
init: starting service 'camera-provider-2-4'...
init: couldn't write 257 to /dev/cpuset/camera-daemon/tasks: No such file or directory
init: property_set("ro.boottime.camera-provider-2-4", "22814684002") failed: property already set
init: starting service 'configstore-hal-1-0'...
init: property_set("ro.boottime.configstore-hal-1-0", "22817080335") failed: property already set
init: starting service 'gralloc-2-0'...
init: property_set("ro.boottime.gralloc-2-0", "22819435669") failed: property already set
init: starting service 'bluetooth-1-0'...
init: property_set("ro.boottime.bluetooth-1-0", "27795209003") failed: property already set
init: cannot execve('/vendor/bin/hw/android.hardware.bluetooth@1.0-service'): No such file or directory
init: Service 'bluetooth-1-0' (pid 267) exited with status 127
init: Sending signal 9 to service 'bluetooth-1-0' (pid 267) process group...

#################################end of log 1#######################################  

2. log_booting_eng mode build

ueventd: Coldboot took 0.367731 seconds
keychord: using input dev gpio-keys for fevent
Console: switching to colour dummy device 80x30
watchdogd: watchdogd started (interval 10, margin 20)!
EXT4-fs (mmcblk3p3): mounted filesystem with ordered data mode. Opts: barrier=1
EXT4-fs (mmcblk3p10): Ignoring removed nomblk_io_submit option
EXT4-fs (mmcblk3p10): recovery complete
EXT4-fs (mmcblk3p10): mounted filesystem with ordered data mode. Opts: errors=remount-ro,nomblk_io_submit
e2fsck: e2fsck 1.43.3 (04-Sep-2016)

e2fsck: Pass 1: Checking inodes, blocks, and sizes

e2fsck: Pass 2: Checking directory structure

e2fsck: Pass 3: Checking directory connectivity

e2fsck: Pass 4: Checking reference counts

e2fsck: Pass 5: Checking group summary information

e2fsck:

e2fsck: /dev/block/by-name/userdata: ***** FILE SYSTEM WAS MODIFIED *****

e2fsck: /dev/block/by-name/userdata: 1308/315120 files (8.6% non-contiguous), 66640/1260032 blocks

EXT4-fs (mmcblk3p10): Ignoring removed nomblk_io_submit option
EXT4-fs (mmcblk3p10): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,noauto_da_alloc,errors=panic
EXT4-fs (mmcblk3p4): Ignoring removed nomblk_io_submit option
EXT4-fs (mmcblk3p4): recovery complete
EXT4-fs (mmcblk3p4): mounted filesystem with ordered data mode. Opts: errors=remount-ro,nomblk_io_submit
e2fsck: e2fsck 1.43.3 (04-Sep-2016)

EXT4-fs (mmcblk3p4): Ignoring removed nomblk_io_submit option
EXT4-fs (mmcblk3p4): mounted filesystem with ordered data mode. Opts: nomblk_io_submit
EXT4-fs (mmcblk3p9): mounted filesystem with ordered data mode. Opts: barrier=1
init: 6 output lines suppressed due to ratelimiting
file system registered
using random self ethernet address
using random host ethernet address
logd.auditd: start
logd.klogd: 17904950001
binder: 235:235 ioctl 620a ac0a143 returned -22
zram0: detected capacity change from 0 to 314572800
mkswap: Swapspace size: 307196k, UUID=6d6bb90e-509a-48ec-90be-a88fa9a53b00
Adding 307196k swap on /dev/block/zram0.  Priority:-1 extents:1 across:307196k SS
init: Service 'exec 1 (/system/bin/vdc --wait cryptfs init_user0)' (pid 246) exited with status 0 waiting took 0.160933 seconds
selinux: SELinux: Skipping restorecon_recursive(/data)

init: starting service 'exec 2 (/system/bin/tzdatacheck /system/usr/share/zoneinfo /data/misc/zoneinfo)'...
init: SVC_EXEC pid 250 (uid 1000 gid 1000+0 context default) started; waiting...
init: Service 'exec 2 (/system/bin/tzdatacheck /system/usr/share/zoneinfo /data/misc/zoneinfo)' (pid 250) exited with status 0 waiting took 0.063018 seconds
init: processing action (post-fs-data) from (/init.usb.rc:6)
init: processing action (post-fs-data) from (/init.freescale.rc:282)
init: processing action (post-fs-data) from (/system/etc/init/bootstat.rc:3)
init: processing action (post-fs-data) from (/system/etc/init/logtagd.rc:4)
init: processing action (ro.crypto.state=unencrypted && zygote-start) from (/init.rc:523)
logd.daemon: reinit
rfkill: BT RF going to : off
type=1400 audit(25768.500:3): avc: granted { read } for pid=1 comm="init" name="ttymxc0" dev="tmpfs" ino=10168 scontext=u:r:init:s0 tcontext=u:object_r:tty_device:s0 tclass=chr_file
sabresd_6dq:/ $ read descriptors
read strings
healthd: unable to get HAL interface, using defaults
healthd: No battery devices found
healthd: battery l=100 v=0 t=42.4 h=2 st=2 chg=a
android_work: sent uevent USB_STATE=CONNECTED
android_work: sent uevent USB_STATE=DISCONNECTED
android_work: sent uevent USB_STATE=CONNECTED
configfs-gadget gadget: high-speed config #1: b
android_work: sent uevent USB_STATE=CONFIGURED
ERROR: v4l2 capture: slave not found!
type=1400 audit(25768.500:3): avc: granted { read } for pid=1 comm="init" name="ttymxc0" dev="tmpfs" ino=10168 scontext=u:r:init:s0 tcontext=u:object_r:tty_device:s0 tclass=chr_file
type=1400 audit(25768.500:4): avc: granted { read open } for pid=1 comm="init" path="/dev/ttymxc0" dev="tmpfs" ino=10168 scontext=u:r:init:s0 tcontext=u:object_r:tty_device:s0 tclass=chr_file
type=1400 audit(25768.500:4): avc: granted { read open } for pid=1 comm="init" path="/dev/ttymxc0" dev="tmpfs" ino=10168 scontext=u:r:init:s0 tcontext=u:object_r:tty_device:s0 tclass=chr_file
type=1400 audit(25768.580:5): avc: granted { read } for pid=271 comm="init" name="ttymxc0" dev="tmpfs" ino=10168 scontext=u:r:init:s0 tcontext=u:object_r:tty_device:s0 tclass=chr_file
type=1400 audit(25768.580:5): avc: granted { read } for pid=271 comm="init" name="ttymxc0" dev="tmpfs" ino=10168 scontext=u:r:init:s0 tcontext=u:object_r:tty_device:s0 tclass=chr_file
type=1400 audit(25768.580:6): avc: granted { read open } for pid=271 comm="init" path="/dev/ttymxc0" dev="tmpfs" ino=10168 scontext=u:r:init:s0 tcontext=u:object_r:tty_device:s0 tclass=chr_file
type=1400 audit(25768.580:6): avc: granted { read open } for pid=271 comm="init" path="/dev/ttymxc0" dev="tmpfs" ino=10168 scontext=u:r:init:s0 tcontext=u:object_r:tty_device:s0 tclass=chr_file
type=1400 audit(25769.000:7): avc: denied { write } for pid=270 comm="iptables-restor" name="etc" dev="mmcblk3p3" ino=427 scontext=u:r:netd:s0 tcontext=u:object_r:system_file:s0 tclass=dir permissive=1
type=1400 audit(25769.000:7): avc: denied { write } for pid=270 comm="iptables-restor" name="etc" dev="mmcblk3p3" ino=427 scontext=u:r:netd:s0 tcontext=u:object_r:system_file:s0 tclass=dir permissive=1
type=1400 audit(25769.000:8): avc: denied { add_name } for pid=270 comm="iptables-restor" name="xtables.lock" scontext=u:r:netd:s0 tcontext=u:object_r:system_file:s0 tclass=dir permissive=1
healthd: battery l=100 v=0 t=42.4 h=2 st=2 chg=a
init: starting service 'bootanim'...
random: crng init done
capability: warning: `main' uses 32-bit capabilities (legacy support in use)
init: processing action (sys.interactive=active) from (/init.freescale.rc:172)
period 0 ,timeout is 0, wake up is :0
healthd: battery l=100 v=0 t=42.4 h=2 st=2 chg=a
period 0 ,timeout is 0, wake up is :0
init: processing action (sys.sysctl.extra_free_kbytes=*) from (/init.rc:682)
init: Unable to open '/proc/sys/vm/extra_free_kbytes': No such file or directory


#######################################################################

It has been observed that just by replacing  boot-imx6dl.img of eng mode with boot-imx6dl.img of userdebug build mode device boots normally. kindly help us in solving issue. 

Labels (5)
1 Solution
2,879 Views
prasannakulkarni
Contributor IV

Hi

We have fixed the issue.. It was due to fstab.freescale file. for debugging purpose i  had made 

/dev/block/by-name/system       /system      ext4    rw,barrier=1 --> this works fine for eng mode but Other modes

(usr / usrdebug) needs this mounting to be in read only option . So I have changed this back to ro mode 

/dev/block/by-name/system       /system      ext4    ro,barrier=1

Then using mfg tool I have flashed usr mode images. It booted properly.

View solution in original post

2 Replies
2,880 Views
prasannakulkarni
Contributor IV

Hi

We have fixed the issue.. It was due to fstab.freescale file. for debugging purpose i  had made 

/dev/block/by-name/system       /system      ext4    rw,barrier=1 --> this works fine for eng mode but Other modes

(usr / usrdebug) needs this mounting to be in read only option . So I have changed this back to ro mode 

/dev/block/by-name/system       /system      ext4    ro,barrier=1

Then using mfg tool I have flashed usr mode images. It booted properly.

2,879 Views
gusarambula
NXP TechSupport
NXP TechSupport

Hello Prasanna Kulkarni,

Thank you for updating this case with your findings! I'm sure it will help other Community users!

Regards,