New
#1
Storage Space - Parity ( RAID5) - Lost data on creation
Hello...this is confusing.
I installed Windows 10, upgrading from Windows 7. It went fine. Nothing of note in Windows.old.
I wanted to utilise W10 Storage Pool RAID 5 Parity option for data security.
I backed up the static data from my 3 x 1.5 TB disks onto a large internal drive.
I checked the windows copy with both synctoy and freefilesync for completeness and zero errors\omissions. Twice. All was OK.
I built the RAID 5 - Parity set some 2.75Gb with the old 3 x 1.5TB drives. I transferred the data (c.1.8TB) back across, from the internal drive to populate the RAID 5 set (painfully slow). Again I checked for completeness with synctoy & freefilesync. No apparent errors.
PROBLEM
The folder M reports 913Gb of data in 1782 folders with 4171 files.
This folder is identical on the original source backup internal drive and the Storage Pool.
However when I look at the individual subfolders within M I can only locate some 151 folders with 831 files totalling c.280Gb. All the other folders are empty. Or are reporting empty. Over 600Gb of data is reported, by size & file numbers at the top level but is not in the folders (apparently).
I have run chkdsk /f on the Storage Pool and the Internal Backup disk. No errors.
I have run SFC /SCANNOW . Some Windows Resource Protection errors but no trace of missing files.
Is this that these files are hidden ? Has WIndows 10 altered all my file attributes ?
Am I missing an obvious trick ?
Did the folder structure copy across but omitted to copy the file content ?
Why did synctoy & freefilesync not pick this up ?
Why does the folder M report files/folders/size that is inconsistent with what I can locate ?
Confused. Looks like a Quantum RAID 5.
The very act of its creation destroys the data it was set up to secure.
Any bright ideas welcome. Thanks for reading.
mydogmuppet.
Quote