Hello, guys! I faced with a problem: I had the "Storage Spaces" on Windows Server, but suddenly a disk broke, therefore to remain only RAID1, which was created early. In this case should have considered redundancy for OS but unfortunately this setting had had before I knew about this decision, i.e. this equipment was configured not by me. And then when I attempt to open any file it doesn't open properly, it doesn't even open at all. I opened this files by DMDE, and discovered files filled up nulls. However, files which less 50-60 kilobyte open properly. Suggest any idea, please. Sorry for my English. Thanks a lot!

I don't know a lot about storage spaces, but the file from the 2nd screenshot is a resident file. As long as you find the MFT entry for it, you'll be able to recover it as it's stored inside the MFT entry - even if you managed to detect the MFT entry from a broken RAID.

For the rest I personally have some trouble following your story.

_________________
Joep - http://www.disktuna.com - video & photo repair & recovery service

First of all, clone the healthy drive and work with the clone.

_________________
Rescue IT Datarecovery service Sweden
Rescue IT Dataräddning Göteborg AB
http://www.rescue-it.se

mr_spokk, I've already made a copy of disk. Thanks!

Arch, thanks! I have only two disks which consist of RAID1 Storage Spaces. I've noticed that files which have "s" (NTFS Sparse Files) attributes don't open and these files consist of nulls. When I opened the MFT file I found some information. This information seems right excluding both #3($DATA) and #4($Other Attribute). Files without "s" attribute open properly and have a valid structure, but files with "s" attribute consist of nulls and have the different MFT record. Could you suggest any idea? Thanks a lot!