Data Recovery and Disk Utilities Forum @R-TT

I checked XOR:

Sector: 1810327936:

1. Hard Disk: 47829C4905B9CE27F5CFD68B7DA8B3D7
2. Hard Disk: CCCCCCCCCCCCCCCCF94401007C23F3FF
3. Hard Disk: 8B4E5085C97502EB0C8BD78B018B4028


Check XOR:
47829C4905B9CE27F5CFD68B7DA8B3D7 xor CCCCCCCCCCCCCCCCF94401007C23F3FF = 8B4E5085C97502EB0C8BD78B018B4028 ...

Hi,


My raid:
Raid 5 (Three Disk)
Intel Software Raid
Async
64k
2 Volume (1. vol1 and 2. vol2)


My raid failed and corrupted data

(No rebuilding etc.)

2 Partition on Vol1 is no problem
1 Partition on Vol2 is corrupted data.


I've looked at why the files are corrupted.


I made a special raid ...

Today I did a scan with the old 2 2 TB disk and found the same JPG file.

I've compared the old 2 TB disk with a funny but new Raid 4 TB disk (used chkdsk).

2 TB with 4 TB disk file is same. No differences.


I think the problem isn't chkdsk, it's something else.

Maybe problem is Raid (XOR) etc.

Example:

corrupted file: pandora_large.jpg
original file: pandora_large_orj.jpg

The file size of the two files is the same.
(191.475 bytes)

11,209 differences found.

offset: E000
From here, the file is corrupted.



Attached to WinHex compare report.

If the MFT is corrupted with chkdsk, half of the file is corrupted, half is normal?

or If the wrong Raid 5 parameter (disk order, block size, block order etc.)
so can the file be corrupted? (half of the file is corrupted)

Does the content of the corrupted file with chkdsk or Raid 5 settings need ...

When Raid the error, Windows ran "chkdsk" and checked all files (3. partition)

Could it have corrupted these files?


my raid 5 volume:
raid volume_1: two partition ( win_test and taner_win7 )
no problem data

raid volume_2: one partition (corrupt data - master )

R-studio when scanning volume_2 ...

Hi,


I have Intel Rapid Stroage RAID 5 (on mainboard)


My raid disks:
1) 2 TB
2) 2 TB
3) 2 TB


I wanted to renew my Raid disks. (for malfunction)

I do:

1) I changed to 1. disk to 4 TB new disk and rebuilded raid.
2) I changed to 2. disk to 4 TB new disk and rebuilded raid.
3) That's how I've ...