If I can't get an RMA, I'll be buying at least 1 new drive. I'll need to hook up the two bad drives and run the manufacturer diagnostics and hopefully get clear evidence of an issue that allows me to RMA the drives. Once that is done, I'll be able to replace Drive 6, and wait for it to rebuild. I'll then have to wait for the Synology to rebuild the array and populate that drive. If the parity check does complete successfully, I'll be able to replace Drive 2, which is the one with the serious problems. So those drives are going to sit in the box for a week-unless a drive dies completely in the meantime. Because I wanted to replace the drives right away, right? But that was before Synology emphasized that I should wait for the parity check to complete. I paid $50 for overnight express shipment with morning delivery. I'm 20% into the parity consistency check, and will have to wait 5+ more days for that to finish.Īs soon as I learned that I had 2 bad drives on Thursday morning, I ordered two replacement drives. I've fixed the email settings so that I am now getting email notifications. Within 30 minutes I received a reply, informing me that the likely issue was a bad disk.Īpparently the bad disk was causing the Synology to deal with read errors, and that was actually causing the Synology OS kernel to become unstable, or "kernel panic". Fortunately, I received a response from Synology support and sent them a debug log that they had requested. On Thursday morning, the Synology was again unresponsive. But it was late and I was tired, so I left it and would look into it in the morning. So at this point, it seemed pretty clear there is a real problem. Once again, the Synology was unresponsive, so I went through the same process, and eventually had to hard reset it to login and get it working again. On Wednesday evening, I got the same error emails from my backup software. Weird.Īs a precaution, I submitted a support case with Synology asking them how I should handle this situation in the future and what might be causing it. I was able to browse the shares and access the web interface. I eventually had to hold the power button down for 10 seconds to hard reset the Synology, and then turned it back on.Īfter it rebooted, it seemed fine. Strangely, after issuing the shutdown command, I was able to login to the web interface, but it was very slow and wasn't displaying properly. I was eventually able to login, so I tried these commands to try and reboot the Synology via the SSH terminal.Īfter issuing the command for a reboot, the power light started blinking, but the unit didn't shutdown. Like 30 seconds to get a login prompt, 30 seconds to respond after entering my username, etc. I was able to connect, but it was VERY slow. I then tried connecting over SSH using Putty. Yup, the lights were on.Īfter several refreshes and a long delay, the login page eventually loaded, but I couldn't login. I then checked to make sure the Synology was turned on. I then opened a web browser to login to the Synology. When I tried to access the UNC path for my Synology on my Windows desktop, I got an error that the device could not be found. Based on the errors, it looks like both backup apps were unable to access my Synology NAS, where their backup files are stored.
0 Comments
Leave a Reply. |