Reboot on ssh command locks up device, how to solve?

[Bo Berglund]

On Wed, 18 May 2022 17:28:36 +0100, Colin Law <clanlaw at gmail.com> wrote:

>On Wed, 18 May 2022, 09:31 Bo Berglund, <bo.berglund at gmail.com> wrote:
>
>> On Wed, 18 May 2022 07:50:57 +0100, Colin Law <clanlaw at gmail.com> wrote:
>>
>> >Have a look at /var/log/syslog to see if it gives any clues about what is
>> >going on.
>> >
>> >Also check that the bios/firmware is up to date.
>>
>> System f/w was updated very recently (a month or so ago).
>>
>
>You said it had been up for 54 days when you tried to reboot so that can't
>be strictly accurate.

Well, it might have been back in March I checked last...

But the HP f/w does not change that often.
I purchased the device in beginning of January (used) and tried to install Linux
Mint. At that time it had a several years old f/w.

But the Windows 10 installation that was on it previously interfered so I had to
do a f/w upgrade at that time. I believe I looked for help here during that
process.

>Always worth checking again in case there is another one.
>
>
>> The syslog does not give me any clues, I know when I power cycled the
>> system via
>> the Shellyplug because it is set up to email me a report when it chjanges
>> state.
>> So I power cycled the system on May 17 at 08:31:00.
>>
>> To reiterate this is what I did leading up to the crash:
>> - sudo apt update
>> - sudo apt full-upgrade
>> - sudo reboot
>>
>> At this point the system became inaccessible and I could no longer log on
>> using
>> ssh.
>>
>> Here is an excerpt from syslog around the power cycle starting about 30 min
>> before I power cycled the unit (I have cut down very long lines) until the
>> normal start log streams along.:
>>
>
>
>What time did you run the reboot command? We need to know what appears in
>the log when you run the reboot command.

I have now searched history for "sudo apt" to locate the last full-upgrade
before the crash:

 2997  2022-05-15 07:59:06 sudo apt update
 2999  2022-05-15 07:59:38 sudo apt full-upgrade -y

And the reboot same way, the last time it was done (February):

 1076  2022-02-15 17:29:13 sudo reboot

Seems like after this back in February, when I issue sudo reboot it does not get
into history anymore...


So the actual reboot I did which failed is not logged.
At that time I first waited a while to be able to connect and when that failed I
used the shellyplug to power cycle the unit.

And that happened at exactly 2022-05-17 08:31:00 as reported by the plug itself.

So the reboot that failed did not get into the history log, but should have
happened some minutes before the shellyplug operation...

I am pretty sure it was not long after I saw the lock-up that I used the
shellyplug to power cycle. Maybe 18 minutes as indicated by syslog?

But I guess that finding this needle in the haystack is bwyond my capabilities,
so I will rely on the shelly plug for future mishaps too.

Luckily this system is NOT a NASA Mars Rover controller...


-- 
Bo Berglund
Developer in Sweden