Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm a newbie, trying to get an embedded USB controller/Linux processor to mount a TEAC CD-ROM drive. My system recognizes the device when I attach it, but I can't seem to be able to mount the drive. I have tried
mount /dev/cdrom /mnt/cdrom
mount /dev/sda /mnt/cdrom
mount /dev/sda1 /mnt/cdrom
mount /dev/sdb /mnt/cdrom
mount /dev/sdb1 /mnt/cdrom
and each time I get the following message:
mount: /dev/sdb is not a valid block device
I have viewed a few other posts similiar to this and have seen fstab settings, ect, however I'm not sure exactly what these are, what they currently are, or what they should be.
Any help would be GREATLY appreciated. Trying to mount this drive so that I might copy a few installation files over to the embedded controller!
well it'll need to be a hotplug USB device and must be detected correctly. try "dmesg | grep usb" to see if it has actually been found at all. also try using a tool like usbview to see what's known to the system
Thanks....I did try that command (although I am unsure of the usbview tool). How will I be able to tell if it has been correctly found? The grep command resulted in:
[root@linux root]$ dmesg | grep usb
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb.c: registered new driver audio
usb.c: registered new driver pegasus
usb.c: registered new driver usb-storage
usb.c: new USB bus registered, assigned bus number 1
usb.c: new USB bus registered, assigned bus number 2
usb.c: new USB bus registered, assigned bus number 3
usb.c: new USB bus registered, assigned bus number 4
usb.c: registered new driver otg_de1
usb.c: registered new driver de3_kbd
And my initial plug in of the device results in:
hub.c: USB new device connect on bus1/1, assigned device numb
er 2
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: TEAC Model: CD-210PU Rev: 10A3
Type: CD-ROM ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
Does this mean that my system is recognizing the drive as a hub? How would I go about mounting this to gain access to the files?
Does this mean that my system is recognizing the drive as a hub? How would I go about mounting this to gain access to the files?
Thanks,
Colleen
No, that doesn't mean it's being picked up asa hub.
It looks good, so far. What's the output of
lsmod,
and have you looked as /proc/scsi/scsi to see
which ID it's actually assigned?
I think that the problem is potentially here? The output of lsmod is :
[root@linux root]$ lsmod
Module Size Used by
lsmod: QM_MODULES: Function not implemented
And when I changed to the /proc directory, I wasn't able to see which ID it was actually assigned (unless it is the usb-storage-0...which is in /proc/scsi, not /proc/scsi/scsi)
[root@linux proc]$ cd scsi
[root@linux scsi]$ ls
scsi usb-storage-0
[root@linux scsi]$ cd scsi
bash: cd: scsi: Not a directory
Thanks so much for the help...I really appreciate it!!
Originally posted by Demonbane If you're running 2.4 kernel, try as root:
mknod /dev/sr0 b 11 0
then try mounting /dev/sr0 and see what it says
The output of this attempt is as follows:
[root@linux root]$ mknod /dev/sr0 11 0
BusyBox v0.51 (2001.05.17-16:55+0000) multi-call binary
Usage: mknod [OPTIONS] NAME TYPE MAJOR MINOR
[root@linux root]$ mount /dev/sr0 /mnt
mount: special device /dev/sr0 does not exist
[root@linux root]$ mount /dev/sr0
mount: can't find /dev/sr0 in /etc/fstab or /etc/mtab
Aaaah that worked slightly better with the b (sorry about that!), but it still will not allow me to mount the drive:
[root@linux root]$ mknod /dev/sr0 b 11 0
[root@linux root]$ mount /dev/sr0
mount: can't find /dev/sr0 in /etc/fstab or /etc/mtab
[root@linux root]$ mount /dev/sr0 /mnt/cdrom
mount: /dev/sr0 is not a valid block device
[root@linux root]$ mount /dev/sr0 /mnt
mount: /dev/sr0 is not a valid block device
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.