AnsweredAssumed Answered

wrong boot device at kernel/ramdisk boot stage... where should I look in to solve this?

Question asked by chadrick kwag on Mar 31, 2016
Latest reply on Apr 5, 2016 by chadrick kwag

after uboot, I am having trouble booting kernel. comparing the logs with a properly booting sd card, I believe the problem is due to the fact that the kernel(or ramdisk) is configured to boot from the wrong device.

 

here is the problematic snippet of the log:

====

UTC (2)

ALSA device list:

  #0: wm8962-audio

  #1: imx-hdmi-soc

Freeing unused kernel memory: 432K (c0be3000 - c0c4f000)

audit: type=1403 audit(2.640:2): policy loaded auid=4294967295 ses=4294967295

audit: type=1404 audit(2.650:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295

Console: switching to colour dummy device 80x30

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

fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/mmcblk3p5 at /system options: barrier=1 error: No such file or directory

random: nonblocking pool is initialized

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

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

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

fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/mmcblk3p6 at /cache options: nomblk_io_submit error: No such file or directory

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

fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/mmcblk3p7 at /device options: (null) error: No such file or directory

init: fs_mgr_mount_all returned an error

init: fs_mgr_mount_all returned unexpected error 255

======

 

meanwhile this is the same part of the properly booting log

======

ALSA device list:

  #0: wm8962-audio

  #1: imx-hdmi-soc

Freeing unused kernel memory: 432K (c0be3000 - c0c4f000)

audit: type=1403 audit(2.670:2): policy loaded auid=4294967295 ses=4294967295

audit: type=1404 audit(2.680:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295

Console: switching to colour dummy device 80x30

bio: create slab <bio-1> at 1

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

EXT4-fs (mmcblk2p4): Ignoring removed nomblk_io_submit option

EXT4-fs (mmcblk2p4): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,noauto_da_alloc,errors=panic

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

EXT4-fs (mmcblk2p6): Ignoring removed nomblk_io_submit option

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

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

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

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

Adding 307196k swap on /dev/block/zram0.  Priority:-1 extents:1 across:307196k SS

======

 

as you can see, the proper configuration should be to boot from 'mmcblk2' while the the problematic sd card image boot from 'mmcblk3'.

 

Which part should I look into to fix this issue?

Am I right to think that the problem is in the ramdisk image since all this 'mounting' is a procedure due to executing '/init' which is located in the ramdisk?

Outcomes