MCAP robotics-log recovery

A partially written MCAP file may retain messages even when its summary, indexes, or footer is missing.

MCAP records timestamped messages, schemas, channels, attachments, and metadata. The optional summary and indexes speed access, while the footer and final magic complete the file.

Understand the symptom

MCAP recovery can rebuild summary data around surviving records.

WHY

What is happening

The MCAP format consists of magic, a header, data records, optional summary sections, a footer, and final magic. The official recover command reads a corrupt or truncated source and writes a new valid copy, reporting when records were discarded or a record ended mid-write.

What you may see

Symptoms that change the recovery path.

01

Expected footer not found

Recording may have stopped before finalization.

02

Invalid magic or record length

The header, footer, or a record boundary may be damaged.

03

Summary or index missing

Messages may remain but fast lookup metadata is absent.

04

Recovery reports lossy output

At least one record was truncated or discarded.

Protect the source

Actions that can make the situation worse.

01

Replacing source loses forensic comparison

Keep original and recovered files separately.

02

Lossy status must be documented

Do not treat a readable output as complete.

03

Schema loss blocks payload decoding

Preserve schemas, channels, and software packages.

Do this now

Safe steps before evaluation.

01

Copy source and companions

Keep MCAP, split logs, schemas, attachments, manifests, and checksums.

02

Record writer context

Note library, version, compression, chunk size, channels, and shutdown event.

03

Define important intervals

List topics, timestamps, attachments, and expected counts.

04

Protect the recording device

Image failing media before sequential recovery reads.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Record-stream assessment

NEPFOSYS maps magic, records, chunks, schemas, channels, summary state, and readable ranges.

02

Copy-based recovery

Surviving records are written to a new valid MCAP without altering the source.

03

Log validation

Topics, schemas, channels, timestamps, counts, attachments, and reported losses are reconciled.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Can MCAP recover a file without a footer?

Often surviving data records can be copied and new summary and footer structures written.

What does lossy recovery mean?

The tool discarded an invalid record or encountered truncation mid-record, so output is not complete.

Are schemas stored in MCAP?

They can be stored as records, but external schema and application context should still be preserved.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case