Raid5 on intel ICH10 accidentialy deleted due to keyboard malfunction with 0xAA55

[PitKoz]

Shell this raid5 after reconstruction be initialised before test disk procedure??
If, how to do it safely.
I will continue in a while with more data still on the process of scanning...

1/. DMDE says invalid sector number and this is initial scan results:
((same says Test disk) what shall I do with it? Manualy change ? to what values? )

[devscan]
scan_dev=1:0:110x0:512:1953519616:"\\?\ide#disk1t1.0.00__#4&9f21a09&0&0.1.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
scan_range="0xe8c1c18400-0xe8e0b00000"
scan_ltrack=1.1:0x20:1.1:740:1759:0x7f7c98f143000
scan_ltrackorg=1.1:740:0x3:0x0:0x0:0xe8d0d48200:0x400000
scan_lbps=512
scan_state_sec="block:0x2000;inc:0x4000;first:0x7460e0c2;shift:0x2000;sec:0x74705800;set:0x0"
scan_modules=0x5
module_flags="7;0x7,0x7,0x7,0x7,0x7,0x7,0x7,"
module_states="7;0x10,0x0,0x10,0x0,0x0,0x0,0x0,"
expgrp="7;0x5,0x1,0x1,0x0,0x0,0x0,0x0,"
modselected=0
volselected=1
volsortcol=3

2/. rebuild raid said before reorganising matrix this:

These instructions are provided for UFS Explorer Professional Recovery versions 5.4 through 5.11
1. Launch UFS Explorer.

2. On the toolbar, select "Build RAID".
3. Set "RAID level" to "RAID 5 - stripe set with distributed parity".
4. Set "Stripe size" to "Custom stripe size (sectors)", and enter a value for a stripe size, "256".
5. Set "Parity distribution" to "Left-asymmetric (backward)".
6. Set "Parity delay" to "1".

7. On the left, select an entry starting with "Drive4:", right-click it and pick "Add to RAID" on the toolbar.
8. On the left, select an entry starting with "Drive3:", right-click it and pick "Add to RAID" on the toolbar.
9. On the left, select an entry starting with "Drive5:", right-click it and pick "Add to RAID" on the toolbar.

10. In the table on the right, for every storage set "Start sector" value to 0. To do this, use "Edit Range" on the toolbar.

11. Click "Build" to close the RAID setup.
3/.


Please help me with decisions and procedures

[cgrenier]

The RAID must be OK (correct parameters) before using TestDisk.

[PitKoz]

"OK" means what?
I am calling the previous post as definitively
it is not comprehensible.

OK=
the same order of disks
we can check it with:
programs helping to do this
1/.reclaim me free raid
2/. Raid reconstructor

FI: scan, not member disks, looks like this:

"This is a plain-text general description of the reconstructed array layout.

The array type is RAID5.
The array consists of 3 disks.

The disks are ordered as follows:
#00: Disk 2 - ST350031 2CS, Serial number 6V0CYM, \\.\PhysicalDrive2
#01: Disk 1 - ST350031 2CS, Serial number 2V4XS0, \\.\PhysicalDrive1
#02: Disk 3 - ST350031 2CS, Serial number 1V3W87, \\.\PhysicalDrive3

Block size is 128.0 KB, same as 256 sectors.
The data starts at sector (LBA) 0 (this is often called "offset" or "start offset").

Block map is as follows:

1 2 P
3 P 4
P 5 6

Generated by ReclaiMe Free RAID Recovery build 2228, www.FreeRaidRecovery.com"

and what else?

What state does it have to be?

Initialized by the system????: either Windows
(dos, fat, other or NTFS: MBR or another way of disk initialisation
dependant on hardware and software),
or other pre-requested in other systems preparations????

What else can go wrong?

I have only one chance to recover this data.

The not initialised array of 2T shows something like this:

this analytical programme brings that information about partitions and claiming a bigger disk than it is seen by it.

Thanks again and waiting for more instructions,

PitKoz