So in that case the only possible culprits are the charon config file
and the System76 stuff (since presumably it won't actually affect a non-
System76 machine). I can poke around with System76 and see if they know
anything, and we should be able to try a run with the charon config put
back to
I am almost certain that the lvm2 messages happen in the couple of
minutes before the box crashes/reboots itself. The fact that they
happen over several minutes is part of what makes me think that it's
coincidental and just something that's unhappy because we're in the
middle of installing stuff
Neither system had LVM configured at all, which is why I thought it
might be coincidental, but I wanted to include it anyway.
I did have to manually deal with our custom edits to /etc/ssh/ssh_config
and /etc/strongswan.d/charon.conf and System76's custom edits to
/etc/default/grub in order to
Honestly, if this were one system I'd be of the opinion that I recovered
it and it's fine. What's concerning me is that we've seen it on three
systems now and we have a bunch more that need to be upgraded.
The only thing I can think of if it's not reproducible outside our
office is that it's
I haven't found any crash files in /var/crash on either system that I
looked at in detail. It actually sort of acts like a normal 'install
for a while, then reboot', it just comes back up in a half-installed
state after that first reboot, which is why I think it crashed rather
than normally
Public bug reported:
I've now had three systems we've tried to upgrade from 16.04 to 18.04.1
which crashed during the upgrade and had to be recovered with dpkg
--configure -a. I was able to recover two of them with a bit of manual
care, but I am now hesitant to upgrade other machines until we
