Geoff where did you get this information? I'd be interesting in reading it. Typically, these issues are: 1) cheap/low quality media, 2) burning at 48X and hoping that old 4x IDE cdrom will read the disk while trying to install. As a test, turn around and mount mount the CD on the machine that burned the disk and try doing a "cp -a" off the cd to your hard disk. A better option, particularly if you have enough machines is to setup a machine as a install server. Over the lan it's much faster than CD (for me any YMMV). This box can also be turned into a local repository for yum updates. It's also much faster doing an upgrade off a local box. :) .dn Geoff Galitz wrote: > > > I recently had the same problem. The package checksums and > everything else turned out to be good and we figured the > problem was with the original RHEL install/upgrade process. > > I did manage to Centos 3.3 working by installing 3.1 and then > using yum to upgrade, but it does make me nervous. > > > > -geoff > > On Oct 12, 2004, at 1:04 PM, Scott Sharkey wrote: > >> Hi All, >> >> I've downloaded this image (disk 2) from several sites, and it >> matches the MD5 sum. Burning it to a CD gives no errors, but the >> disk is failing the self-check at the start, and if I ignore that and >> try to install I get random packages which "cannot be read". I know >> the burner is OK, as I've burned other CDs on it just fine after >> burning the CentOS ones. Any thoughts? >> >> -Scott >> _______________________________________________ >> CentOS mailing list >> CentOS at caosity.org >> http://lists.caosity.org/mailman/listinfo/centos >> > http://www.galitz.org > > _______________________________________________ > CentOS mailing list > CentOS at caosity.org > http://lists.caosity.org/mailman/listinfo/centos >