I've seen this type of stuff happen from IDE drives running too fast (DMA
problems), from bad cables on IDE (longer than 18"), and from poorly terminated
scsi busses (especially Adaptec).
Harald, I'd suggest giving the following a try. If you don't get the same
sums each time, you've got a hardware problem... whether drive, cable,
controller, or bad memory is left as an excerise to the reader. :)
dd if=/dev/sda bs=1024k count=400 | md5sum
# read 400mb off the disk, give us a checksum
Run that 3 or more times. If the sums change you may have a problem. This
works best on unmounted drives of course.
PS: I had an IDE drive on a 24" cable that I could e2fsck all day long and
it never got fixed. Just before throwing the whole machine out the window
I did a md5sum check, and a few minutes later determined the problem.
PPS: A friend of mine ran a Quake2 server from an Adaptec SCSI controller.
The checksums the Quake2 server does of it's maps (to determine hacked player
maps) kept coming up wrong. md5sum verified a machine problem, and not a
bad install of Quake.
-- Ted Deppner ted@psyber.com http://www.psyber.com- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/