USB and Hard Drive listed in /proc but not /dev
First off I'm working in CentOS 5.4 with the default 2.6.18-164 kernel (which I will be editing but have reverted back to in order to solve this problem.)
Near the end of the init script I have thrown a /bin/sh to get into a busybox bash shell in order to test some scripts. Ive attached the init below. While in this shell I can see my usb drive in /proc/bus/usb/devices and my hard drive in /proc/scsi/device_info however I cannot mount them as they are not in /dev. I have scsi emulation set in the kernel. When I plug in a USB stick it finds the address but still no sign of it in /dev. There are other modules listed in /sys/module such as usbcore that dont show up in lsmod, is that possibly the problem? Is there any obvious reason this could happen? Thanks in advance, Init Script Quote:
Quote:
|
Tried loading ide_disk and ide_core as modules (just a random guess) but no still no luck today.
|
Still working on this problem but feel like ive made a little progress.
I noticed usb-storage isnt in the kernel (even though its selected in the config) so I added it and insmod'ed the .ko. This automatically brings up information about the usb when its plugged in and the SCSI emulation announcement. However still no sign of it in /dev Quote:
Quote:
Quote:
Quote:
If I cat /dev/sdb1 to make sure somethings there I get a stream of data until I unplug the usb, so its pointing in the right place (this is a pretty crude way of checking but its the best I could figure out :D) What am I missing? Thanks, ::SOLVED:: In case someone stumbles on this thread in the future here is what I was missing For CDROM insmod cdrom.ko insmod sr_mod.ko insmod ide-cd.ko mknod hda b 3 0 and then mount it For USB insmod fat.ko insmod vfat.ko mknod sdb b 8 16 mknod sdb1 b 8 17 |
Thanks for coming back and explaining :).
|
Good on you Potatos for writing your solution afterwards.
I have a similar problem with a 32G Kingston Drive, and I'm trying to find something in this thread that will help me. What I find puzzling here is that you do get output identifying sdb1 as your device, though no file seems to exist (before you created it) in udev. My general conclusion here is that everything was working correctly and it was just a case of creating the device nodes and then some associated filesystem modules. |
All times are GMT -5. The time now is 02:21 PM. |