cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Adventurer
Adventurer
3,130 Views
Registered: ‎11-26-2018

Petalinux 2019.2: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)

Hi,

I've created a new petalinux 2019.2 project, I set the boot to sd-card, but when I turn on the zcu106 board I get a kernel panic error:

[    6.917181] Buffer I/O error on dev mmcblk0, logical block 0, async page read
[    6.924319]  mmcblk0: unable to read partition table
[    6.929832] VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2): error -6
[    6.937747] Please append a correct "root=" boot option; here are the available partitions:
[    6.946097] 0100           65536 ram0
[    6.946098]  (driver?)
[    6.952193] 0101           65536 ram1
[    6.952194]  (driver?)
[    6.958293] 0102           65536 ram2
[    6.958295]  (driver?)
[    6.964380] 0103           65536 ram3
[    6.964382]  (driver?)
[    6.970479] 0104           65536 ram4
[    6.970480]  (driver?)
[    6.976568] 0105           65536 ram5
[    6.976570]  (driver?)
[    6.982667] 0106           65536 ram6
[    6.982668]  (driver?)
[    6.988756] 0107           65536 ram7
[    6.988758]  (driver?)
[    6.994846] 0108           65536 ram8
[    6.994847]  (driver?)
[    7.000927] 0109           65536 ram9
[    7.000928]  (driver?)
[    7.007016] 010a           65536 ram10
[    7.007018]  (driver?)
[    7.013184] 010b           65536 ram11
[    7.013186]  (driver?)
[    7.019369] 010c           65536 ram12
[    7.019371]  (driver?)
[    7.025537] 010d           65536 ram13
[    7.025538]  (driver?)
[    7.031714] 010e           65536 ram14
[    7.031715]  (driver?)
[    7.037886] 010f           65536 ram15
[    7.037887]  (driver?)
[    7.044056] 1f00            1024 mtdblock0
[    7.044058]  (driver?)
[    7.050577] 1f01             256 mtdblock1
[    7.050579]  (driver?)
[    7.057092] 1f02           22528 mtdblock2
[    7.057094]  (driver?)
[    7.063615] b300        15558144 mmcblk0
[    7.063617]  driver: mmcblk
[    7.070395] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
[    7.078821] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.19.0-xilinx-v2019.2 #1
[    7.086031] Hardware name: ZynqMP ZCU106 RevA (DT)
[    7.090806] Call trace:
[    7.093244]  dump_backtrace+0x0/0x148
[    7.096893]  show_stack+0x14/0x20
[    7.100193]  dump_stack+0x90/0xb4
[    7.103499]  panic+0x120/0x268
[    7.106538]  mount_block_root+0x1b0/0x260
[    7.110530]  mount_root+0x11c/0x148
[    7.114002]  prepare_namespace+0x158/0x1a0
[    7.118082]  kernel_init_freeable+0x1b8/0x1d4
[    7.122425]  kernel_init+0x10/0xfc
[    7.125817]  ret_from_fork+0x10/0x18
[    7.129378] SMP: stopping secondary CPUs
[    7.133292] Kernel Offset: disabled
[    7.136763] CPU features: 0x0,20802004
[    7.140495] Memory Limit: none
[    7.143538] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2) ]---

 I recreated the project, but I always get that error.

0 Kudos
15 Replies
Highlighted
Moderator
Moderator
3,073 Views
Registered: ‎12-04-2016

Hi andrea@ross 

I hope you have rootfs copied to the second partition of SD card. As per log, kernel expecting rootfs to be in second partition

 

Best Regards

Shabbir

0 Kudos
Highlighted
Adventurer
Adventurer
3,055 Views
Registered: ‎11-26-2018

I've created the sd patition like in 2019.1, but I get that error. This is my sd-card:
sdcard.jpg

In BOOT there are: BOOT.bin and image.ub

In rootfs there are: rootfs.tar.gz (extract) and rootfs.cpio

0 Kudos
Highlighted
Contributor
Contributor
2,955 Views
Registered: ‎11-02-2017

Modify the device tree!

     / {

           chosen {

                           bootargs = "earlycon clk_ignore_unused consoleblank=0 cma=1700M uio_pdrv_genirq.of_id=generic-uio root=/dev/mmcblk0p2 rootfstype=ext4 rw rootwait ";

                           stdout-path = "serial0:115200n8";

                        };

             };

but  I donot know why?

 

0 Kudos
Highlighted
Adventurer
Adventurer
2,920 Views
Registered: ‎11-26-2018

I tried to modify the device tree, but without success. I stil get the same error, if I try to do 

mmc rescan

I get this error:

arasan_sdhci_execute_tuning:Tuning failed
sdhci_set_clock: Timeout to wait cmd & data inhibit
sdhci_set_clock: Timeout to wait cmd & data inhibit

 

0 Kudos
Highlighted
Contributor
Contributor
2,892 Views
Registered: ‎11-02-2017

I also encountered this problem.But I found some differences

2019.1(right)

[ 6.694469] mmcblk0: mmc0:aaaa SB16G 14.8 GiB
[ 6.703180] mmcblk0: p1 p2

2019.2(wrong)

[ 5.320066] mmcblk0: mmc0:aaaa SB16G 14.8 GiB
[ 5.362236] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'

Print information shows that the SD card boot partition is not recognized!

0 Kudos
Highlighted
Adventurer
Adventurer
2,867 Views
Registered: ‎09-05-2018

Seams that the kernel don't read your partition table

[    7.063615] b300        15558144 mmcblk0
[    7.063617]  driver: mmcblk

note b300 is b3h=179 / 00

the kernel is searching for a device (179,2)

1- you need to check the harware

2- reformat the card w/o GPT

0 Kudos
Highlighted
Teacher
Teacher
2,835 Views
Registered: ‎06-16-2013

Hi andrea@ross 

 

Make sure the followings.

 

- write protection for SD card.

- broken sector on SD card.

 

I guess you use ex. UltraZed.

If yes, it's write protection issue.

You muse set low on write protection port.

 

Best regards,

0 Kudos
Highlighted
Adventurer
Adventurer
2,809 Views
Registered: ‎11-26-2018

I'm using the zcu106 board.

The sd-card is ok

0 Kudos
Highlighted
Adventurer
Adventurer
2,768 Views
Registered: ‎09-05-2018

try to reformat the SD card by erasing it with dd

dd if=/dev/zero of=/dev/sd<X> bs=1M

be carefull on the /dev/sd<X> device that identify exactly your SD card and not your internal disk

then format it with fdisk dont' use gpartd and don't leave 4M free at the beginning

here is an example of my SD card

Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 2048 526335 524288 256M c W95 FAT32 (LBA)
/dev/mmcblk0p2 526336 14942207 14415872 6.9G 5 Extended
/dev/mmcblk0p5 528384 6819839 6291456 3G 83 Linux
/dev/mmcblk0p6 6821888 13113343 6291456 3G 83 Linux
/dev/mmcblk0p7 13115392 13135871 20480 10M 83 Linux
/dev/mmcblk0p8 13137920 13342719 204800 100M 83 Linux
/dev/mmcblk0p9 13344768 14942207 1597440 780M 83 Linux

 

0 Kudos
Highlighted
Adventurer
Adventurer
2,741 Views
Registered: ‎11-26-2018

I tried formatting with fdisk, but I get the same error, in one test I get this error " Bad Linux ARM64 Image magic! ".

 mmc_part.jpg

mmc_list.jpg

0 Kudos
Highlighted
Adventurer
Adventurer
2,709 Views
Registered: ‎09-05-2018

You could also check the system.dts 

&sdhci0 {
	status = "okay";
	xlnx,has-cd = <0x1>;
	xlnx,has-power = <0x0>;
	xlnx,has-wp = <0x1>;
	disable-wp;
	no-1-8-v;
};
0 Kudos
Highlighted
Observer
Observer
2,601 Views
Registered: ‎09-10-2018

Anyone solved it?
I have exact same issue. Tried with different bootargs, doesn't work.

0 Kudos
Highlighted
Contributor
Contributor
2,474 Views
Registered: ‎11-02-2017

这个说明是正确的,,造成这个结果的原因是BSP 里面设备树的问题,导致系统无法识别SD卡分区!详细可参考一下网址,已验证成功!

https://www.xilinx.com/support/answers/73079.html

0 Kudos
Highlighted
Visitor
Visitor
2,384 Views
Registered: ‎12-09-2017

Hello All

I have the same problem ( 2018.3 works fine ...)

setting  "no-1-8-v"  didn't help.

any ideas ?

0 Kudos
Highlighted
Adventurer
Adventurer
2,256 Views
Registered: ‎11-05-2018

 Any solutions to this problem, I get a similar message:

 

VFS: Unable to mount root fs on unknown-block(0,0)

0 Kudos