CDROM mounting problem => /dev/cdrom is not a valid block device
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
/dev/cdrom is a symbolic link to the actual device. Is it a plain CDROM, CD-RW or what exactly? Without knowing the hardware, I don't know what the actual device is.
When you first boot up, did you see that the kernel reconized your cdrom as an IDE device?
Is it an IDE device (or scsi)? Mine for example shows up as "/dev/hdc", which i have a symbolic link
from to /dev/cdrom. Check your
Code:
dmesg
output to see if the drive was recognized.
My dmesg shows this:
hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.12
Do you have cdrom support compiled into the kernel itself? or as a module?
Thnx for all your help guys, but everything you said was fine.
i have just formated the disk and installed slackware 9.1 again from scratch, because it was a fresh install and my kernel wasn't even configured yet.
Now everything works just fine and i did everything just as the first time.
I don't have a clue what went wrong before.
Hey all, a few weeks ago I formatted my data hard drive. I made it a fat32 type (using windows fdisk). Formerly it had been split between BSD and Win32, however I was unsuccessful in my learning attempt on BSD so I just have Mandrake 10.1 and win98 again.
Now, when I started MDK 10.0 again I was unable to mount hdc2. It says that it is not a valid block device at least twice when I boot into MDK.
I checked in /dev and have discovered that there is a directory named hdc2 but no block device file. Something has apparently damaged the file.
The drive was formerly mounted successfully as a fat32 mount on hdc2 and worked flawlessly.
I attempted the "dmesg" that was in a previous post in this thread and I came up with "hdc: ST3120026A, ATA DISK drive". MDK seems to do something to mount hdc to dev hdc2. As I said, the drive was formerly mounted at hdc2 and worked fine until I started playing with BSD. It even worked after I had BSD installed, but I could not access the BSD portion of the drive through MDK. Once I fdisked the BSD and windows partitions and remade a new win partition is when all of the issues started.
Anyway, is it possible to rebuild a block device file for hdc2?
1. Have you done a scandisk on that drive in Windows?
2. Does the bios recognise the drive as being attached to the machine?
3. Post the output of the command fdisk -l
4. Have you examined the disk with fdisk /dev/hdc? I only have one ext3 partition on mine:
Code:
root@tinwhistle ~ # fdisk /dev/hdc
The number of cylinders for this disk is set to 19457.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/hdc: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdc1 1 19457 156288321 83 Linux
Command (m for help):
If you have a /dev/MAKEDEV script in your distro, you could run that and see if it will make the devices.
thanks this post and the indicated links, I could mount my CDROM in DamnSmallLinux by
doing
mount -t iso9660 /dev/cdaudio /mnt/cdrom
Unfortunately the ls-l dont show any content (this CDROM has files.. this is indicated in the CDROM of my wife which has Ubuntu 10.04).
The content of /mnt/auto/cdrom indicate the files by using emelFM 0.9.2.
But how to copy the files into the directory indicated on the left side?
Can somebody help and indicate the way of copying files from this CDROM into a directory?
Thanks
Pascal
System: AMD K6-2 450, 780MB RAM, 6GB HDD, CDROM, USB (not mounted.. too), FritzWLAN USB (I am trying to connect with ndiswrapper and the files are on this CDROM), Damnsmalllinux with frugal install on HDD
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.