LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 03-17-2008, 08:37 AM   #1
nadsab
Member
 
Registered: Mar 2004
Posts: 30

Rep: Reputation: 15
Problem mounting CDRW in Centos 5.1


Hi,

I know this is elementary, I'm pulling my hair out trying to mount my cdrw disk.

Here's what I did - I executed the command "mount /mnt/cdrom" and got the reply:
mount: can't find mnt/cdrom in /etc/fstab or /etc/mtab

So then I added the entry "mount /mnt/cdrom" into my /etc/fstab file, executed the command "mount /mnt/cdrom" again and got the reply "mount: mount point /mnt/cdrom does not exist"

So then I created the directory "/mnt/cdrom", tried "mount /mnt/cdrom" again, and now I'm getting: "mount: unknown filesystem type ''"

Here is info from cat /etc/fstab and fdisk -l:

/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

[root@localhost /]# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext3 rw,data=ordered 0 0
/dev /dev tmpfs rw 0 0
/proc /proc proc rw 0 0
/sys /sys sysfs rw 0 0
none /selinux selinuxfs rw 0 0
/proc/bus/usb /proc/bus/usb usbfs rw 0 0
devpts /dev/pts devpts rw 0 0
/dev/sda1 /boot ext3 rw,data=ordered 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
/etc/auto.misc /misc autofs rw,fd=6,pgrp=2758,timeout=300,minproto=5,maxproto=5,indirect 0 0
-hosts /net autofs rw,fd=11,pgrp=2758,timeout=300,minproto=5,maxproto=5,indirect 0 0

fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 60801 488279610 8e Linux LVM

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 60801 488384001 8e Linux LVM

At this point I am stuck, don't know what to do next. Anyone have a suggestion or know what I'm doing wrong?

Last edited by nadsab; 03-17-2008 at 08:56 AM.
 
Old 03-17-2008, 09:07 AM   #2
nadsab
Member
 
Registered: Mar 2004
Posts: 30

Original Poster
Rep: Reputation: 15
For jschiwal - answer to your question...

Does the "disc" already have data on it? It needs a filesystem before it can be mounted.

Yes the disk has data on it (I think), I ran a cdrecord command and apparently it copied a file from PC to CDRW OK.

If the cdrom drive is /dev/sr0 and you have a mount point /mnt/cdrom available, this command will mount the disc's filesystem:
sudo mount -t iso9660 /dev/sr0 /mnt/cdrom -o ro,unhide


I ran sudo mount -t iso9660 /dev/sr0 /mnt/cdrom -o ro,unhide and got back:
mount: special device /dev/sr0 does not exist

The most recent distros use hal & udev that automatically create a device node and a mount point after you insert a disc. Then you get a popup on what you want to do.

I saw a popup when I first put a blank disk in, but after I ejected and put the disk (which I copied files to) back in, the popup does not show up.

If it is a blank disc, then you need to burn it using a program, such as K3b.

I have been doing all of this with CLI not with any GUI's that come with KDE.

If it is an audio disc, you can't mount it because it doesn't have a filesystem.


It's not an audio disk, just a CDRW - just want to copy data files to and from CDRW's to PC for now.
__________________
If you see the "read" command in a bash script, it is probably wrong.

Last edited by nadsab; 03-17-2008 at 09:35 AM.
 
Old 03-17-2008, 09:10 AM   #3
DJ_Barney
Space Data Wiki
 
Registered: Mar 2008
Location: UK
Distribution: Slackware
Posts: 27

Rep: Reputation: 15
I'd suggest making a backup of fstab before you edit it. Also try not to fiddle with setup files in /etc unless you are sure what you're doing ! It's the quickest way to Bork your installation and cause frustration. Then again, saying that, you've got the right idea really. You just need to read up on the structure of fstab.

In the meantime you could mount your drive as root using...

mount <device> <mountpoint>

EXAMPLE: mount /dev/hdc /mnt/dvd

You would have to create a mount point (as root) in /mnt if it's not there. Make sure you log out of root before you try anything else.

DJ Barney
 
Old 03-17-2008, 09:22 AM   #4
nadsab
Member
 
Registered: Mar 2004
Posts: 30

Original Poster
Rep: Reputation: 15
I'd suggest making a backup of fstab before you edit it. Also try not to fiddle with setup files in /etc unless you are sure what you're doing ! It's the quickest way to Bork your installation and cause frustration. Then again, saying that, you've got the right idea really. You just need to read up on the structure of fstab.

OK will do, reading up about fstab in my RHEL book...

In the meantime you could mount your drive as root using...

mount <device> <mountpoint>

EXAMPLE: mount /dev/hdc /mnt/dvd


How would I find the device name (or do I need to create it)?

You would have to create a mount point (as root) in /mnt if it's not there. Make sure you log out of root before you try anything else.

I created "mount /mnt/cdrom" & still can't mount the CD.

Last edited by nadsab; 03-17-2008 at 09:31 AM.
 
Old 03-17-2008, 09:42 AM   #5
jschiwal
Guru
 
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654
Look at "dmesg | grep -i -e CD -e CD-ROM". This should tell you which device is the cdrom drive from the boot up messages.

Do you have a different disc you can try? How about mounting your install disc. You know that one has a filesystem on it.

Last edited by jschiwal; 03-17-2008 at 09:45 AM.
 
Old 03-17-2008, 10:00 AM   #6
nadsab
Member
 
Registered: Mar 2004
Posts: 30

Original Poster
Rep: Reputation: 15
I used the SCSI ID for the CDRW, what I did was execute cdrecord -scanbus, and got back:

scsibus6:
6,0,0 600) 'TSSTcorp' 'CDDVDW SH-S202J ' 'SB00' Removable CD-ROM
6,1,0 601) *
6,2,0 602) *
6,3,0 603) *
6,4,0 604) *
6,5,0 605) *
6,6,0 606) *
6,7,0 607) *

and with this, the actual cdrecord command I used to copy was:

cdrecord -v speed=2 dev=6,0,0 -data /home/mydir/Desktop/filename.iso
(This command comes from Fedora 8 and red hat enterprise linux, by Negus)

Does this mean that I have a SCSI CDRW drive, and that I can only mount CD's using the SCSI bus number? Actually how would i find out if I have a SCSI CDRW or not? I don't think it's scsi because the CDRW I installed to my new Intel model # DP35DP motherboard has a regular IDE cable connected between motherboard IDE connector and CDRW - DVD drive.

Negus says on page 552 - "If you have an ATAPI CD Drive, you no longer need a SCSI ID for that drive to be able to record to it. You could enter the device name instead of the SCSI ID (such as dev=/dev/cdrom). However if you have a SCSI CD drive, before you can write the image file to a CD, you muct first discover the SCSI bus number,..."


Since I could write to the disk with the scsi id but could not mount it, i assumed that i can not mount the disk/drive with the device name? Or are ATAPI drives actually connected to the SCSI bus, and I can either use the scsi address or the device name?

Last edited by nadsab; 03-17-2008 at 10:42 AM.
 
Old 03-17-2008, 10:08 AM   #7
nadsab
Member
 
Registered: Mar 2004
Posts: 30

Original Poster
Rep: Reputation: 15
I ejected and tried the actual Centos distro disk 1, same problem. This is the output of dmesg | grep -i -e CD -e CD-ROM :

uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1a.0: irq 193, io base 0x000030e0
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1a.1: irq 74, io base 0x000030c0
uhci_hcd 0000:00:1a.2: UHCI Host Controller
uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1a.2: irq 177, io base 0x000030a0
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.0: irq 82, io base 0x00003080
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.1: irq 201, io base 0x00003060
usb 2-1: new low speed USB device using uhci_hcd and address 2
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1d.2: irq 193, io base 0x00003040
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 7
ehci_hcd 0000:00:1a.7: debug port 1
ehci_hcd 0000:00:1a.7: irq 177, io mem 0xe3225c00
ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 8
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: irq 82, io mem 0xe3225800
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb 2-1: new low speed USB device using uhci_hcd and address 3
usb 3-2: new low speed USB device using uhci_hcd and address 2
Vendor: TSSTcorp Model: CDDVDW SH-S202J Rev: SB00
Type: CD-ROM ANSI SCSI revision: 05
sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 6:0:0:0: Attached scsi CD-ROM sr0
cdrom: This disc doesn't have any tracks I recognize!
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready. Make sure there is a disc in the drive.
sr0: CDROM not ready yet.
sr0: CDROM not ready yet.
sr0: CDROM not ready yet.
sr0: CDROM not ready yet.

Last edited by nadsab; 03-17-2008 at 10:15 AM.
 
Old 03-17-2008, 11:08 AM   #8
jschiwal
Guru
 
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654
Well, you know that the CDROM device is /dev/sr0. I don't know why you have the problems with disc or drive however.

Insert the disc again and after the light goes out try:
sudo mount -t iso9660 /dev/sr0 /mnt/cdrom
 
Old 03-17-2008, 11:20 AM   #9
nadsab
Member
 
Registered: Mar 2004
Posts: 30

Original Poster
Rep: Reputation: 15
When I use :

sudo mount -t iso9660 /dev/sr0 /mnt/cdrom

I get:

mount: special device /dev/sr0 does not exist

When I use:

mount /dev/cdrom /mnt/cdrom

I get:

mount: block device /dev/cdrom is write-protected, mounting read-only
mount: you must specify the filesystem type

When I use:
mount /dev/scd0 /mnt/cdrom

I get:

mount: block device /dev/scd0 is write-protected, mounting read-only
mount: you must specify the filesystem type

Last edited by nadsab; 03-17-2008 at 11:49 AM.
 
Old 03-17-2008, 11:29 AM   #10
nadsab
Member
 
Registered: Mar 2004
Posts: 30

Original Poster
Rep: Reputation: 15
When I use:

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

I get:

mount: block device /dev/scd0 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/scd0,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


WHen I use:

sudo mount -t iso9660 /dev/scd0 /mnt/cdrom -o ro,unhide

I get:

mount: wrong fs type, bad option, bad superblock on /dev/scd0,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

When I use:

sudo mount -t iso9660 /dev/sr0 /mnt/cdrom -o ro,unhide

I get:

mount: special device /dev/sr0 does not exist

Last edited by nadsab; 03-17-2008 at 11:50 AM.
 
Old 03-17-2008, 06:03 PM   #11
jschiwal
Guru
 
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654
Quote:
When I use:

mount /dev/cdrom /mnt/cdrom

I get:

mount: block device /dev/cdrom is write-protected, mounting read-only
mount: you must specify the filesystem type
I looks like udev created a /dev/cdrom device node. If you only have a single cdrom drive you could try:
sudo mount -t iso9660 /dev/cdrom /mnt/cdrom -o ro,unhide

the "-t iso9660" part specifies the filesystem type.

You can look in /dev/ to see if a device exists before running the mount command. One might be a link to another. I think that might be the case for /dev/cdrom. If you have a cd/dvd drive, a /dev/cdrom device may be created after inserting a cdrom and a /dev/dvd device created if you insert a dvd disc.
ls -l /dev/cdrom /dev/cd0 /dev/sr0
 
Old 03-17-2008, 09:00 PM   #12
nadsab
Member
 
Registered: Mar 2004
Posts: 30

Original Poster
Rep: Reputation: 15
Yes, I only have the one CDRW-DVD combo drive, no other optical drives in PC. Running "sudo mount -t iso9660 /dev/cdrom /mnt/cdrom -o ro,unhide" yeilds:

mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


This is what I have in /dev :

[root@localhost dev]# ls -la
total 8
drwxr-xr-x 13 root root 4220 Mar 17 07:11 .
drwxr-xr-x 24 root root 4096 Mar 17 08:23 ..
crw------- 1 root root 14, 12 Mar 17 07:10 adsp
crw------- 1 root root 14, 4 Mar 17 07:10 audio
drwxr-xr-x 3 root root 60 Mar 17 07:10 bus
lrwxrwxrwx 1 root root 4 Mar 17 07:10 cdrom -> scd0
lrwxrwxrwx 1 root root 4 Mar 17 07:10 cdrom-sr0 -> scd0
lrwxrwxrwx 1 root root 4 Mar 17 07:10 cdrw -> scd0
lrwxrwxrwx 1 root root 4 Mar 17 07:10 cdrw-sr0 -> scd0
lrwxrwxrwx 1 root root 4 Mar 17 07:10 cdwriter -> scd0
lrwxrwxrwx 1 root root 4 Mar 17 07:10 cdwriter-sr0 -> scd0
crw------- 1 root root 5, 1 Mar 17 07:11 console
lrwxrwxrwx 1 root root 11 Mar 17 07:10 core -> /proc/kcore
drwxr-xr-x 4 root root 80 Mar 17 07:11 cpu
drwxr-xr-x 6 root root 120 Mar 17 07:10 disk
crw------- 1 root root 14, 3 Mar 17 07:10 dsp
lrwxrwxrwx 1 root root 4 Mar 17 07:10 dvd -> scd0
lrwxrwxrwx 1 root root 4 Mar 17 07:10 dvdrw -> scd0
lrwxrwxrwx 1 root root 4 Mar 17 07:10 dvdrw-sr0 -> scd0
lrwxrwxrwx 1 root root 4 Mar 17 07:10 dvd-sr0 -> scd0
lrwxrwxrwx 1 root root 4 Mar 17 07:10 dvdwriter -> scd0
lrwxrwxrwx 1 root root 4 Mar 17 07:10 dvdwriter-sr0 -> scd0
lrwxrwxrwx 1 root root 13 Mar 17 07:10 fd -> /proc/self/fd
crw-rw-rw- 1 root root 1, 7 Mar 17 07:10 full
srwxrwxrwx 1 root root 0 Mar 17 07:11 gpmctl
crw------- 1 root root 180, 96 Mar 17 07:10 hiddev0
crw------- 1 root root 10, 228 Mar 17 07:10 hpet
prw------- 1 root root 0 Mar 17 07:11 initctl
drwxr-xr-x 2 root root 180 Mar 17 07:10 input
crw------- 1 root root 1, 11 Mar 17 07:10 kmsg
srw-rw-rw- 1 root root 0 Mar 17 07:11 log
brw-r----- 1 root disk 7, 0 Mar 17 07:10 loop0
brw-r----- 1 root disk 7, 1 Mar 17 07:10 loop1
brw-r----- 1 root disk 7, 2 Mar 17 07:10 loop2
brw-r----- 1 root disk 7, 3 Mar 17 07:10 loop3
brw-r----- 1 root disk 7, 4 Mar 17 07:10 loop4
brw-r----- 1 root disk 7, 5 Mar 17 07:10 loop5
brw-r----- 1 root disk 7, 6 Mar 17 07:10 loop6
brw-r----- 1 root disk 7, 7 Mar 17 07:10 loop7
lrwxrwxrwx 1 root root 13 Mar 17 07:10 MAKEDEV -> /sbin/MAKEDEV
drwxr-xr-x 2 root root 100 Mar 17 07:10 mapper
crw------- 1 root root 10, 227 Mar 17 07:10 mcelog
brw-r----- 1 root disk 9, 0 Mar 17 07:10 md0
crw-r----- 1 root kmem 1, 1 Mar 17 07:10 mem
crw------- 1 root root 14, 0 Mar 17 07:10 mixer
drwxr-xr-x 2 root root 60 Mar 17 07:10 net
crw-rw-rw- 1 root root 1, 3 Mar 17 07:10 null
crw-rw-rw- 1 root root 195, 0 Mar 17 07:10 nvidia0
crw-rw-rw- 1 root root 195, 255 Mar 17 07:10 nvidiactl
crw-rw---- 1 root root 10, 144 Mar 17 07:10 nvram
crw------- 1 root root 1, 12 Mar 17 07:10 oldmem
crw-rw---- 1 root lp 99, 0 Mar 17 07:10 parport0
crw-rw---- 1 root lp 99, 1 Mar 17 07:10 parport1
crw-rw---- 1 root lp 99, 2 Mar 17 07:10 parport2
crw-rw---- 1 root lp 99, 3 Mar 17 07:10 parport3
crw-r----- 1 root kmem 1, 4 Mar 17 07:10 port
crw------- 1 root root 108, 0 Mar 17 07:10 ppp
crw-rw-rw- 1 root tty 5, 2 Mar 17 21:56 ptmx
drwxr-xr-x 2 root root 0 Mar 17 07:10 pts
lrwxrwxrwx 1 root root 4 Mar 17 07:10 ram -> ram1
brw-r----- 1 root disk 1, 0 Mar 17 07:10 ram0
brw-r----- 1 root disk 1, 1 Mar 17 07:10 ram1
brw-r----- 1 root disk 1, 10 Mar 17 07:10 ram10
brw-r----- 1 root disk 1, 11 Mar 17 07:10 ram11
brw-r----- 1 root disk 1, 12 Mar 17 07:10 ram12
brw-r----- 1 root disk 1, 13 Mar 17 07:10 ram13
brw-r----- 1 root disk 1, 14 Mar 17 07:10 ram14
brw-r----- 1 root disk 1, 15 Mar 17 07:10 ram15
brw-r----- 1 root disk 1, 2 Mar 17 07:10 ram2
brw-r----- 1 root disk 1, 3 Mar 17 07:10 ram3
brw-r----- 1 root disk 1, 4 Mar 17 07:10 ram4
brw-r----- 1 root disk 1, 5 Mar 17 07:10 ram5
brw-r----- 1 root disk 1, 6 Mar 17 07:10 ram6
brw-r----- 1 root disk 1, 7 Mar 17 07:10 ram7
brw-r----- 1 root disk 1, 8 Mar 17 07:10 ram8
brw-r----- 1 root disk 1, 9 Mar 17 07:10 ram9
lrwxrwxrwx 1 root root 4 Mar 17 07:10 ramdisk -> ram0
crw-rw-rw- 1 root root 1, 8 Mar 17 07:10 random
crw------- 1 root root 162, 0 Mar 17 07:10 rawctl
brw------- 1 root root 253, 0 Mar 17 07:10 root
crw-r--r-- 1 root root 10, 135 Mar 17 07:10 rtc
brw-rw---- 1 root disk 11, 0 Mar 17 07:10 scd0
brw-r----- 1 root disk 8, 0 Mar 17 07:10 sda
brw-r----- 1 root disk 8, 1 Mar 17 07:10 sda1
brw-r----- 1 root disk 8, 2 Mar 17 07:10 sda2
brw-r----- 1 root disk 8, 16 Mar 17 07:10 sdb
brw-r----- 1 root disk 8, 17 Mar 17 07:10 sdb1
crw------- 1 root root 14, 1 Mar 17 07:10 sequencer
crw------- 1 root root 14, 8 Mar 17 07:10 sequencer2
crw------- 1 root root 21, 0 Mar 17 07:10 sg0
crw------- 1 root root 21, 1 Mar 17 07:10 sg1
crw------- 1 root root 21, 2 Mar 17 07:10 sg2
drwxrwxrwt 2 root root 40 Mar 17 07:10 shm
crw------- 1 root root 10, 231 Mar 17 07:10 snapshot
drwxr-xr-x 2 root root 160 Mar 17 07:10 snd
lrwxrwxrwx 1 root root 15 Mar 17 07:10 stderr -> /proc/self/fd/2
lrwxrwxrwx 1 root root 15 Mar 17 07:10 stdin -> /proc/self/fd/0
lrwxrwxrwx 1 root root 15 Mar 17 07:10 stdout -> /proc/self/fd/1
crw------- 1 root root 4, 0 Mar 17 07:10 systty
crw-rw-rw- 1 root tty 5, 0 Mar 17 07:10 tty
crw-rw---- 1 root root 4, 0 Mar 17 07:10 tty0
crw------- 1 root root 4, 1 Mar 17 07:11 tty1
crw-rw---- 1 root tty 4, 10 Mar 17 07:10 tty10
crw-rw---- 1 root tty 4, 11 Mar 17 07:10 tty11
crw-rw---- 1 root tty 4, 12 Mar 17 07:10 tty12
crw-rw---- 1 root tty 4, 13 Mar 17 07:10 tty13
crw-rw---- 1 root tty 4, 14 Mar 17 07:10 tty14
crw-rw---- 1 root tty 4, 15 Mar 17 07:10 tty15
crw-rw---- 1 root tty 4, 16 Mar 17 07:10 tty16
crw-rw---- 1 root tty 4, 17 Mar 17 07:10 tty17
crw-rw---- 1 root tty 4, 18 Mar 17 07:10 tty18
crw-rw---- 1 root tty 4, 19 Mar 17 07:10 tty19
crw------- 1 root root 4, 2 Mar 17 07:11 tty2
crw-rw---- 1 root tty 4, 20 Mar 17 07:10 tty20
crw-rw---- 1 root tty 4, 21 Mar 17 07:10 tty21
crw-rw---- 1 root tty 4, 22 Mar 17 07:10 tty22
crw-rw---- 1 root tty 4, 23 Mar 17 07:10 tty23
crw-rw---- 1 root tty 4, 24 Mar 17 07:10 tty24
crw-rw---- 1 root tty 4, 25 Mar 17 07:10 tty25
crw-rw---- 1 root tty 4, 26 Mar 17 07:10 tty26
crw-rw---- 1 root tty 4, 27 Mar 17 07:10 tty27
crw-rw---- 1 root tty 4, 28 Mar 17 07:10 tty28
crw-rw---- 1 root tty 4, 29 Mar 17 07:10 tty29
crw------- 1 root root 4, 3 Mar 17 07:11 tty3
crw-rw---- 1 root tty 4, 30 Mar 17 07:10 tty30
crw-rw---- 1 root tty 4, 31 Mar 17 07:10 tty31
crw-rw---- 1 root tty 4, 32 Mar 17 07:10 tty32
crw-rw---- 1 root tty 4, 33 Mar 17 07:10 tty33
crw-rw---- 1 root tty 4, 34 Mar 17 07:10 tty34
crw-rw---- 1 root tty 4, 35 Mar 17 07:10 tty35
crw-rw---- 1 root tty 4, 36 Mar 17 07:10 tty36
crw-rw---- 1 root tty 4, 37 Mar 17 07:10 tty37
crw-rw---- 1 root tty 4, 38 Mar 17 07:10 tty38
crw-rw---- 1 root tty 4, 39 Mar 17 07:10 tty39
crw------- 1 root root 4, 4 Mar 17 07:11 tty4
crw-rw---- 1 root tty 4, 40 Mar 17 07:10 tty40
crw-rw---- 1 root tty 4, 41 Mar 17 07:10 tty41
crw-rw---- 1 root tty 4, 42 Mar 17 07:10 tty42
crw-rw---- 1 root tty 4, 43 Mar 17 07:10 tty43
crw-rw---- 1 root tty 4, 44 Mar 17 07:10 tty44
crw-rw---- 1 root tty 4, 45 Mar 17 07:10 tty45
crw-rw---- 1 root tty 4, 46 Mar 17 07:10 tty46
crw-rw---- 1 root tty 4, 47 Mar 17 07:10 tty47
crw-rw---- 1 root tty 4, 48 Mar 17 07:10 tty48
crw-rw---- 1 root tty 4, 49 Mar 17 07:10 tty49
crw------- 1 root root 4, 5 Mar 17 07:11 tty5
crw-rw---- 1 root tty 4, 50 Mar 17 07:10 tty50
crw-rw---- 1 root tty 4, 51 Mar 17 07:10 tty51
crw-rw---- 1 root tty 4, 52 Mar 17 07:10 tty52
crw-rw---- 1 root tty 4, 53 Mar 17 07:10 tty53
crw-rw---- 1 root tty 4, 54 Mar 17 07:10 tty54
crw-rw---- 1 root tty 4, 55 Mar 17 07:10 tty55
crw-rw---- 1 root tty 4, 56 Mar 17 07:10 tty56
crw-rw---- 1 root tty 4, 57 Mar 17 07:10 tty57
crw-rw---- 1 root tty 4, 58 Mar 17 07:10 tty58
crw-rw---- 1 root tty 4, 59 Mar 17 07:10 tty59
crw------- 1 root root 4, 6 Mar 17 07:11 tty6
crw-rw---- 1 root tty 4, 60 Mar 17 07:10 tty60
crw-rw---- 1 root tty 4, 61 Mar 17 07:10 tty61
crw-rw---- 1 root tty 4, 62 Mar 17 07:10 tty62
crw-rw---- 1 root tty 4, 63 Mar 17 07:10 tty63
crw-rw---- 1 root root 4, 7 Mar 17 07:10 tty7
crw-rw---- 1 root tty 4, 8 Mar 17 07:10 tty8
crw-rw---- 1 root tty 4, 9 Mar 17 07:10 tty9
crw-rw---- 1 root uucp 4, 64 Mar 17 07:10 ttyS0
crw-rw---- 1 root uucp 4, 65 Mar 17 07:10 ttyS1
crw-rw---- 1 root uucp 4, 66 Mar 17 07:10 ttyS2
crw-rw---- 1 root uucp 4, 67 Mar 17 07:10 ttyS3
drwxr-xr-x 4 root root 100 Mar 17 21:53 .udev
cr--r--r-- 1 root root 1, 9 Mar 17 07:10 urandom
crw------- 1 root root 442, 0 Mar 17 07:10 usbdev1.1_ep00
crw------- 1 root root 442, 0 Mar 17 07:10 usbdev1.1_ep81
crw------- 1 root root 442, 2048 Mar 17 07:10 usbdev2.1_ep00
crw------- 1 root root 442, 2048 Mar 17 07:10 usbdev2.1_ep81
crw------- 1 root root 442, 2050 Mar 17 07:10 usbdev2.3_ep00
crw------- 1 root root 442, 2050 Mar 17 07:10 usbdev2.3_ep81
crw------- 1 root root 442, 2050 Mar 17 07:10 usbdev2.3_ep82
crw------- 1 root root 442, 4096 Mar 17 07:10 usbdev3.1_ep00
crw------- 1 root root 442, 4096 Mar 17 07:10 usbdev3.1_ep81
crw------- 1 root root 442, 4097 Mar 17 07:10 usbdev3.2_ep00
crw------- 1 root root 442, 4097 Mar 17 07:10 usbdev3.2_ep81
crw------- 1 root root 442, 4097 Mar 17 07:10 usbdev3.2_ep82
crw------- 1 root root 442, 6144 Mar 17 07:10 usbdev4.1_ep00
crw------- 1 root root 442, 6144 Mar 17 07:10 usbdev4.1_ep81
crw------- 1 root root 442, 8192 Mar 17 07:10 usbdev5.1_ep00
crw------- 1 root root 442, 8192 Mar 17 07:10 usbdev5.1_ep81
crw------- 1 root root 442, 10240 Mar 17 07:10 usbdev6.1_ep00
crw------- 1 root root 442, 10240 Mar 17 07:10 usbdev6.1_ep81
crw------- 1 root root 442, 12288 Mar 17 07:10 usbdev7.1_ep00
crw------- 1 root root 442, 12288 Mar 17 07:10 usbdev7.1_ep81
crw------- 1 root root 442, 14336 Mar 17 07:10 usbdev8.1_ep00
crw------- 1 root root 442, 14336 Mar 17 07:10 usbdev8.1_ep81
crw------- 1 vcsa tty 7, 0 Mar 17 07:10 vcs
crw------- 1 vcsa tty 7, 1 Mar 17 07:11 vcs1
crw------- 1 vcsa tty 7, 2 Mar 17 07:11 vcs2
crw------- 1 vcsa tty 7, 3 Mar 17 07:11 vcs3
crw------- 1 vcsa tty 7, 4 Mar 17 07:11 vcs4
crw------- 1 vcsa tty 7, 5 Mar 17 07:11 vcs5
crw------- 1 vcsa tty 7, 6 Mar 17 07:11 vcs6
crw------- 1 vcsa tty 7, 7 Mar 17 07:11 vcs7
crw------- 1 vcsa tty 7, 128 Mar 17 07:10 vcsa
crw------- 1 vcsa tty 7, 129 Mar 17 07:11 vcsa1
crw------- 1 vcsa tty 7, 130 Mar 17 07:11 vcsa2
crw------- 1 vcsa tty 7, 131 Mar 17 07:11 vcsa3
crw------- 1 vcsa tty 7, 132 Mar 17 07:11 vcsa4
crw------- 1 vcsa tty 7, 133 Mar 17 07:11 vcsa5
crw------- 1 vcsa tty 7, 134 Mar 17 07:11 vcsa6
crw------- 1 vcsa tty 7, 135 Mar 17 07:11 vcsa7
drwx------ 2 root root 80 Mar 17 07:10 VolGroup00
lrwxrwxrwx 1 root root 4 Mar 17 07:10 X0R -> null
crw-rw-rw- 1 root root 1, 5 Mar 17 07:10 zero
 
Old 03-18-2008, 03:52 AM   #13
jschiwal
Guru
 
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654Reputation: 654
The /dev/scd0 is the actual device:


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

is the same as

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

if the device is present. The /dev/cdrom & /dev/dvd links are created as a convenience.

if
Code:
sudo mount -t iso9660 /dev/cdrom /mnt/cdrom -o ro
doesn't work, then most likely there is a problem with the drive or the disc.

For a read/writable disc, you might try the UDF filesystem. You may need to modprobe the udf module. However your boot system should be using iso9660. A DVD disc has a bridge format that uses both. You would use iso9660 to mount a DVD video disk.

http://en.wikipedia.org/wiki/Universal_Disk_Format

Also, just before trying to mount the disc in one terminal, run "sudo tail -f /var/log/messages" in a second terminal. The kernel messages about the failure will probably contain more information.

---

I'm not home at my Linux computer now and am working from memory now. Does "lsmod | grep -e iso9660 -e udf" show either filesystem.
If a filesystem needs a kernel module loaded, failure to load the module could give you that generic mount failure message.

Last edited by jschiwal; 03-18-2008 at 04:01 AM.
 
Old 03-18-2008, 07:05 AM   #14
nadsab
Member
 
Registered: Mar 2004
Posts: 30

Original Poster
Rep: Reputation: 15
OK FINALLY, "sudo mount -t iso9660 /dev/cdrom /mnt/cdrom -o" ro worked! Thanks so much jschiwal!

Only problem now is I can't unmount. I tried cdrecord -eject, then tried "umount /dev/scd0 /mnt/cdrom", umount /dev/scd0, umount /dev/cdrom, umount /mnt/cdrom, umount /cdrom, umount /dev/cdrom /mnt/cdrom, nothing worked.
 
Old 03-18-2008, 07:51 AM   #15
nadsab
Member
 
Registered: Mar 2004
Posts: 30

Original Poster
Rep: Reputation: 15
Ah I got it, I had to cd out of /mnt/cdrom and push the eject button, that's the only way i could unmount.

I'm curious am wondering about the entries I made in fstab yesterday, do I need to reload those changes into fstab after editing the fstab file? Or does PC need to be rebooted for changes to take effect? Because last night, "sudo mount -t iso9660 /dev/cdrom /mnt/cdrom -o ro,unhide" did not work and today it does. Maybe that's why I had trouble yesterday because PC was on all day and I shut it down late last night?

Also, what is purpose of sudo and unhide? Did not see them in man mount.

And does it make sense that the only way I can umount is to cd from /mnt/cdrom and then push the eject button? Is that harware specific?

Last edited by nadsab; 03-18-2008 at 08:04 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
help mounting cdrw jgmyshko Fedora 7 11-16-2005 06:52 PM
Mounting firewire cdrw kohokuak Slackware 9 09-23-2004 12:47 AM
xinit fails just after Xserver start up, scsi-ide problem while mounting cdrw askjha Red Hat 0 06-03-2004 11:25 AM
xinit fails just after Xserver start up, scsi-ide problem while mounting cdrw askjha Red Hat 0 06-03-2004 09:54 AM
Problem mounting CDRW. puntme Slackware 6 07-12-2003 06:47 PM


All times are GMT -5. The time now is 03:09 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration