ubuntu10.04: cd-rom not mounting
 

Many times the cd-rom station cannot be used because it does not show in the file-manager. Whenever I want to start a music cd extraction the program cannot find the cd.
After "#cat /proc/filesystems" I get a listing of all the file systems, but there is no iso9660 file system, which means that the device was not detected.

How can I ensure that I can use it at all times?

I run with a gnome desktop.

You do not mount music CD's. If you want the music files off, you need a ripping program. The ripping program will be able to read the music file, and create an output file on your system. You can choose the type of compression you like, assuming you have the correct files installed. ie .mp3 or .ogg or what ever you like. I use Grip, it is on most of the repos, there are others.

If you want to play the music CD, there are programs that will do that also. For example, Kscd will play music CD's.

I did not ask for advice on ripping audio cds, but how I can ensure that the cdrom is detected during startup. I admit that the title of my question is not very to the point.
Problem is that the cdrom is not available at the moment that I want to use it. I tested this with "cat /proc/filesystems", and there is no iso9660 file system present on my computer.
The latter means that no cdrom was detected, although there is a cd/dvd-rewriter present in my computer. So the hardware is there but the system does not detect it.
It is a bit like russian roulette: one time it is detected, another time it is not detected. Annoying ...

My first point was you do not mount music CD's.

I have a music CD playing right now, here is what I see in filesystems....

I would not expect to see iso9660 present with a music CD.

Is this a IDE drive? Have you looked at the /dev directory for the device and its permissions?

Here is what I see on mine...

It doesn't. /proc/filesystems just lists filesystems supported by the kernel. And, BTW, CDDA doesn't use any FS. It's just a sequence of tracks.
To check cdrom presence you can try if this command works:
If the cdrom is detected and properly working, this command will likely eject/retract the tray (but may not, in which case another way of checking would be needed).
If it doesn't work, check if /dev/sr? file(s) are present.

What program are you using to extract audio?

iso9660 filesystem is only for data CDs. Music CDs do not have a filesystem and as already stated can not be mounted. Ubuntu should detect when a audio CD is inserted and start Sound Juicer (assuming installed as default) automatically. What other sound applications if any are installed on your PC?

https://help.ubuntu.com/community/CDRipping

My cd/dvd-rewriter has a sata2 interface.

It is empty at the time of booting, and after the system has started it is not available.

The command "ls -l /dev/cdrom" results in an error message: "ls: cannot access /dev/cdrom: No such file or directory".

The command "eject -T" results in an error message: "eject: unable to find or open device for: `cdrom'".

Inserting an audio cd does not result in an action by the system, but I have no sound applications installed; in fact the soundchip has been disabled in the bios, because this computer already acts as a Logitech Squeezebox music server.

For ripping an audio cd I use Sound Juicer in case Exact Audio Copy is unable to get past he glitches. Sound Juicer was installed late Saturday and I have ripped an audio cd immediately after.

Now I hope I answered all questions that you launched, and thanks a lot for helping so far!

Sound Juicer needs the haldaemon running to gather information on the optical drives. Is it running?

TS, post output of dmesg command.

To be certain about the hardware, I booted from a cdrom: flawless. So technically the cd/dvd-rewriter seems to be ok.


hald is running:
The output of the dmesg command is too much. Please specify what I should look at.

Check for drive detection messages. Anyway, you'd better paste this output here: pastebin.com or attach the file to your message. You can generate file to attach this way:

Ok here is the latest dmesg...

ATA driver has printed many errors about trying to talk to your drive. This means either the driver supports your drive/SATA controller poorly, or the drive is faulty. Try checking if this drive works on another machine or OS.

Would you be so kind to return the dmesg file with highlighted messages?

You can highlight them yourself this way:
Just look at the output of this command - it will give you all the messages from ATA driver.