RAID 5 corrupted file

[TanerJames]

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 worked normally, I've formatted the old raid disk (2 TB) (non-raid)

4) It's been 10-15 days. I changed to 3. disk to 4 TB new disk but there was a "failed" error while processing for rebuilding.

Then the raid disk became unusable.
When I looked at it later, I found out that it was bad sector on 2nd disk. I guess that's why he couldn't do the rebuild.


my raid 5 layout:

1. raid volume: raid_1 (700gb) strip: 64kb
2. raid volume: raid_2 (2.9tb) strip: 64kb

Ofset: 0
Left Async

R-Studio with "missing disk" as a complete scan of the disk.
I have three NTFS partition and I founded three NTFS partition.

1. and 2. partition no problem, every things okay.

But 3. partition is problem: I see my files, but after recovery, the file contents are corrupted.
picture, video, music etc. corrupted.


What is problem ? How do I fix this problem?


Thanks.


raid build layout:

forum4.png

example corrupted image:

forum_bad.jpg

Check Raid consistency is problem but it reads and finds files and partition.

forum2.png

Some bad sector have a read error but the bad sector is not on the third partition.

[TanerJames]

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 (master partition):
Unexpected MFT record 38076 at 763824849408. If you are scanning RAID and this message will reappear constantly, check RAID for consistence.
..
..

forum.png

[Alt]

I think the third partition is where the RAID rebuild failed. chkdsk added insult to injury. You may run Check for consistency for that RAID and find where the inconsistent area starts.
Failed RAID rebuilds are among the most difficult cases for data recovery that requires a work of a professional data recovery specialist. But even they cannot always help.

[MHoff]

There are many software for the RAID recovery. You can give them a try. You can use the software demo version first to check whether the software can recover the data or not.

[Alt]

There are many software for the RAID recovery. You can give them a try. You can use the software demo version first to check whether the software can recover the data or not.

It's possible to try them, but a failed RAID rebuild causes a such severe damage to data that manual attention of a skilled professional is still required.

[MHoff]

It's possible to try them, but a failed RAID rebuild causes a such severe damage to data that manual attention of a skilled professional is still required.

That is why i have mentioned that he can check their Demo version. Otherwise contact any expert that will be risk free option.

[TanerJames]

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 to be completely corrupted?

If raid 5 settings are problem, how are the files in the two partition on raid 1. volume recovered?

What would you suggest?

Thanks.

pandora.png

[TanerJames]

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.

[TanerJames]

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.