Hi Mathias, On 01/18/2016 10:33 AM, Mathias Mueller wrote: > Hi Phil, > > first thanks a lot for all your help and time you already spent on me > and my problem. I gathered some more information and hope you can help > me a bit more. You're welcome. > First I tried to figure out the chunk size. I used a jpg file that was > stored on the raid for sure and read 8x32 Bytes with an offset of 64k > from that file. Than I used bgrep to search for the bytestrings on my > physical devices. I found five sequent byte strings on one physical > device, so I think the chunk sice must be bigger than 256k. Very interesting. You could go one step further and compare the jpeg file contents in the first 1M against the locations found to determine where the chunks actually start and end on each device. The final offset will be a chunk multiple before these boundaries. Or do md5 sums of 4k blocks to reduce the amount to inspect. > If I am right, it would mean, that the order of my physical devices is > sdf1 sdd1 sde1 sdc1 (without knowing which one is the first partition) > and the offset between sdd1 and the other devices is f0000. Are my > assumptions correct? How can I go on with this information? This will help (and looks correct), but I don't remember what we did to try to find the beginning of your filesystem. Did we search for a filesystem signature? Please re-summarize that. Phil -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
