also, are you sure your cd-rom drive is the primary master (/dev/hdc)???

...if you get an error like this while trying to mount the drive, this indicates at least, that it is the correct drive...
If you would try to access the wrong drive you would get an error: not a valid block-device...

Be sure to use a data-CD - preferrably one of your installation-CDs, because you know that they are working.

to verify everything the error message mentioned, issue:

mount

and see if it reports something already mounted on /mnt/cdrom - but even if that is the case, this should not cause an error like this...

Despite what I was just saying: you get an indication from the error-message, telling you: the error might be caused by your system using ide-scsi emulation and you are trying to access that drive as an ide-drive.

The output of those commands I was asking for also indicates this!

This was the output you gave:

root@paul:~# ls -l /proc/scsi
total 0
dr-xr-xr-x 2 root root 0 Aug 10 08:34 ide-scsi/
-r--r--r-- 1 root root 0 Aug 10 08:34 scsi
dr-xr-xr-x 2 root root 0 Aug 10 08:34 sg/
dr-xr-xr-x 2 root root 0 Aug 10 08:34 usb-storage-0/


If all else failed until now - give this a shot:


try to access the drive as if it is an scsi-drive - the mount command to do that is almost the same, except for the device...:

mount -t iso9660 /dev/scd0 /mnt/cdrom

or it could be:

mount -t iso9660 /dev/scd1 /mnt/cdrom

...see what that gives you

I might not have been on the wrong track after all...

Yes the cd that Iam trying is actually another linux cd. I just tried another cd and I am still getting the same error message. I know the cdrom works I'v been ablel to boot off of it is there any possibility it has to do with my partitioning scheme, I have a boot manager and windows 98 installed on another partition?

This is the output of the last command that you gave meroot@paul:~# mount -t iso9660 /dev/scd1 /mnt/cdrom
mount: /dev/scd1: unknown device
root@paul:~# mount: /dev/scd1: unknown device
-bash: mount:: command not found
root@paul:~# oot@paul:~# mount -t i

I'm almost at my whits end here - the most obvious reason now could be - the driver for iso9660 is compiled as a module and did not get loaded - thus the kernel does not know how to deal with your CD...

please give the output of (and please include the command itself and separate each from the other):

lsmod

cat /etc/lilo.conf --> if you are using lilo as bootloader

cat /etc/grub.conf --> if you are using grub as bootloader

ls -l /lib/modules/`uname -r`/kernel/drivers/cdrom/

ls -l /lib/modules/`uname -r`/kernel/fs/

ls -l /lib/modules/`uname -r`/kernel/fs/isofs/

cat /proc/filesystems

copy and paste that - so you get it right...

all this will help to determine how your kernel is set up and what to do in case the module is not loaded...

I have the same problem. When I click the cdrom icon, I get a cannot mount error. However, if I found that if I went to a console and su, then try to mount the drive via the console, it works.

TTomb> try replace ' owner' by ' user ' in your corresponding line for cdrom in /etc/fstab

Thanks, worked great.

this is ghe output that I got from the commands

cat /etc/lilo.con

LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="hdc=ide-scsi"
boot = /dev/hda1
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# DOS bootable partition config begins
other = /dev/hda4
label = DOS
table = /dev/hda
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda1

cat /etc/grub.conf
no such file or directory


ls -l /lib/modules/`uname -r`/kernel/drivers/cdrom/

-rw-r--r-- 1 root root 12114 Sep 2 2003 aztcd.o.gz
-rw-r--r-- 1 root root 14269 Sep 2 2003 cdu31a.o.gz
-rw-r--r-- 1 root root 8821 Sep 2 2003 cm206.o.gz
-rw-r--r-- 1 root root 4541 Sep 2 2003 gscd.o.gz
-rw-r--r-- 1 root root 2295 Sep 2 2003 isp16.o.gz
-rw-r--r-- 1 root root 7692 Sep 2 2003 mcd.o.gz
-rw-r--r-- 1 root root 7385 Sep 2 2003 mcdx.o.gz
-rw-r--r-- 1 root root 9305 Sep 2 2003 optcd.o.gz
-rw-r--r-- 1 root root 30150 Sep 2 2003 sbpcd.o.gz
-rw-r--r-- 1 root root 7888 Sep 2 2003 sjcd.o.gz
-rw-r--r-- 1 root root 8441 Sep 2 2003 sonycd535.o.gz
bash-2.05b#

ls -l /lib/modules/`uname -r`/kernel/fs/

drwxr-xr-x 2 root root 4096 Sep 2 2003 autofs
drwxr-xr-x 2 root root 4096 Sep 2 2003 autofs4
drwxr-xr-x 2 root root 4096 Sep 2 2003 befs
-rw-r--r-- 1 root root 3442 Sep 2 2003 binfmt_aout.o.gz
-rw-r--r-- 1 root root 4822 Sep 2 2003 binfmt_misc.o.gz
drwxr-xr-x 2 root root 4096 Sep 2 2003 coda
drwxr-xr-x 2 root root 4096 Sep 2 2003 cramfs
drwxr-xr-x 2 root root 4096 Sep 2 2003 freevxfs
drwxr-xr-x 2 root root 4096 Sep 2 2003 hfs
drwxr-xr-x 2 root root 4096 Sep 2 2003 hfsplus
drwxr-xr-x 2 root root 4096 Sep 2 2003 hpfs
drwxr-xr-x 2 root root 4096 Sep 2 2003 intermezzo
drwxr-xr-x 2 root root 4096 Sep 2 2003 jfs
drwxr-xr-x 2 root root 4096 Sep 2 2003 minix
drwxr-xr-x 2 root root 4096 Sep 2 2003 ncpfs
drwxr-xr-x 2 root root 4096 Sep 2 2003 nfsd
drwxr-xr-x 2 root root 4096 Sep 2 2003 nls
drwxr-xr-x 2 root root 4096 Sep 2 2003 ntfs
drwxr-xr-x 2 root root 4096 Sep 2 2003 qnx4
-rw-r--r-- 1 root root 4599 Sep 2 2003 quota_v2.o.gz
drwxr-xr-x 2 root root 4096 Sep 2 2003 smbfs
drwxr-xr-x 2 root root 4096 Sep 2 2003 sysv
drwxr-xr-x 2 root root 4096 Sep 2 2003 udf
drwxr-xr-x 2 root root 4096 Sep 2 2003 ufs
bash-2.05b#ls -l /lib/modules/`uname -r`/kernel/fs/isofs/
No such file or directory

cat /proc/filesystems

nodev rootfs
nodev bdev
nodev proc
nodev sockfs
nodev tmpfs
nodev shm
nodev pipefs
ext3
ext2
nodev ramfs
umsdos
msdos
vfat
iso9660
nodev nfs
reiserfs
nodev devpts
nodev usbdevfs
nodev usbfs
bash-2.05b#

[edit]

Try to put in lilo.conf :
append="hdc=ide-scsi"

after the line :
root = /dev/hda1

oops - Cedrik - you just suggested the opposite of what I was going to suggest - and which is already in the config-file...

He is using ide-scsi already - by commenting it out - everything else will be correct now...

Please correct me, when I'm wrong!



paul62:

Please answer these questions:

Is your CDROM a burner or is it just a "normal" CDROM-drive?
(if it is no burner - you do not need to use ide-scsi - which you actually do!)


Which kernel are you using ? (you get that by issuing: uname -r )


try mounting again! - this time use also this command - which I gave to you but you did not post the output for:

mount -t iso9660 /dev/scd0 /mnt/cdrom


IF that succeeds - tell us!


IF not: edit the file /etc/lilo.conf --> comment out the line that says:

append="hdc=ide-scsi"

by putting # in front of it - so it will look like this:

#append="hdc=ide-scsi"

after ! you have done this - issue the command:

lilo -v

then reboot and look if it is working now...

What this does is this: the "append=...." statement tells the kernel to use scsi-emulation for your CDROM - so it will be accessible as /dev/scd0 (it should be...)
Your current configuration is set up to see your CDROM as a normal ide-drive (as /dev/hdc ).
By commenting out the line that tells the kernel to treat your drive as scsi we are making sure, that the configuration is correct and in sync with the boot-options...

on my current system i have scsi-emulation setup for both my dvd drive and my cd-rw, when scsi-emualtions kicks in it doesn't use scd0 or scd1, however it does use sr0 and sr1, you might want to give this a try

mount -t iso9660 /dev/sr0 /mnt/cdrom
or
mount -t iso9660 /dev/sr1 /mnt/cdrom

just a suggestion

-Justin

..it was /dev/scd0 ... and so on on my system - that is why I used that - you could be right!

lets wait what he gets out of my last suggestion...

Do you know, what the difference actually is - between /dev/scd? and /dev/sr? - I think i tried both and
1.) /dev/scd? worked
2.) I think it was suggested that this was the correct device-file to use

yes I have been using a data cd all along

I am using the 2.4.22 kernel and the cdrom does not have a burner.