From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1K8tBI-00049m-04
	for qemu-devel@nongnu.org; Wed, 18 Jun 2008 04:38:16 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1K8tBG-00048h-8V
	for qemu-devel@nongnu.org; Wed, 18 Jun 2008 04:38:15 -0400
Received: from [199.232.76.173] (port=50997 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1K8tBF-00048F-L0
	for qemu-devel@nongnu.org; Wed, 18 Jun 2008 04:38:13 -0400
Received: from kurt.tools.de ([192.76.135.70]:39385)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <jk@tools.de>) id 1K8tBE-0005GG-Pa
	for qemu-devel@nongnu.org; Wed, 18 Jun 2008 04:38:13 -0400
Received: from imap.tools.intra (homes.tools.intra [172.20.0.4])
	by kurt.TooLs.DE (Postfix) with ESMTP id A41FC45814
	for <qemu-devel@nongnu.org>; Wed, 18 Jun 2008 10:38:09 +0200 (MEST)
Received: from tiger2.tools.intra (tiger2.tools.intra [172.20.0.11])
	by imap.tools.intra (Postfix) with SMTP id 915D64D19E
	for <qemu-devel@nongnu.org>; Wed, 18 Jun 2008 10:38:09 +0200 (CEST)
Date: Wed, 18 Jun 2008 10:38:09 +0200 (CEST)
From: Juergen Keil <jk@tools.de>
Subject: Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Et1Q07+G/WXrz7yXueqPNQ==
Message-Id: <20080618083809.915D64D19E@imap.tools.intra>
Reply-To: Juergen Keil <jk@tools.de>, qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Anthony Liguori wrote:

> Volkan YAZICI wrote:
> > On Tue, 17 Jun 2008, Volkan YAZICI <yazicivo@ttmail.com> writes:
> >   
> >>   root:~# diff \
> >>   > /root/scd0.iso.md5sum
> >>   > /home/windows/windows-server-2003-standard-x86-64-sp2.iso.md5sum
> >>   1c1
> >>   < b5d670b7360dc43af8157a50de43bac1  scd0.iso
> >>   ---
> >>   > cfcf3b24d9b44e75826259c9e914bf40  
windows-server-2003-standard-x86-64-sp2.iso
> >>     
> >
> > More interesting results:
> >
> >   windows:~# md5sum windows-server-2003-standard-x86-64-sp2-dd-bs-*
> >   b5d670b7360dc43af8157a50de43bac1  
windows-server-2003-standard-x86-64-sp2-dd-bs-1024.iso
> >   b253aa547f8a7269b6589caa001bd566  
windows-server-2003-standard-x86-64-sp2-dd-bs-2048.iso
> >   64a9d318690bfe223b0e3c5c15b392e3  
windows-server-2003-standard-x86-64-sp2-dd-bs-32768.iso
> >   b5d670b7360dc43af8157a50de43bac1  
windows-server-2003-standard-x86-64-sp2-dd-bs-512.iso
> >
> > Quite funny. (By the way, all of them are of same size.) Should I trust
> > that bs={1024,512} produce the right result?  Anyway, neither of them
> > solve the problem. Any ideas?
> >   
> 
> Sounds like there are errors on your disk.


Assuming these are errors on the optical media:  Why doesn't the
drive detect and report them?  Shouldn't the "dd" have failed with
some sort of EIO errors?