CD-Writing HOWTO: Troubleshooting

Next Previous Contents

## 5. Troubleshooting

Always remember, that you can still use corrupt CD-ROMs as coasters. :-)

## 5.1 It doesn't work: under Linux

Please check first, that the writer works under the software it is shipped with (=under another operating system). Concretely:

- Does the controller recognize the writer as a SCSI device?
- Does the driver software recognize the writer?
- Is it possible to make a CD using the accompanied software?

If "it doesn't even work" with the accompanied software you have a hardware conflict or defective hardware. If it works and you use loadlin to boot Linux, then that is a problem with loadlin. Loadlin makes a warm-boot with most of the hardware already initialized and that can confuse the Linux kernel.

## 5.2 Error-message: No read access for 'dev=0,6,0'.

Under Linux, some versions of the C-library are incompatible (buggy), so that an application linked against one version will not work with another. An example for an error triggered by pre-compiled binaries is the following:

> `

>     [root@Blue /dev]# cdrecord -eject dev=0,6,0
>     cdrecord: No such file or directory. No read access for 'dev=0,6,0'.

> `

The solution is to install a newer C-library.

## 5.3 It doesn't work: under DOS and friends

Try to use Linux. Installation and configuration of SCSI drivers for DOS is the hell. Linux is too complicated? Ha!

## 5.4 SCSI errors during the burning phase

Most likely those errors are caused by

- missing dis-/reconnect feature on the SCSI bus
- insufficiently cooled hardware
- defective hardware (should be detected by 5.1.)

Under various circumstances SCSI devices dis- and reconnect themselves (electronically) from the SCSI bus. If this feature is not available (check controller and kernel parameters) some writers run into trouble during burning or fixating the CD-R.

Especially the NCR 53c7,8xx SCSI driver has the feature disabled by default, so you might want to check it first:

> `

>     NCR53c7,8xx SCSI support                  [N/y/m/?] y
>        always negotiate synchronous transfers [N/y/?] (NEW) n
>        allow FAST-SCSI [10MHz]                [N/y/?] (NEW) y
>        allow DISCONNECT                       [N/y/?] (NEW) y

> `

## 5.5 Medium errors If cdrecord reports medium errors in the form of"Sense Key: ... Medium Error, Segment ...", then the mediumis not empty. If you use CD-RW, then try to switch fromblank=fast to the more reliable blank=all. If you use CD-Ronly, then make sure the CD-R has never seen a CD-writer beforeor try out discs from another manufacturer.

## 5.6 Newly written CDs are not readable on some players.

Some people reported problems with playing their self-written CDs. Very old audio players or car devices can have problems with CD-Rs, although this is extremly rare. Quite frequent are problems with CD-RWs, because they don't reflect the laserlight as good as CD-Rs and factory-pressed "silver" discs.

## 5.7 My scanner stopped working after I loaded the ide-scsi module

By inserting the SCSI-hostadaptor emulation, the naming of SCSI devices changes. If your scanner was /dev/sg0 before, it might be /dev/sg1 or /dev/sg2 now. Prominent kernel developers did not think this is completely braindead and denied solutions like devfs in the past. But that is another story, the first thing you should try is to set the link /dev/scanner to point to the actual generic SCSI device. Examples:

> `

>     cd /dev
>     ls -l scanner     # shows current setting
>     ln -sf sg2 scanner
>     # test the scanner
>     ln -sf sg1 scanner
>     # test the scanner
>     # and so on

> `

Application developers should carefully think about support for this dangerous and error prone naming scheme. Please consider at least to use intermediate solutions like the SCSI coordinates used by cdrecord.

Next Previous Contents