08:24:00 <szilard> I am facing an unreliable reboot with my NAS. It start to belive it have something to do with the way I issue the reboot command. According to my experiences the machine reboots just fine using the reboot command If I am connected via LAN to the machine. However most of the time I connect via VPN, which runs in a zone and I have set it up to forward ipv4. So i suspect when I issue the rebot command via 
08:24:06 <szilard> tailscale it starts to shutdown the zones. But while it does this it still prints info in the ssh session. But OmniOS will shutdown the tailscale zone, so the reboot command looses its stdout and it dies before it fully reboots the machine.
08:24:10 <szilard> Do you think this can be the reson?
08:25:38 <szilard> I should try to reboot the server running reboot in tmux...
08:32:21 <szilard> I have also noticed when the reboot command doesn1t successfulyl reboots the machine I loose all contact with it. I can dial into the router the machine connected to but the machine doesn't answer to ping in this state
08:32:37 <szilard> MAybe the networking is already shutdown, but the machine still runs.
08:34:08 <szilard> I am not even sure, where it hangs, It can be before or after the reboot. I always find the machine powered on, fans going on high speed, but no other signs of life. I need to hardware reset it using the power button.
08:37:22 <szilard> Is there any alternative command which i should use, which doesnt relies on stdout?
08:46:42 <ptribble> You could always issue the reboot command from within a screen session
08:47:27 <ptribble> But I wouldn't expect stdout to be a problem
08:50:48 <ptribble> If it is related to connecting via vpn then I suspect the vpn itself might be holding up the reboot, but even that shouldn't happen
09:18:20 <szilard> Then I am not sure, what can be te culprit. There is nothing on the display output, the machine doesn't react to anything and I don't know if there is any log which can give any hints regarding the state of the machine.
09:19:02 <szilard> Maybe the machine sucessfully reboots, and it freezes somewhere in the bootloader.
09:20:34 <tsoome_> does it start up ok on power cycle?
09:22:10 <tsoome_> hung system on "reboot" command is often related to "bad" method to perform the reboot. But, if you do suspect the bootloader stage, you better get access to the console and then you can be sure.
09:25:30 <szilard> tsoome_: it always starts up just fine after power cycling it.
09:26:24 <tsoome_> btw, is it booting UEFI or bios?
09:26:46 <szilard> it is uefi.
09:27:28 <szilard> maybe i shoul try init 6 to reboot
09:49:28 <tsoome_> its the same as reboot.
10:47:25 <tsoome_> It may help to check for firmware update from vendor; but part of the problem is that we do not have yet an access to UEFI RunTime functions from kernel to call uefi method for reboot/shutdown, so the default is to use acpi method to trigger reboot...
11:11:38 <szilard> There is a new firmware, let me try to install it ...