harmakhis

hi, follow this tutorial

hi, followed those two tutorials https://www.dsebastien.net/2015/05/19/recovering-a-raid-array-in-e-state-on-a-synology-nas/ https://blogs.dbcloudsvc.com/life/fixed-the-crashed-basic-volume-of-synology-nas/ and applying on my BASIC 1HDD crashed volume # Stop all NAS services except from SSH > sudo syno_poweroff_task -d $ sudo mdadm --detail /dev/md5 /dev/md5: Version : 1.2 Creation Time : Mon May 4 20:54:01 2020 Raid Level : raid1 Array Size : 5331334464 (5084.36 GiB 5459.29 GB) Used Dev Size : 5331334464 (5084.36 GiB 5459.29 GB) Raid Devices : 1 Total Devices : 1 Persistence : Superblock is persistent Update Time : Sun May 10 00:40:01 2020 State : clean, FAILED Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : SynoNas:5 UUID : 6bbaadf9:fccd6e69:66518019:2ee66ad8 Events : 22 Number Major Minor RaidDevice State 0 8 35 0 faulty active sync /dev/sdc3 $ sudo mdadm --examine /dev/sdc3 /dev/sdc3: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : 6bbaadf9:fccd6e69:66518019:2ee66ad8 Name : SynoNas:5 Creation Time : Mon May 4 20:54:01 2020 Raid Level : raid1 Raid Devices : 1 Avail Dev Size : 10662668960 (5084.36 GiB 5459.29 GB) Array Size : 5331334464 (5084.36 GiB 5459.29 GB) Used Dev Size : 10662668928 (5084.36 GiB 5459.29 GB) Data Offset : 2048 sectors Super Offset : 8 sectors Unused Space : before=1968 sectors, after=32 sectors State : clean Device UUID : 524c0a00:3ef4e283:2d9a4151:0764a8ed Update Time : Sun May 10 00:40:01 2020 Checksum : 1f2a1c29 - correct Events : 22 $cat /proc/mdstat md5 : active raid1 sdc3[0](E) 5331334464 blocks super 1.2 [1/1] [E] $ sudo mdadm --stop /dev/md5 mdadm: stopped /dev/md5 $ sudo mdadm -Cf /dev/md5 -e1.2 -n1 -l1 /dev/sdc3 -u6bbaadf9:fccd6e69:66518019:2ee66ad8 mdadm: /dev/sdc3 appears to be part of a raid array: level=raid1 devices=1 ctime=Mon May 4 20:54:01 2020 Continue creating array? y mdadm: array /dev/md5 started. admin@SynoJeux:/$ cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [raidF1] md5 : active raid1 sdc3[0] 5331334464 blocks super 1.2 [1/1] $ sudo e2fsck -pvf -C0 /dev/md5 and voilaaaaaaa

hi, my server stopped during file moving beetween hdds it results in crashed volume, no repair button and big red button if you need to to that on synology they said "you cant repair it yourself call technical" yeah yeah yeah i will do that....lol in fact, you can, if you are experienced first, i read that, but no effect for me and commands dont runs on me http://www.vsam.pro/crashed-synology-volume-and-how-to-restore-ds415-play/ after, i read BTRFS wiki https://btrfs.wiki.kernel.org/index.php/Btrfsck you need to sign root user, and make sudo commands so i made it, go to ssh after activated it on DSM, search your volumes in /etc/fstab mine was volume 1 who crashed, mounted on /dev/md2 as the volume is crashed its unmounted so you can proceed, it will not run on mounted volumes they are busy i used this to repair the volume, answer "yes" when it ask to delete root logs tree sudo btrfs check --repair /dev/md2 it needs time to repair, it will make messages as incorrect checksum and repair file system when its finished reboot the system as DSM can restart service and mount volume by itsefl but its done its usually as the well known FS2CK command used by linux users when file system is corrupted hope it helps ;-)