Raid 5 and file data corrupted

Discussions on using the professional data recovery program R-STUDIO for RAID re-construction, NAS recovery, and recovery of various disk and volume managers: Windows storage spaces, Apple volumes, and Linux Logical Volume Manager.
TanerJames
Posts: 7
Joined: Sun Dec 16, 2018 8:26 am

Raid 5 and file data corrupted

Post by TanerJames » Fri Dec 21, 2018 1:47 pm

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 definition and did a scan.
File names and folders are no problem but file contents are corrupted.


for Example: GPL.txt



File Start Offset: D7CED2F000
offset 1..4096 = First 4096 byte of file is no problem.

(D7CED30000 offset): The file is getting corrupted here.

(D7CED31000 offset): Next 4096 byte: Data is no problem.

So the first 4096 blocks are normal, the next 4096 blocks are corrupted and the next 4096 blocks are normal.


How that happens ?



Thanks.


Image

Image

Image

Image

Image

Image

Image

Image

TanerJames
Posts: 7
Joined: Sun Dec 16, 2018 8:26 am

Re: Raid 5 and file data corrupted

Post by TanerJames » Sun Dec 23, 2018 6:15 am

I checked XOR:

Sector: 1810327936:

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


Check XOR:
47829C4905B9CE27F5CFD68B7DA8B3D7 xor CCCCCCCCCCCCCCCCF94401007C23F3FF = 8B4E5085C97502EB0C8BD78B018B4028


XOR no problem.


But how does data corrupted?


Raid builded result:
Image


1. Hard Disk:
Image

2. Hard Disk:
Image

3. Hard Disk:
Image

Alt
Site Moderator
Posts: 2459
Joined: Tue Nov 11, 2008 2:13 pm
Contact:

Re: Raid 5 and file data corrupted

Post by Alt » Mon Dec 24, 2018 11:47 am

You may check the integrity of the RAID by checking its consistency.
The problem is apparently with the volume on the RAID rather than the RAID itself. What has happened?

Post Reply