cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Contributor
Contributor
188 Views
Registered: ‎06-03-2018

PetaLinux build image failed with corrupted RAMDISK

Hello folks,

 

PetaLinux sporadically building corrupted image.

What can cause this issue?

Is this some configuration problem ?

 

[ 12.000712] mmc0: new HS200 MMC card at address 0001
[ 12.006244] mmcblk0: mmc0:0001 Q2J54A 1.80 GiB
[ 12.010983] mmcblk0boot0: mmc0:0001 Q2J54A partition 1 16.0 MiB

[ 12.017114] mmcblk0boot1: mmc0:0001 Q2J54A partition 2 16.0 MiB

[ 12.023177] mmcblk0rpmb: mmc0:0001 Q2J54A partition 3 512 KiB, chardev (246:0)
[ 13.126680] RAMDISK: incomplete write (17670 != 30473)
[ 13.131831] write error
[ 13.134412] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[ 13.141913] Please append a correct "root=" boot option; here are the available partitions:
[ 13.150269] 0100 65536 ram0
[ 13.150270] (driver?)
[ 13.156364] 0101 65536 ram1
[ 13.156365] (driver?)
[ 13.162462] 0102 65536 ram2
[ 13.162466] (driver?)
[ 13.168558] 0103 65536 ram3
[ 13.168559] (driver?)
[ 13.174656] 0104 65536 ram4
[ 13.174657] (driver?)
[ 13.180750] 0105 65536 ram5
[ 13.180751] (driver?)
[ 13.186844] 0106 65536 ram6
[ 13.186845] (driver?)
[ 13.192946] 0107 65536 ram7
[ 13.192947] (driver?)
[ 13.199042] 0108 65536 ram8
[ 13.199043] (driver?)
[ 13.205140] 0109 65536 ram9
[ 13.205141] (driver?)
[ 13.211229] 010a 65536 ram10
[ 13.211230] (driver?)
[ 13.217415] 010b 65536 ram11
[ 13.217416] (driver?)
[ 13.223598] 010c 65536 ram12
[ 13.223599] (driver?)
[ 13.229783] 010d 65536 ram13
[ 13.229784] (driver?)
[ 13.235958] 010e 65536 ram14
[ 13.235959] (driver?)
[ 13.242144] 010f 65536 ram15
[ 13.242145] (driver?)
[ 13.248333] 1f00 2048 mtdblock0
[ 13.248334] (driver?)
[ 13.254869] 1f01 2048 mtdblock1
[ 13.254870] (driver?)
[ 13.261404] 1f02 6144 mtdblock2
[ 13.261406] (driver?)
[ 13.267935] 1f03 16384 mtdblock3
[ 13.267936] (driver?)
[ 13.274469] 1f04 4096 mtdblock4
[ 13.274470] (driver?)
[ 13.281005] 1f05 6144 mtdblock5
[ 13.281006] (driver?)
[ 13.287535] 1f06 86016 mtdblock6
[ 13.287536] (driver?)
[ 13.294067] 1f07 8064 mtdblock7
[ 13.294068] (driver?)
[ 13.300598] 1f08 128 mtdblock8
[ 13.300599] (driver?)
[ 13.307126] b300 1884160 mmcblk0
[ 13.307128] driver: mmcblk
[ 13.313920] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 13.322181] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.4.0-xilinx-v2020.1 #1
[ 13.329302] Hardware name: xlnx,zynqmp (DT)
[ 13.333476] Call trace:
[ 13.335920] dump_backtrace+0x0/0x140
[ 13.339570] show_stack+0x14/0x20
[ 13.342879] dump_stack+0xac/0xd0
[ 13.346185] panic+0x140/0x308
[ 13.349233] mount_block_root+0x1d0/0x284
[ 13.353233] mount_root+0x124/0x158
[ 13.356714] prepare_namespace+0x15c/0x1a4
[ 13.360803] kernel_init_freeable+0x238/0x25c
[ 13.365150] kernel_init+0x10/0xfc
[ 13.368545] ret_from_fork+0x10/0x18
[ 13.372114] SMP: stopping secondary CPUs
[ 13.376027] Kernel Offset: disabled
[ 13.379506] CPU features: 0x0002,20002004
[ 13.383507] Memory Limit: none
[ 13.386549] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

 

Regards,

Kayas Ahmed

0 Kudos
4 Replies
Highlighted
Moderator
Moderator
120 Views
Registered: ‎12-04-2016

Hi @kayas257 

Try to format SD card to create 2 partitions and copy the ext4 formattted rootfs to the 2nd partition

 

Regards

Shabbir

0 Kudos
Highlighted
Moderator
Moderator
108 Views
Registered: ‎02-07-2018

HI @kayas257 

Can you please share the complete boot logs, that will help us to find the root cause of this issue.

we can see this kind of issues only when the bootargs are wrong.

 

Thanks & regards

Aravind

----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
---------------------------------------------------------------------------------------------

0 Kudos
Highlighted
Contributor
Contributor
86 Views
Registered: ‎06-03-2018

Hi @shabbirk,

Thanks for your reply, 

Actually, I am not using an SD card for RFS, it's a read-only RFS using ramdisk which is wrapped with kernel image using fit image.

 

Thanks,

Kayas Ahmed

0 Kudos
Highlighted
Contributor
Contributor
85 Views
Registered: ‎06-03-2018

Hello @aravindb,

I don't think the problem is with bootargs,  as I mentioned before it is an RO file system. any I will post an early kernel log soon.

 

Thanks,

Kayas Ahmed

0 Kudos