Synology NAS Error Code 59: How to Fix It

Medium 45–90 minutes Medium Severity Verified June 2026
Summarize with ChatGPTSummarize with ClaudeSummarize with Perplexity Add as Preferred Source on Google
Error Code
59
Brand
Synology
Product Type
nas
Severity
Medium
DIY Difficulty
Medium
Estimated Fix Time
45–90 minutes
Synology NAS Error Code 59 appears when a DiskStation Manager (DSM) software update fails partway through and the system automatically initiates a rollback to the previous version. This typically happens due to a corrupted update package, interrupted network connection, or insufficient storage space on the system partition. While the automatic rollback protects your data, you will need to take a few steps to get your NAS fully stable and successfully updated.
Ad

Tools You'll Need

How to Fix Error Code 59

  1. Do Not Power Off During Rollback

    Never force-shut down your Synology NAS during an active rollback. Wait for the status LED to return to a steady blue or green before proceeding.

  2. Confirm the Rollback Completed Successfully

  3. Check Available System Space

  4. Re-download the DSM Update Package

  5. Verify the Downloaded File Integrity

  6. Disable All Third-Party Packages Temporarily

  7. Apply the Update via Manual Upload

    Ensure the NAS is connected to a UPS (uninterruptible power supply) if possible during the update to guard against power loss.

  8. Check Storage Pool and Volume Health After Update

  9. Review System Logs for Residual Errors

Ad

When to Call a Professional

Contact Synology Support (support.synology.com) or a qualified NAS technician if: (1) the rollback itself fails and DSM does not load after 30 minutes, (2) you see red drive health warnings in Storage Manager after the rollback, (3) the system enters a boot loop and you cannot access DSM at all, or (4) multiple update attempts continue to fail with Error 59. In those cases, Synology Support may guide you through a reinstallation using Synology Assistant without data loss, or the unit may require warranty service.

Frequently Asked Questions

Will Synology Error Code 59 cause me to lose my data?
In most cases, no. Error Code 59 triggers an automatic rollback specifically designed to protect your data and revert DSM to the last working version. Your files stored on the data volumes are separate from the system partition and should remain intact. However, always maintain up-to-date backups using Hyper Backup before performing any DSM update.
Why did my Synology DSM update fail with Error Code 59?
The most common causes are: a corrupted or incomplete update package download, an interrupted network connection during the update, insufficient free space on the system partition, a conflicting third-party package, or a brief power fluctuation during the update process. Identifying and resolving the root cause before retrying will prevent the error from recurring.
How do I manually update DSM after Error Code 59?
Download the correct .pat update file for your NAS model directly from the Synology Download Center, verify its SHA-256 checksum, then go to DSM > Control Panel > Update & Restore > Manual DSM Update, upload the file, and apply it over a stable wired connection. Stop all third-party packages before starting.
Is it safe to restart my Synology NAS after Error Code 59?
Yes, once the rollback has fully completed and the status LED is steady, it is safe to restart. Do not restart or power cycle the NAS while the rollback is still actively running, as this could corrupt the system partition. If the NAS appears stuck for more than 30 minutes, contact Synology Support before taking action.
How can I prevent Synology Error Code 59 from happening again?
To minimize future update failures: always use a wired Ethernet connection for updates, connect your NAS to a UPS to prevent power interruptions, ensure at least 2 GB of free system space before updating, stop non-essential third-party packages before each update, and always verify the checksum of manually downloaded .pat files. Consider enabling automatic backups via Hyper Backup before each scheduled update.

Related Error Codes