![]() ![]() So first I connected to my Synology with ssh and checked if there was still a volume present. Unfortunately, I’ve lost some of the screenshots that I made off the console, but I still know the commands and step that I’ve used. Getting my Synology volume back to work / mounted again. With my Synology up and running again, it was time to troubleshoot. I also knew that I removed the right disk, and that I didn’t touch the others. Logic said that my data was still there, since I used a RAID 5 (SHR) setup with 4 disks, and only 1 disk was broken. After that action Synology finally booted up, but the next panic attack started since I saw the screen above. Then, I decided to boot up without the faulty or replacement disk, and booted the Synology with only 3 disks. ![]() I replaced the disk but still no improvement. Luckily, I knew which disk was having problems, and so I decided to pull out the probably defected disk. So stuck in a boot loop, with no possible way to view the web interface or console, I was getting pretty nervous. So the Synology seemed to be stuck in a sort of boot loop. I hoped that it was busy with some consistency checks, but after a few days letting it do its own thing, I noticed that the disks spinned up and down every 10 min by the sound that it was making. This all happened after an update, but I think this may also have been a problem in combination with the disk failure of one of the 4 disks that I had. A soft reset was not possible through one the interfaces, and the Synology also didn’t reboot by pushing the power button. For instance, ssh was rejected, shares couldn’t be accessed, the web interface was also down, and DSM assistant couldn’t even reach or see the Synology. The Synology became sometimes unresponsive and became unreachable. It started with the fact that my Synology was having disk errors on one of the disks and that the Synology itself was getting some weird problems. This is what happened on my Synology DS415play after a power cut. The fun stops however, when you know that you might possibly lost all of your personal data on your NAS. (I've mounted both NAS's to my local computer to be able to run the duplicate check, too.As an IT guy, I have started to get a little bit of my own personal lab, and when sometimes something breaks, I always try to see it as a fun way to gain some experience and put on my troubleshooting hat. Is there some sort of CLI I can run to check which files might not be on the DS920+? I was looking at jdupes commands but didn't exactly find anything matching this situation. I moved over about a dozen or so files that may have missed the sync, but want to be sure everything is copied over. However, there was a time of about a month when the DS920+ was full and didn't get the sync. I run a backup task and all the data should be replicated on the DS920+. I've been slowly migrating from the DS220j to a DS920+. Is a crash like this covered under warranty? The drive is a WD Red Plus that's maybe a year or so old. I went on Synology's KB site and found the following regarding replacing the drive, but I'm still unsure as to a few things:ĭo I need to throw out the drive? Even if I don't need to, would it be wise not to use it again? I can still access all the data through Quickconnect so I'm not sure how "corrupted" the data is.
0 Comments
Leave a Reply. |