Bugzilla – Bug 117411
No CDROM Drive
Last modified: 2005-11-04 14:35:19 UTC
After a fresh cold-boot, sometimes the mountpoint of the cdrom/dvd drive has gone. After replacing the line in /etc/fstab, with a reboot, the drive works again. I don't know what caused this bug, but I'm still searching.
I think this has nothing to do with the fstab. What is the entry in you fstab for the cdrom? Please add the output of: udevinfo -n /dev/hdc -q symlink (you must maybe replace /dev/hdc with the path of your device)
udevinfo shows: dvd cdrom disk/by-path/pci-0000:11.1-ide-1:0
What means: "sometimes the mountpoint of the cdrom/dvd drive has gone."? Are they removed from /media ? What if you umount the device, remove the related dirs and add new directorys with the same name with mkdir?
Now, it happened again, and the entry in fstab is somehow strange: /dev/dvd /media/ subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf0 0 0 It happened after a reboot after pressing the power key. AFAIK, the computer is entering in runlevel 0, or am I wrong? udevinfo -n /dev/dvd -q symlink shows: no record for '/dev/dvd' in database Al
The fstab entry is complete broken. Looks like a problem of udev or yast (and not subfs/submount/hal). First the target (/media) is complete wrong and also the iocharset=utf0 is wrong. Christian and Hare: please take a look at this, maybe a udev issue. If not reassign to the yast guys.
To check udev, please call these commands and attach the output to this bug: cat /etc/udev/rules.d/55-cdrom.rules udevcontrol log_priority=6 logger aaaaa echo -n 1.0 > /sys/bus/ide/drivers/ide-cdrom/unbind echo -n 1.0 > /sys/bus/ide/drivers/ide-cdrom/bind logger bbbbb sed -n /aaaaa/,/bbbbb/p /var/log/messages The string '1.0' in the echo command lines may differ on your system. Get the id of your cdrom ide device with ls /sys/bus/ide/drivers/ide-cdrom The name of the link is your device id.
I have a similar problem which could be caused by the same bug: Sometimes /dev/hdd and /dev/hdc disappear - I need to run "udevstart" or reboot to fix this.
Marcel, what means sometimes? Is it reproducible in any way? Could you make udev verbose and then, after it happened again, attach the last relevant lines from /var/log/messages? Set /etc/udev/udev.conf:udev_log=info (not debug, debug will fill syslog very fast) to make udev verbose. Would you please test, what i wrote in comment 6? Alex, do you still have this problem?
> Alex, do you still have this problem? > No, I don't
What changed in your setup? Did you fix anything?
Not enough info to see a bug.