rootfs image is not initramfs (write error); looks like an initrd

[mihaitaivascu]

Hello,

    I have the following situation on imx6ul platforms: trying to modify the default u-boot settings for KERNEL load addr in order to free more memory for the second OS that runs on core #1.

    So I modified kernel load/entry from 0x10008000 t o0x20008000 and ramdisk load/entry from 0x18000000 to 0x28000000. RAM size is 1GB

    But my kernel crashed now with the following issue:

  0.510417] Trying to unpack rootfs image as initramfs...
[ 3.436372] rootfs image is not initramfs (write error); looks like an initrd
[ 3.443581] /initrd.image: incomplete write (-28 != 50405002)
[ 3.501259] Freeing initrd memory: 49224K (8c2e8000 - 8f2fa000)

.....................................................................................................................................

4.034506] RAMDISK: Couldn't find valid RAM disk image starting at 0.
[ 4.041137] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[ 4.048615] Please append a correct "root=" boot option; here are the available partitions:

I have tried to add ramdisk_size parameter in kernel bootargs to 50405002 as suggested in other posts but the crash is still happening.

Does anybody have any suggestion on how to fix this issue?

Thanks,

      Mihaita

[b36401]

Please make sure that you placed rootfs at right place of the media you are booting the OS from.

Have a great day,
Victor

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[mihaitaivascu]

Hello,

   Thank you for your reply but I don't think is related to my question.

    In my case I have only changed the load/entry address for kernel and ramdisk in device tree.

    The boot device is as always SPI nor flash, only that in this case the kernel crashes.

Best regards,

         Mihaita

[b36401]

I mean it seems the kernel is unable to load ramdisk from this new place.

[mihaitaivascu]

There is no new place. Just changed the offset in RAM where the .itb image should unpack the ramdisk and kernel:

 For me it appeared once I changed the load/entry addresses for kernel and ramdisk in the device tree.

    Before it was 0x10008000/0x18000000, now is 0x20008000/0x28000000. RAM is 1G.

Best regards,

         Mihaita

[b36401]

By the way. Did you update the address in kernel options in u-boot environment?

[b36401]

Possibly this new place where you moved ramdisk is located on faulty memory.

Please try to perform memory test:
https://community.nxp.com/docs/DOC-105652