NAS Codex › Synology › Synology volume has become read-only: the two causes Synology gives and how it says to fix each
Synology volume has become read-only: the two causes Synology gives and how it says to fix each
In Storage Manager a Synology volume shows Read-only and no longer works normally. Synology's article on this gives two possible causes: the volume has features the current system or model does not support, or a hardware fault, usually drives or the file system, has damaged it. The fix is different for each. This page follows Synology's article and adds its guidance on file system errors and on preventing volume crashes.
Written against: Synology Knowledge Center articles for DSM 7 series, DSM legacy versions and DSM Enterprise (PAS). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.
Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.
Fast Answer
First work out which cause applies. If the volume came from another Synology system and has or had features such as WriteOnce or immutable snapshots, update DSM to the latest version, and if it stays read-only, move the drives to a compatible Synology device. If not, Synology treats it as a hardware fault: copy the data off with File Station, remove the volume in Storage Manager > Storage, create a new volume and copy the data back. Synology says to act quickly, because crash-related corruption tends to get worse over time.
Cause 1: features the system does not support
Synology says this can happen in cases such as migrating a volume from another Synology storage system, when the volume has, or used to have, features that the current operating system or your model does not support. Its examples are WriteOnce and immutable snapshots. Synology says this incompatibility does not corrupt data, but it makes the volume unavailable and needs to be dealt with.
Synology's fix
- Update the operating system to the latest version.
- If the volume is still read-only, move the drives to a compatible Synology device to assemble the storage pool there.
- If you have no compatible Synology device for the drives, back up the data and remove the read-only volume, then create the storage pool again.
Cause 2: hardware malfunctions
Synology says the other cause is hardware in the storage system not working properly, and that drive or file system failures often lead to volume crashes. Its article points to three checks to find the faulty part:
- whether drive failures come from the drives themselves or from the drive slots;
- whether the memory is working properly;
- the cause of any improper shutdown.
Synology says volume crashes usually involve uncorrectable data corruption that tends to worsen over time, and strongly recommends dealing with the issue as soon as possible.
Synology's fix: back up, remove, recreate
- Use File Station to copy the data on the read-only volume to another volume on the same Synology system, or to another storage device.
- Remove the volume. Go to Storage Manager > Storage. On DSM, click the upper-right icon of the volume. On DSM Enterprise (PAS), select the volume and click Action. Select Remove.
- Create a new volume.
- Copy the backed-up data to the new volume.
- Take Synology's steps to prevent volume crashes (below).
Synology notes that removing a volume only stops the related services for a while. It does not uninstall or erase DSM, because system data is kept in the system partition of the installed drives, not on volumes.
Where file system errors fit in
Synology's file system errors article says these errors usually come from bad sectors, drives installed improperly, incompatible drives or a hardware problem, and that faulty memory and improper shutdowns can also corrupt the file system. Left unresolved, Synology says the file system may be unable to read and write normally, run packages, repair or expand a volume, change a pool's RAID type, or sync and back up data.
For an ext4 volume in Warning status on DSM 7.1 and above, Synology's fix is the file system check link under the storage pool's Suggestion in Storage Manager > Storage. DSM unmounts that volume and stops its packages and services while the check runs, which can take from several minutes to several hours. You can still use DSM and other volumes. If the errors persist, Synology's next step is the same as above: back up, including package settings, remove the volume, create a new one and restore. For Btrfs volumes, Synology points to Btrfs self-healing and to running data scrubbing regularly.
Preventing it next time
Synology's volume-crash article lists these common causes:
- more drives removed from a RAID than it can tolerate, through drive errors, accidental removal or a crashed SSD read-write cache;
- file system errors from improper shutdowns, non-Synology memory modules or drive errors;
- a Btrfs volume migrated to a Synology NAS that does not support Btrfs.
Its prevention steps:
- use drives on the Synology Products Compatibility List;
- run data scrubbing twice a year;
- set up hot spare drives;
- do not install non-Synology memory modules, and run a memory test;
- enable UPS support.
When to stop and get help
Copy your data off before removing anything. Synology's fix for a hardware-caused read-only volume starts with copying the data to another volume or device through File Station, and only then removes the volume. If the volume shows Crashed instead of Read-only, see volume crashed. If the NAS has been sending improper shutdown notifications, see "Improper Shutdown" notifications.
Questions
Why did my Synology volume become read-only?
Synology gives two causes. The volume may have, or once have had, features the current system or model does not support, such as WriteOnce or immutable snapshots, often after a migration. Or hardware is not working properly, with drive or file system failures, which often lead to volume crashes.
Does a read-only Synology volume mean data loss?
Not in the unsupported-features case: Synology says that incompatibility does not corrupt data. In the hardware case, Synology says volume crashes usually involve uncorrectable data corruption that tends to worsen over time, so it recommends backing up and acting as soon as possible.
Will removing a Synology volume erase DSM?
No. Synology says removing a volume only stops the related services temporarily and does not uninstall or erase the operating system, because system data is stored in the system partition of the installed drives, not on volumes.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-17.