FC3 and DVD/CDROM can't mount

Jimbo99 · 03-04-2005, 05:07 PM

After installing FC3 I've encountered an inordinant number of issues with the install. After a month of working on them I have finally reduced them down to two major issues for me.

On this machine I used to have Suse 9.1 Pro but because Novell does not upgrade their kernel module drivers for video I chose to switch to another product--FC3, due mostly to the fact that I'd used FC1 for a while and managed to have it running for a while, albeit not error free. These used to work under Suse 9.1 pro without a hitch.

I switched to Suse 9.1 to give those guys a chance. I'd looked at various other distros and found I did not like them.

The problems I am having now is that after the install I can no longer mount a disc of any kind: dvd, cd blank, cd audio, or data cd. The second major problem is that I can't play enemy-territory or quake3 full screen. No changes that I make to the configuration files for either will allow them to go full screen.

CD/DVD issue:

I get the following message box: /dev/hda: Input/output error
mount: /dev/hda: can't read superblock
Please check that the disk is entered correctly

What seems to be wrong here is that it is pointing to hda (which is typically a HDD). Second, no matter what I try, if I modify the line (in /etc/fstab) upon reboot the system initialization will add the line back so I have little ability to modify it or remove it. Third, it seems odd that it says disk as the device is a CD/DVD writer/reader and it should be referring to it as a "disc" instead of "disk".

When the boot process adds the line back to the fstab file it also seems to make a new subdirectory under /media called cdrecorder# (where # stands for a number) (i.e., /media/cdrecorder3).

ET/Quake3 issues:

I've zapped all profiles and reinstalled ET and ensured that under the options dialog it is set to full screen. I've also ensured that the resolution matched that of the desktop.

In Quake3 I have done the same thing.

Nothing seems to help.

Help on either/both of these would be greatly appreiciated.

-Jim

michaelk · 03-04-2005, 05:23 PM

You can not mount a blank CD or an audio CD because they do not contain a valid filesystem. What is the output of the following command:

dmesg | grep CD (Use a capital CD)

Jimbo99 · 03-04-2005, 08:53 PM

Quote:

Originally posted by michaelk
You can not mount a blank CD or an audio CD because they do not contain a valid filesystem. What is the output of the following command:

dmesg | grep CD (Use a capital CD)

I know you are trying to help but the idea of mounting a blank cdrom is not the main thrust of my post. Thanks again for trying your best.

Jim

Jimbo99 · 03-04-2005, 08:54 PM

- Added public key 6ECDA687281A73E5
hda: SAMSUNG CDRW/DVD SM-352B, ATAPI CD/DVD-ROM drive
hda: ATAPI 32X DVD-ROM CD-R/RW drive, 8192kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20

michaelk · 03-04-2005, 09:09 PM

Ok this proves that your CDROM drive device is /dev/hda.
Post your /fstab line entry for the CD drive.

Can you manually mount a data CD.
mount /dev/hda

Any errors? The CD should be mounted to the current mount point as indicated in the fstab file.

If the fstab entry has kudzu as an option then remove it. This should keep the OS from changing it at boot but I do not know about FC3.

Jimbo99 · 03-04-2005, 09:20 PM

The command:

mount /dev/hda

results in:

/dev/hda: Input/output error
mount: block device /dev/hda is write-protected, mounting read-only
/dev/hda: Input/output error
mount: /dev/hda: can't read superblock

fstab reference line:

/dev/hda /media/cdrecorder4 auto pamconsole,exec,noauto,fscontext=system_u

bject_r:removable_t,managed 0 0

There's no referene to kudzu. The above line is the line it keeps adding.

Below is the contents of the fstab file:

# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
#/dev/hda /media/cdrecorder auto pamconsole,fscontext=system_u

bject_r:removable_t,ro,exec,noauto,managed 0 0
/dev/hda /media/cdrecorder4 auto pamconsole,exec,noauto,fscontext=system_u

bject_r:removable_t,managed 0 0
/dev/fd0 /media/floppy auto pamconsole,exec,noauto,fscontext=system_u

bject_r:removable_t,managed 0 0

michaelk · 03-04-2005, 09:24 PM

Is this a data CD?
Post your /etc/fstab file.

Jimbo99 · 03-04-2005, 09:25 PM

Every cd, no matter what, generates this or a similar error.

The contents of the fstab file are listed in my last post.

PTrenholme · 03-04-2005, 10:32 PM

Strange -- I've had no problems with CD/DVD mounting. I've got two DVD drives, one RO and the other RW. (Actually, I do have a problem, but it's hardware, and not relevant here: the RO drive is quite sporadic, but on both FC3 and XP.)

Oh, when michaelk suggests a "data disk," I think he means a "disk containing a Linux file system." A good example would be your distribution CD or DVD. What happens when you try one of them?

The other point is worth repeating: mount is going to look for a Linux/Unix file system. If you want to use a music CD or a video DVD, you need an application like "mplayer" to do so. I mostly use the KDE desktop, so I've installed "kplayer," which is a nice front-end to mplayer.

For what it's worth, here's what my fstab looks like: (Note that the first device after the VolGroup device is hda, so "hda" is not, necessarily, the "first hard drive.")

Code:

# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/VolGroup00/LogVol00 /                      ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
/dev/VolGroup00/LogVol01 swap                   swap    defaults        0 0

# Added by hand . . .
/dev/hda1               /mnt/WinXP/c            ntfs    ro,umask=0222,uid=peter,gid=peter       0 0
/dev/hdb1               /mnt/WinXP/d            ntfs    ro,umask=0222,uid=peter,gid=peter       0 0
/dev/hdc1               /mnt/WinXP/g            ntfs    ro,umask=0222,uid=peter,gid=peter       0 0
/dev/hdg1               /mnt/WinXP/t            vfat    uid=peter,gid=peter    0 0
/dev/hdh1               /mnt/WinXP/z            vfat    uid=peter,gid=peter    0 0
/dev/hdd1               /mnt/Win98/c            vfat    uid=peter,gid=peter    0 0
/dev/hdd2               /mnt/Win98/d            vfat    uid=peter,gid=peter    0 0

# Non-HDD devices
/dev/hdf                /media/cdrecorder       auto  pamconsole,exec,noauto,fscontext=system_u:object_r:removable_t,managed 0 0
/dev/hde                /media/cdrom            auto    pamconsole,exec,noauto,fscontext=system_u:object_r:removable_t,managed 0 0
/dev/fd0                /media/floppy           auto    pamconsole,exec,noauto,fscontext=system_u:object_r:removable_t,managed 0 0

Jimbo99 · 03-04-2005, 10:56 PM

I've used solely iso9660 complaint CDs. I'm sure most posting here, including me, are aware of a data cd vs. a music cd vs. a dvd movie vs. a dvd data disc.

As I said--same hadware under suse 9.1 pro --I could access any CD/DVD platter.

PTrenholme · 03-05-2005, 05:48 AM

It was late! I wasn't thinking! SORRY!

Disregard almost everything I wrote!

I don't know what your problem is,

but FC3 does understand ISO file systems. And, of course, the "auto" file type is telling the system to probe for the type you've inserted.

Perhaps, like me, you've got a sick drive. Sometimes these things happen in the middle of other changes.

Do you have a bootable CD? Can you boot from it? If you can't, you've probably got a hardware problem. (I've had drives fail because of "kinked" ribbon cables. In fact, so often that I replaced all my ribbon cables with round ones.)

Anyhow, again, I'm sorry for my misleading comments. (And in bold, too!)

Pete M · 03-05-2005, 06:44 AM

Jimbo99

Check the permissions of dev/hda, on my Fedora install only user 'root' and group 'disc' had read/write permission

To solve this I added myself to group 'disc' from then on everything worked fine

Another point is that xine looks for dev/dvd so I added a symlink from dev/dvd to, in my case dev/hdd this solved another problem when trying to play DVD's

Hope this helps

Pete

Jimbo99 · 03-05-2005, 10:28 AM

The CD drive and cds themselves are good. I've tried multiple CD of various formats and I get the same or similar error messages.

The DVD/CDRW combo drive is fully functional. I've tested it with boot CD, by switching back to the old HDDs that had the Suse 9.1 installed on them, etc.

Why did the grep utility display two lines instead of one?

hda: SAMSUNG CDRW/DVD SM-352B, ATAPI CD/DVD-ROM drive
hda: ATAPI 32X DVD-ROM CD-R/RW drive, 8192kB Cache, UDMA(33)

I've also tested this as root. Same issues.

-Jim

Jimbo99 · 03-05-2005, 10:33 AM

I removed the nVidia drivers and reinstalled them (the same 6629 version) and now I can play enemy-territory in full screen. What troubles me now tho is that when I enter a map for the game the mouse cursor seems to spin around and then finally the mouse cursor disappears.

I've attempted to host a game and load a map. In these situations this bit with the mouse doesn't appear to happen. I've then zapped my install and reloaded ET. Same issue (I can now get full screen but the mouse wiggs out when I go online and load a map). The mouse is a trusted usb logitech mouse that I've used for the past 2 years.