RE: Ver. 7.2 block device definition errors

Not to rehash previous discussions, but I have skipped looking at this until
now...
Perhaps I can help a little here - forgive any repeated questions.
"??????" sequences are shell commands to be executed, type in the ??????
text at the shell prompt.

As ROOT (superuser):

1. Do a  "grep cdrom /etc/fstab"  which will return what the installer
decided the cdrom drive was
to be mounted as. It should be:

/dev/cdrom              /mnt/cdrom              iso9660
noauto,owner,kudzu,ro 0 0

2. do a "ls -ld /mnt/cdrom"  to make sure it is a valid directory. It should
return:

drwxrwxr-x    2 root     root         4096 Oct  9  1998 /mnt/cdrom

The date/time may be different. The filesize (4096) may also be different.

3. do a "ls -l /dev/cdrom". It should return:

lrwxrwxrwx    1 root     root            8 Mar 11  2002 /dev/cdrom ->
/dev/hdc

The date/time may be different. The /dev/hdc  may be a different device.
This is
the symbolic link (alias) for the real device that is the cdrom drive, in
this case
the real device name is /dev/hdc.

If all the above makes sense, then "cd /var/log" and edit the messages file
you find there.

Your problem is likely the device does not exist according to the OS, no
driver is loaded,
the cdrom is bad (hardwrae issue). The information that may identify the
cause will hopefully
appear in the messages file from the last system boot.

You need to post the linux boot sequence messages, especially(/hopefully
only just) the section that
shows the detection and configuration of the CDROM drive and IDE bus devices
like the hard drives.
Since you also appear to be having problems with the floppy drive, include
anything in the messages
file on that. Cut out the relavent section and paste it
into a email screen for this newsgroup. If you cant edit the file, then do
the following to save everyone
from getting a huge email from you.

1) Kick everyone but you off this system. You might want to stop syslog
as well - "service syslog stop"

2) "cd /var/log"

3) "mv messages messages.save", this saves the current file
against the next step

4) Reboot the system. This will create a messages file containing only the
boot time output of the OS and startup scripts.

5) Log back in.

6) "cd /var/log"

7) Email the messages file
	do a "ls -l messages" and see how large it is. If it is relatively small,
	email it to the enigma-list.
	if it is large, email it directly to me "[email protected]"
	and I will look at it and if necessary
	chop it down and post the relavent section for you for group input.


I am presuming that you have already checked the IO cables to the drives in
question and that
they are properly installed and that the BIOS on the system is detecting all
these drives.