On 08 Oct 2002 09:33:58 -0600, John Weber wrote: > On Tue, 2002-10-08 at 06:17, Michael Schwendt wrote: > > > > > Safer: > > > > $ md5sum /dev/cdrom > > > > Is this the supposed to be the same test as the mediacheck routine? No. The mediacheck verifies an embedded checksum. On the contrary, above check should return exactly the same MD5 fingerprint than running md5sum on the corresponding ISO image file. > I > tried this on both an umounted and mounted disc #1 and in both cases > it appears to read the disk for a few minutes and then gives > > [jweber@ceora RH8.0]$ md5sum /dev/cdrom > md5sum: /dev/cdrom: Input/output error > [jweber@ceora RH8.0]$ Incorrectly burnt CD which has a few run-out sectors at the end. Sometimes this corrupts the CD, often not. The MD5 checksum will never be okay, however. See my other messages in this thread, in particular this one: Date: Tue, 8 Oct 2002 13:50:33 +0200 Message-Id: <20021008135033.07bfebb6.rh0210ms@arcor.de> If your CD-writer doesn't support DAO mode, trying adding padding options when burning in TAO mode. If that doesn't help with the run-out sectors, consult my message on the "readcd" command. That's the one linked above. > I used > > cdrecord -v -eject speed=2 dev=0,0,0 <image.iso> > > to burn the CD's. Any ideas what's going on? Do I have 2 bad cdrom > drives? If your writer supports DAO mode, try adding option "-dao".
Attachment:
pgp00081.pgp
Description: PGP signature
