AnsweredAssumed Answered

Failed to mount system image!

Question asked by Oliver Kuo on Oct 5, 2015
Latest reply on Jul 6, 2016 by Oliver Kuo

Hi,

 

  I'm trying to port Android L5.0.0-1.0.0 on our custom board, but fail to boot into system image.

From the boot log, looks like VERITY_METADATA_MAGIC_NUMBER can't be read and fail to mount mmcblk3p5.

fs_mgr: Couldn't find verity metadata at offset 0!

fs_mgr: Could not set up verified partition, skipping!

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,noauto_da_alloc,errors=panic

fs_mgr: __mount(source=/dev/block/mmcblk3p4,target=/data,type=ext4)=0

EXT4-fs (mmcblk3p6): Ignoring removed nomblk_io_submit option

EXT4-fs (mmcblk3p6): recovery complete

EXT4-fs (mmcblk3p6): mounted filesystem with ordered data mode. Opts: nomblk_io_submit

fs_mgr: __mount(source=/dev/block/mmcblk3p6,target=/cache,type=ext4)=0

EXT4-fs (mmcblk3p7): mounted filesystem with ordered data mode. Opts: (null)

fs_mgr: __mount(source=/dev/block/mmcblk3p7,target=/device,type=ext4)=0

Could someone give me a hint which step or setting I missed?

What should I do to keep verified boot enabled and mount system image successfully, except "androidboot.dm_verity=disabled"?

 

Thanks,

Oliver

Original Attachment has been moved to: boot_failed.log.zip

Outcomes