Click to See Complete Forum and Search --> : CDRom mount error


blobaugh
01-18-2003, 10:10 PM
I recently did a clean install of RH 7.2 on my machine and now the cdrom drive won't mount. It worked before.
This is the error
mount:/dev/cdrom unknown device

I looked in /dev and it is in there, it also shows up on the KDE desktop but I can't mount it through the terminal or though KDE.

Any suggestions?

adikgede
01-19-2003, 02:12 AM
What do the following report

cat /etc/fstab | grep cdrom

ls -al /dev/cdrom

blobaugh
01-19-2003, 02:44 AM
This is what I got back
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0
0
/dev/cdrom1 /mnt/cdrom1 iso9660 noauto,owner,kudzu,ro 0
0

and

lrwxrwxrwx 1 root root 9 Jan 8 17:52 /dev/cdrom -> /dev/scd0

That help any?

jason490
01-19-2003, 02:51 AM
I am having the same problem with mandrake 9.1 beta2 here is what I get from those commands

[jason@comcast jason]$ cat /etc/fstab | grep cdrom
/dev/scd0 /mnt/cdrom auto user,iocharset=iso8859-1,codepage=850,noauto,ro,umask=0,exec 0 0
[jason@comcast jason]$ ls -al /dev/cdrom
lr-xr-xr-x 1 root root 13 Jan 18 19:21 /dev/cdrom -> cdroms/cdrom0
[jason@comcast jason]$


any ideas on how to get it to work?

adikgede
01-19-2003, 11:43 AM
Originally posted by blobaugh This is what I got back /dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0 /dev/cdrom1 /mnt/cdrom1 iso9660 noauto,owner,kudzu,ro 0 0 and lrwxrwxrwx 1 root root 9 Jan 8 17:52 /dev/cdrom -> /dev/scd0 That help any?

1. Do you have two cdroms?
2. Is one a IDE CDRecordableor is it a SCSI CD
3. If you know where they are (look at dmesg if you don't) you can try mounting them yourself

i.e.
IDE CDROM master on secondary ide channel

mount /dev/hdc1 -t auto /mnt/cdrom
or
mount /dev/hdc1 -t iso9660 /mnt/cdrom

mount /dev/scd0 -t auto /mnt/cdrom


If it is a IDE CDRecordable there needs to be a SCSI emulation boot argument in your boot manager configuration, again that should show up in your boot log.

jason490
01-19-2003, 01:00 PM
Okay blobaugh, here is how you fix it

Log in as root. Click on your home folder on the desktop, go up until you are at the root directory. Click on the ETC folder, then open up FSTAB with kwrite.

You will see a couple of lines one for the floppy and one for the cdrom. REMOVE where it says noauto

Then just save it and reboot. Works like a charm.

blobaugh
01-27-2003, 11:48 PM
Ok, I have two regular CDRom drives on my secondary channel. I do have a burner but it is not hooked up right now. And the thing with fstab about taking out the noauto did not work, furthermore I was watching my boot messages and the CDRom drives are trying to mount or something at startup, but fail. I think maybe if I could resolve the problem with the startup then the drives would be fixed. Where is the boot.log located? I am pretty sure that I don't have the drives set to mount on startup but they try to do something. Anymore advice would be helpful.

adikgede
01-28-2003, 03:23 AM
Where is the boot.log located?

Try /var/log

michaelk
01-28-2003, 12:30 PM
Originally posted by blobaugh
Ok, I have two regular CDRom drives on my secondary channel. I do have a burner but it is not hooked up right now. And the thing with fstab about taking out the noauto did not work, furthermore I was watching my boot messages and the CDRom drives are trying to mount or something at startup, but fail. I think maybe if I could resolve the problem with the startup then the drives would be fixed. Where is the boot.log located? I am pretty sure that I don't have the drives set to mount on startup but they try to do something. Anymore advice would be helpful.

When you deleted the noauto from /etc/fstab the system will try to mount your cdroms and fail because there isn't any media loaded. Stick the noauto back in.

Since your cdwriter is no longer hooked up /mnt/cdrom is not pointed to the correct device.
Assuming ide devices for everything you will need to remove the bootloader line that says hdx=ide-scsi and you might have to recreate the link /mnt/cdrom to point to /mnt/hdc or /mnt/hdd

DMR
01-28-2003, 04:30 PM
michaelk is correct; your /dev/cdrom link is pointing to scd0, which indicates that you are running it under SCSI emulation (probably a result of having your burner installed previously).

Remove the ide-scsi reference in your bootloader's config file, delete the existing /dev/cdrom symlink, and then create a new link which points to the correct /dev/hdx device. For example, if the CD-ROM is the Secondary Master IDE device:

ln -s /dev/hdc /dev/cdrom

blobaugh
01-31-2003, 02:21 AM
Ok I deleted the /dev/cdrom and /dev/cdrom1 files and did ln -s /dev/hdc /dev/cdrom for both, but when I rebooted they were back on scd0 and scd1. I changed it again and got this message
mount: wrong fs type, bad option, bad superblock on /dev/cdrom, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?)

I took the hdx=ide-scsi line out of lilo.conf and put the noauto back into fstab. What am I still doing wrong? Did I miss a step on relinking?

mdwatts
01-31-2003, 10:24 AM
Originally posted by blobaugh

I took the hdx=ide-scsi line out of lilo.conf and put the noauto back into fstab. What am I still doing wrong? Did I miss a step on relinking?

After modifying /etc/lilo.conf, did you run /sbin/lilo (as root) to rewrite the changes to the boot record?

DMR
01-31-2003, 12:57 PM
Originally posted by blobaugh Ok I deleted the /dev/cdrom and /dev/cdrom1 files and did ln -s /dev/hdc /dev/cdrom for bothYou probably just didn't phrase that correctly, but if you really did do what you're saying, you'll have to redo the links:

ln -s /dev/hdc /dev/cdrom

ln -s /dev/hdd /dev/cdrom1

Other than that, removing the ide-scsi line from lilo.conf and executing /sbin/lilo should do it.

As far as the " mount: wrong fs type, bad option...etc. error goes, that might not be such a bad thing- it means that the system seems to find at least one of the CD-ROM drives.

One mistake that a lot of people make is to try to actually mount an audio CD, which is something you can't do and will give you that exact error message. Make sure you're using data (iso9660) CDs while testing the drives.

blobaugh
01-31-2003, 07:37 PM
Well I'm dumb, I forgot to run the boatloader changes. Now the cdrom points to hdc and cdrom1 to hdd, but I still can't access them. It tells me invalid block. I tried several cds, all of which I had burned previously using iso9660 but none of them worked.

Ok so we got the cdrom links correct. Now we just need to get the things to mount!

DMR
01-31-2003, 09:30 PM
Don't sweat it, lots of people forget to re-execute lilo to write the changes. Just an FYI: if you use Grub as your bootloader you don't have to re-run grub after making changes to /boot/grub/grub.grub.conf; it reads the file each time you boot.

:)

As far as mounting the CDs goes, if you try to mount them manually, what is the exact syntax of the mount command that you are using?

adikgede
02-01-2003, 05:25 AM
The January addition of Linux Format (UK) has this little gem


CD Detect & Execute (CDDE)


http://www.wretchedbliss.net/cdde/

blobaugh
02-02-2003, 01:11 AM
Ok the mount I'm using is the disk management under KDE that already has the commands in it. But if I were to do it myself I would use:
mount -t auto /dev/cdrom /mn/cdrom

mdwatts
02-02-2003, 10:33 AM
mount -t iso9660 /dev/cdrom /mnt/cdrom

or if the cdrom is setup properly in /etc/fstab,

mount /mnt/cdrom

Is Redhat 7.2 the version that has the known cdrom module dependency problem?

Try (as root)

depmod -ae

and then see if you can mount the cdrom.

DMR
02-02-2003, 02:58 PM
Originally posted by mdwatts
Is Redhat 7.2 the version that has the known cdrom module dependency problem?Yes, it was 7.2. I'd forgotten about that bug- good catch Mike.

:)

mdwatts
02-02-2003, 03:03 PM
Thanks David... I had forgotten also until the little bell (ding-dong) went off in my head. :)

blobaugh
02-03-2003, 07:57 PM
Thanks Guy!! After all that work and posting it finally worked. That last command you gave me depmod -ae fixed it. I can't thank you enough, And thanks for all you patience in helping me.

Although I still can't figure out why it work in my previous install and not this one. Same board and everything, just a bigger hard drive.