Was the bad 64-bit experience running on raw hardware? Or in some VM environment? I am running ZS on raw hardware.

Out of interest, what is the recovery procedure if it fails to boot? How easy is it to get the system to boot from the other kernel slot with the known-good system? I haven't needed to try it yet, and would rather figure out how before the system is broken instead of afterwards!

Was the bad 64-bit experience running on raw hardware? Or in some VM environment? I am running ZS on raw hardware.

Out of interest, what is the recovery procedure if it fails to boot? How easy is it to get the system to boot from the other kernel slot with the known-good system? I haven't needed to try it yet, and would rather figure out how before the system is broken instead of afterwards!

I am currently managing total of 6 Zeroshell routers. 5 of them are physical, 1 in virtualbox. All currently running 3.8.0, 32-bit. Memory usage currently between 90 and 120MB. 2 failed upgrade routers were physical.

I am stuck at 3.7.1 with 4.9.27-ZS , 32 bits.
I tried 3.8 on a vbox dev env in order to compile apu drivers but dev env is still broken, I get segmentation fault error when I try to compile the kernel.

FYI, i faced a quite big issue : the update modified my admin password!!! (i had to boot a live linux to retrieve it), and transform all $ characters to _ characters...
Don't know about other characters...

FWIW, I just upgraded to 3.8.0 from 3.6 using the package manager. No issues at all, if anything memory usage is slightly down and performance seems somewhat better (though it might just be a slow night). I did not install the 64 bit kernel.

I keep getting random reboots on my ZS, running on Proxmox host.
version 3.8 keeps rebooting randomly.
I have tried clean installs, and also upgrades.
The results are the same.
Everytime I go back to v3.7.1, it works again fine.

Admin logs show the reboots follow no time_related pattern:
00:14:24 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
01:07:01 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
04:27:08 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
06:16:46 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
12:20:54 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
12:48:09 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
12:57:58 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
15:40:36 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
16:41:11 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
17:47:12 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
20:02:51 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0
20:32:51 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS and ZeroShell 3.8.0

I cannot see a reason for reboot.
Proxmox vm running the zeroshell does not report error either, it shows it's up all the time.

Do you recommend anywhere else to check?
My workaround is to go back to v3.7.1, but might not be a safe choice.

Well... since yesterday, it started misbehaving again. I am downgrading.
I have OpenVPN tunnels between 4 sites, maybe the restarts have to do with unstable VPN links, it is the only abnormality I see with this particular Zeroshell vm.

I will downgrade back to v3.7.1 and cross fingers. Maybe in the meantime, I will restore an existing vm backup and continue checking why this is happening.

LOG
02:55:34 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
03:51:03 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
04:27:49 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
04:55:19 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
05:01:27 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
05:25:05 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
05:33:14 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
06:21:04 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
06:38:06 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
07:31:59 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
07:50:42 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
08:07:18 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
09:05:51 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
09:11:56 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
10:02:17 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
10:22:16 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
12:29:08 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
12:32:36 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
13:25:35 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
13:43:59 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0
15:04:20 SUCCESS: System successfully started with Linux kernel 4.9.36-ZS-64 and ZeroShell 3.8.0

Out of interest, what is the recovery procedure if it fails to boot? How easy is it to get the system to boot from the other horsebettingsites.org kernel slot with the known-good system? I haven't needed to try it yet, and would rather figure out how before the system is broken instead of afterwards!

@Janice,
the boot screen shows the various boot kernels and you choose to boot from the one you prefer.
Once running, you may tell Zeroshell the default kernel to use (menu SETUP, button BOOT, dropdown list BOOTIMAGE)