I'm getting a fail when I'm booting up recently
updating /etc/fstab cannot stat /dev/cdrom: no such file or directory failed

looking in the /dev/ directory i cannot find a cdrom or cdrom1 devices!!!

also the directories /mnt/cdrom and /mnt/cdrom1 folders had been deleted. i don't understand i cant figure this out i haven't changed anything.

i cant think of any thing that i have changed lately other than adding a line into /etc/fstab for a digital camera.
/dev/sda1 /mnt/camera vfat noauto,user,ro 0 0

what i don't understand is that during boot up my cdrom1 device isn't failing. i would think that it should fail also.

does anyone have any ideas about what might have happened and what to do to get my cdroms to work again.

thanks,
AD


LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hde7 swap swap defaults 0 0
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0
/dev/hde2 /mnt/hde2 vfat auto 0 0
/dev/hde3 /mnt/hde3 vfat auto 0 0
/dev/hde4 /mnt/hde4 vfat auto 0 0
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0
/dev/cdrom1 /mnt/cdrom1 iso9660 noauto,owner,kudzu,ro 0 0
/dev/sda1 /mnt/camera vfat noauto,user,ro 0 0



prompt
timeout=50
default=linux
boot=/dev/hde
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear
vga=792

image=/boot/vmlinuz-2.4.18-14
label=linux.bak
initrd=/boot/initrd-2.4.18-14.img
read-only
append="hdc=ide-scsi root=LABEL=/"

image=/boot/vmlinuz-2.4.20-13.8
label=linux.bak1
append="hda=ide-scsi hdc=ide-scsi root=LABEL=/"
read-only
initrd=/boot/initrd-2.4.20-13.8.img

image=/boot/vmlinuz-2.4.20-18.8
label=linux
append="hda=ide-scsi hdc=ide-scsi root=LABEL=/"
read-only
initrd=/boot/initrd-2.4.20-18.8.img

Maybe caused by kudzu. Did you boot using anyone of the other configurations besides the linux label?

Do you have a /dev/hda or /dev/hdc?

If so just you should be able to mount them to /mnt/cdrom and /dev/cdrom1. /dev/cdrom was only a link to /dev/hda and so you can create it again.

ok im not drunkkkkkk or stoneddddd right now i sweat it. i changed my fstab from
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0
/dev/cdrom1 /mnt/cdrom1 iso9660 noauto,owner,kudzu,ro 0 0

to

/dev/hda /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0
/dev/hdc /mnt/cdrom1 iso9660 noauto,owner,kudzu,ro 0 0

just like u had suggested.....and it worked!!!!! thanks.

when i looked back at my fstab file today while i was writing a reply to this post things had changed on there own i swear it. it was back again to /dev/cdrom and cdrom1. and when i went to the /dev/ folder and checked to see if there was a cdrom and cdrom1 in the folder there was and its a block device.


man how confusing does this get or am i just stupid.

i know that ln -sf /dev/scd0 /dev/cdrom will create my link but how do i tell what links there are. for instance if i look at someone elses machine i have never seen before how can i tell that there is a symlink between hda and cdrom. the only way is to look at the lilo.config file and then do a

[joe@schrock joe]$ ls -l /dev/cdrom
lrwxrwxrwx 1 root root 9 Jun 30 17:43 /dev/cdrom -> /dev/scd0
[joe@schrock joe]$ ls -l /dev/cdrom1
lrwxrwxrwx 1 root root 9 Jun 30 17:43 /dev/cdrom1 -> /dev/scd1
[joe@schrock joe]$ ls -l /dev/scd0
brw------- 1 joe disk 11, 0 Aug 30 2002 /dev/scd0
[joe@schrock joe]$ ls -l /dev/scd1
brw------- 1 joe disk 11, 1 Aug 30 2002 /dev/scd1
[joe@schrock joe]$

thanks for your help,
AD