Nanopi Duo (allwinner H2+) kernel panic

[ratnarajsbc]

Hi,

For long (long) time I did not update my nano pi duo image, recently I changed microSD card and wanted start fresh with latest image.

 

I have tried latest debian image and also tried building image for the BOARD target as `nanopiduo`, but in in both cases my board is stuck at ...
 

U-Boot SPL 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-Va723-Bb703-R448a (Mar 09 2025 - 03:54:39 +0000)
DRAM: 128 MiB                           
Trying to boot from MMC1                
ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19
                                        
                                        
U-Boot 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-Va723-Bb703-R448a (Mar 09 2025 - 03:54:39 +0000) Allwinner Technology
                                        
CPU:   Allwinner H3 (SUN8I 1680)        
Model: FriendlyARM NanoPi DUO           
DRAM:  128 MiB
Core:  57 devices, 16 uclasses, devicetree: separate
WDT:   Not starting watchdog@1c20ca0
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial,usbkbd
Out:   serial
Err:   serial
Net:   No ethernet found.
starting USB...
No working controllers found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
5475 bytes read in 6 ms (890.6 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
182 bytes read in 6 ms (29.3 KiB/s)
Load fdt: /boot/dtb/sun8i-h2-plus-nanopi-duo.dtb
8431400 bytes read in 357 ms (22.5 MiB/s)
11476944 bytes read in 484 ms (22.6 MiB/s)
Found mainline kernel configuration
36294 bytes read in 20 ms (1.7 MiB/s)
Working FDT set to 43000000
504 bytes read in 17 ms (28.3 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo
504 bytes read in 17 ms (28.3 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo
4185 bytes read in 17 ms (240.2 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 45000000
Kernel image @ 0x42000000 [ 0x000000 - 0xaf1fd0 ]
## Loading init Ramdisk from Legacy Image at 43400000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    8431336 Bytes = 8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
Working FDT set to 43000000
   Loading Ramdisk to 497f5000, end 49fff6e8 ... OK
   Loading Device Tree to 42ee4000, end 42f55fff ... OK
Working FDT set to 42ee4000

Starting kernel ...

[    2.314576] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    2.322869] CPU: 2 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.43-current-sunxi #1
[    2.330722] Hardware name: Allwinner sun8i Family
[    2.335438] Call trace: 
[    2.335467]  unwind_backtrace from show_stack+0x11/0x14
[    2.343286]  show_stack from dump_stack_lvl+0x37/0x42
[    2.348377]  dump_stack_lvl from panic+0xc9/0x278
[    2.353116]  panic from mount_root_generic+0x171/0x1f4
[    2.358299]  mount_root_generic from prepare_namespace+0x161/0x1ae
[    2.364527]  prepare_namespace from kernel_init_freeable+0x1f9/0x20a
[    2.370928]  kernel_init_freeable from kernel_init+0x21/0x100
[    2.376720]  kernel_init from ret_from_fork+0x11/0x1c
[    2.381808] Exception stack(0xc8821fb0 to 0xc8821ff8)
[    2.386881] 1fa0:                                     00000000 00000000 00000000 00000000
[    2.395074] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    2.403265] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[    2.410060] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

 

In older images, CPU was detected as `Allwinner H2+`, however now it's detecting as H3.

I have tried couple other SD cards, with same error.

 

What config I can try to get my `nanopi duo` working?

offtopic: I tried images available from  friendlyelec drive, which are getting stuck at "Starting kernel".

[Werner]

3 minutes ago, ratnarajsbc said:

was detected as `Allwinner H2+`, however now it's detecting as H3.

Hm that should not be a BIG issue since H2+ and H3 are quite similar, just a few features were stripped IIRC.

3 minutes ago, ratnarajsbc said:

friendlyelec drive, which are getting stuck at "Starting kernel".

I don't know for their images but I assume there is something similar like Armbian has. Edit /boot/armbianEnv.txt and set verbosity to 7 to increase the output of the kernel while it is starting. So you may know why it is stuck.

 

Overall I'd recommend to try some older images like https://fi.mirror.armbian.de/archive/nanopiduo/archive/

or https://fi.mirror.armbian.de/oldarchive/nanopiduo/archive/

and then bump kernel step by step via armbian-config to know where it starts failing.

[ratnarajsbc]

Hey @Werner Thanks for quick reply.

I tested with verbosity=7, may be correct fs driver is not loading?
 

[    4.103985] /dev/root: Can't open blockdev
[    4.108224] VFS: Cannot open root device "UUID=dc3421ab-734e-47cb-8f5d-5b8ffecf9484" or unknown-block(0,0): error -6
[    4.118847] Please append a correct "root=" boot option; here are the available partitions:
[    4.127246] 0100            4096 ram0 
[    4.127265]  (driver?)
[    4.133442] 0101            4096 ram1 
[    4.133458]  (driver?)
[    4.139623] 0102            4096 ram2 
[    4.139639]  (driver?)
[    4.145787] 0103            4096 ram3 
[    4.145803]  (driver?)
[    4.151982] b300        15558144 mmcblk0 
[    4.151999]  driver: mmcblk
[    4.158846]   b301         1060864 mmcblk0p1 a9741697-01
[    4.158866] 
[    4.165738] List of all bdev filesystems:
[    4.169781]  ext3
[    4.169792]  ext2
[    4.171748]  ext4
[    4.173685]  squashfs
[    4.175645]  vfat
[    4.177929]  fuseblk
[    4.179888]  f2fs
[    4.182086]  btrfs
[    4.184046] 
[    4.187565] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    4.195841] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.43-current-sunxi #1
[    4.203689] Hardware name: Allwinner sun8i Family
[    4.208406] Call trace: 
[    4.208435]  unwind_backtrace from show_stack+0x11/0x14
[    4.216251]  show_stack from dump_stack_lvl+0x37/0x42
[    4.221341]  dump_stack_lvl from panic+0xc9/0x278
[    4.226080]  panic from mount_root_generic+0x171/0x1f4
[    4.231264]  mount_root_generic from prepare_namespace+0x161/0x1ae
[    4.237491]  prepare_namespace from kernel_init_freeable+0x1f9/0x20a
[    4.243893]  kernel_init_freeable from kernel_init+0x21/0x100
[    4.249686]  kernel_init from ret_from_fork+0x11/0x1c
[    4.254774] Exception stack(0xc8821fb0 to 0xc8821ff8)
[    4.259847] 1fa0:                                     00000000 00000000 00000000 00000000
[    4.268041] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    4.276231] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[    4.282974] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

my next steps, 
- testing image from oldarchieve
- experiment rebuilding armbian with kernel menuconfig?

 

[going]

13 часов назад, ratnarajsbc сказал:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

This is similar to physical damage to the SD card