dvd/cd-rom problem

inhaler · 05-07-2008, 03:31 PM

I have a problem with a new system I built. I loaded opensuse 10.3, updated all. The problem is with the dvd/cd rom drives, they are seen when booting and when the system is up. But after awhile they disappear. I updated the motherboard bios. I've googled and I'm stuck. Any clues?

inhaler

TB0ne · 05-08-2008, 08:07 AM

What happens when you put a known good CD or DVD into the drive, while the system is up?

pixellany · 05-08-2008, 08:13 AM

Most modern distros will automatically recognize when a CD aor DVD is inserted. As a minimum, there should be a mount point already setup in /mnt or /media. If it does not automount, try--eg--"mount /media/cdrom".

inhaler · 05-08-2008, 01:41 PM

Quote:

Originally Posted by pixellany

Most modern distros will automatically recognize when a CD aor DVD is inserted. As a minimum, there should be a mount point already setup in /mnt or /media. If it does not automount, try--eg--"mount /media/cdrom".

Tried "mount /media/cdrom" and I get "mount: can't find /media/cdrom in /etc/fstab or /etc/mtab" I know this is a good cd because I can boot from it. I didn't think dvd/cd-rom was in fstab?

TB0ne · 05-08-2008, 02:22 PM

Quote:

Originally Posted by inhaler

Tried "mount /media/cdrom" and I get "mount: can't find /media/cdrom in /etc/fstab or /etc/mtab" I know this is a good cd because I can boot from it. I didn't think dvd/cd-rom was in fstab?

Then try something like "mount /dev/cdrom /media/cdrom". Your device will be something like /dev/cdrom (if it's a CD drive), or /dev/dvd (if it's a DVD drive). It may have a number or something after it, if you have more than one.

The "/media/cdrom" is whatever directory on your system you want to mount it to. Make sure it exists first, or pick another one that does.

inhaler · 05-08-2008, 05:58 PM

Quote:

Originally Posted by TB0ne

Then try something like "mount /dev/cdrom /media/cdrom". Your device will be something like /dev/cdrom (if it's a CD drive), or /dev/dvd (if it's a DVD drive). It may have a number or something after it, if you have more than one.

The "/media/cdrom" is whatever directory on your system you want to mount it to. Make sure it exists first, or pick another one that does.

Opened Konsole su'ed and typed "mount /dev/cdrom /media/cdrom"
the konsile is still hanging also tried mount /dev/cdrom0 /media/cdrom0
because I have 2. Still hangs.

inhaler · 05-09-2008, 12:06 AM

Thanks for your suggestions but I think I'm going to wait for 11.0 and try again.

TB0ne · 05-09-2008, 08:25 AM

Quote:

Originally Posted by inhaler

Opened Konsole su'ed and typed "mount /dev/cdrom /media/cdrom"
the konsile is still hanging also tried mount /dev/cdrom0 /media/cdrom0
because I have 2. Still hangs.

I've got 10.3 running on at least a dozen boxes in my environment, with no problems at all.

First, what is your device name? Is it /dev/dvd, /dev/cdrom, etc.??
Second, is the directory for your mount-point there?

If you've got several CD or DVD drives, you have to specify the one with the disk in it. Also, are these IDE drives? Since they're 'disappearing', have you checked to see if the drives are set up correctly? The master/slave jumpers are in the right places?

Have you tried only plugging in one CD drive, to see what happens then?

roastedmnm · 05-15-2008, 05:10 PM

I seem to be having a similar issue but I might have some more information.

The following is what showed up in /var/log/messages after the drive disappeared (in the middle of ripping a cd I should add).

Code:

May  5 18:31:30 red kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
May  5 18:31:30 red kernel: ata3.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0xbe data 129360 in
May  5 18:31:30 red kernel:          res 40/00:02:00:0c:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
May  5 18:31:35 red kernel: ata3: port is slow to respond, please be patient (Status 0xd0)
May  5 18:31:40 red kernel: ata3: device not ready (errno=-16), forcing hardreset
May  5 18:31:40 red kernel: ata3: hard resetting link
May  5 18:31:40 red kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
May  5 18:31:40 red kernel: ata3.00: failed to IDENTIFY (I/O error, err_mask=0x3)
May  5 18:31:40 red kernel: ata3.00: revalidation failed (errno=-5)
May  5 18:31:40 red kernel: ata3: failed to recover some devices, retrying in 5 secs
May  5 18:31:45 red kernel: ata3: hard resetting link
May  5 18:31:46 red kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
May  5 18:31:46 red kernel: ata3.00: failed to IDENTIFY (I/O error, err_mask=0x3)
May  5 18:31:46 red kernel: ata3.00: revalidation failed (errno=-5)
May  5 18:31:46 red kernel: ata3: limiting SATA link speed to 1.5 Gbps
May  5 18:31:46 red kernel: ata3.00: limiting speed to UDMA/100:PIO3
May  5 18:31:46 red kernel: ata3: failed to recover some devices, retrying in 5 secs
May  5 18:31:51 red kernel: ata3: hard resetting link
May  5 18:31:52 red kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May  5 18:31:52 red kernel: ata3.00: failed to IDENTIFY (I/O error, err_mask=0x3)
May  5 18:31:52 red kernel: ata3.00: revalidation failed (errno=-5)
May  5 18:31:52 red kernel: ata3.00: disabled
May  5 18:31:52 red kernel: ata3: EH pending after completion, repeating EH (cnt=4)
May  5 18:31:53 red kernel: ata3: soft resetting link
May  5 18:31:53 red kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
May  5 18:31:53 red kernel: ata3: EH complete

uname says
Linux red 2.6.22.17-0.1-default #1 SMP 2008/02/10 20:01:04 UTC x86_64 x86_64 x86_64 GNU/Linux

Oh, and the single/only drive is a Samsung Writemaster that is actually using sata which I don't understand seeing the above but I built it myself so I know that's what it is. Meh, what do I know, I've only spent a few weeks trying to fix this.

roastedmnm · 05-16-2008, 03:30 PM

I just forced the same error, the error was exactly the same as my last post.

inhaler · 05-16-2008, 05:44 PM

I get this in /var/log/message

May 16 17:36:41 linux kernel: sr0: CDROM (ioctl) error, command: Test Unit Ready 00 00 00 00 00 00
May 16 17:36:41 linux kernel: sr: Sense Key : Aborted Command [current] [descriptor]
May 16 17:36:41 linux kernel: sr: Add. Sense: No additional sense information

It's very frustrating. The drives show up in the bios correctly.They also work on that other os, m$. They are dvd-ram drives by lite-on.

inhaler · 05-31-2008, 02:10 PM

Quote:

Originally Posted by inhaler

I have a problem with a new system I built. I loaded opensuse 10.3, updated all. The problem is with the dvd/cd rom drives, they are seen when booting and when the system is up. But after awhile they disappear. I updated the motherboard bios. I've googled and I'm stuck. Any clues?

inhaler

I solved this. It appears to be a problem with libata. I have to install with hwprobe=-modules.pata as a boot option to bypass libata and use the older method. Otherwise it thinks the dvd-rw drives are scsi. Both are ide. My hard drive is sata. Don't know if this is the sata bug or not? I tried fedora, kubuntu and ubuntu none of which I liked but all worked with the standard install.
system
Both dvd-rw drives are lite-on ide
asus p5n-d motherboard
2gig ram
seagate sata hard drive
620 watt power suppply
nvidia geforce 8800 gt