mount: can't find /media/cdrom in /etc/fstab or /etc/mtab
Brian Fristensky
the result of a yum update, but I need help diagnosing the problem.
1. There is no /media/cdrom when I put a CD or DVD into the drive.
If I type "mount /media/cdrom", I get the message:
mount: can't find /media/cdrom in /etc/fstab or /etc/mtab
Here is /etc/fstab:
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
Here is /etc/mtab:
/dev/mapper/VolGroup00-LogVol00 / ext3 rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
/dev/sda1 /boot ext3 rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
fusectl /sys/fs/fuse/connections fusectl rw 0 0
2. I looked at my Fedora 8 laptop, and the fstab file is identical to
the one shown above, but the CDROM drive works fine on that machine.
3. It does not appear to be an SE-Linux problem because if I change SE-linux to
permissive mode, the problem persists.
4. Could it be a kudzu problem? If I go into Services and try restarting kudzu,
I get the message:
kudzu failed. The error was: Usage /etc/init.d/kudzu {start|stop}
5. The drive stopped working sometime after I did a recent round of yum updates
on Oct. 2 and Oct. 3. Perhaps these yum.log messages will give a clue:
Oct 02 07:21:05 Installed: kernel-2.6.26.5-28.fc8.x86_64
Oct 02 07:21:10 Updated: kernel-headers-2.6.26.5-28.fc8.x86_64
Oct 02 07:21:41 Installed: kernel-devel-2.6.26.5-28.fc8.x86_64
Oct 03 20:44:05 Updated: libxml2-2.7.1-2.fc8.x86_64
Oct 03 20:44:06 Updated: nss_compat_ossl-0.9.4-1.fc8.x86_64
Oct 03 20:44:07 Updated: libbtctl-0.9.0-4.fc8.x86_64
Oct 03 20:44:08 Updated: pam_krb5-2.2.18-2.fc8.x86_64
Oct 03 20:44:08 Updated: 3:traceroute-2.0.12-1.fc8.x86_64
Oct 03 20:44:13 Updated: selinux-policy-3.0.8-117.fc8.noarch
Oct 03 20:44:14 Updated: plague-common-0.4.5.6-1.fc8.noarch
Oct 03 20:44:14 Updated: plague-client-0.4.5.6-1.fc8.noarch
Oct 03 20:44:31 Updated: selinux-policy-devel-3.0.8-117.fc8.noarch
Oct 03 20:44:46 Updated: selinux-policy-targeted-3.0.8-117.fc8.noarch
Oct 03 20:44:47 Updated: libxml2-2.7.1-2.fc8.i386
Oct 03 20:44:48 Updated: pam_krb5-2.2.18-2.fc8.i386
Oct 03 20:44:49 Updated: libxml2-python-2.7.1-2.fc8.x86_64
Oct 03 20:44:53 Updated: libxml2-devel-2.7.1-2.fc8.i386
Oct 03 20:44:56 Updated: libxml2-devel-2.7.1-2.fc8.x86_64
Oct 03 20:44:57 Updated: 1:NetworkManager-glib-0.7.0-0.11.svn4022.4.fc8.x86_64
Oct 03 20:44:59 Updated: 1:NetworkManager-0.7.0-0.11.svn4022.4.fc8.x86_64
Oct 08 07:44:49 Updated: fakeroot-1.9.7-18.fc8.x86_64
Oct 08 07:44:51 Updated: fuse-libs-2.7.4-1.fc8.x86_64
Oct 08 07:44:54 Updated: fuse-2.7.4-1.fc8.x86_64
Oct 08 07:44:54 Updated: fuse-libs-2.7.4-1.fc8.i386
6. Yes, I have tried putting disks into and out of the drive, and rebooting
numerous times.
Where do I go from here?
BrianF
Fedora 8 Live DVD, and the system came up just fine. This shows
that the hardware is okay.
Bill Marcum
On 2008-10-09, Brian Fristensky <bfri...@shaw.ca> wrote:
> On my Fedora 8 x86_84 system, /media/cdrom has disappeared. I suspect this is
> the result of a yum update, but I need help diagnosing the problem.
>
> 1. There is no /media/cdrom when I put a CD or DVD into the drive.
> If I type "mount /media/cdrom", I get the message:
>
> mount: can't find /media/cdrom in /etc/fstab or /etc/mtab
>
and mount it.
--
The difference between a Miracle and a Fact is exactly the difference
between a mermaid and a seal.
-- Mark Twain
Frank Steinmetzger
> I forgot to mention that I also tried booting my machine from the
> Fedora 8 Live DVD, and the system came up just fine. This shows
> that the hardware is okay.
[top-posting corrected]
Maybe the working machine has a daemon that creates a dir and mounts the cd
automagically. A daemon which is not running on the problem machine. I also
don't have an entry /mnt/cdrom in fstab - everything on my Gentoo system is
done by HAL/udev and KDE's service for removable media.
--
Gruß | Greetings | Qapla'
Windows is great - you can download Linux with it.
BrianF
> ["Followup-To:" header set to comp.os.linux.hardware.]
> On 2008-10-09, Brian Fristensky <bfri...@shaw.ca> wrote:
>> On my Fedora 8 x86_84 system, /media/cdrom has disappeared. I suspect this is
>> the result of a yum update, but I need help diagnosing the problem.
>>
>> 1. There is no /media/cdrom when I put a CD or DVD into the drive.
>> If I type "mount /media/cdrom", I get the message:
>>
>> mount: can't find /media/cdrom in /etc/fstab or /etc/mtab
>>
> Try the command "pmount cdrom". If it works it will create /media/cdrom
> and mount it.
>
I tried both "pmount cdrom" and "pmount /media/cdrom", both of which
gave the following message:
Error: could not determine real path of the device: No such file or
directory
In any case, pmount would be a workaround that doesn't solve the root
problem. As Frank Steinmetzger points out in this thread, the system
should be able to automatically detect when a disc is loaded
in the CD/DVD drive and mount it. As I understand it, HAL, udev, and I
believe, kudzu are all involved, but I only have a fuzzy concept
of what each does. That has always worked, until last
week, with no special entry in fstab required. So something broke.
What I want to find out is, what broke, and how to fix it.
Whoever
What does dmesg show when you insert the disk? Have you tried different
disks?
Mark Hobley
> If I type "mount /media/cdrom", I get the message:
>
> mount: can't find /media/cdrom in /etc/fstab or /etc/mtab
As root type this:
mkdir /media
mkdir /media/cdrom
mount /dev/cdrom /media/cdrom
Mark.
--
Mark Hobley,
393 Quinton Road West,
Quinton, BIRMINGHAM.
B32 1QE.
BrianF
Nothing new appears in /var/log/dmesg when I insert any of a number of
CDs. In fact, the file was last written yesterday when I rebooted the
system.
BrianF
> Brian Fristensky <bfri...@shaw.ca> wrote:
>
>> If I type "mount /media/cdrom", I get the message:
>>
>> mount: can't find /media/cdrom in /etc/fstab or /etc/mtab
>
>
> As root type this:
>
> mkdir /media
> mkdir /media/cdrom
> mount /dev/cdrom /media/cdrom
>
> Mark.
>
It's not that simple. Linux has daemons that check for new
hardware and create directories like /media/cdrom as needed.
/media/cdrom depends on there being one or two other directories
in /dev, which have to be configured correctly for anything at all
to be mounted.
I did try what you have above, which resulted
in the message:
mount: /dev/cdrom is not a block device
Whoever
Don't look at this file, depending on your distro, I think it is ONLY
updated immediatly after booting. Instead run the command:
dmesg
Or pipe it into tail:
dmesg | tail
>
>
>
>
Brian Fristensky
Okay, I put a CD into the drive and close the drive. The lights on the drive
blink a bit, and I wait a few minutes while. Now, dmesg
it87: Found IT8716F chip at 0xe80, revision 1
it87: in3 is VCC (+5V)
hwmon-vid: Unknown VRM version of your x86 CPU
warning: `dbus-daemon' uses 32-bit capabilities (legacy support in use)
eth1: no IPv6 routers present
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.9
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bridge firewalling registered
virbr0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
virbr0: starting userspace STP failed, starting kernel STP
ip_tables: (C) 2000-2006 Netfilter Core Team
virbr0: no IPv6 routers present
hda-intel: Invalid position buffer, using LPIB read method instead.
(I have only shown the last 23 lines because clearly most of this stuff
is leftover from the boot process.)
Whoever
Nothing interesting here. the last line "hda-intel" appears to relate to
sound hardware.
Is your optical drive SATA or IDE (PATA)?
Search /var/log/dmesg for anything that might relate to the optical drive
-- grep for words such as DVD, CD-ROM, etc. (use the "-i" switch to make
the search case-insensitive) and see if it detects the drive while
booting.
Frank Steinmetzger
>>>> What does dmesg show when you insert the disk? Have you tried
>>>> different disks?
>>>>
>>> Nothing new appears in /var/log/dmesg when I insert any of a number of
>>> CDs. In fact, the file was last written yesterday when I rebooted the
>>> system.
AFAIK, dmesg only shows the log of the booting.
>> Don't look at this file, depending on your distro, I think it is ONLY
>> updated immediatly after booting. Instead run the command:
>>
>> dmesg
>>
>> Or pipe it into tail:
>>
>> dmesg | tail
What about tail -f /var/log/messages?
--
Gruß | Greetings | Qapla'
Die Paßwörter, an die du dich noch erinnerst, hast du letzte Woche geändert.
Allodoxaphobia
> Brian Fristensky schrob:
>
>>>>> What does dmesg show when you insert the disk? Have you tried
>>>>> different disks?
>>>>>
>>>> Nothing new appears in /var/log/dmesg when I insert any of a number of
>>>> CDs. In fact, the file was last written yesterday when I rebooted the
>>>> system.
>
> AFAIK, dmesg only shows the log of the booting.
s/shows/shows some of/
Yesterday I saw a "/tmp too full" (or something to that effect) flash up
the screen on a boot.
Nothing showed via dmesg.
It was in /var/log/messages , tho'.
I've seen other instances like this.
Not everyone sits around and watches the boot messages flash by....
Jonesy
--
Marvin L Jones | jonz | W3DHJ | linux
38.24N 104.55W | @ config.com | Jonesy | OS/2
* Killfiling google & XXXXbanter.com: jonz.net/ng.htm
Jerry Peters
> On Mon, 13 Oct 2008 14:54:14 +0200, Frank Steinmetzger wrote:
>> Brian Fristensky schrob:
>>
>>>>>> What does dmesg show when you insert the disk? Have you tried
>>>>>> different disks?
>>>>>>
>>>>> Nothing new appears in /var/log/dmesg when I insert any of a number of
>>>>> CDs. In fact, the file was last written yesterday when I rebooted the
>>>>> system.
>>
>> AFAIK, dmesg only shows the log of the booting.
>
> s/shows/shows some of/
>
> Yesterday I saw a "/tmp too full" (or something to that effect) flash up
> the screen on a boot.
> Nothing showed via dmesg.
> It was in /var/log/messages , tho'.
>
> I've seen other instances like this.
> Not everyone sits around and watches the boot messages flash by....
>
> Jonesy
Because dmesg shows the messages from the _kernel_ printk buffer. /tmp
too full message is not coming from the kernel. Try adding "quiet" as
a parameter on the kernel command line. It shuts up almost all of the
myriads of driver messages during boot. I get just over one screenful
of messages during boot, makes spotting errors/warnings much easier.
Jerry