Synology Btrfs read-only state

A Synology Btrfs volume can switch to read-only to limit further damage while storage or metadata is inconsistent.

Read-only status can follow disk errors, RAID degradation, metadata faults, power loss, or space exhaustion. It may preserve access long enough to copy critical data, but it does not prove the storage pool is stable.

Understand the symptom

Btrfs protects metadata with checksums and copy-on-write, but still depends on readable RAID members.

WHY

What is happening

Synology layers storage-pool RAID, Btrfs allocation trees, subvolumes, snapshots, and applications. A read-only transition can be triggered below or inside the filesystem. Recovery separates member health from RAID assembly and Btrfs metadata before any scrub or repair writes occur.

What you may see

Symptoms that change the recovery path.

01

Volume status is read-only

DSM prevents ordinary writes after detecting an unsafe storage or filesystem state.

02

Shared folders are accessible but apps stop

Reads may work while databases and packages require writable metadata.

03

Btrfs or I/O errors appear in logs

Checksums, tree blocks, or underlying sectors cannot be read consistently.

04

Problem followed outage or disk warning

An interrupted transaction or degraded member may be the initiating event.

Protect the source

Actions that can make the situation worse.

01

Forced remount creates new writes

Applications can immediately change metadata on an unstable volume.

02

Scrub stresses weak members

A full read can accelerate a degrading disk before images exist.

03

Volume recreation destroys allocation trees

Creating a replacement volume overwrites the structures needed to find files.

Do this now

Safe steps before evaluation.

01

Stop packages and clients

Pause Drive, Hyper Backup, containers, VMs, databases, media indexing, and network writes.

02

Record DSM storage status

Save pool, volume, Btrfs, disk, SMART, scrub, snapshot, and event details.

03

Label all NAS disks

Preserve bay order, serials, removed members, replacements, cache devices, and chassis.

04

Copy only critical data if stable

Use separate storage and avoid broad scans if the NAS is slow, disconnecting, or reporting I/O errors.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Layer diagnosis

NEPFOSYS identifies whether member, RAID, pool, Btrfs, snapshot, or application metadata is blocking access.

02

Source protection

Unstable members and metadata are preserved before write-based repair.

03

Filesystem reconstruction

Btrfs trees, subvolumes, snapshots, and priority files are evaluated from protected copies.

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.

Does read-only mean all data is intact?

No. It limits writes but can coexist with unreadable sectors, missing members, or damaged Btrfs metadata.

Should I run data scrubbing?

Not before checking disk health and protecting unstable members. Scrubbing reads the full set and may also repair data.

Can snapshots help?

They may preserve earlier metadata and file versions, but they use the same underlying pool and should not replace source preservation.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case