SYNOLOGY DRIVE CRASHED BUT HEALTHY UPDATE

The fix (Please scroll down and see updates) On a fresh boot of the NAS, it would consume over 500MB of memory. Finally the kernel would panic and attempt to reduce memory usage once the swap file had filled up (keep in mind my DS1813+ has 4GB of memory).Īnalyzing “top” as well as looking at processes, I noticed the Synology index service was causing excessive memory and CPU usage. I also noticed that the issue would occur when restarting any of my 3 ESXi hosts, and would definitely occur if I restarted more than one.ĭuring the restarting, while logged in to the web GUI and SSH, I was able to see that the memory (RAM) usage would skyrocket. This occurred for over a month until it started to interfere with ESXi hosts.

SYNOLOGY DRIVE CRASHED BUT HEALTHY UPDATE

I’m currently running DSM 6.2.2-24922 Update 2. This is extremely risky as it can cause data corruption. When this occured, I would need to press and hold the power button to force it to shutdown, or pull the power. In this state, NFS sometimes would become unresponsive. The Synology DS1813+ would become unresponsive and I wouldn’t be able to SSH or use the web GUI to access it.

I just hope that this is a one-time thing and not an indication that my almost-new hardware is failing.Once I upgraded my Synology NAS to DSM 6.2 I started to experience frequent lockups and freezing on my DS1813+. Synology has done a good job of detecting drive disconnection and guiding the user through the removal and repair process. If not, I’ll need to replace the drive, then repair the storage pool by re-adding the deactivated or new drive to the pool: If the test passes, I’ll be ready to repair the degraded storage pool.

The system advised me that the test will take something like 32 hours for this 16TB drive: I’m following the advice in the first article, with instructions from the second article, to run an extended S.M.A.R.T. HDD/SSD: Drive Tests, Analytics, and Predictions (It could just as well be the NAS drive slot that is faulty, or a more random loose connection.) Two helpful Synology knowledge base articles:ĭrive errors occurred, but I am not sure if they resulted from the drives or the drive slots. I could start the repair now, but first I want to test the drive and see if the drive itself is failing. So I guess I really do have to first go to HDD and Deactivate the drive,:Īfter removing the drive and re-installing it, it appears as Not Initialized: A pop-up message advised me that insufficient drives were available: I followed the advice in that message and tried to Repair. The storage pool shows the degraded status with the crashed drive: Now the drive appeared in the HDD list as “Crashed”: I re-inserted it and its drive light came back on and turned green. The HDD log shows “Drive plugged out.” And in fact, the drive’s light on the NAS is off, as if the drive wasn’t even there: The alert shows the storage pool degraded: (Be sure you have alerts working, especially if your NAS is in a location where the beeping might not be heard.) I thought I’d share some screen shots of what the failure and recovery process looks like. Checking email confirmed my suspicion that a drive had failed-the storage pool was in a “degraded” state. Today I arrived in my office to hear my new Synology DS-1520+ NAS beeping softly.

Synology drive crashed but healthy