Apparently, the card I had is incompatibile in some way with the
motherboard I was using, a Via chipset board. Both the cards work fine
in a different motherboard. I guess this is case closed.
Thanks to everyone!
--
Josh Litherland ([EMAIL PROTECTED]
-
To unsubscribe from this list: send
Henrik Holst [EMAIL PROTECTED] wrote:
It would be good to have an analog to memtest but for PATA and SATA
ports. Anyone seen something like that out there on the web?
Are you looking for `badblocks'?
There is also a `memtest.sh' from Doug Ledford. It's main intention is,
as the name suggests,
Stranger than we dreamt it...
I got a new, identical card, the Syba 4-port PCI card and had EXACTLY
the same problems. Tried with all new cables, exact same problems.
Moved the card into each PCI slot in the system. Same problems.
I put the drives and cables into a different system onto an
On Mon, 2006-09-04 at 15:12 +1000, Neil Brown wrote:
It this repeatable?
100% repeatable.
Does the checksum stay wrong?
Yes, once they have changed to the bad value, they don't move again that
I've seen (done several trials over the past few days).
If you stop the array and run 'mdadm -E'
On Mon, 2006-09-04 at 12:00 -0400, Josh Litherland wrote:
I'll test to see if they actually change values, but I can say for
certain that they are still invalid checksum, i.e. once I stop the array
I have to assemble it with -U resync to get it back online. (and it of
course rebuilds)
Some
This one will really curl your hair. So, operating with the knowledge
that the checksum's state of correctness or incorrectness was changing
all the time, I did this:
while [ $? != 0 ] ; do
mdadm -A /dev/md0 /dev/sd[abcd]1
done
after 1,518 trials it successfully assembled.
*beats head
On Monday September 4, [EMAIL PROTECTED] wrote:
This one will really curl your hair. So, operating with the knowledge
that the checksum's state of correctness or incorrectness was changing
all the time, I did this:
while [ $? != 0 ] ; do
mdadm -A /dev/md0 /dev/sd[abcd]1
done
On Tue, 2006-09-05 at 07:35 +1000, Neil Brown wrote:
Something is SERIOUSLY wrong.
As it affects all drives, I suspect the drives are fine.
As that machine doesn't crash instantly, I suspect the cpu/memory is
fine.
Which leaves the controller and cables.
for i in `seq 1 20`; do
dd
On Tue, 2006-09-05 at 07:35 +1000, Neil Brown wrote:
Try
for i in `seq 1 20`; do
dd if=/dev/sda of=/tmp/try-$i conv=direct
done
for i in `seq 2 20`; do
cmp -l /tmp/try-1 /tmp/try=$i
done
I tried a variant of this:
for i in `seq 1 20`; do
dd if=/dev/sda1 of=/tmp/try-$i
On Mon, 2006-09-04 at 17:46 -0400, Josh Litherland wrote:
I've only used it for a couple days, but never got any read errors or invalid
file problems.
Feh, disregard that. I've beaten it up some more, and occasional errors
are cropping up. Bad card. Nothing more to see here, move along.
On Monday September 4, [EMAIL PROTECTED] wrote:
On Mon, 2006-09-04 at 17:46 -0400, Josh Litherland wrote:
I've only used it for a couple days, but never got any read errors or
invalid file problems.
Feh, disregard that. I've beaten it up some more, and occasional errors
are cropping
Josh Litherland wrote:
Feh, disregard that. I've beaten it up some more, and occasional errors
are cropping up. Bad card. Nothing more to see here, move along.
It would be good to have an analog to memtest but for PATA and SATA
ports. Anyone seen something like that out there on the web?
On Saturday September 2, [EMAIL PROTECTED] wrote:
Attempting to build a new raid5 md array across 4 hard drives. At the
exact moment that the drive finishes rebuilding, the superblock checksum
changes to an invalid value. During the rebuild, mdadm -E for the 4
drives shows:
Attempting to build a new raid5 md array across 4 hard drives. At the
exact moment that the drive finishes rebuilding, the superblock checksum
changes to an invalid value. During the rebuild, mdadm -E for the 4
drives shows:
Checksum : 70c0863a - correct
Checksum : 70c0864c -
14 matches
Mail list logo
