Hello,

I have just updated the latest kernel available on my sbc orangepi+2e with the armbian-config tool and after that it no longer boots. After plugging in the serial port it complains

"## Executing script at 44000000

Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid".

How can I fix it without having to reinstall everything? I run home-assistant and all the data is on emmc.

 

 

U-Boot 2019.04-armbian (Jul 15 2019 - 18:03:30 +0200) Allwinner Technology      
                                                                                
CPU:   Allwinner H3 (SUN8I 1680)                                                
Model: Xunlong Orange Pi Plus 2E                                                
DRAM:  2 GiB                                                                    
MMC:   Device 'mmc@1c11000': seq 1 is in use by 'mmc@1c10000'                   
mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1                                  
Loading Environment from EXT4... MMC: no card present                           
In:    serial                                                                   
Out:   serial                                                                   
Err:   serial                                                                   
Net:   phy interface7                                                           
eth0: ethernet@1c30000                                                          
MMC: no card present                                                            
MMC: no card present                                                            
starting USB...                                                                 
USB0:   USB EHCI 1.00                                                           
USB1:   USB OHCI 1.0                                                            
USB2:   USB EHCI 1.00                                                           
USB3:   USB OHCI 1.0                                                            
USB4:   USB EHCI 1.00                                                           
USB5:   USB OHCI 1.0                                                            
USB6:   USB EHCI 1.00                                                           
USB7:   USB OHCI 1.0                                                            
scanning bus 0 for devices... 1 USB Device(s) found                             
scanning bus 1 for devices... 1 USB Device(s) found                             
scanning bus 2 for devices... 1 USB Device(s) found                             
scanning bus 3 for devices... 1 USB Device(s) found                             
scanning bus 4 for devices... 1 USB Device(s) found                             
scanning bus 5 for devices... 1 USB Device(s) found                             
scanning bus 6 for devices... 1 USB Device(s) found                             
scanning bus 7 for devices... 1 USB Device(s) found                             
       scanning usb for storage devices... 0 Storage Device(s) found            
Autoboot in 1 seconds, press <Space> to stop                                    
switch to partitions #0, OK                                                     
mmc1(part 0) is current device                                                  
Scanning mmc 1:1...                                                             
Found U-Boot script /boot/boot.scr                                              
3798 bytes read in 2 ms (1.8 MiB/s)                                             
## Executing script at 43100000                                                 
U-boot loaded from eMMC or secondary SD                                         
MMC: no card present                                                            
Boot script loaded from mmc                                                     
283 bytes read in 0 ms                                                          
8378512 bytes read in 403 ms (19.8 MiB/s)                                       
Found mainline kernel configuration                                             
33059 bytes read in 7 ms (4.5 MiB/s)                                            
804 bytes read in 3 ms (261.7 KiB/s)                                            
Applying kernel provided DT overlay sun8i-h3-spi-spidev.dtbo                    
4185 bytes read in 2 ms (2 MiB/s)                                               
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)                   
## Executing script at 44000000                                                 
Wrong Ramdisk Image Format                                                      
Ramdisk image is corrupt or invalid                                             
SCRIPT FAILED: continuing...                                                    
switch to partitions #0, OK                                                     
mmc1(part 0) is current device                                                  
Scanning mmc 1:1...                                                             
Found U-Boot script /boot/boot.scr                                              
3798 bytes read in 1 ms (3.6 MiB/s)                                             
## Executing script at 43100000                                                 
U-boot loaded from eMMC or secondary SD                                         
MMC: no card present                                                            
Boot script loaded from mmc                                                     
283 bytes read in 1 ms (276.4 KiB/s)                                            
8378512 bytes read in 403 ms (19.8 MiB/s)                                       
Found mainline kernel configuration                                             
33059 bytes read in 7 ms (4.5 MiB/s)                                            
804 bytes read in 3 ms (261.7 KiB/s)                                            
Applying kernel provided DT overlay sun8i-h3-spi-spidev.dtbo                    
4185 bytes read in 2 ms (2 MiB/s)                                               
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)                   
## Executing script at 44000000                                                 
Wrong Ramdisk Image Format                                                      
Ramdisk image is corrupt or invalid                                             
SCRIPT FAILED: continuing... 

 

Edited September 2, 20224 yr by Manel
add

I don't have an answer to this problem, but what might help someone else to help you troubleshoot this issue is what Kernel version was your board using and to what version Kernel did you try upgrade it to?

 

Have a look through some of the articles on this Google search.

https://www.google.com/search?q=linux+"Wrong+Ramdisk+Image+Format"

 

 

 

There is ls -l of /boot partition:

 

-rw-r--r-- 1 root root     283 31 août  19:08 armbianEnv.txt
-rw-r--r-- 1 root root    1536  7 sept.  2019 armbian_first_run.txt.template
-rw-r--r-- 1 root root  230454  7 sept.  2019 boot.bmp
-rw-r--r-- 1 root root    3726  7 sept.  2019 boot.cmd
-rw-r--r-- 1 root root    4882  7 sept.  2019 boot-desktop.png
-rw-r--r-- 1 root root    3798  7 sept.  2019 boot.scr
-rw-r--r-- 1 root root  200877 22 juin  09:35 config-5.15.48-sunxi
lrwxrwxrwx 1 root root      17 31 août  19:33 dtb -> dtb-5.15.48-sunxi
drwxr-xr-x 3 root root   12288 31 août  19:32 dtb-5.15.48-sunxi
lrwxrwxrwx 1 root root      17  7 sept.  2019 dtb.old -> dtb-4.19.59-sunxi
-rw-r--r-- 1 root root 9777425 31 août  19:33 initrd.img-5.15.48-sunxi
drwxr-xr-x 2 root root    4096  7 sept.  2019 overlay-user
-rw-r--r-- 1 root root 4449753 22 juin  09:35 System.map-5.15.48-sunxi
lrwxrwxrwx 1 root root      21 31 août  12:05 uInitrd -> uInitrd-4.19.62-sunxi
-rwxr-xr-x 1 root root 8378512 22 juin  09:35 vmlinuz-5.15.48-sunxi
lrwxrwxrwx 1 root root      21 31 août  19:33 zImage -> vmlinuz-5.15.48-sunxi

 

I can see uInitrd have no link...what happened ?

 

After removing bad link uInitrd-4.19.62-sunxi, adding new uInitrd-5.15.48-sunxi and relinking uInitrd I bring back my system. Is armbian-config  or me the culprit ? 😅