Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I am running rh 7.1 on a cyrix mediaGX platform, i have had a CDROM connected all the time, as i installed RH from it. I also have used the CDROM without any complications before.
All of a sudden, mount reports: /dev/cdrom is not a block device (try -o loop).
i tried -o loop, then mount reports:
mount: no such device or address.
FAT bread failed
mount: you must specify file system type
or
/dev/loop0 no such device or address
FAT bread failed
mount: you must specify file system type
for mount to work it needs 3 things
1. a device to mount it from (/dev/hd#)
2. the filesystem type of the media (vfat, ext2, iso9660)
3. a dir to mount it to
an example on the cmdline should look something like:
"mount /dev/hdd -t iso9660 /mnt/cdrom"
check if mounts manually, then correct the line in /etc/fstab:
in /etc/fstab theres a line with the roughly same contents, lookin smptin like:
/dev/hdd /mnt/cdrom iso9660 defaults 0 0
just substitute the device ure cdrom is at from the example. look in dmesg or /var/log/messages for the line mentioning the cd.
*the "loop" part btw is used by mount or losetup to ask it to mount a file containing a filesystem, like a boot image for a custom bootdisk or an .iso file. this isnt needed for a regular cdrom.
Thanks, but I havent' added any devices to the machine, and i looked through boot.log and dmesg, but i can only find what i stated in previous posts.
At the time the cd stopped working, i was mounting/umounting it a lot, because i was looking for somehting on a bunch of cds without labels. could this have something to do with it?
I remember getting some funky "missed interrupt"s from hda0 at the time, which locked up the whole box.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.