Topic: Problem after applying Update2

[Graeme Fleming]

Hi all

I have just installed (twice to be sure) a clean build of 5.6u and then applied Update2; I have done the post-upgrade process and rebooted.

Now (both times) I cannot access the cdrom.  If I execute the command:

mount /dev/cdrom /mnt/cdrom

as I usually do so I can use the cdrom drive I get this error displayed:

         /dev/cdrom is not a valid block device

This worked fine prior to the application of Update2.

The cdrom drive is a generic 52x UDMA on its own cable, the mobo is a VIA PLE133 based unit (MSI 6330).

Anyone with any ideas??  Anyone strike the same prob??

I will report as a bug once I have tested on an entirely different h/w rig and verified that the h/w isn't an issue.

[Graeme Fleming]

Well after some investigation on the Redhat side of things I have discovered the following:

**********************
Red Hat Linux 7.2 Install FAQ

CD-ROM fails to mount after install/upgrade to 7.2

We have found an installer related bug in some hardware set-ups. After an installation of 7.2 or upgrade of an existing system, these units report "/dev/cdrom not a valid block device" causing the mount to fail and a possible system crash. Running the command as root "depmod -ae" should solve this issue. Additionally, upgrading to the latest kernel errata will solve this issue.

To view the bug report: Bugzilla 55071 (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=55071)

**********************

The fix as stated above didn't work for me but put me on the right path.

If you look at the Bugzilla item part of the initial description and fix is the following:

To fix:
i) add a line that says "modprobe cdrom > /dev/null 2>&1" to /etc/rc.sysinit just above the line that says "modprobe ide-cd > /dev/null2>&1".
ii) delete the /dev/cdromX symbolic links
iii) delete any cdrom entries in /etc/fstab that refer to "kudzu"
iv) reboot - kudzu will be able to create a valid configuration

Did items (i) & (ii), (iii) & (iv) are not required under SME.

I recreated the symlink (/dev/cdrom is symlinked to /dev/scd0; scsi cd 0) but it still didn't work.

In the end I recreated the symlink but pointed it to /dev/hdc (3rd hd device) and this worked (I wonder if I had done this right at the beginning if this might have been all that was required??).

I now suspect that this mobo and Update2 has an issue with the translation of ide devices to scsi device so consequently the symlink to scd0 didn't work but the symlink to hdc does.

Hope this missive is of use to someone else as this prob just cost me about 2 hours of messing around

[molski]

Hi Graeme,

Also I had problems mounting my (ide) cdrom on SME5.6U4. This is what I did to get things working:

I deleted the symlink /dev/cdrom and after that I made a new symlink for this one. I symlinked /dev/hdc (cause that's where my ide cdrom is connected to /dev/cdrom and after that mounted my cdrom with the command mount /dev/cdrom and things worked great.

Molski

[Dan Williams]

I have the same problems, however in my case this is a fresh install of 5.6 no updates yet.
How do you delete the symlink?
I don't understand how to do that?
Dan