Yes, it’s device 40fa62f7a85eb88f5548acf3a13812c0. I actually already granted support access so @20k-ultra could load on a debug supervisor for another ticket related to device restarts (https://forums.balena.io/t/unexpected-supervisor-crash-container-restart-on-network-change). Feel free to take a look.
If you want to give it a shot, you should be able to replicate it by rebooting twice as described above. That seems to work for me every time.
FYI, I’ve been trying to replicate yet another issue on that device where the nemo container can’t talk to the supervisor (connection refused) or can’t be mounted (fork/exec /proc/self/exe: no such file or directory) when it boots after being offline for a few days. We thought it might be related to chrony, (https://forums.balena.io/t/chronyc-config-is-bad-if-device-comes-online-without-internet) but it’s not entirely clear if that’s the cause anymore from my testing yesterday and today. In any case, I’ve been changing setting time backwards and clearing the journal to try to replicate that issue. Don’t worry if you notice some weird stuff in the journal.