Should the NAS system prompt update and go up immediately? I delayed for three months before ordering, but my colleague's phone was so reckless that it turned into bricks instantly
last week, my colleague Lao Zhou messaged me saying that after his NAS restarted, it kept spinning in circles and couldn't access the backend. When I asked, a system update notification popped up in the lower right corner of the backend the night before. He casually clicked confirm, and after a nap, the machine stopped responding. That was a Taiwan critic of Synology. Last year, I followed the Synology installation guide helped him install it. After installation, I specifically reminded him, "Don't touch the update button," but he didn't take it seriously.
at the same time, my old DS220j received the DSM 7.2 update notification. I delayed for three whole months before clicking it, and nothing happened after the upgrade. Even with system updates, one becomes bricked and the other runs smoothly. The difference isn't luck, but several types of updates, and machines are also different. In this article, I'll share my experience upgrading these two NAS devices along the way.
first distinguish between the three types of updates before deciding whether to click them
Many people get nervous when they see "a new version," but in fact, NAS update notifications fall into three categories, each with completely different risks.
the first category is minor system version updates, such as upgrading from DSM 7.2 to 7.2.1, or Feiniu from 0.8.31 to 0.8.32, where the last digit changes. Almost all installations are security patches and bug fixes, without modifying the underlying system layers, minimizing risk. I basically upgrade as soon as I see these kinds of patches, especially security patches. Don't think that just because no one is watching a home NAS, you can ignore it. Recently, Feiniu urgently pushed version 1.1.18 to fix a targeted attack vulnerability and even added a malicious file scanning feature. Every day this update drags on is like running naked. I previously wrote about NAS ransomware that most of the machines attacked are old firmware that has stopped updating.
the second category is major system version updates , such as DSM 6.2 upgrading to 7.0 or 7.1 upgrading to 7.2, where the middle digit changes. This is the type of hesitation to truly have: if the underlying system is moved, the suite compatibility may fail. Video Station incompatibility on DSM 7.2.2 is a typical example; when video playback issues occur, even HEIC photo thumbnails can't be generated, so community scripts have to fix it. My approach for major releases is to wait—wait for the first minor version (like 7.2.1), and wait for the forum complaints to die down before making any moves.
third category is package update , which is updates to Docker containers, albums, and downloads of these applications. It's a different matter from system updates. The worst case is that a single application fails; reinstalling the kit won't damage data or systems, minimizing risk.
| update type | example | what is installed | my approach |
| a minor system version | 7.2 upgrades 7.2.1 | security patches, bug fixes | upgrade |
| major system version at | 6.2, new features 7.2 | , Base changes | wait for one or two minor versions before upgrading |
| suite update | containers, albums App | single application iterations | upgrade on the spot, mess up, reinstall |
o'clock, I only did three things
no matter which upgrade I did, I couldn't skip the first three, and it took less than ten minutes combined.
first item, if you have a quick drive, take a snapshot first; if not, confirm and back up your . My Feiniu's photo drive is Btrfs. Before upgrading, I took a snapshot—this feature is provided by the file system, which ext4 doesn't have. I included the cost of choosing the model in the ext4 comparison between Btrfs. The old DS220j didn't have the conditions, so I confirmed that the rsync backup on another machine was done the same day. To be honest, NAS updates are about system partitions, so theoretically, you can't touch the data in the storage pool. But the word 'theoretical' means nothing in the face of data. backup principle always make sure to get your money before you start.
second item, review the update log from the beginning . What to look at? First, check if it's a security patch (if it is, don't drag it out); second, check if there are changes to the storage pool, file system, or the underlying package (if there are, be extra cautious); third, check if the minimum hardware requirements have changed—the issue of old machines failing to run when upgrading to new systems has really happened with J-series models like the DS220j.
the third item, pick a clean time window to . During the upgrade, the device will automatically restart. During this process, don't cut off the power. If you have a UPS at home, make sure it's working properly; if not, check the weather and the power grid. I've experienced this kind of trip before. The feeling of a RAID rebuilding at 62% and losing power is really bad. I wrote about it in UPS . Also, I avoid scheduled tasks: my home has rsync backups in the early morning, and hard drive sleep is set during those periods. If an update restart coincides with a task writing the drive, it slows down upgrades and might disrupt task status. Which tasks are secretly written down? the hibernation check is very detailed, and the other way around is perfect for choosing when to level up.
the update button for Synology is basically just decoration
back to Old Zhou's brick-like machine. The problem with Synology cannot be upgraded online lies in guidance.
to criticize Synology's boot files (called loaders in the early days, now popular with RedPill and RR series) is to "trick" the DSM kernel, making the system think it's running on genuine Synology hardware, and then insert common network card and SATA controller drivers in. The problem is that each bootstrap is only compatible with a specific version of the DSM. When you click update online, the machine writes the new firmware into the system partition. At the moment of reboot, the old bootstrap can't handle the new kernel, so the machine gets stuck at the startup stage and won't start. This is exactly what Old Zhou said: 'I keep spinning and can't get in.'
even more troublesome is that once DSM installs a major version, you can't downgrade back. The idea behind Synology brick repair is to use RR boot to force a reinstall and delete version verification files—a very roundabout operation. So the correct approach for Synology users is to turn off the automatic updates in the background, ignore the update prompt popping up in the lower right corner, and if you really want new features, follow the path of "first using the new version to boot and redo the boot disk, then manually installing the corresponding version system," taking two separate steps.
by the way, after bricking, never rush to repeatedly restart or format the structure, as that will mix in the RAID structure and double the recovery difficulty. Old Zhou's car was finally saved by reinstalling the data and struggling for a whole weekend.
my Feiniu upgrade record, I climbed from 0.8 all the way up
and then the more comfortable half of it. The Feiniu on my N100 mini PC has been up since the 0.8 era. The entry is in the desktop's "Settings" section for System Update. Click to check, Update, Download, and Install, and the machine will automatically restart once, taking five to six minutes.
Feiniu's system partition and data are separate; upgrading only affects the system part, while the storage space and shared directories remain as they are. But after each upgrade, I don't leave immediately; instead, I regularly check whether the storage pool is normal, whether several Docker containers have crawled up on their own, and whether the SMB directory mapped on the computer is still connected. Sometimes the container won't start; just enter the panel and click restart. the downloader's qBittorrent path and password are in the configuration, so they won't be lost during system upgrades.
the benefits of the upgrade are truly real. On version 0.8.27, it brought native UPS support and Time Machine backup, so my machine got two features for free; 0.8.32 added file deletion preferences, allowing SMB deleted files to go to the Recycle Bin. the accidental deletion recovery where snapshots are a backup, there's another layer of insurance. This 'one extra feature after upgrade' experience is why I don't mind Feiniu updates—its small version is definitely fixing things, not just for show.
What ifupgrade and your car goes wrong? Three options should be taken accordingly
If something really goes wrong after the upgrade, first identify the problem before taking action.
most common is packages that are incompatible , causing an application to fail to open or report version errors. For this kind of static data, go to the kit center to see if there's an update for the new system. If not, uninstall and reinstall first; if not, wait for the kit author to adapt. Usually, it takes a few days to a few weeks. Video Station's community script rescue is an advanced approach; beginners shouldn't mess with it themselves.
The second is the system itself can't run properly, old machines upgrade to a new version, with fans spinning wildly and response slowing down. At this point, downgrading is impossible because DSM does not offer a way to downgrade. If you have also enabled large file optimization in ext4, cross-version file downgrading will directly cause incompatibility. The solution for older machines is to stay in the current version and disable automatic updates, or simply move to a new machine. hard drive migration process still work.
The third type is completely unable to get up, like Old Zhou's black Synology or white Synology upgrade with power interruptions and stuck in the process. White Synology is relatively calm: all data is on the drive. When reinstalling the system with the official assistant, select "Save Data," and after system reinstallation, files remain. Here's a pitfall that's easy to overlook: Hyper Backup requires the new system version to be no lower than the backup version when restoring files, so try to use the latest version when reinstalling—don't rush with old installation packages.
just copy the table according to the number of seats
just copy it and wrap it up. NAS system updates aren't mystical—just one thing: check the version clearly, keep a backup plan, and choose the right time to .
| your situation | I suggest |
| prompt is a security minor patch | upgrade it the same day, don't drag it out |
| prompt is a major version update | waiting for one or two minor versions. Check forum reviews |
| Synology gets the update notification | automatically updates and pretends not to see it |
| old machines have tight specs | stay in the current version, turn off auto-updates |
| no snapshots or backups | add backups first, then talk about upgrades |
my fixed order: take a snapshot or confirm backup→ read the update log→ avoid scheduled task periods to update at → o'clock→ and after upgrading to check the storage pool and containers. The most time-consuming part of the whole process was actually the few minutes spent reading the logs. Compared to the weekend Old Zhou spent on it, those few minutes were worth it.
