Odd raid 5 situation.

[rsh]

Client dropped off the 3 drives. All drives imaged fine. I reassembled raid in rstudio found the correct parameters and recovered the first and largest partition with no problem. (pics and files all work). The next two partitions, everything is corrupt. Pictures look like the parameters are not correct. UFS gives me the same result. When the drives came in they were out of order. Instead of 1, 2, 3 the correct order appears to be 2, 1, 3. off set 128 and block size 32kb Anyone run into this before?

[hddguy]

I guess RAID was running degraded for some time, find which disk failed

[DR-Kiev]

I guess RAID was running degraded for some time, find which disk failed

Agree , or parametres for other 2 partitions was another.
What the name of controller?

[ReclaiMe]

If the partition table is from the original array, I'd expect parameters to stay the same for all partitions (as it was originally a single LUN). If this is the case, try excluding drives one by one.

If the partition table was reconstructed (as in TestDisk), or partition locations do not come from the original data (for whatever other reason), I'd say there were one LUN per partition, and a new parameter set need to be determined for each partition.

[lcoughey]

Let's start at the beginning. What kind of RAID hardware/software was being used? What file system is on each partition?

[rsh]

NTFS all partitions
Dell Power Edge 2650 with biult in Perc 3
He did say that 2 drives showed bad and he reseated both. He thinks his tech did this hot.

[rsh]

I took Drive2.img out of the array. All is well. I swear I did this last night. Must not of had enough coffee. Thanks for the input.