# Pynq image boot error: end kernel panic -not syncing VFS : unable to mount root f-

**URL:** <https://discuss.pynq.io/t/pynq-image-boot-error-end-kernel-panic-not-syncing-vfs-unable-to-mount-root-f/3191>\
**Category:** Support\
**Created:** [October 25, 2021, 11:37am UTC](https://discuss.pynq.io/t/pynq-image-boot-error-end-kernel-panic-not-syncing-vfs-unable-to-mount-root-f/3191 "2021-10-25T11:37:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vijaykumarvg1](https://avatars.discourse-cdn.com/v4/letter/v/b38774/32.png) [@vijaykumarvg1](https://discuss.pynq.io/u/vijaykumarvg1)\
**Post date:** [October 25, 2021, 11:37am UTC](https://discuss.pynq.io/t/pynq-image-boot-error-end-kernel-panic-not-syncing-vfs-unable-to-mount-root-f/3191/1 "2021-10-25T11:37:12Z")

</div>

Hi,

When I tried to boot the Pynq image on the custom Xilinx ultrascale scale board I got the following error. I tried changing a few things in the devicetree but no effect.

4.433994] mmcblk0: mmc0:0001 00016G 14.6 GiB  
[4.438751] mmcblk0boot0: mmc0:0001 00016G partition 1 4.00 MiB  
[4.444898] mmcblk0boot1: mmc0:0001 00016G partition 2 4.00 MiB  
[4.451639] cfg80211: Loaded X.509 cert ‘sforshee: 00b28ddf47aef9cea7’  
[4.458172] clk: Not disabling unused clocks  
[4.462444] ALSA device list:  
[4.465411] No soundcards found.  
[4.469171] platform regulatory.0: Direct firmware load for regulatory.db fa2  
[4.477783] cfg80211: failed to load regulatory.db  
[4.482622] mmcblk0rpmb: mmc0:0001 00016G partition 3 4.00 MiB, chardev (244)  
[4.493267] VFS: Cannot open root device “mmcblk0p2” or unknown-block(179,2)6  
[4.501199] Please append a correct “root=” boot option; here are the availa:  
[4.509552] 0100 65536 ram0  
[4.509553] (driver?)  
[4.515648] 0101 65536 ram1  
[4.515649] (driver?)  
[4.521747] 0102 65536 ram2  
[4.521748] (driver?)  
[4.527843] 0103 65536 ram3  
[4.527844] (driver?)  
[4.533942] 0104 65536 ram4  
[4.533943] (driver?)  
[4.540039] 0105 65536 ram5  
[4.540040] (driver?)  
[4.540176] usb 1-1: new high-speed USB device number 2 using xhci-hcd  
[4.543786] 0106 65536 ram6  
[4.543788] (driver?)  
[4.558735] 0107 65536 ram7  
[4.558737] (driver?)  
[4.564834] 0108 65536 ram8  
[4.564835] (driver?)  
[4.570931] 0109 65536 ram9  
[4.570932] (driver?)  
[4.577031] 010a 65536 ram10  
[4.577032] (driver?)  
[4.583213] 010b 65536 ram11  
[4.583214] (driver?)  
[4.589398] 010c 65536 ram12  
[4.589399] (driver?)  
[4.595582] 010d 65536 ram13  
[4.595583] (driver?)  
[4.601767] 010e 65536 ram14  
[4.601768] (driver?)  
[4.607942] 010f 65536 ram15  
[4.607943] (driver?)  
[4.614129] b300 15269888 mmcblk0  
[4.614130] driver: mmcblk  
[4.620924] Kernel panic - not syncing: VFS: Unable to mount root fs on unkn)  
[4.629352] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.4.0-xilinx-v2020.1 #1  
[4.636473] Hardware name: xlnx,zynqmp (DT)  
[4.640647] Call trace:  
[4.643092] dump\_backtrace+0x0/0x140  
[4.646742] show\_stack+0x14/0x20  
[4.650051] dump\_stack+0xac/0xd0  
[4.653356] panic+0x140/0x2f8  
[4.656404] mount\_block\_root+0x1d0/0x284  
[4.660404] mount\_root+0x124/0x158  
[4.663885] prepare\_namespace+0x15c/0x1a4  
[4.667973] kernel\_init\_freeable+0x234/0x258  
[4.672323] kernel\_init+0x10/0xfc  
[4.675716] ret\_from\_fork+0x10/0x18  
[4.679285] SMP: stopping secondary CPUs  
[4.683199] Kernel Offset: disabled  
[4.686678] CPU features: 0x0002,20002004  
[4.690677] Memory Limit: none  
[4.693720] —[end Kernel panic - not syncing: VFS: Unable to mount root f-[log.txt](https://discuss.pynq.io/uploads/short-url/6aeMYk4si7tczNoPp755z2BKAKs.txt) (35.3 KB)

Here attaching the log file for reference.

---

<div class="post-metadata">

**Author:** ![zheng\_yue](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/zheng_yue/32/4931_2.png) [@zheng\_yue](https://discuss.pynq.io/u/zheng_yue)\
**Post date:** [February 5, 2024, 4:33pm UTC](https://discuss.pynq.io/t/pynq-image-boot-error-end-kernel-panic-not-syncing-vfs-unable-to-mount-root-f/3191/2 "2024-02-05T16:33:17Z")

</div>

Have you resolved it? I encountered the same problem
