LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   eject -v says "unable to open /dev/hdc" (https://www.linuxquestions.org/questions/slackware-14/eject-v-says-unable-to-open-dev-hdc-380036/)

Simon Bridge 11-04-2005 06:33 PM

eject -v says "unable to open /dev/hdc"
 
This is a call to Slackware fans to have a look at this thread.

In a nutshell:

Kaamoss starts with a complaint of being unable to eject his CDR/W - connected as secondary master. Transpires that data cd's won't mount either. Has since installed a new DVD drive to secondary slave and is having the same problems. Output of eject -v on each device (with a blank disk in the drive, or an empty drawer) is as follows:
Code:

bash-3.00$ eject -v /dev/hdc
eject: device name is `/dev/hdc'
eject: expanded name is `/dev/hdc'
eject: `/dev/hdc' is not mounted
eject: `/dev/hdc' is not a mount point
eject: `/dev/hdc' is a multipartition device
eject: unable to open `/dev/hdc'
bash-3.00$ eject -v /dev/hdd
eject: device name is `/dev/hdd'
eject: expanded name is `/dev/hdd'
eject: `/dev/hdd' is not mounted
eject: `/dev/hdd' is not a mount point
eject: `/dev/hdd' is a multipartition device
eject: unable to open `/dev/hdd'

My initial feeling was that the jumper settings were out - but Kaamoss insists that BIOS shows both drives correctly. B'Sides, the slack 10 install was from this (CD) drive. So perhaps the ide-cd drivers are not installed?

Have a look and see what you think.

rkelsen 11-05-2005 01:48 AM

Re: eject -v says "unable to open /dev/hdc"
 
Quote:

Originally posted by Simon Bridge
So perhaps the ide-cd drivers are not installed?
They're built into the default kernels.

There has to be something in his dmesg output which offers a clue.

I notice that he has quite a few /var/log/message files for a supposedly new installation. Maybe the clue is in one of them.

Simon Bridge 11-05-2005 01:55 AM

This is what I thought - I've instructed him to powerdown, reboot, then immediately do dmesg. Also to look through the other syslog files.

It may be there are lots of error messages from something broken... however:

Perhaps I should have asked for replies to go in the other thread - that way we keep everything in one place and the guy with the trouble can see all the help he's getting. I mean, I could just relay the winning combination and take all the credit if you want?

:)


All times are GMT -5. The time now is 08:11 PM.