hdc vanished

[me at mattgillen.net (Matthew Gillen)]

dan moylan wrote:
> matthew gillen wrote:
>> dan moylan wrote:
>>> my laptop internal dvd/cdrom has always shown up in dmesg as:
>>>   hdc: UJDA740 DVD/CDRW, ATAPI CD/DVD-ROM drive
>>>   hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
>>>
>>> in /dev, cdrecorder was linked to hdc and /media/cdrecorder
>>> had the good stuff when the CDROM was mounted.  for some
>>> inexplicable reason, hdc has disappeared from /dev, and as
>>> a consequence, i am unable to mount a disk in that drive
>>> (as one might expect).
>>>
>>> in the old days, i could fumble with MAKEDEV to rescue the
>>> missing device, but MAKEDEV no longer exists.  i browsed
>>> through yast2 and found nothing appropriate.  any
>>> suggestions would be greatly appreciated.
>>>
>>> i'm running suse10 on a panasonic cf-50.
> 
>> mknod /dev/hdc b 22 0
> 
>> Probably suse does some tricks with hal/udev/hotplug to
>> dynamically create the device file when appropriate, and
>> for whatever reason that service/daemon isn't running.
> 
>> The mknod command should get you the device file you
>> need.  It won't last across a reboot if suse is
>> udev-based, but there are other tricks if that's the case.
> 
> thanks, worked like a charm, except that when i looked in
> dev, cdrecorder was linked to fd0!  fixed that and the disk
> mounted just fine.
> 
> you're right, it did not survive a reboot.  i can continue
> to use the mknod command, and suppose i could put it in
> /etc/init.d/boot.local, but i would guess that there must
> be a better way.
> 
> wonder what went wrong in the first place -- used to work.
> 
> anyway, thanks,
> dan

Copy the device file (using 'cp -d' to avoid trying to copy the contents; or
just do the mknod command again) to /etc/udev/devices/ (at least that's where
it is on Fedora).  This will re-create it on reboot.

If you want to figure out what went wrong, you might look to see if the udev
configuration got munged somehow (using rpm's 'verify' mode or the suse
equivalent)

Matt

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.