Re: Failed create or resync - incorrect checksums

On Wednesday August 16, ryo.away@gmail.com wrote:

Hello,

I have been trying to get a raid5 array going on SuSE 10.1 Final
(2.6.16.21-0.13-default) but every time I create, resync, or rebuild a
spare it seems to have worked, but

    # mdadm --examine /dev/sd[bcd]1

gives a report that the checksum is off:

    /dev/sdb1:

...

           Checksum : 4a95604a - expected 4a955f4e

Weird.... does this happen for all drives?

Furthermore, I can work with the array at this point and it seems to
be ok unless I were to reboot or stop and re-assemble it:

    # mdadm --assemble /dev/md1
    mdadm: failed to add /dev/sdc1 to /dev/md1: Invalid argument
    mdadm: failed to add /dev/sdd1 to /dev/md1: Invalid argument
    mdadm: failed to add /dev/sdb1 to /dev/md1: Invalid argument
    mdadm: /dev/md1 assembled from 0 drives - not enough to start the array.

I've tried to assemble with --update=resync, super-minor, or
summaries.  The latter two seem to work, but the data on the array has
become corrupt as a result.  I would greatly appreciate any help
anybody could give.

This shouldn't corrupt the array...
I'd be very suspicious of your hardware, whether controller cabling or
drives..

It really looks like you aren't getting back what you wrote out.

Can you try creating a filesystem on just one drive, copy some very
larges files into it, and the sha1sum the files to make sure they
haven't changed.

NeilBrown