DB-유

Synology DSM 6.2 Upgrade Guide

· synology, dsm, upgrade

I put off DSM 6.2 for months on my own units because I don't like being first, and by now the release has settled enough. It brings iSCSI Manager, Active Backup for Business, the newer Storage Manager with storage pools and a pile of security fixes. It also changes things under the hood, so I treat it as more than a patch. Below is what I did on a DS918+ and a DS216+, both going from 6.1.7 to 6.2.2.

Before starting, get a verified backup, know every third-party package you run (some have no 6.2 build), and set aside an hour when the NAS can be offline.

Check the model and packages first

Confirm your model supports 6.2 in the Download Center. Then list your packages:

sudo synopkg list --name

Anything not from Synology's Package Center should be checked against its publisher for a 6.2 version; the SynoCommunity packages, for example, were updated well after the release. Note the Docker package version too: 6.2 comes with a newer Docker engine, and containers are preserved, but the upgrade restarts them.

Export the configuration and write things down

Control Panel → Update & Restore → Configuration Backup → Export Configuration. Save the .dss file off the NAS. Also record a few things DSM does not put into that file:

  • Docker: docker ps -a --format '{{.Names}} {{.Image}}' and your compose files.
  • Reverse proxy rules: cat /etc/nginx/app.d/server.ReverseProxy.conf.
  • Any manual edits under /etc or /usr/local/etc (these do not survive).

Read the release notes

Go to Download Center → your model → DSM → 6.2.2 and read the release notes, especially the "Important Note" block. Two items regularly bite people: the change from ext4-based Storage Manager terminology to storage pools (harmless) and the removal of the 32-bit compatibility layer for some old packages. If you are on 6.0, upgrade to 6.1 first; Synology does not support skipping a major-minor step.

Download the .pat file to your PC. Check its size against the Download Center page; a truncated download fails with a "corrupted file" error later.

The upgrade itself

Control Panel → Update & Restore → Manual DSM Update → Browse → the .pat → OK. DSM verifies the file, asks for confirmation, and reboots into the update. The status LED blinks for 5 to 15 minutes; the web interface returns when it is done. Do not power-cycle if it seems slow; a large volume with many snapshots can take longer while the storage manager migrates its metadata.

If you prefer the automatic route: Control Panel → Update & Restore → Update → Download → Update Now. It fetches the same file.

After the reboot

Log in and work through this list:

  1. Control Panel → Info Center → DSM version shows 6.2.2-24922 (or whichever build you installed).
  2. Package Center → Installed: every package shows Running. Packages that need an update will show a button; update them now.
  3. Storage Manager → Overview: Healthy. The old "Disk Group" is now called Storage Pool.
  4. Docker → Container: all containers back up. From SSH:
sudo docker ps --format 'table {{.Names}}\t{{.Status}}'
  1. Control Panel → Application Portal → Reverse Proxy: rules intact.
  2. Control Panel → Security → Certificate: certificates assigned as before.

Settings I touch afterwards

Two things I change right after the upgrade:

  • Control Panel → Update & Restore → Update Settings → Install important updates only, if the upgrade reset it.
  • Storage Manager → Storage Pool → Action → Data Scrubbing → Schedule: monthly, now that scheduled scrubbing exists.

And on units with a Btrfs volume, Package Center → Active Backup for Business is now available.

Final check

cat /etc.defaults/VERSION
sudo synopkg list | grep -i 'docker\|hyper'

The version file should show majorversion="6" and minorversion="2". Run a Hyper Backup task manually and make sure it completes; the backup package is the one that most often needs a relink after an upgrade. Finally, from a client, confirm SMB access and one reverse-proxied service.

If it goes sideways

  • "Failed to install the file. The file is probably corrupted. (13)": wrong model or truncated download. Compare the MD5 published on the Download Center page.
  • After the reboot the NAS is stuck with a blinking blue LED and no web interface for more than 30 minutes: connect with Synology Assistant; if it shows "Recoverable", click to restore, which reinstalls DSM but keeps data.
  • A package shows "This package is not supported on the current platform" or "Repair" in Package Center: the package has no 6.2 build. Uninstall it (Repair usually fails), or install the publisher's new version.
  • Cloud Station Server stopped working: on 6.2 it is replaced by Synology Drive Server. Install Drive from Package Center; it imports the Cloud Station database on first start.

Backup, compatibility check, read the notes, then click. Skip one of those and it isn't uneventful.