LinuxQuestions.org - CD-Rom drive won't open any more when logged into FC6

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - CD-Rom drive won't open any more when logged into FC6 (https://www.linuxquestions.org/questions/linux-hardware-18/cd-rom-drive-wont-open-any-more-when-logged-into-fc6-502684/)

CD-Rom drive won't open any more when logged into FC6

Everything was working well, then I needed to install something so I tried opening my CD-ROM drive (DVD-RW if it matters) and it won't open. It opens and works before linux loads up, but I don't even get a power light once I'm in Fedora.

Last time I remember it working was when I had a different kernel version. Would this matter? Also, in KInfoCenter it does say I have a CD-ROM, labled hdf. If I navigate to /dev/ and there is indeed an hdf. mount /dev/hdf /mnt/somdirectory just hangs. "mount /mnt/cdrom" gives me:

Code:

mount: can't find /mnt/cdrom in /etc/fstab or /etc/mtab

Any ideas?

Check that /media/cdrom is there... the command should be

# mount /dev/hdf -t iso9668 /media/cdrom

Your error is understandable, /mnt/cdrom is not in /etc/fstab nor in /etc/mtab. It isn't expected to be since it is a directory rather than a block special file.

You probably should check /etc/fstab to see that /dev/hdf is actually present.
Also check dmesg for anything relating to hdf: dmesg | grep hdf (for eg).

I tried these commands and it hung on the last one. I made the directory /mnt/cdrom.

Code:

[tnunamak@localhost ~]$ sudo mount /dev/hdf -t iso9668 /media/cdrom

Password:

mount: mount point /media/cdrom does not exist

[tnunamak@localhost ~]$ sudo mount /dev/hdf -t iso9668 /mnt/cdrom

mount: unknown filesystem type 'iso9668'

mount: maybe you meant 'iso9660'?

[tnunamak@localhost ~]$ sudo mount /dev/hdf -t iso9660 /mnt/cdrom

Drat - typo! Yes, I meant iso9660 :(

Anyhow - when the mount hangs, try ps from a different terminal and see what it says about the mount process. Could be in uninterruptable sleep ... sometimes a sign of a device driver working with bad hardware. (Have you checked the drive out on another system since you started having trouble?)

You should also check the syslog for messages about it - "dmesg | grep hdf" Check fstab for the line about hdf too.

The drive works perfectly in windows, and it's less than two years old with very light use... should be ok.

The error message I get when I run that line is using dmesg is:

Code:

    ide2: BM-DMA at 0x9000-0x9007, BIOS settings: hde:pio, hdf:pio

hdf: SONY DVD RW DW-U18A, ATAPI CD/DVD-ROM drive

hdf: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)

hdf: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recov                                                                            er by ending request.

hdf: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recov                                                                            er by ending request.

hdf: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recov                                                                            er by ending request.

hdf: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recov                                                                            er by ending request.

hdf: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recov                                                                            er by ending request.

hdf: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recov                                                                            er by ending request.

hdf: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recov                                                                            er by ending request.

hdf: status error: status=0x58 { DriveReady SeekComplete DataRequest }

hdf: drive not ready for command

hdf: irq timeout: status=0xd0 { Busy }

hdf: DMA disabled

hdf: ATAPI reset complete

hdf: irq timeout: status=0xc0 { Busy }

hdf: ATAPI reset timed-out, status=0x80

hdf: status timeout: status=0x80 { Busy }

hdf: drive not ready for command

Quote:

The drive appears confused (ireason = 0x01).

ASUS motherboard?

Sometimes this is an irq sharing issue - sometimes, hardware failing.
There's a big discussion on LQ:
http://www.linuxquestions.org/questi...d.php?t=499811

Gigabyte actually, GA-965P. It's less than 3 months old, and I would be suprised to find that it's a hardware issue.

I have the same motherboard - Gigabyte GA-965P-S3. Also a Core2Duo E6600. kernel 2.6.18-4-amd64 SMP. A Sony DVD-RW.
When the drive is emply, the dmesg | tail reveals stuff like

Code:

ide: failed opcode was: unknown

hda: status error: status=0x50 { DriveReady SeekComplete }

ide: failed opcode was: unknown

hda: ATAPI reset complete

hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.

hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.

hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.

hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.

hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.

hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.

I can't tell how often these errors occur. It works fine: ejects and plays stuff properly. For some reason though it likes to switch out of DMA mode once in a while.
Right now, hdparm /dev/hda returns:

Code:

/dev/hda:

 IO_support    =  0 (default 16-bit)

 unmaskirq    =  0 (off)

 using_dma    =  0 (off)

 keepsettings  =  0 (off)

 readonly      =  0 (off)

 readahead    = 256 (on)

 HDIO_GETGEO failed: Inappropriate ioctl for device

Disregarding other issues, I would say this has not affected my system.

Well... there is always "ide=nodma" on the kernel line in menu.lst ... also trying noacpi and noapic. This is looking at these other errors. However, I should stress that this sort of thing can also result from dud hardware. Even a new mobo can be a dud.