Hi All,

 

I have a couple of H3 based boards (Orange Pi Zero and FriendlyArm NanoPi Duo 2). With all of them I have the same issue:
command like "reboot" turn the board off instead of rebooting.

The workaround is to add following line in /boot/armbianEnv.txt
 

extraargs=reboot=warm

 

Running latest image on all of the boards.

 

 

Edited December 26, 2025Dec 26 by Geoffrey F4FXL
corrected /etc/armbianEnv.txt => /boot/armbianEnv.txt

I think it must be  /boot/armbianEnv.txt

Besides that, I never had this issue with my 5 NanoPi-NEO boards, originally Armbian Buster, always in-place upgraded. Also 1 now tested with kernel 6.18, no issues.

So I think you maybe need to look at what U-Boot you use, what kernel is it and logs ( all via armbianmonitor -u )

Edited May 6May 6 by eselarm
typo

Ooops, you are right I meant /boot/armbianEnv.txt, I edited the topic to correct.

The output of armbianmonitor -u can be found here:
https://paste.armbian.com/foyunagisu

What should I look for?

I do not see something clearly wrong, but likely is is a newer U-Boot, maybe something wrong there; version in SD-card you can show with:

dd if=/dev/mmcblk0 count=32k status=none | strings | grep "U-Boot SPL"

 

Here is the output:
 

U-Boot SPL 2024.01_armbian-2024.01-S866c-P6b16-Ha5c2-V7d7d-Bbf55-R448a (Dec 22 2025 - 03:39:51 +0000)

 

Note that prior to this I tried to update uboot through armbian-install, it did not change anything to my reboot issue.

OK, I have the following in my test NanoPi-NEO (using 6.18 kernel):

U-Boot SPL 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-V2b78-Bb703-R448a (Mar 09 2025 - 03:54:42 +0000)

Same base, but it is older and anyway different hardware, although H3 SoC. I have no more ideas why you need that extra kernel cmdline statement. I think I have seen it as well for another board/SoC, but does not ring a bell.

 

The thing is that I need it on different boards .... Tried Armbian Trixie and Ubuntu based, same issue thus it might be uoot and/or kernel related.

Thanks for your help though.

Update, this is also working ....

extraargs=reboot=watchdog

UPDATE:  It stopped working after 3 successful reboots...

Edited December 26, 2025Dec 26 by Geoffrey F4FXL

Today I needed to reboot one of the Orange Pi which is at a remote location....

It did not come back to life.... Maybe some update removed the 

extraargs=reboot=warm

parameter ....

Hello, @Geoffrey F4FXLyou just saved me a lot of debugging time. I have multiple orange pi zero with h2+ and h3 and I had the same problem as you. With the reboot command, the sbc shutsdown but doesn't boot again, i need to reset the power for getting it booting again. On my side , this command extraargs=reboot=warm didn't worked but extraargs=reboot=watchdog worked perfectly. I just rebooted it 5 times in a row and it always rebooted well.  
My version : v25.11.2 for Orange Pi Zero running Armbian Linux 6.12.58-current-sunxi
 

@Issou thanks for the feedback, I eventually got my hands on the Orange Pi zro I had in a remote location, I will make a fresh install and see how it behaves.

Yes it looks like but with reboot on Ornage Pi zero back. After fixing the problem with kernel 6.12.xx

https://github.com/armbian/build/issues/8197

 

now when we use kernel like 6.18.24 we can not reboot OZPI v1. When we run 'reboot' it is rather to power off

so it looks like it is a problem with Crust

https://github.com/armbian/build/pull/8503

 

it wille nice to fix this problem with reboot in kernel 6.18.x like was fixed in 6.12.x

 

I know that the Orange Pi Zero platform is on community support, but maybe there will be a volunteer who will fix this problem.

 

but extraargs=reboot=watchdog  help solve  problem