MongoDB missing collection

A missing WiredTiger collection file can let MongoDB start only by replacing the collection with an empty stub.

WiredTiger connects collection metadata in the MongoDB catalog to ident files in dbPath. If a .wt file is missing, orphaned, renamed, or no longer matches the catalog, repair may prioritize starting the server over preserving every document.

Understand the symptom

Collection recovery depends on both WiredTiger metadata and MongoDB catalog identity.

WHY

What is happening

Recovery maps collection UUIDs, idents, WiredTiger.wt, _mdb_catalog, checkpoints and journal history. A file known to one metadata source may be salvageable; a file missing from both metadata sources may not be automatically associated with its original collection.

What you may see

Symptoms that change the recovery path.

01

File not found for ident

The catalog references a WiredTiger table whose .wt file is absent.

02

Collection opens empty after repair

Repair created a stub so the database could start.

03

Orphaned .wt file remains

A collection file exists but is missing from one or both metadata catalogs.

04

Startup requests salvage

WiredTiger metadata or a collection table cannot be opened normally.

Protect the source

Actions that can make the situation worse.

01

Repair can discard documents

Unsalvageable data may be renamed or replaced with an empty table.

02

Copying one .wt file is incomplete

Checkpoints, journal and catalog identity must match the same database state.

03

Replica rejoin can spread inconsistency

A repaired node should not rejoin until data changes and replica state are understood.

Do this now

Safe steps before evaluation.

01

Stop MongoDB and automation

Prevent restart loops, repair, compaction and replica resync.

02

Preserve the complete dbPath

Copy every WiredTiger file, journal, lock state, diagnostics, keys and configuration.

03

Record collection identity

Save namespace, UUID, ident, server version, topology and exact startup errors.

04

Protect the volume

Snapshot or image the underlying storage before salvage or file replacement.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Catalog-ident mapping

NEPFOSYS correlates collection metadata, idents, files and checkpoints on the copy.

02

Salvage and source comparison

Candidate files, backups, replica members and journals are evaluated without altering production.

03

Document validation

Recovered BSON, indexes and priority collections are checked in an isolated environment.

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.

What does mongod --repair do with a missing file?

It may create an empty stub so the server starts, which does not recover the missing documents.

Can an orphaned .wt file be recovered?

Sometimes, when enough catalog or WiredTiger metadata remains to identify and salvage it.

Should I copy the missing file from another node?

Not directly into production without confirming checkpoint, catalog and replica consistency.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case