public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Massive IDE problems. Who leaves data here?
Date: Tue, 22 Jan 2008 15:25:28 -0500	[thread overview]
Message-ID: <47965138.8060603@garzik.org> (raw)
In-Reply-To: <fn5ivo$ck2$1@ger.gmane.org>

Manuel Reimer wrote:
> 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

If your IDE interface is complaining about BadCRC errors, then it's 
complaining about hardware problems (bad cable, etc.)

	Jeff




  reply	other threads:[~2008-01-22 20:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 20:24 Massive IDE problems. Who leaves data here? Manuel Reimer
2008-01-22 20:25 ` Jeff Garzik [this message]
2008-01-22 20:40   ` Manuel Reimer
2008-01-22 20:46     ` Ray Lee
2008-01-22 21:04       ` Manuel Reimer
2008-01-22 21:12         ` Ray Lee
2008-01-24 16:25           ` Manuel Reimer
2008-01-24 16:26           ` Manuel Reimer
2008-01-22 23:50         ` Jan Engelhardt
2008-01-24 16:27           ` Manuel Reimer
2008-01-22 22:25     ` Alan Cox
2008-01-24 16:29       ` Manuel Reimer
2008-01-23  1:03 ` Bill Davidsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47965138.8060603@garzik.org \
    --to=jeff@garzik.org \
    --cc=Manuel.Spam@nurfuerspam.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox