MariaDB Aria recovery

Corrupt Aria recovery logs can stop MariaDB before you know which tables still contain usable data.

MariaDB uses the Aria engine for user tables and some system tables. The aria_log_control file and aria_log files track recovery state; corruption or an interrupted shutdown can make startup fail or leave tables marked as crashed.

Understand the symptom

Log cleanup and table recovery solve different parts of the failure.

WHY

What is happening

Removing corrupted Aria recovery logs may allow startup in documented scenarios, but it does not prove every Aria table is consistent. aria_chk must not run while MariaDB uses the tables, and repair modes can rebuild indexes or discard unreadable rows. A protected copy supports comparison and targeted extraction.

What you may see

Symptoms that change the recovery path.

01

MariaDB stops during Aria recovery

Startup logs identify aria_log or aria_log_control before shutdown.

02

Table is marked as crashed

An Aria table failed consistency checks after an outage.

03

Can't read control file

The recovery control state is missing, corrupt or inaccessible.

04

System tables prevent startup

Aria-backed internal metadata may be affected.

Protect the source

Actions that can make the situation worse.

01

Deleting logs removes recovery evidence

The original sequence helps explain which writes were incomplete.

02

aria_chk while online can conflict

The server and repair utility must not modify the same tables.

03

Repair success can hide lost rows

Index reconstruction does not guarantee full data-file recovery.

Do this now

Safe steps before evaluation.

01

Stop automatic restarts

Prevent repeated crash recovery from changing files.

02

Copy the full data directory

Preserve Aria control, logs, table files, system tables and configuration.

03

Record the first startup failure

Save the complete error log and the outage or disk event that preceded it.

04

Image suspect storage

Protect the volume before log deletion, filesystem work or table repair.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Aria state review

NEPFOSYS maps control files, recovery logs, table files and affected system metadata.

02

Copy-based startup testing

Documented log handling and table repair are evaluated on an isolated copy.

03

Table validation

Recovered tables are compared for readability, row counts and application-critical records.

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 is aria_log_control?

It stores Aria recovery-control information used with the Aria log sequence.

Can I delete Aria logs?

MariaDB documents scenarios where logs are removed, but preserve them and every table file first because cleanup is not the same as data recovery.

Can aria_chk run with MariaDB online?

No. MariaDB documentation warns not to use it while the server is running.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case