Re: [Qemu-devel] Re: Boot Failure (CDROM boot failure code : 0004)

[Juergen Keil <jk@tools.de>]

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?