NANOPIM4V2 + OMV and 4xSATA HAT does not boot-up after updating armbian-firmware/buster,buster 22.05.1

[Guest]

Hi,

Is anyone can able to help me with this ?

NANOPIM4V2 + OMV and 4xSATA HAT does not boot-up after updating armbian-firmware/buster,buster 22.05.1

Is there any additional info I can get from my system and put here that will help ?

Is this the right place to post this ?

Thanks

-----------------------------------------------------------------------------------                                      
Welcome to Armbian 22.05.1 Buster with Linux 4.4.213-rk3399

System load:   5%               Up time:       6 min
Memory usage:  6% of 3.72G      IP:            192.168.8.60
CPU temp:      37°C             Usage of /:    16% of 29G    
storage/:      48% of 1.8T      storage temp:  30°C           

[ 0 security updates available, 3 updates total: apt upgrade ]
Last check: 2022-06-18 11:07

-----------------------------------------------------------------------------------

sergio@SpirareVault:~$ apt list --upgradable
Listing... Done
armbian-firmware/buster,buster 22.05.1 all [upgradable from: 22.02.2]
linux-dtb-legacy-rk3399/buster 22.05.1 arm64 [upgradable from: 21.08.2]
linux-image-legacy-rk3399/buster 22.05.1 arm64 [upgradable from: 21.08.2]
sergio@SpirareVault:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  armbian-firmware linux-dtb-legacy-rk3399 linux-image-legacy-rk3399
3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/25.7 MB of archives.
After this operation, 426 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 68025 files and directories currently installed.)
Preparing to unpack .../armbian-firmware_22.05.1_all.deb ...
Unpacking armbian-firmware (22.05.1) over (22.02.2) ...
Preparing to unpack .../linux-dtb-legacy-rk3399_22.05.1_arm64.deb ...
Unpacking linux-dtb-legacy-rk3399 (22.05.1) over (21.08.2) ...
Preparing to unpack .../linux-image-legacy-rk3399_22.05.1_arm64.deb ...
Unpacking linux-image-legacy-rk3399 (22.05.1) over (21.08.2) ...
Setting up armbian-firmware (22.05.1) ...
Setting up linux-image-legacy-rk3399 (22.05.1) ...
update-initramfs: Generating /boot/initrd.img-4.4.213-rk3399
update-initramfs: Converting to u-boot format
Setting up linux-dtb-legacy-rk3399 (22.05.1) ...
sergio@SpirareVault:~$

-----------------------------------------------------------------------------------

20220608_Nanopim4v2_not-booting.txt

Edited June 18, 2022 by Spirare
Adding the serial output

[Guest]

The last system update have solve this problem...thank you.

[Werner]

Asking the same question on multiple places within forums is considered abusive behavior. Therefor your other topic has been deleted without further review.

Please take a moment and review the usage terms of our forums you agreed on registration: https://forum.armbian.com/terms

[Guest]

Using the forum is a steep learning curve...thought that posting a question was different than reporting a bug...oh well...thanks for your help.

[Nico21311]

Dear all 

 

I have the same issue with my nanopi M4 V2

 

My configuration is a sd card for booting + a NVME  for the system.

 

I have installled a lot of applications :

 

OMV 

Docker with portainer

  

history :

I would  change version from nightlight to stable with a bug during the pre-configuration of  OMV.

I need to perfrom a CTRL + C to stop this frozen action.

 

After that I reboot my device with the same issue from post 1

 

Could you please help me to recover my device ?

 

Thanks in advance for your support. 

 

example of message during the boot.

 

failed to find ep-gpios property
ethernet@fe300000 Waiting for PHY auto negotiation to complete.... done
Speed: 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.8.60 (22 ms)
*** Warning: no boot file name; using 'C0A8083C.img'
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'C0A8083C.img'.
Load address: 0x800800
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-0e-26-67-a6-1d-cf
Speed: 100, full duplex
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'pxelinux.cfg/01-0e-26-67-a6-1d-cf'.
Load address: 0x600000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A8083C
Speed: 100, full duplex
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'pxelinux.cfg/C0A8083C'.
Load address: 0x600000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A8083
Speed: 100, full duplex
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'pxelinux.cfg/C0A8083'.
Load address: 0x600000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A808
Speed: 100, full duplex
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'pxelinux.cfg/C0A808'.
Load address: 0x600000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A80
Speed: 100, full duplex
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'pxelinux.cfg/C0A80'.
Load address: 0x600000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A8
Speed: 100, full duplex
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'pxelinux.cfg/C0A8'.
Load address: 0x600000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A
Speed: 100, full duplex
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'pxelinux.cfg/C0A'.
Load address: 0x600000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0
Speed: 100, full duplex
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'pxelinux.cfg/C0'.
Load address: 0x600000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C
Speed: 100, full duplex
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'pxelinux.cfg/C'.
Load address: 0x600000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-rk3399-evb_rk3399
Speed: 100, full duplex
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'pxelinux.cfg/default-arm-rk3399-evb_rk3399'.
Load address: 0x600000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-rk3399
Speed: 100, full duplex
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'pxelinux.cfg/default-arm-rk3399'.
Load address: 0x600000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
Speed: 100, full duplex
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'pxelinux.cfg/default-arm'.
Load address: 0x600000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
Speed: 100, full duplex
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'pxelinux.cfg/default'.
Load address: 0x600000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
Config file not found
failed to find ep-gpios property
Speed: 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.8.60 (53 ms)
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'boot.scr.uimg'.
Load address: 0x500000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
Speed: 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.8.60 (52 ms)
Using ethernet@fe300000 device
TFTP from server 192.168.8.1; our IP address is 192.168.8.60
Filename 'boot.scr.uimg'.
Load address: 0x2080000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
Invalid bus 0 (err=-19)
Failed to initialize SPI flash at 0:0 (error -19)
=> 

Edited March 25 by Nico21311