eject: unable to find or open device for: `cdrom'

[Nigel Henry]

On Tuesday 09 September 2008 16:18, Mikkel L. Ellertson wrote:
> Paul Smith wrote:
> > On Tue, Sep 9, 2008 at 1:09 AM, Mikkel L. Ellertson
> >
> > Thanks, Mikkel, but my /etc/udev/rules.d/70-persistent-cd.rules does
> > not look as you describe:
> >
> > # more /etc/udev/rules.d/70-persistent-cd.rules
> > # This file was automatically generated by the /lib/udev/write_cd_rules
> > # program, probably run by the cd-aliases-generator.rules rules file.
> > #
> > # You can modify it, as long as you keep each rule on a single line
> > # and set the $GENERATED variable.
> >
> > # DVD_RW_ND-3520A (pci-0000:04:06.0-scsi-0:0:1:0)
> > ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:04:06.0-scsi-0:0:1:0",
> > SYMLINK+="cdrom", ENV{GENERATED}="1"
> > ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:04:06.0-scsi-0:0:1:0",
> > SYMLINK+="cdrw", ENV{GENERATED}="1"
> > ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:04:06.0-scsi-0:0:1:0",
> > SYMLINK+="dvd", ENV{GENERATED}="1"
> > ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:04:06.0-scsi-0:0:1:0",
> > SYMLINK+="dvdrw", ENV{GENERATED}="1"
> > #  (pci-0000:00:1f.2-scsi-1:0:1:0)
> > ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:1:0",
> > SYMLINK+="cdrom1", ENV{GENERATED}="1"
> > ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:1:0",
> > SYMLINK+="cdrw1", ENV{GENERATED}="1"
> > ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:1:0",
> > SYMLINK+="dvd1", ENV{GENERATED}="1"
> > ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:1:0",
> > SYMLINK+="dvdrw1", ENV{GENERATED}="1"
> > #
> >
> > Paul
>
> It looks like you changed where the the drive was plugged in. I
> guess my explanation left something to be desired. I should have
> provided an example to make it clear what I was talking about. In
> any case, you can change it as shown below.
>
> Change it to:
>
> # more /etc/udev/rules.d/70-persistent-cd.rules
> # This file was automatically generated by the /lib/udev/write_cd_rules
> # program, probably run by the cd-aliases-generator.rules rules file.
> #
> # You can modify it, as long as you keep each rule on a single line
> # and set the $GENERATED variable.
>
> # DVD_RW_ND-3520A (pci-0000:00:1f.2-scsi-1:0:1:0)
> ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:1:0",
>  SYMLINK+="cdrom", ENV{GENERATED}="1"
>
> ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:1:0",
>  SYMLINK+="cdrom0", ENV{GENERATED}="1"
>
> ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:1:0",
>  SYMLINK+="cdrw0", ENV{GENERATED}="1"
>
> ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:1:0",
>  SYMLINK+="dvd0", ENV{GENERATED}="1"
>
> ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:1f.2-scsi-1:0:1:0",
>  SYMLINK+="dvdrw0", ENV{GENERATED}="1"
>
> You will have to remove the line wrap cause by the long lines. I put
> a blank line between rules to make that easier. One of the comments
> is also wrapped, but that is easy to see. Do you understand the
> change I was talking about?
>
> Mikkel

Hi Mikkel. On the Ubuntu list I saw the suggestion to remove the 
70-persistant-cd.rules file, where someone was having a problem with Kaffeine 
identifying the correct name for the optical device (hda versus scd0).

I wouldn't suggest removing the file, but re-naming it (just in case), but 
shouldn't the next time you re-boot, just re-create the file, based on the 
fact that Paul only has one optical drive, and the newly created rules should 
be using cdrom, and not cdrom1.

Just a thought, and I'm definately no udev guru.

Nigel.