[Bug]: T-Echo reboot loop due to node database too large

[elektra42]

Category

Hardware Compatibility

Hardware

T-Echo

Firmware Version

2.5.18.89ebafc

Description

With many nodes in the database, the T-Echo gets trapped in a boot loop due to lack of space. Obviously the max number of nodes needs to be reduced for the T-Echo. Meshtastic here is quite crowded. Greetings and thanks from Berlin!

Relevant log output

INFO  | ??:??:?? 0 Adding node to database with 1 nodes and 159004 bytes free!
DEBUG | ??:??:?? 0 Expand short PSK #1
INFO  | ??:??:?? 0 Wanted region 3, using EU_868
DEBUG | ??:??:?? 0 Coerce telemetry to min of 30 minutes on defaults
INFO  | ??:??:?? 0 Save /prefs/db.proto
lfs warn:314: No more free space 224
lfs warn:314: No more free space 224
ERROR | ??:??:?? 0 Error: can't encode protobuf io error
ERROR | ??:??:?? 0 LFS assert: head >= 2 && head <= lfs->cfg->block_count

[todd-herbert]

Thanks for reporting the issue! We've hopefully chased this bug down yesterday with #5916

We've been tracking the issue over at #5839
The fix will be included in the next release, or if you're brave you could try the nightly builds (bleeding) at https://meshtastic.org/downloads/#firmware.

You may also need to erase your T-Echo first, if you haven't already taken that step.