Comment 1 for bug 1843417

I'm just triaging this bug to leave a trace.

I'm periodically working with Roger to debug this issue. It seems to be a combination of several different problems that are unfortunately occur together.

We already identified and fixed a single issue with certainty: core18 did not ship fsck for vfat so a corruption of the boot partition, caused by anything at all, would not be automatically fixed.

We are working on the following additional threads now:

1) Understanding what is causing the reboot on that particular machine and if that is snapd or another service on the system.

2) Understanding why the machine does not come up cleanly after reboot. That is, the reboot seems to fail and requires a power cycle or two to recover from.

3) Understanding the situation of the hardware watchdog during the reboot process and in the bootloader. It is possible that we could at least fix the need to manually power cycle a device that has failed to boot correctly.

We've received a copy of the 1st partition of the SD card that this machine is using and we will perform additional analysis on how uboot and linux agree or disagree about the contents of the essential boot variables.