cdrom was /dev/hdd now /dev/scd0. Can someone explain?
woody box with 2.4.9 kernel I compiled. I've been using this kernel
since 23 Sep 2001. For over a year, /dev/cdrom has been linked to
/dev/hdd, and "mount /dev/cdrom" worked with no problem. /etc/fstab
entry is:
/dev/cdrom /cdrom iso9660 defaults,ro,user,noauto,exec 0 0
Tonight mount /dev/cdrom returned this error message:
mount: wrong fs type, bad option, bad superblock on /dev/hdd,
or too many mounted file systems
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)
Looking at /var/log/dmesg and various entries in /proc I find that the
last time I rebooted, my cdrom was identified as ide-scsi.
/var/log/dmesg says:
hdc: HP COLORADO 8GB, ATAPI TAPE drive
hdd: CD-ROM 48X/AKU, ATAPI CD/DVD-ROM drive
<snip>
scsi1 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: HP Model: COLORADO 8GB Rev: 2.08
Type: Sequential-Access ANSI SCSI revision: 02
Vendor: E-IDE Model: CD-ROM 48X/AKU Rev: U22
Type: CD-ROM ANSI SCSI revision: 02
The COLORADO is my tape drive and lilo.conf has always had append
"hdc=ide-scsi" to get it to work. There is no such entry in lilo.conf
about hdd.
To mount the cdrom I now need to mount /dev/scd0.
It's been about a month since the last time I did an apt-get install
upgrade. I don't recall mounting cdrom since then until tonight. The
only other thing that I can think of that may be pertinent is a couple
of week ago I was trying to configure wine to play multimedia files
(unsuccessfully), and wine kept giving me warning messages that I didn't
have generic scsi devices sg, sg1,... So I looked up what these are in
kernel documentation and created them with mknod.
Does anyone have an explanation why cdrom is now ide-scsi?
--
Jerome
Reply to: