Red Hat Bugzilla – Bug 124426
can not use devname with cdrecord
Last modified: 2007-11-30 17:10:43 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Description of problem:
cdrecord no longer finds my ide cdrw driver, it also crashes and
complains about devname
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. [root@box root]# cdrecord -scanbus -dev=/dev/hdc
Actual Results: Cdrecord-Clone 2.01a27-dvd (i686-pc-linux-gnu)
Copyright (C) 1995-2004 Jï¿½rg Schilling
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to
Note: The author of cdrecord should not be bothered with problems in
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
cdrecord: No such device or address. Cannot open '/dev/hdc'. Cannot
open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
Expected Results: output should show details about my cdrw drive
[root@box root]# ll /dev/cdrom
lrwxrwxrwx 1 root root 8 May 16 17:01 /dev/cdrom -> /dev/hdc
I have mounted cds, and have used the burner with Fedora Core 1 with
the ide-scsi kernel option.
ide-scsi=hdc was in the grub.conf, and was not removed during the
upgrade process. After removing ide-scsi=hdc, the results from
`cdrecord -scanbus` are what are to be expected.
anaconda is to be blamed
Can you attach your grub.conf?
I had a similar problem and tracked it down to an ide-scsi parameter
that should not have been copied over by anaconda during the update to
The entry in grub.conf as created by anaconda:
title Fedora Core (2.6.5-1.358)
kernel /boot/vmlinuz-2.6.5-1.358 ro root=LABEL=/ hdc=ide-scsi
hdc is a cd burner. The max luns entry is unrelated; it was added to
keep a 6-in-1 USB memory card reader from producing dozens of
duplicate scsi entries.
You might want to roll this and other similar bugs up into a single
one. There's a whole host of cdr- and dvd-related symptoms caused by
the retention of that boot parameter.
Closing due to inactivity. Please reopen if you have further
information to add to this report.