Luke Scharf wrote: > Have you tried running memtest86 on the faulty system? > Or have you all covered that already? I had done that, but the error turned out to be hardware-related anyway; when I finally could put the hard drive in another system there was nothing wrong with it. It appears illogical, because there was no error in /root on the "home" system, but I hadn't taken load into account. The encrypted partition run heavier than /root because of kcryptd, that's what made the difference. Or so I suspect anyway, because when I put the system under some load on the side and tried md5sum again on /root, I got the same error there too. Thus, dm-crypt was aquitted, my old junk was found guilty and was condemned, my maybe-sane-and-maybe-corrupted data got a brand-new box to live in, and I have now a whole new set of headaches to deal with and significantly less entertainment budget left to make up for it :( Z --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
