1. Current Location: Home >  NAS >  Don't copy the router's routine for NAS scheduled restarts; the cost isn't the hard drive being in these three places

Don't copy the router's routine for NAS scheduled restarts; the cost isn't the hard drive being in these three places

Should the NAS be restarted regularly: comparison of costs between router and NAS restarts, hard drive start-stop specifications, the three signals for rebooting, and the correct sequence

Last week, a friend visited my home and saw that the router in the weak current box automatically restarts at 4 a.m. every Wednesday. Afterwards, I set a weekly reset for my four-bay Synology unit as well. After setting it up in the third week, he asked me: Why does every time I reboot, the seeds in qBittorrent have to spin in circles for ages, and the album index task runs all over again? After hearing this, I could say one thing—the maintenance logic for routers really can't be directly applied to NAS. This article will break down the score and settle the score.

First, to correct a misconception: a scheduled restart doesn't damage the hard drive at all

Many people restart when not setting up the NAS, reasoning that "frequent start-stop motors will damage the hard drive." This sounds reasonable, but in reality, it doesn't hold up to being counted. Looking through hard drive specifications, mechanical drives generally have a Start/Stop Cycle rated at 50,000 times, NAS drives have a headload and unload rate of 600,000 times, and desktop disks have 300,000 cycles. These are the numbers stated in Western Digital's white paper, not merchant slogans.

Restarting once a week means 52 shutdowns plus 52 starts, which is counted as 104 times at most. A quota of 50,000 times is enough to keep going through this for over four hundred years. So the reason "damaged drive" can be set aside—the real reasons NAS drives fail are bad circuits, aging heads, or weak power connections. These were written in the article the warning signs of a broken drive, and basically have nothing to do with the planned start-stop schedule of dozens of times a year.

On the other hand, be cautious: just because the hard drive's start-stop loss is low doesn't mean 'unplugging' comes without cost. If the drive loses power halfway through writing, the file system must rely on log rollback to save the situation, which in extreme cases could put the entire pool at risk. I'll explain this in detail later.

Why should the router be restarted, and why shouldn't the NAS be used

?

My old AC2100 really restarts once a week. After running over 900 hours, the 5G speed drops, but the effect is immediate after restarting. The root of the router's problem lies in its hardware conditions: about 100 megabytes of memory, having to support NAT session tables, DHCP lease tables, and a bunch of state machines. On the night you connect to BT, the session table is completely full, and all new connections are lost. This kind of resource-accumulation lag is the only solution for home users. The specific account was calculated in the article NAT session table. So scheduled router restart is proper maintenance. I've written about five brands and how to set them up, see < article on a href="https://www.shunot.com/en/192-168-1-1/882.html"> router scheduled restart setup.

NAS is another resource model. My N100 mini PC has 8GB of RAM, and Feiniu system has run for over 200 days. At a free -h glance, usable memory stays around 40% year-round. When the kernel is tight, it recycles cache and uses swaps, so no need to cut off power to clear memory. Linux servers running for hundreds of days is the industry norm, which is completely different from the Windows era of "rebooting cures all problems" experience.

The key difference lies here: the router restarts, the whole family disconnects for thirty seconds, and IoT devices reconnect and it's done; Once the NAS restarts, all running operations stop. This is the real cost; let's count them one by one.

Restarting your NAS once—what exactly are you losing

?

First, seeding and downloading must be reconciled. For a normal soft reboot, qBittorrent will write the progress in the fastresume section, so after starting up, you can resume the status yourself, with little cost. But if it's an abnormal interruption like a power outage, you have to perform integrity checks on the seeds—I have 230 seeds, and checking them means reading the download disk from start to finish. The hundreds of gigabytes of the disk take a couple of hours to read, and during this time, the disk is fully loaded and can't get other tasks into the queue. The complete history of seed farming is in the article NAS as a downloader.

Second, all scheduled tasks are ruined. My backup task was done early Friday morning. rsync pushed the new photos onto my mom's old Synology machine. This window was deliberately chosen to avoid the router's Wednesday restart—a rule I set after making a mistake when scheduling tasks back then. If you casually set the NAS restart on the backup window, it's like personally breaking your own backup chain once a week, and even if it fails, no errors appear—it's the most frustrating part. The entire remote sync setup is in the article on two NAS remote backups.

Third, the restarted service needs to be "warmed up." From pressing reboot to fully service-ready, my N100 took over three minutes in actual testing: the system took one and a half minutes, then a dozen or so Docker containers were pulled up one by one for another and another minute. Album indexes and Jellyfin media library scans still needed a while before returning to normal response speed. If you've installed surveillance, you need to be even more aware—the monitoring kit runs on the NAS, and during the few minutes of reboot, there is a gap in the recording. If you want to adjust that period, you'll only see a black segment. Camera addition and recording troubleshooting are done at NAS as a surveillance recorderIn that chapter. Backing up clients on computers is even more direct—tools like Time Machine recognize continuity. When the NAS goes offline for a few minutes, the client just silently retries and leaves a failure record, making troubleshooting a waste of time.

When will it really be restarted

?

Not restarting when set does not mean never restarting. When these three signals appear, restart when necessary—don't force it.

? : it. . . Restart
How to confirm signal actions
After installing the system update, the background prompts for reboot to take effect. Choose a time when there are no tasks to restart. How to choose between updates and resolutions. See this article
Memory keeps running tight free -h Looks like the long-term availability is less than 10%, swap takes up a few gigabytes. First, find a memory-hungry container; if you can't find it, restart
Service lag is stuck and unresponsiveWebpage backend spinning, SMB cannot connect, container restarts repeatedlyindividual containers first, then run the whole system

System updates are the most legitimate reason. After installing minor security patches, restart when needed. Don't be like me, dragging things out for three months—that journey is in the article NAS system update. Don't rush to restart the memory issue. Most likely, some container is missing. If you sort the memory tabs in Docker, you'll probably find the culprit. If you really can't figure out how to allocate memory, refer to the three-level test in the NAS memory upgrade article. Commands like free -h require SSH to be enabled first. The entry point is the NAS SSH activation.

If you really want to restart, follow this order

The order follows one principle: let the writing work stop first. Step one: pause all tasks in qBittorrent, wait a minute or two for it to load the data onto the platform; Step two: glance at the task schedule to confirm that you haven't hit the backup window or index task, and also check the list of stolen drives in the hard drive hibernation check article, so you have a clear idea. Step three: Restart the webpage backend point to allow it to gracefully stop the service.

Unplugging the battery is the bottom of the cabinet, and you must turn off the device before unplugging. Having a UPS at home is much more respectable. After the mains power goes off, it can hold the NAS to shut down service and then safely shut down. I wrote about this setup in the article >about NAS with UPS

There's another pitfall that's especially easy to miss: the restart strategy for Docker containers. If the policy is not set to always or unless-stopped when installing containers, after the NAS reboots, the container will not revive itself and will have to manually tap each point. Several friends' Jellyfin disappeared after rebooting, and this is very likely the reason. When loading the container, I glanced at this setting again—it's much more convenient than manually putting out fires every time I restart later.

Just copy the homework accordingly

, no need to . when downloading or doing will make the device
For your situationit's recommended
to just save photos and back up. No services have been used,reboot regularly, and you might not remember it even once a year
Restartsomething is not set up, and manually restart when updating
patches FamilyMart video library + albums + surveillance cameras are all stacked on top and can't be restarted regularly. Manually using the device during peak periods
lag more and more with full memory. If you can't figure it out, then restart—don't rely on restarting to get by

Finish with order: turn off the idea of scheduled restart and let it run normally; When restarting, stop farming, avoid backup windows, and restart softly; Before unplugging the power, turn off the device; if you have a UPS, rely on the UPS. Restarting the router weekly is maintenance, but the ONT losing power every day is a loss. That amount is calculated in whether the ONT should be restarted regularly; NAS restarts from time to time aren't lazy either—three types of devices, three different logics, and for me, this comparison is no exception.

Read More


Copyright Notice Scan to read on mobile
All Rights Reserved: 《SHUNOT》 => 《Don't copy the router's routine for NAS scheduled restarts; the cost isn't the hard drive being in these three places》
Article URL: https://www.shunot.com/en/nas/1090.html
Unless otherwise stated, all articles are original by 《SHUNOT》. Reposting is welcome! Please indicate the original URL when reposting, thank you.

Contact Us

Online Consultation: Click here to send me a message

WeChat ID: master_135

Scan to follow