Florian  Freshman Member

Thanks again, Mijzelf! Let me know when you are in Berlin, then I will invite you for a beer :) Florian

Mijzelf, you are the best! I tried it first on my test system and then on the original one. After stopping md2 and entering the command the NAS said: mdadm: /dev/sda3 appears to be part of a raid array:<br> level=raid5 devices=4 ctime=Wed Jul 12 10:16:08 2017<br>mdadm: /dev/sdc3 appears to be part of a raid array:<br>…

What happened was: Disk 2 failed and the volume was degraded. When restoring the volume it crashed due to a failure of disk 4, so it was set to 'volume down'. In fact all disks are ok, and according to the PC recovery program the data can be restored using disk 1, 3 and 4. Does this help? The --examine command gives:…

1) Yes, kind of a simulation. I took a 2nd NAS (same type, same FW) and put some "old" HDDs in it. When executing mdstat the original NAS says: Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]<br>md2 : inactive sda3[0](S) sdb3[4](S) sdc3[2](S)<br> 8778405888 blocks super 1.2<br>md1 : active raid1…

Hello Mijzelf, hello all, I set up a test system with 4 x 500GB HDDs and tried to reproduce the error. The NAS is still accessible. Do you think there is a chance to recover the data? Thanks, Florian --- 'cat /proc/mdstat': --- Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md2 : inactive…

Thanks for your hints, Mijzelf! Any other ideas, especially with respect to a solution using the Zyxel NAS?