Rihc0

Rightnow I use reclaime pro recovery software from a friend of mine and I can see the data, and try to get it of the raid. hopefully it works

Okay, I'll wait for flyride

I shut down the server and removed the GPU that was causing problems. I started the server and the virtual machine and this is the output of the commands you have send me. this is with the harddrives the xpenology VM had in the first place I won't touch it unless you say so ^^. sorry for doing many things wrong output of "cat /proc/mdstat" ash-4.3# cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [raidF1] md3 : active raid5 sdg3[0] sde3[1] 15606591488 blocks super 1.2 level 5, 64k chunk, algorithm 2 [5/2] [UU___] md2 : active raid1 sdb3[0] sdc3[1] 11955200 blocks super 1.2 [2/2] [UU] md127 : active raid1 sde1[1] sdg1[0] 2490176 blocks [12/2] [UU__________] md1 : active raid1 sdb2[0] sdc2[1] sde2[2] sdg2[3] sdh2[4] 2097088 blocks [12/5] [UUUUU_______] md0 : active raid1 sdb1[0] sdc1[1] 2490176 blocks [12/2] [UU__________] unused devices: <none> output of "mdadm --detail /dev/md3" ash-4.3# mdadm --detail /dev/md3 /dev/md3: Version : 1.2 Creation Time : Sat Jun 20 00:46:08 2020 Raid Level : raid5 Array Size : 15606591488 (14883.61 GiB 15981.15 GB) Used Dev Size : 3901647872 (3720.90 GiB 3995.29 GB) Raid Devices : 5 Total Devices : 2 Persistence : Superblock is persistent Update Time : Sun Nov 22 18:24:28 2020 State : clean, FAILED Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K Name : Dabadoo:2 UUID : ff64862b:9edfe233:c498ea84:9d4b9ffd Events : 39112 Number Major Minor RaidDevice State 0 8 99 0 active sync /dev/sdg3 1 8 67 1 active sync /dev/sde3 - 0 0 2 removed - 0 0 3 removed - 0 0 output of "mdadm --examine /dev/sd[efgh]3" ash-4.3# mdadm --examine /dev/sd[efgh]3 /dev/sde3: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : ff64862b:9edfe233:c498ea84:9d4b9ffd Name : Dabadoo:2 Creation Time : Sat Jun 20 00:46:08 2020 Raid Level : raid5 Raid Devices : 5 Avail Dev Size : 7803295744 (3720.90 GiB 3995.29 GB) Array Size : 15606591488 (14883.61 GiB 15981.15 GB) Data Offset : 2048 sectors Super Offset : 8 sectors Unused Space : before=1968 sectors, after=0 sectors State : clean Device UUID : a5de7554:193b06b9:b1f1a8df:3c917e8b Update Time : Sun Nov 22 18:24:28 2020 Checksum : 381624 - correct Events : 39112 Layout : left-symmetric Chunk Size : 64K Device Role : Active device 1 Array State : AA... ('A' == active, '.' == missing, 'R' == replacing) /dev/sdg3: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : ff64862b:9edfe233:c498ea84:9d4b9ffd Name : Dabadoo:2 Creation Time : Sat Jun 20 00:46:08 2020 Raid Level : raid5 Raid Devices : 5 Avail Dev Size : 7803295744 (3720.90 GiB 3995.29 GB) Array Size : 15606591488 (14883.61 GiB 15981.15 GB) Data Offset : 2048 sectors Super Offset : 8 sectors Unused Space : before=1968 sectors, after=0 sectors State : clean Device UUID : e0c37824:42d56226:4bb0cdcc:d29cca2f Update Time : Sun Nov 22 18:24:28 2020 Checksum : cf085fb5 - correct Events : 39112 Layout : left-symmetric Chunk Size : 64K Device Role : Active device 0 Array State : AA... ('A' == active, '.' == missing, 'R' == replacing) mdadm: No md superblock detected on /dev/sdh3. ash-4.3#

Sorry for not saying the purple screen happend, totally forgot it due some personal issues. I have removed the gpu which cause the purple screen and will be uploading the output of the commands. And wont touch the server until you guys say so . Sorry for the trouble, I appreciate you guys helping me.

The whole server rebooted because i got a purple screen view days ago. Also removed a few hard drives but those did not belong to the original raid, maybe i added them accidentally to the virtual machine en removed them when i pulled them out of the server. you still think this can work ?

ash-4.3# fdisk -l /dev/sd* Disk /dev/sdb: 16 GiB, 17179869184 bytes, 33554432 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x22d5f435 Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdb2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdb3 9437184 33349631 23912448 11.4G fd Linux raid autodetect Disk /dev/sdb1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdb2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdb3: 11.4 GiB, 12243173376 bytes, 23912448 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdc: 16 GiB, 17179869184 bytes, 33554432 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x8504927a Device Boot Start End Sectors Size Id Type /dev/sdc1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdc2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdc3 9437184 33349631 23912448 11.4G fd Linux raid autodetect Disk /dev/sdc1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdc2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdc3: 11.4 GiB, 12243173376 bytes, 23912448 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdd: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sde: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: EB6537B4-CC88-4A1B-99A4-C235A327CFB6 Device Start End Sectors Size Type /dev/sde1 2048 4982527 4980480 2.4G Linux RAID /dev/sde2 4982528 9176831 4194304 2G Linux RAID /dev/sde3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sde1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sde2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sde3: 3.6 TiB, 3995288469504 bytes, 7803297792 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes The primary GPT table is corrupt, but the backup appears OK, so that will be used. Disk /dev/sdf: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E3D1C69D-D406-4A97-BF00-168262F1025C Device Start End Sectors Size Type /dev/sdf1 2048 4982527 4980480 2.4G Linux RAID /dev/sdf2 4982528 9176831 4194304 2G Linux RAID /dev/sdf3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sdg: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: AB3D10CC-2A35-4075-AF8B-135C47B30870 Device Start End Sectors Size Type /dev/sdg1 2048 4982527 4980480 2.4G Linux RAID /dev/sdg2 4982528 9176831 4194304 2G Linux RAID /dev/sdg3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sdg1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdg2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdg3: 3.6 TiB, 3995288469504 bytes, 7803297792 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdh: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: F681C773-F2AE-452F-8E71-55511FA5AEE0 Device Start End Sectors Size Type /dev/sdh1 2048 4982527 4980480 2.4G Linux RAID /dev/sdh2 4982528 9176831 4194304 2G Linux RAID /dev/sdh3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sdh1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdh2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdh3: 3.6 TiB, 3995288469504 bytes, 7803297792 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdm3: 4 MiB, 4177408 bytes, 8159 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes I don't know what happend but according to the log it rebooted yea

so I did the first 3 commands, and with the third command I got this. output of: # mdadm -v --create --assume-clean -e1.2 -n5 -l5 /dev/md3 /dev/sdg3 /dev/sde3 /dev/sdf3 /dev/sdh3 missing -uff64862b:9edfe233:c498ea84:9d4b9ffd ash-4.3# mdadm -v --create --assume-clean -e1.2 -n5 -l5 /dev/md3 /dev/sdg3 /dev/sde3 /dev/sdf3 /dev/sdh3 missing -uff64862b:9edfe233:c498ea84:9d4b9ffd mdadm: layout defaults to left-symmetric mdadm: chunk size defaults to 64K mdadm: /dev/sdg3 appears to be part of a raid array: level=raid5 devices=5 ctime=Sat Jun 20 00:46:08 2020 mdadm: /dev/sde3 appears to be part of a raid array: level=raid5 devices=5 ctime=Sat Jun 20 00:46:08 2020 mdadm: cannot open /dev/sdf3: No such file or directory ash-4.3#

I see, I thought I used raid 5, but not sure, and filesystem is ext4 for sure. lets try. Btw, how did you configure your nas? I want to do it the best way but at the moment I learn by making mistakes, and I don't know what is the best way to set it up.

I don't, I guess that is something that shows how the raid is configured?

Okay, Sorry for the late reply, the lifecycle controller on my server was not doing great and had to troubleshoot it. Ill redo all the commands because there might have been some changes. output of sudo fdisk -l /dev/sd* ash-4.3# sudo fdisk -l /dev/sd* Disk /dev/sdb: 16 GiB, 17179869184 bytes, 33554432 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x22d5f435 Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdb2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdb3 9437184 33349631 23912448 11.4G fd Linux raid autodetect Disk /dev/sdb1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdb2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdb3: 11.4 GiB, 12243173376 bytes, 23912448 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdc: 16 GiB, 17179869184 bytes, 33554432 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x8504927a Device Boot Start End Sectors Size Id Type /dev/sdc1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdc2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdc3 9437184 33349631 23912448 11.4G fd Linux raid autodetect Disk /dev/sdc1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdc2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdc3: 11.4 GiB, 12243173376 bytes, 23912448 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdd: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sde: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: EB6537B4-CC88-4A1B-99A4-C235A327CFB6 Device Start End Sectors Size Type /dev/sde1 2048 4982527 4980480 2.4G Linux RAID /dev/sde2 4982528 9176831 4194304 2G Linux RAID /dev/sde3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sde1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sde2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sde3: 3.6 TiB, 3995288469504 bytes, 7803297792 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes The primary GPT table is corrupt, but the backup appears OK, so that will be used. Disk /dev/sdf: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E3D1C69D-D406-4A97-BF00-168262F1025C Device Start End Sectors Size Type /dev/sdf1 2048 4982527 4980480 2.4G Linux RAID /dev/sdf2 4982528 9176831 4194304 2G Linux RAID /dev/sdf3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sdg: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: AB3D10CC-2A35-4075-AF8B-135C47B30870 Device Start End Sectors Size Type /dev/sdg1 2048 4982527 4980480 2.4G Linux RAID /dev/sdg2 4982528 9176831 4194304 2G Linux RAID /dev/sdg3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sdg1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdg2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdg3: 3.6 TiB, 3995288469504 bytes, 7803297792 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdh: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: F681C773-F2AE-452F-8E71-55511FA5AEE0 Device Start End Sectors Size Type /dev/sdh1 2048 4982527 4980480 2.4G Linux RAID /dev/sdh2 4982528 9176831 4194304 2G Linux RAID /dev/sdh3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sdh1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdh2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdh3: 3.6 TiB, 3995288469504 bytes, 7803297792 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdm3: 4 MiB, 4177408 bytes, 8159 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes output of cat /proc/mdstat ash-4.3# cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [raidF1] md3 : active raid5 sdg3[0] sde3[1] 15606591488 blocks super 1.2 level 5, 64k chunk, algorithm 2 [5/2] [UU___] md2 : active raid1 sdb3[0] sdc3[1] 11955200 blocks super 1.2 [2/2] [UU] md127 : active raid1 sde1[1] sdg1[0] 2490176 blocks [12/2] [UU__________] md1 : active raid1 sdb2[0] sdc2[1] sde2[2] sdg2[3] sdh2[4] 2097088 blocks [12/5] [UUUUU_______] md0 : active raid1 sdb1[0] sdc1[1] 2490176 blocks [12/2] [UU__________] unused devices: <none> output of: mdadm --detail /dev/md3 ash-4.3# mdadm --detail /dev/md3 /dev/md3: Version : 1.2 Creation Time : Sat Jun 20 00:46:08 2020 Raid Level : raid5 Array Size : 15606591488 (14883.61 GiB 15981.15 GB) Used Dev Size : 3901647872 (3720.90 GiB 3995.29 GB) Raid Devices : 5 Total Devices : 2 Persistence : Superblock is persistent Update Time : Tue Nov 17 03:41:41 2020 State : clean, FAILED Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K Name : Dabadoo:2 UUID : ff64862b:9edfe233:c498ea84:9d4b9ffd Events : 39101 Number Major Minor RaidDevice State 0 8 99 0 active sync /dev/sdg3 1 8 67 1 active sync /dev/sde3 - 0 0 2 removed - 0 0 3 removed - 0 0 4 removed output of: mdadm --examine /dev/sd[defgh]3 | egrep 'Event|/dev/sd' ash-4.3# mdadm --examine /dev/sd[defgh]3 | egrep 'Event|/dev/sd' mdadm: No md superblock detected on /dev/sdh3. /dev/sde3: Events : 39101 /dev/sdg3: Events : 39101 mdadm --examine /dev/sdg3 ash-4.3# mdadm --examine /dev/sdg3 /dev/sdg3: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : ff64862b:9edfe233:c498ea84:9d4b9ffd Name : Dabadoo:2 Creation Time : Sat Jun 20 00:46:08 2020 Raid Level : raid5 Raid Devices : 5 Avail Dev Size : 7803295744 (3720.90 GiB 3995.29 GB) Array Size : 15606591488 (14883.61 GiB 15981.15 GB) Data Offset : 2048 sectors Super Offset : 8 sectors Unused Space : before=1968 sectors, after=0 sectors State : clean Device UUID : e0c37824:42d56226:4bb0cdcc:d29cca2f Update Time : Tue Nov 17 03:41:41 2020 Checksum : cf00f943 - correct Events : 39101 Layout : left-symmetric Chunk Size : 64K Device Role : Active device 0 Array State : AA... ('A' == active, '.' == missing, 'R' == replacing) mdadm --examine /dev/sdh3 ash-4.3# mdadm --examine /dev/sdh3 mdadm: No md superblock detected on /dev/sdh3.

Okay, I had to do this on an another virtual machine because I deleted the other one because i thought it was hopeless :P. output of sudo fdisk -l /dev/sd* ash-4.3# sudo fdisk -l /dev/sd* Disk /dev/sdb: 16 GiB, 17179869184 bytes, 33554432 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x22d5f435 Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdb2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdb3 9437184 33349631 23912448 11.4G fd Linux raid autodetect Disk /dev/sdb1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdb2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdb3: 11.4 GiB, 12243173376 bytes, 23912448 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdc: 16 GiB, 17179869184 bytes, 33554432 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x8504927a Device Boot Start End Sectors Size Id Type /dev/sdc1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdc2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdc3 9437184 33349631 23912448 11.4G fd Linux raid autodetect Disk /dev/sdc1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdc2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdc3: 11.4 GiB, 12243173376 bytes, 23912448 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdd: 3.7 TiB, 3999688294400 bytes, 7811891200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 88AB940C-A74C-425C-B303-3DD15285C607 Device Start End Sectors Size Type /dev/sdd1 2048 7811889152 7811887105 3.7T unknown Disk /dev/sdd1: 3.7 TiB, 3999686197760 bytes, 7811887105 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sde: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: EB6537B4-CC88-4A1B-99A4-C235A327CFB6 Device Start End Sectors Size Type /dev/sde1 2048 4982527 4980480 2.4G Linux RAID /dev/sde2 4982528 9176831 4194304 2G Linux RAID /dev/sde3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sde1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sde2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sde3: 3.6 TiB, 3995288469504 bytes, 7803297792 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdf: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: AB3D10CC-2A35-4075-AF8B-135C47B30870 Device Start End Sectors Size Type /dev/sdf1 2048 4982527 4980480 2.4G Linux RAID /dev/sdf2 4982528 9176831 4194304 2G Linux RAID /dev/sdf3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sdf1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdf2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdf3: 3.6 TiB, 3995288469504 bytes, 7803297792 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdg: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: F681C773-F2AE-452F-8E71-55511FA5AEE0 Device Start End Sectors Size Type /dev/sdg1 2048 4982527 4980480 2.4G Linux RAID /dev/sdg2 4982528 9176831 4194304 2G Linux RAID /dev/sdg3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sdg1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdg2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdg3: 3.6 TiB, 3995288469504 bytes, 7803297792 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes The primary GPT table is corrupt, but the backup appears OK, so that will be used. Disk /dev/sdh: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E3D1C69D-D406-4A97-BF00-168262F1025C Device Start End Sectors Size Type /dev/sdh1 2048 4982527 4980480 2.4G Linux RAID /dev/sdh2 4982528 9176831 4194304 2G Linux RAID /dev/sdh3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sdi: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdm3: 4 MiB, 4177408 bytes, 8159 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes ash-4.3# output of cat /proc/mdstat ash-4.3# cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [raidF1] md3 : active raid5 sdf3[0] sde3[1] 15606591488 blocks super 1.2 level 5, 64k chunk, algorithm 2 [5/2] [UU___] md2 : active raid1 sdb3[0] sdc3[1] 11955200 blocks super 1.2 [2/2] [UU] md127 : active raid1 sde1[1] sdf1[0] 2490176 blocks [12/2] [UU__________] md1 : active raid1 sdb2[0] sdc2[1] sde2[2] sdf2[3] sdg2[4] 2097088 blocks [12/5] [UUUUU_______] md0 : active raid1 sdb1[0] sdc1[1] 2490176 blocks [12/2] [UU__________] unused devices: <none> ash-4.3# output of: mdadm --detail /dev/md3 ash-4.3# mdadm --detail /dev/md3 /dev/md3: Version : 1.2 Creation Time : Sat Jun 20 00:46:08 2020 Raid Level : raid5 Array Size : 15606591488 (14883.61 GiB 15981.15 GB) Used Dev Size : 3901647872 (3720.90 GiB 3995.29 GB) Raid Devices : 5 Total Devices : 2 Persistence : Superblock is persistent Update Time : Fri Nov 13 02:22:44 2020 State : clean, FAILED Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K Name : Dabadoo:2 UUID : ff64862b:9edfe233:c498ea84:9d4b9ffd Events : 39091 Number Major Minor RaidDevice State 0 8 83 0 active sync /dev/sdf3 1 8 67 1 active sync /dev/sde3 - 0 0 2 removed - 0 0 3 removed - 0 0 4 removed ash-4.3# output of: mdadm --examine /dev/sd[defgh]3 | egrep 'Event|/dev/sd' ash-4.3# mdadm --examine /dev/sd[defgh]3 | egrep 'Event|/dev/sd' mdadm: No md superblock detected on /dev/sdg3. /dev/sde3: Events : 39091 /dev/sdf3: Events : 39091 ash-4.3#

forgot this one

I created the 2x 16gb so I could boot the Synology Nas. I had a ds918+ but the hardware was slow :(. I asked if you think I won't be able to repair this because if not then, I know it is pointless on working on this problem. I should learn more abut the raid and how it works, I am too unfamiliar with it

you think I won't be able to repair this?

Disk /dev/sdb: 16 GiB, 17179869184 bytes, 33554432 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xa43eb840 Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdb2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdb3 9437184 33349631 23912448 11.4G fd Linux raid autodetect Disk /dev/sdb1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdb2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdb3: 11.4 GiB, 12243173376 bytes, 23912448 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdc: 16 GiB, 17179869184 bytes, 33554432 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x7a551fe7 Device Boot Start End Sectors Size Id Type /dev/sdc1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdc2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdc3 9437184 33349631 23912448 11.4G fd Linux raid autodetect Disk /dev/sdc1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdc2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdc3: 11.4 GiB, 12243173376 bytes, 23912448 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdd: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: AB3D10CC-2A35-4075-AF8B-135C47B30870 Device Start End Sectors Size Type /dev/sdd1 2048 4982527 4980480 2.4G Linux RAID /dev/sdd2 4982528 9176831 4194304 2G Linux RAID /dev/sdd3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sdd1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdd2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdd3: 3.6 TiB, 3995288469504 bytes, 7803297792 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes The primary GPT table is corrupt, but the backup appears OK, so that will be used. Disk /dev/sde: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E3D1C69D-D406-4A97-BF00-168262F1025C Device Start End Sectors Size Type /dev/sde1 2048 4982527 4980480 2.4G Linux RAID /dev/sde2 4982528 9176831 4194304 2G Linux RAID /dev/sde3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sdf: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: EB6537B4-CC88-4A1B-99A4-C235A327CFB6 Device Start End Sectors Size Type /dev/sdf1 2048 4982527 4980480 2.4G Linux RAID /dev/sdf2 4982528 9176831 4194304 2G Linux RAID /dev/sdf3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sdf1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdf2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdf3: 3.6 TiB, 3995288469504 bytes, 7803297792 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdg: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdh: 3.7 TiB, 4000225165312 bytes, 7812939776 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: F681C773-F2AE-452F-8E71-55511FA5AEE0 Device Start End Sectors Size Type /dev/sdh1 2048 4982527 4980480 2.4G Linux RAID /dev/sdh2 4982528 9176831 4194304 2G Linux RAID /dev/sdh3 9437184 7812734975 7803297792 3.6T Linux RAID Disk /dev/sdh1: 2.4 GiB, 2550005760 bytes, 4980480 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdh2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdh3: 3.6 TiB, 3995288469504 bytes, 7803297792 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sdm3: 4 MiB, 4177408 bytes, 8159 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes the 5 drives in my Synology right now, are the drives I had in the first place.

okay, so the physical controller had the 5 disks in raid 0 each disk working on the dsm (everything was fine from here and smoothly. I made a raid 5 disk and put it in windows because I wanted to try data recovery on it because I used the disk as raid 5 on a virtual machine before I used it for DSM, when I scanned the disk and recovered the data. I configured the 5 disks as raid 0 each disk. and connected them to dsm and now I have the error, do you guys get it, might be a bit confusing xD

There is data on it that I want to keep :(, I can't repair it because dam says I need more disks for some reason

Hello everyone, So I have a Dell r720 rack server installed with ESXi 6.7 u3. the server is running virtual machines like xpenology, but my dsm crashed somehow (really dont know what happend). i have 5x 4tb sas drives configured in the raid controller as 1 disk each Virtual disks. so 5 virtual disks total. to push the whole disk to the virtual machine and use raw disk mapping. my expenology has 5 RDM (5x 4 tb sas drives) . my DSM handles the raid and it has been set in a raid 5 ext4 file system. but now when i booted xpenology VM i got this (Picture1). when when i try to repair the storage pool (picture 3,4,5) you can see the message :(. Can anyone help me with this PS: Now i remember i deleted the virtual disks in the raid controller, made a raid 5 virtual disk for windows, booted a windows vm with the virtual disk (for some data recovery) and made seperare virtual disk for each disk and added them to expenology again)

You still get the problem with with the btrfs or the ext4 fs over the btrfs. Trust me, dont use the physical raid controller and use the dsm one. Been there

You don't want to use the raid controller and the dsm raid.because it makes it impossible for dsm to handle it. I had this done with my dell R720, I made a VD in the raid controller with 5 x 4tb hdd in raid 5. but my system got shutdown. unexpected. the raid controller of the dell could not do anything and the raid of dsm could also not do anything. becuase it had only 1 VMDK of 16tb. now i RMD all my disks to the dsm and dsm handles the raid fine. I tested it with plugging out a harddrive and plugging it in and i did not have a problem. at al. so use RDM trust me it is better. also if you make a raid with the physical raid controller and add it as a datastore in esxi it gets a VMFS format. and if you install the dsm it gets btrfs or ext4 on top of the vmfs which also makes it impossible to save it if somethings gets corrupt. also Don't use btrfs. Greetz Moi

you mean what hardware?

I have a Dell r720 installed with ESXi 6.7, I have installed a virtual machine with DSM and gave it a virtual disk of 14TB (5x4TB sas drives in raid 5) but the storage pool has crashed and I can't acces my data. Can somebody help me? root@VinflixDSM:~# mdadm --examine /dev/sd* /dev/sdb: MBR Magic : aa55 Partition[0] : 4294967295 sectors at 1 (type ee) /dev/sdb1: Magic : a92b4efc Version : 0.90.00 UUID : 703fe7fc:51255f38:3017a5a8:c86610be Creation Time : Fri Jan 17 21:42:48 2020 Raid Level : raid1 Used Dev Size : 2490176 (2.37 GiB 2.55 GB) Array Size : 2490176 (2.37 GiB 2.55 GB) Raid Devices : 12 Total Devices : 1 Preferred Minor : 0 Update Time : Fri May 8 16:43:14 2020 State : clean Active Devices : 1 Working Devices : 1 Failed Devices : 11 Spare Devices : 0 Checksum : 2044a806 - correct Events : 1861412 Number Major Minor RaidDevice State this 0 8 17 0 active sync /dev/sdb1 0 0 8 17 0 active sync /dev/sdb1 1 1 0 0 1 faulty removed 2 2 0 0 2 faulty removed 3 3 0 0 3 faulty removed 4 4 0 0 4 faulty removed 5 5 0 0 5 faulty removed 6 6 0 0 6 faulty removed 7 7 0 0 7 faulty removed 8 8 0 0 8 faulty removed 9 9 0 0 9 faulty removed 10 10 0 0 10 faulty removed 11 11 0 0 11 faulty removed /dev/sdb2: Magic : a92b4efc Version : 0.90.00 UUID : 60b54d3a:8cf29066:3017a5a8:c86610be Creation Time : Fri Jan 17 21:42:51 2020 Raid Level : raid1 Used Dev Size : 2097088 (2047.94 MiB 2147.42 MB) Array Size : 2097088 (2047.94 MiB 2147.42 MB) Raid Devices : 12 Total Devices : 1 Preferred Minor : 1 Update Time : Fri May 8 16:00:39 2020 State : clean Active Devices : 1 Working Devices : 1 Failed Devices : 11 Spare Devices : 0 Checksum : 4c48691b - correct Events : 307 Number Major Minor RaidDevice State this 0 8 18 0 active sync /dev/sdb2 0 0 8 18 0 active sync /dev/sdb2 1 1 0 0 1 faulty removed 2 2 0 0 2 faulty removed 3 3 0 0 3 faulty removed 4 4 0 0 4 faulty removed 5 5 0 0 5 faulty removed 6 6 0 0 6 faulty removed 7 7 0 0 7 faulty removed 8 8 0 0 8 faulty removed 9 9 0 0 9 faulty removed 10 10 0 0 10 faulty removed 11 11 0 0 11 faulty removed /dev/sdb3: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : e83b0c59:a57672c5:81bc8de6:2ee43ed4 Name : VinflixDSM:2 (local to host VinflixDSM) Creation Time : Fri Jan 17 23:37:33 2020 Raid Level : raid1 Raid Devices : 1 Avail Dev Size : 30055127040 (14331.40 GiB 15388.23 GB) Array Size : 15027563520 (14331.40 GiB 15388.23 GB) Data Offset : 2048 sectors Super Offset : 8 sectors Unused Space : before=1968 sectors, after=0 sectors State : clean Device UUID : ea70f066:9d36166a:ff7b1eef:15a0369c Update Time : Fri May 8 16:00:55 2020 Checksum : 7763dc4e - correct Events : 192 Device Role : Active device 0 Array State : A ('A' == active, '.' == missing, 'R' == replacing) mdadm: No md superblock detected on /dev/sdm3.

Hello, I have issues streaming 4k movies to my television, but it is lagging a lot or has to load a lot. I used xpenology to install DSM 3615xs I used the 1.03 version installer for this. the DSM is installed on a ESXI 6.7 vm on a Dell R520 with 8 cores and 160gb of RAM. everything is connected with cat6 stp and the television is a Sony 55XE9305. before I used xpenology I used a real DS918+ from synology and that worked fine. In my opinion everything is overpowered so it should work?