Can't mount cdrom any more.
I've been able to mount CDs fine until recently, and now I can't at all. When I type
Code:
mount /mnt/cdrom Code:
mount: /dev/hdb is not a valid block device I think it might have something to do with a kernel module, since I've been fidling around with them recently...but I'm not sure what to do. Any suggestions? |
Could you please post the output of 'lsmod', 'uname -r', and 'cat /proc/ide/hdb/model'?
Also, if your harddrive is hda, I would recommend putting your CD-ROM on the other IDE channel on your motherboard. IDE can only go as fast as the slowest device on the chain, and that's usually the CD-ROM. By putting the HDD and CD-ROM on seperate IDE channels, each is able to operate at maximum speed. |
lsmod:
Code:
Module Size Used by Tainted: P Code:
2.4.26 Code:
LITE-ON COMBO SOHC-5232K |
*bump* Can you still help me?
|
Take a look at /boot/config and look at the values of CONFIG_BLK_DEV_IDESCSI and CONFIG_BLK_DEV_IDECD. If they're both equal to 'y', then I have no idea how to help you. If either of them is set to 'm' then you need to load the respective module, ide-scsi or ide-cd respectively. If this solves the problem you need to make sure the module gets loaded at boot-up.
The other possible problem is one with the node in /dev. To check this do 'ls -l /dev/hdb'. It should return something like 'brw-rw---- 1 root disk 3, 64 2005-03-24 09:46 /dev/hdb'. If it starts with anything other than b, then you need to replace the node. Also, just for kicks, why don't you post your fstab. |
Well if your fstab is mounting "/dev/hdb", then you're not using ide-scsi, at least not to do normal read operations (I recommend using ide-scsi if you're going to be doing any cd burning, however).
Thus don't worry about the ide-scsi stuff just yet. Since the output of cat /proc/ide/hdb/model is showing a model number, then that means that the kernel "knows" your drive is there. It actually was able to access it on the IDE bus and read the model number. This is good. This means one of two things: 1. the actual device node could be corrupt, as noted by Iztac. 2. your CD-ROM is being flaky and has decided to quit reading CDs. I'd bet on the second one before the first, unless you've been doing something as root recently in /dev... |
All times are GMT -5. The time now is 04:11 PM. |