--- On Mon, 25/1/10, Goswin von Brederlow <goswin-v-b@xxxxxx> wrote: > From: Goswin von Brederlow <goswin-v-b@xxxxxx> > Subject: Re: Fw: Why does one get mismatches? > To: Jon@xxxxxxxxxxxxxxx > Cc: "Goswin von Brederlow" <goswin-v-b@xxxxxx>, linux-raid@xxxxxxxxxxxxxxx > Date: Monday, 25 January, 2010, 10:37 > Jon Hardcastle <jd_hardcastle@xxxxxxxxx> > writes: > > > Now the array is completely dismantled and I am > running bad blocks on the drives but I am on the last 2 of > the 7 drives and I still have no leads. No bad blocks, no > offline uncorrectable, no pending sectors no dmesg errors no > nothing. I have absolutely no leads what so ever. > > > > The only thing i have left to try is a full Mem test > and disconnect and reseat the additional sata controllers, > oh and buy 7 new sata cables incase 1 is bad. > > The problem with badblocks is that it writes the same > pattern > everywhere. If the problem is that data gets read/written > to the wrong > block then that will not show up. > > Try formating each drive and run fstest [1] on it. Or some > other test > that verifies data integrity using different patterns per > block. > > MfG > Goswin > > [1] http://mrvn.homeip.net/fstest/ > This is going to be a time consuming process as i'll have to remove and read from the array each drive 1 at a time then resync. Thanks for the link, but could a similar result be achieved with the -w option for badblocks? or perhaps a dd if=/dev/urandom? hmm scratch that the urandom wont work as you need to read AND write. Just a worry as i clearly have mismatches and therefore corrupted data. -- 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
