On 04/23/2017 08:15 AM, Patrik Dahlström wrote: > > > On 04/23/2017 02:11 PM, Wols Lists wrote: >> On 23/04/17 12:58, Roman Mamedov wrote: >>> On Sun, 23 Apr 2017 12:36:24 +0100 >>> Wols Lists <antlists@xxxxxxxxxxxxxxx> wrote: >>> >>>> And, as the raid wiki tells you, download lspci and run that >>> >>> Maybe you meant lsdrv. https://github.com/pturmel/lsdrv >>> >> Sorry, yes I did ... (too many ls_xxx commands :-) > Ok, I had to patch lsdrv a bit to make it run. Diff: Thanks for the patch. Could you elaborate a bit on the errors you received so I can reproduce and document this fully? Also, do you have some large files (media files, perhaps) that you know are in your array but you have a copy in hand? If so, you could use the findHash script in my github account to map how that file is laid out on your array's devices. Since large media files tend to be contiguous, such a map would definitively show your chunk size and device order. It would also show if your data offsets are consistent among the member drives (but not the absolute value of the offset). 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
