Thanks for the report! I can see the error from your screenshot.

Root Cause

Your SQLite database file is corrupted (SQLITE_CORRUPT). The exact error is:

SqliteError: database disk image is malformed
code: 'SQLITE_CORRUPT'

This is triggered when MeshMonitor 4.6.1 tries to run migration 059 (telemetry_source_node_type_ts_index) against your existing database. The database itself is damaged — not the migration. On Raspberry Pi / Raspbian this is very commonly caused by:

SD card failure or wear (most common cause)
Unexpected power loss during a write operation
File system errors on the SD card

Immediate Fix

To get MeshMonitor running again:

# 1. Stop MeshMonitor first, then:

# Back up the corrupted database (optional but recommended)
cp /path/to/meshmonitor.db /path/to/meshmonitor.db.bak

# Delete the corrupted database
rm /path/to/meshmonitor.db

# Restart MeshMonitor — it will create a fresh database automatically

The default database path is typically /root/meshmonitor/data/meshmonitor.db or wherever your DATA_DIR is configured.

Historical node/message data will be lost, but the app will be fully functional again. If you want to attempt recovery of the data, the sqlite3 CLI tool has a .recover command that can sometimes salvage rows from a corrupt database.

What We're Fixing in MeshMonitor

Currently the app crashes with a raw Node.js stack trace when SQLITE_CORRUPT is detected. A fix is being prepared that will instead print a clear, actionable error message with the exact database path and recovery steps before exiting cleanly. This will be much more helpful for Raspberry Pi users who hit this issue.

Generated by Claude Code

Uh oh!

[SUPPORT] 4.6.1 on Raspbian baremetal #3085

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions