During Change version from nightlight to stable a bug step the pre-configuration of OMV.

[Nico21311]

Dear all 

 

My nanopi M4 V2 does not start 

 

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

 

I have installed 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 perform 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 ?

 

I would like tried to comeback to the previous version 

 

But I do not find the process.

 

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)
=> 

[mcfo]

Hi, have you sorted this out? If not,

I suggest that you reload the original downloaded os or a fresh copy back to the reformatted microSD card. Also note advice re the SD quality written elsewhere on this forum. That should give you access to the system. Then you can review your procedures for setting up the NVME and boot options and try again.

 

[mcfo]

I just saw advice from martinayotte

Posted May 23, 2020

"Rockchip SoCs always have eMMC as boot priority.

So, to boot from SDCard, you need to stop U-Boot from eMMC by pressing <spacebar> several times during startup.

Then, at U-Boot command line, you can type "setenv devnum 1" followed with "run mmc_boot", it will then boot from SD."

 

I've made a note of this for myself as well, cheers

[Simon S.]

Consider me in - mine also becomes increasingly unreliable so I'm finally pulling the trigger.

 

I have a strong suspicion that your 3x WD Black died are not related to them but the SBC having unstable internal power circuit.

 

Because I do also have 2x Enterprise SSDs failed and 2x White Labels making troubles after being connected to both the USB3 and the SATA-HAT. 

 

Right now I'm using it with the NVMe Hat with OMV but whenever I restart I get an smart error counter increase - on each single restart.

 

After the USB related issues making the drives mounted RO I'm finally giving up on this and Arm-SBCs as a whole (bookworm/5.16-rockchip) and going back to x86 completely. I have had a shitload of them and all the fun issues regards to big.LITTLE (e.g. KVM) and lack of distro support because of the bootloader mess / missing Adoption is just making this a big no-fun adventure anymore ...for me personally.