----- Original Message ----
From: Nigel Henry <cave.dnb@xxxxxxxxxx>
To: fedora-list@xxxxxxxxxx
Sent: Thursday, July 12, 2007 8:32:54 AM
Subject: F7 Problem with automount and cdrom drive
I've fixed most of the little problems on this fresh install of Fedora 7, but
am left with 2 that I'm having problems with.
I'm getting lots of output from running tailf /var/log/messages as root, as
below.
# tailf /var/log/messages
Jul 12 14:53:20 localhost smartd[2475]: smartd has fork()ed into background
mode. New PID=2475.
Jul 12 14:53:26 localhost pcscd: winscard.c:219:SCardConnect() Reader E-Gate 0
0 Not Found
Jul 12 14:53:27 localhost last message repeated 3 times
Jul 12 14:53:35 localhost gdmgreeter[2579]: The accessibility registry was not
found.
Jul 12 14:54:18 localhost kernel: sr0: CDROM not ready. Make sure there is a
disc in the drive.
Jul 12 14:54:21 localhost last message repeated 3 times
Jul 12 14:54:21 localhost kernel: NET: Registered protocol family 4
Jul 12 14:54:22 localhost kernel: NET: Registered protocol family 5
Jul 12 14:54:22 localhost kernel: sr0: CDROM not ready. Make sure there is a
disc in the drive.
Jul 12 14:54:53 localhost last message repeated 31 times
Jul 12 14:55:54 localhost last message repeated 61 times
On the previous run of tailf /var/log/messages there was a pid about these
"sr0: CDROM not ready" messages, which identified "automount", and the man
page for it sent me to /etc/auto.misc, which shows the following.
# $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $
#
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# Details may be found in the autofs(5) manpage
cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom
# the following entries are samples to pique your imagination
#linux -ro,soft,intr ftp.example.org:/pub/linux
#boot -fstype=ext2 :/dev/hda1
#floppy -fstype=auto :/dev/fd0
#floppy -fstype=ext2 :/dev/fd0
#e2floppy -fstype=ext2 :/dev/fd0
#jaz -fstype=ext2 :/dev/sdc1
#removable -fstype=ext2 :/dev/hdd
It looks like I can just comment out the "cd" line above, and the problem will
be resolved, but I don't understand why the message line above mentions "sr0:
CDROM not ready". If "sr0" is referencing a block device, no such one
exists. The one for the cddrive is "scd0", and there are a bunch of links
pointing to it. The cddrive is a CDRW/DVD one, and music cd's play ok with
Kscd, and Kscd as default is pointing to /dev/cdrom, which points
to /dev/scd0.
The question is:
Why does "sr0" appear to be tied in with the CDROM drive, resulting in all
thes messages (one per second)?
I've booted with both kernels (not the xen ones), with the same results.
$ uname -r
2.6.21-1.3228.fc7 (the currently booted one)
and
2.6.21-1.3194.fc7 (the one installed from the install cdroms)
For the 1st time on a Fedora install I've left selinux running per default
"Enforcing", just to see how it goes, and don't want to just disable it, if
the above problem has nothing to do with selinux.
Any observations, suggestions would be very welcome.
Nigel.
btw: This is problem 1, and the other one will follow if I can't resolve it.
--
----- End of Original Message ----
Doing a dmesg returns
scsi 1:0:0:0: CD-ROM _NEC DVD_RW ND-3520A 1.04 PQ: 0 ANSI: 5
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@xxxxxxxxxx
and a line
sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
follows. They are alternate names for the first SCSI CD-ROM. I believe it relates the CDRW part of /dev/scd0
[root@localhost ~]# ls /dev/sr0 -l
ls: cannot access /dev/sr0: No such file or directory
Hope someone sheds more list on this issue.
Regards,
Antonio
____________________________________________________________________________________
Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow
