NAS Codex › Synology › Synology DSM or package update fails with an insufficient system capacity error
Synology DSM or package update fails with an insufficient system capacity error
A DSM, package or Synology drive firmware update fails with an insufficient storage error, even though Storage Manager shows plenty of free space. Synology's article on this is titled "There is insufficient system capacity for system or package updates." The space that ran out is the small system partition, not your volume, and Synology lists what usually fills it.
Written against: Synology Knowledge Center articles tagged DSM 7 series and DSM legacy versions (some fixes differ for DSM 6.2 and earlier and DSM 7.0 and later; factory reset only for DSM 7.1 and above). 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
Synology says the system lacks room to unzip and install update files in the system partition, and that Storage Manager's free space does not reflect it. Work through its list: data or command output stored outside shared folders, Docker containers writing to system paths, third-party packages, detailed system logs, the LogicalDoc and Media Server packages, then a restart. A Mode 2 reset or factory reset are last resorts, and need a backup first.
Why free space in Storage Manager doesn't help
Synology formats each drive into a system partition (DSM, settings and logs), a SWAP partition, and a data partition that holds your storage pools, volumes and packages. Synology says the available space shown in Storage Manager does not reflect the free space in the system partition, and the update error means there is not enough room there to unzip and install the update files.
What Synology says to check, in order
Data stored outside shared folders
Output from terminal commands, such as files or folders created in system locations like /root or /opt, or custom binaries and scripts, can fill the system partition. Move that data into shared folders and keep it there.
Docker containers
Containers can write to the system partition if they are configured to. Synology's example is docker run with --volume or --mount mapping system paths such as / or /root into a container. Ask the image provider if unsure, and remove unused containers in Container Manager.
Third-party packages
Packages not published or verified by Synology may cause problems, and Synology says removing them may not fully fix it.
Oversized personal wallpaper (DSM 6.2 and earlier)
Click the person icon (upper right) > Personal > Desktop > Customize wallpaper > Select image > My Images > My Previous Images > Clear All.
Detailed system logs
- Launch Support Center.
- Go to Support Services > System Log Tools.
- DSM 6.2 and earlier: untick Log more detailed information for diagnosis. DSM 7.0 and later: untick Log system status periodically.
- Click Apply.
LogicalDoc and Media Server packages
LogicalDoc's log files use system space; uninstall it in Package Center if unused. In Media Server > General Settings > Diagnose, untick Enable DMA communication log for diagnostic purpose and click Clear.
Synology High Availability (DSM 6.2.3 and earlier)
Updates need extra system capacity; Synology asks you to contact its Technical Support.
Restart
If the NAS has run for a long time, restarting at a suitable time may free capacity.
Last resorts: reset
Synology says systems first installed with DSM 7.0 or earlier (including migrated drives) may not have enough system partition space for major updates, because OS patches keep growing.
Warning: both options below need a full backup first.
- Mode 2 reset (quick fix): per Synology's reset article it wipes all system configurations and clears the administrator password and the encryption key vault. Back up system configurations and packages with Hyper Backup to a USB drive or shared folder, reset, then restore. Have licence keys for licensed packages ready, and reinstall any package Hyper Backup cannot restore. After the reset the NAS should show Configuration Lost, with volume data intact. If it shows Not Installed, do not proceed; contact Synology Technical Support. Synology notes a Mode 2 reset only clears the system partition and does not enlarge it, so you may need to repeat it at the next major update.
- Factory reset (permanent fix, DSM 7.1 and above only): it erases all data and creates a larger system partition. Back up configurations, packages and all shared-folder data to another device first, then restore.
When to stop and get help
Stop before either reset if your shared-folder data is not backed up to another device. Stop immediately if, after a Mode 2 reset, Synology Assistant shows Not Installed instead of Configuration Lost: Synology says contact its Technical Support.
Questions
Why does my Synology say there's not enough space when the volume has plenty?
Synology says updates unpack into the system partition, and the free space Storage Manager shows does not reflect free space in the system partition.
Will a Mode 2 reset delete my files?
Synology says that after the reset the status should be Configuration Lost with volume data intact, but it still requires a Hyper Backup of configurations and packages first, and says to stop if the status is Not Installed.
Does a factory reset fix it for good?
Synology calls it the permanent fix because it creates a larger system partition, but it erases all data and is only for systems on DSM 7.1 or above.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-14.