For a long time the Synology was checking the file system, and constantly prompting me if I wanted to take a corrective action for the corrupted data, which I replied with yes. With that I knew that the volume was ext4, and thus I could start the file system check with: Syn-vSAM> fsck.ext4 /dev/vg1000/lvĪfter that I got a lot of (scary) messages which almost gave me the feeling that it was not recoverable. dev/vg1000/lv /volume1 ext4 usrjquota=er,grpjquota=oup,jqfmt=vfsv0,synoacl 0 0 I actually found a similar post that was having a similar issue, which reconfirmed my thoughts. I noticed the 0, which after some googling, means 0 bytes. lrwxrwxrwx 1 root root 25 Sep 22 15:35 lv -> /dev/mapper/vg1000-lvĪfter that I checked the mapper. Syn-vSAM> sudo cd /dev/vg1000/ Syn-vSAM> ls -la drwxr-xr-x 4 root root 45 Sep 22 15:35. So most probably there was some corruption that blocked the mounting of the volume. The data was still there as I could see that the Logical Volume Manager (LVM) still had the PV, LV, and VG mapped. Logical volume -īlock device 253:0 - Physical volumes. The next command gave some good insight about the logical structure of the PV, LV and VG. Syn-vSAM> mount /dev/vg1000/lv /volume1 mount: mounting /dev/vg1000/lv on /volume1 failed: No such deviceīut unfortunately, this didn’t work. So the Logical Volume in the volume group vg1000 became active.Ī small step in the recovery process, but a big step for getting my hopes up.Īfter that I tried to mount the volume with the command. Syn-vSAM> lvm vgchange -a y vg1000 1 logical volume(s) in volume group "vg1000" now active I Then tried to Enable this with the command. So this was good news, It saw a volume group called “vg1000”. Found volume group "vg1000" using metadata type lvm2 Syn-vSAM> lvm vgscan Reading all physical volumes. So I scanned for the Physical Volume (PV) with the command. 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. 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.
0 kommentar(er)
