Mount problems

**genlee** · 04-08-2003

Ok do you know which device your cdrom drive is? It is not /dev/hdc. if you cd /proc/ide, in there it will have all your available ide devices.

**BFastenau** · 04-08-2003

Code:

&#91;root@RH9-ltop root&#93;# cd /proc/ide
&#91;root@RH9-ltop ide&#93;# ls
drivers  hda  hdc  ide0  ide1  piix

hda and hdc are symlinks and ide0 and ide1 are directories and piix is an empy document
My cd rom does spin up when I try and mount it.

**genlee** · 04-08-2003

Can you paste output from

Code:

ls -al /dev/hdc

**BFastenau** · 04-08-2003

Code:

&#91;root@RH9-ltop root&#93;# ls -al /dev/hdc
brw-rw----    1 root     disk      22,   0 Jan 30 02&#58;24 /dev/hdc
&#91;root@RH9-ltop root&#93;#

**Dolda2000** · 04-09-2003

After you try and mount /dev/hdc, check /var/log/messages if any errors have been put there from the kernel.

**BFastenau** · 04-09-2003

Code:

Apr  9 10&#58;18&#58;23 RH9-ltop kernel&#58; udf&#58; registering filesystem
Apr  9 10&#58;18&#58;23 RH9-ltop kernel&#58; ide-floppy driver 0.99.newide
Apr  9 10&#58;18&#58;24 RH9-ltop kernel&#58; hdc&#58; ATAPI 24X CD-ROM drive, 128kB Cache, DMA
Apr  9 10&#58;18&#58;24 RH9-ltop kernel&#58; Uniform CD-ROM driver Revision&#58; 3.12
Apr  9 10&#58;18&#58;34 RH9-ltop kernel&#58; hdc&#58; DMA interrupt recovery
Apr  9 10&#58;18&#58;34 RH9-ltop kernel&#58; hdc&#58; lost interrupt
Apr  9 10&#58;18&#58;34 RH9-ltop kernel&#58; hdc&#58; status error&#58; status=0x58 &#123; DriveReady SeekComplete DataRequest &#125;
Apr  9 10&#58;18&#58;34 RH9-ltop kernel&#58; hdc&#58; status error&#58; error=0x00
Apr  9 10&#58;18&#58;34 RH9-ltop kernel&#58; hdc&#58; drive not ready for command
Apr  9 10&#58;18&#58;34 RH9-ltop kernel&#58; hdc&#58; command error&#58; status=0x51 &#123; DriveReady SeekComplete Error &#125;
Apr  9 10&#58;18&#58;34 RH9-ltop kernel&#58; hdc&#58; command error&#58; error=0x51
Apr  9 10&#58;18&#58;34 RH9-ltop kernel&#58; end_request&#58; I/O error, dev 16&#58;00 &#40;hdc&#41;, sector 1323860
Apr  9 10&#58;18&#58;44 RH9-ltop kernel&#58; hdc&#58; DMA interrupt recovery
Apr  9 10&#58;18&#58;44 RH9-ltop kernel&#58; hdc&#58; lost interrupt
Apr  9 10&#58;18&#58;44 RH9-ltop kernel&#58; hdc&#58; status error&#58; status=0x58 &#123; DriveReady SeekComplete DataRequest &#125;
Apr  9 10&#58;18&#58;44 RH9-ltop kernel&#58; hdc&#58; status error&#58; error=0x00
Apr  9 10&#58;18&#58;44 RH9-ltop kernel&#58; hdc&#58; drive not ready for command
Apr  9 10&#58;18&#58;54 RH9-ltop kernel&#58; hdc&#58; DMA interrupt recovery
Apr  9 10&#58;18&#58;54 RH9-ltop kernel&#58; hdc&#58; lost interrupt
Apr  9 10&#58;18&#58;54 RH9-ltop kernel&#58; hdc&#58; status error&#58; status=0x58 &#123; DriveReady SeekComplete DataRequest &#125;
Apr  9 10&#58;18&#58;54 RH9-ltop kernel&#58; hdc&#58; status error&#58; error=0x04Aborted Command 
Apr  9 10&#58;18&#58;54 RH9-ltop kernel&#58; hdc&#58; drive not ready for command
Apr  9 10&#58;19&#58;04 RH9-ltop kernel&#58; hdc&#58; DMA interrupt recovery
Apr  9 10&#58;19&#58;04 RH9-ltop kernel&#58; hdc&#58; lost interrupt
Apr  9 10&#58;19&#58;04 RH9-ltop kernel&#58; hdc&#58; status error&#58; status=0x58 &#123; DriveReady SeekComplete DataRequest &#125;
Apr  9 10&#58;19&#58;04 RH9-ltop kernel&#58; hdc&#58; status error&#58; error=0x04Aborted Command 
Apr  9 10&#58;19&#58;04 RH9-ltop kernel&#58; hdc&#58; drive not ready for command
Apr  9 10&#58;19&#58;14 RH9-ltop kernel&#58; hdc&#58; DMA interrupt recovery
Apr  9 10&#58;19&#58;14 RH9-ltop kernel&#58; hdc&#58; lost interrupt
Apr  9 10&#58;19&#58;14 RH9-ltop kernel&#58; hdc&#58; status error&#58; status=0x58 &#123; DriveReady SeekComplete DataRequest &#125;
Apr  9 10&#58;19&#58;14 RH9-ltop kernel&#58; hdc&#58; status error&#58; error=0x04Aborted Command 
Apr  9 10&#58;19&#58;14 RH9-ltop kernel&#58; hdc&#58; drive not ready for command
Apr  9 10&#58;19&#58;24 RH9-ltop kernel&#58; hdc&#58; DMA interrupt recovery
Apr  9 10&#58;19&#58;24 RH9-ltop kernel&#58; hdc&#58; lost interrupt
Apr  9 10&#58;19&#58;24 RH9-ltop kernel&#58; hdc&#58; status error&#58; status=0x58 &#123; DriveReady SeekComplete DataRequest &#125;
Apr  9 10&#58;19&#58;24 RH9-ltop kernel&#58; hdc&#58; status error&#58; error=0x04Aborted Command 
Apr  9 10&#58;19&#58;24 RH9-ltop kernel&#58; hdc&#58; drive not ready for command
Apr  9 10&#58;19&#58;34 RH9-ltop kernel&#58; hdc&#58; DMA interrupt recovery
Apr  9 10&#58;19&#58;34 RH9-ltop kernel&#58; hdc&#58; lost interrupt
Apr  9 10&#58;19&#58;34 RH9-ltop kernel&#58; hdc&#58; status error&#58; status=0x58 &#123; DriveReady SeekComplete DataRequest &#125;
Apr  9 10&#58;19&#58;34 RH9-ltop kernel&#58; hdc&#58; status error&#58; error=0x04Aborted Command 
Apr  9 10&#58;19&#58;34 RH9-ltop kernel&#58; hdc&#58; drive not ready for command
Apr  9 10&#58;19&#58;44 RH9-ltop kernel&#58; hdc&#58; DMA interrupt recovery
Apr  9 10&#58;19&#58;44 RH9-ltop kernel&#58; hdc&#58; lost interrupt
Apr  9 10&#58;19&#58;44 RH9-ltop kernel&#58; hdc&#58; status error&#58; status=0x58 &#123; DriveReady SeekComplete DataRequest &#125;
Apr  9 10&#58;19&#58;44 RH9-ltop kernel&#58; hdc&#58; status error&#58; error=0x04Aborted Command 
Apr  9 10&#58;19&#58;44 RH9-ltop kernel&#58; hdc&#58; drive not ready for command
Apr  9 10&#58;19&#58;54 RH9-ltop kernel&#58; hdc&#58; DMA interrupt recovery
Apr  9 10&#58;19&#58;54 RH9-ltop kernel&#58; hdc&#58; lost interrupt
Apr  9 10&#58;19&#58;54 RH9-ltop kernel&#58; hdc&#58; status error&#58; status=0x58 &#123; DriveReady SeekComplete DataRequest &#125;
Apr  9 10&#58;19&#58;54 RH9-ltop kernel&#58; hdc&#58; status error&#58; error=0x04Aborted Command 
Apr  9 10&#58;19&#58;54 RH9-ltop kernel&#58; hdc&#58; drive not ready for command
Apr  9 10&#58;20&#58;04 RH9-ltop kernel&#58; hdc&#58; DMA interrupt recovery
Apr  9 10&#58;20&#58;04 RH9-ltop kernel&#58; hdc&#58; lost interrupt
Apr  9 10&#58;20&#58;04 RH9-ltop kernel&#58; hdc&#58; status error&#58; status=0x58 &#123; DriveReady SeekComplete DataRequest &#125;
Apr  9 10&#58;20&#58;04 RH9-ltop kernel&#58; hdc&#58; status error&#58; error=0x04Aborted Command 
Apr  9 10&#58;20&#58;04 RH9-ltop kernel&#58; hdc&#58; drive not ready for command
Apr  9 10&#58;20&#58;14 RH9-ltop kernel&#58; hdc&#58; DMA interrupt recovery
Apr  9 10&#58;20&#58;14 RH9-ltop kernel&#58; hdc&#58; lost interrupt
Apr  9 10&#58;20&#58;14 RH9-ltop kernel&#58; hdc&#58; status error&#58; status=0x58 &#123; DriveReady SeekComplete DataRequest &#125;
Apr  9 10&#58;20&#58;14 RH9-ltop kernel&#58; hdc&#58; status error&#58; error=0x04Aborted Command 
Apr  9 10&#58;20&#58;14 RH9-ltop kernel&#58; hdc&#58; drive not ready for command
Apr  9 10&#58;20&#58;24 RH9-ltop kernel&#58; hdc&#58; DMA interrupt recovery
Apr  9 10&#58;20&#58;24 RH9-ltop kernel&#58; hdc&#58; lost interrupt
Apr  9 10&#58;20&#58;24 RH9-ltop kernel&#58; hdc&#58; status error&#58; status=0x58 &#123; DriveReady SeekComplete DataRequest &#125;
Apr  9 10&#58;20&#58;24 RH9-ltop kernel&#58; hdc&#58; status error&#58; error=0x04Aborted Command 
Apr  9 10&#58;20&#58;24 RH9-ltop kernel&#58; hdc&#58; drive not ready for command
Apr  9 10&#58;35&#58;48 RH9-ltop syslogd 1.4.1&#58; restart.

at the point it shows restart, that was due to me rebooting becuase the system hung.

**genlee** · 04-09-2003

I looked up some of those errors and it seems to effect random cd drives on 2.4.20. Some users have installed prerelease of 2.4.21 and it fixed. You could also try using scsi emulation on the cd drive. In your grub or lilo config, you can add the option hdc=scsi to enable scsi emulation on the cd drive.

**genlee** · 04-09-2003

http://groups.google.com/groups?hl=e...8%26oe%3DUTF-8

That link might be of some use to you.

**BFastenau** · 04-10-2003

Thanks for all the help so far.
I tried SCSI emultation and that didn't make a difference. As for updating the kernel, this will be a new experience for me. I am currently using the 2.4.20-9, just used the red hat update utility yesterday to install it. I was hoping that this would fix the cd issue but it did not.

Thread Tools

Display

Posting Permissions