search

siemens / meta-iot2050

SIMATIC IOT2050 Isar/Debian Board Support Package
MIT License
129 stars 76 forks source link

Can't find the root device with matching UUID! #441

Closed SCordibella closed 1 year ago

SCordibella commented 1 year ago

Dear all, I am trying to run a custom swupdate-image on a real device. Unforunately my image doesn't boot and I have the following error (full log here):

Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... [    4.867698] EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts: (null)
[    4.916963] EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: (null)
Begin: Waiting for IMAGE_UUID=cd87ddf8-0c1c-46e3-ae41-a0c653316ce9 ... [   13.389476] tidss 4a00000.dss: [drm] Cannot find any crtc or sizes
[   16.783164] random: crng init done

[   33.867190] tps62363-vout: disabling
done.
Can't find the root device with matching UUID!
(initramfs) (initramfs) (initramfs)

My image recipe just inherit from swu-example and add some packages.

It could be related to this?

Best regards, Stefano.

jan-kiszka commented 1 year ago

Initrd and rootfs need to be in lock-step. Your initrd is carrying the UUID cd87ddf8-0c1c-46e3-ae41-a0c653316ce9, but none the rootfs have that (you find it in /etc/os-release there). This might be due to some transient build issues, e.g. when doing a partial rebuild (or was this a clean build from scratch?). Or it could be caused by the customizations you did on top of meta-iot2050. I assume you tried a original swupdate image from this layer already as well and found it working?

SCordibella commented 1 year ago

Hi @jan-kiszka , yes, an original swupdate image works as expected. My custom build was a clean build from scratch. I think that is problem could be related to the swupdate image inheritance. If I extend the swupdate image through a bbappend instead of inherit with a require recipes-core/images/iot2050-image-swu-example.bb I am able to boot. Also the problem reported here about dtb clash in deploy dir disappear if I extend swupdate image via bbappend.

For now I will proceed extending swupdate example image via bbappend.

jan-kiszka commented 1 year ago

Let's close this for now. If you find out more details about the issue without bbappend, feel free to reopen.