Recovery Mode: unknown process issue

[gregrahn]

jetkvm-recovery-unknown-2025-12-18T11-44-36-674Z.txt

Issue Description

The unknown process encountered an error and failsafe mode was activated.

Reason: unknown
Timestamp: 2025-12-18T11:44:38.682Z
App Version: 0.5.0
System Version: 0.2.5

Logs

Please attach the recovery logs file that was downloaded to your computer:
jetkvm-recovery-unknown-2025-12-18T11-44-36-674Z.txt

Note

Please remove any sensitive information from the logs. The reports are public and can be viewed by anyone.

Additional Context

[Please describe what you were doing when this occurred]

[adamshiervani]

Thanks for reporting the issue, @gregrahn!

I just pushed a new dev version, which contains far more diagnostic logs in the failsafe logs. Could you please update the device to the latest dev version:

1. Settings > Advanced > Enable "Dev Channel Updates"
2. Settings > General > Check for Updates > Update now

Once the update is applied, wait for the failsafe mode trigger and send me the logs here.

After that you can just downgrade to 0.4.8, so you have a working device, while I figure out the cause of the crash.

[gregrahn]

The device is now up on the new bits - I can just leave it to see if it repro and then update the issue with new logs unless you have other advice.

[adamshiervani]

It’s interesting that it doesn’t crash immediately. The 0.5.1-dev release includes only one major fix, which addresses an issue that triggers failsafe mode (see: #1066). That may have been the root cause in your case too, but it’s hard to say for sure since the logs were cut off for some reason.

If you’re near the device, could you try tap and hold on the JetKVM display to see whether a menu appears? If it doesn’t, that was likely the cause of the crash in 0.5.0.

[gregrahn]

When I tap and hold, it goes into the Settings menu.

[adamshiervani]

Thanks for testing that! Ok, then let's keep this issue open and send me the logs if you manage to trigger failsafe mode again.

[DouglasByers]

Hi there, I believe I have experienced the same issue, though have some more info about the lead up to it. I am including my report here as it is still likely a duplicate.

Issue Description

The unknown process encountered an error and failsafe mode was activated.

Reason: unknown
Timestamp: 2025-12-21T20:01:36.882Z
App Version: 0.5.0
System Version: 0.2.5

Logs

Please attach the recovery logs file that was downloaded to your computer:

jetkvm-recovery-unknown-2025-12-21T20-01-34-872Z.txt

Note

Please remove any sensitive information from the logs. The reports are public and can be viewed by anyone.

Additional Context

In the last week I noticed my JetKVM had entered a broken state and was unable to access the web UI. I could still see it with an IP address in my network management, but it had no traffic since it had gone down. The hourly requests to time.google.com had stopped. Last night I finally got physical access, and I noticed that the device's screen had an error message on it. Unfortunately I can't recall what it was. (Edit: this "error message" might have been the "Initialising..." screen)

Anyway, I unplugged and replugged the USB cable to power cycle it, and shortly after, I recieved a notification from my uptime monitor that the web UI was accessable again, so I went to bed. Today I checked the web UI and seemed to be in failsafe mode, like others.

Much of this detail could be meaningless, I'm unsure if the lead-up broken state is related, or that the failsafe mode was triggered by the hard reboot itself.

Once in the failsafe menu I selected reboot, and it then seemed to be behaving as normal on 0.5.0. I then updated to version 0.5.1-dev202512211114, so that I can give the more detailed logs if I end up in failsafe mode again.

[adamshiervani]

Thanks for taking the time writing that! Once it happens again, we'll be closer to figure out the cause.

[adamshiervani]

Version 0.5.1 is now fully rolled out and should include far more information than just the last crash log, which seems gets cut way too early.

Did anyone get this triggered again?

[gregrahn]

I've hit the "Fail safe mode activated" screen again, but the "download logs" button just spins when clicked - nothing gets downloaded in the browser - and I've tried both Safari & Vivaldi on macOS.

{"deviceVersion":"0.5.2-dev202512291946"}

# cat /version
0.2.5

It seems to be something related to the ws/client is broken by looking at the web console.