Overview. dvdisaster provides several information about the scanning results: Examples for good media

Good CD: This screen shot shows a perfect CD: All blocks under "Medium state" are green, no C2 errors have been reported and the reading curve runs smoothly. A rising reading speed is normal for most media (see the next screen shot for a counter example). The small spikes at the beginning and at the end of the curve are normal; minor glitches like the one shown at 250M are also harmless. Sometimes the reading curve won't rise steadily: Multi-layered media might yield reading curves which are rising and dropping in a symmetric pattern. Not shown but also possible are flat curves without any change in reading speed (most typically seen with DVD-RAM).

An example for a weak medium

This medium is still readable as indicated by the green spiral shown under "Medium state". However there are clear signs of serious trouble ahead: The drive must slow down significantly towards the end of the medium in order to read from it. Note the steep fall of reading speed after the 600M mark. This comes along with C2 error rates rising to the 100 mark; this is another warning that the medium is decaying in the outer region. If you have not created error correction data this is probably the last opportunity to do so as the medium will develop the first read errors soon.

Examples of defective media

Defective CD. The red sectors in the spiral visualize large unreadable sections in the outer region of the medium. At the bottom of the window you will find the information that the medium contains 28752 unreadable sectors. This sums up to about 8.2% defective sectors (of 352486 sectors total) and is well within the recovery bounds by error correction (ecc) data made with default settings - if you have made the ecc data in time! Otherwise the contents of the red sectors are lost since ecc data cannot be created from already defective media.

Checksum errors. Yellow spots in the spiral depict places where the medium was fully readable, but the data read did not match checksums in the error correction data. There are two main causes: