> Hello,
>
> anything started with a try to burn Slackware 12.0 from the original DVD
> to an new medium with different boot settings. I always got corrupted
> results and didn't know why.
>
> So I started with an "md5sum -c CHECKSUMS.md5" directly on the original
> media. This resulted in "anything OK".
>
> Now I copied the whole DVD to my hard drive and created an ISO from it.
> I mounted the ISO locally and my md5sum now results in 5 corrupted files.
>
> --> A Bug in mkisofs?
>
> No, unfortunately not, as a md5sum on the copy, I have created from the
> original DVD by using "cp -vr" is corrupted, too!
>
> So md5sum on the original DVD is OK, but after copying to my hard drive,
> several files are corrupted.
>
> I'm using kernel 2.6.21.5. Distribution is Slackware 12.0
> All my "partitions" are LVs in LVM2
>
> I also updated the kernel to 2.6.23.12 to test with this one, but I
> still get corrupted files.
>
> Is this a LVM bug? Do I already have a corrupted LVM filesystem? How to
> check/fix it? Is this a known kernel bug? Which may be the reason for
> corrupted files?
>
> I've created a backup of my important data to a second disc to a "real
> ext2 partition" (without LVM), but this is connected to the same IDE
> controller and I don't even know if I may still trust my mainboard...
>
> I also get those kernel messages via dmesg:
>
>
http://pastebin.org/16537
