LinuxQuestions.org - usb thumbdrive. can't mount? not listed?!

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - usb thumbdrive. can't mount? not listed?! (https://www.linuxquestions.org/questions/linux-hardware-18/usb-thumbdrive-cant-mount-not-listed-211721/)

usb thumbdrive. can't mount? not listed?!

Got myself a thumbdrive today and was expecting a problem or two, because I've read quite a bit about these things on these forums. I've tried the basics and read some other threads, but to no help.
I tried mounting sda through sdg, and 1-15 on each one pretty much. I have no other scsi drives on here so I would assume it'd just be sda :) Here's what I get.

Code:

root@floods[box]:/home/floods# mount -t vfat /dev/sda /mnt/usbstick/

mount: /dev/sda is not a valid block device

and I get the same thing when I try mounting it from the fstab.

Code:

root@floods[box]:/mnt# mount usbstick/

mount: /dev/sda is not a valid block device

root@floods[box]:/mnt#

and here is my lsmod.

Code:

root@floods[box]:/home/floods# lsmod | grep usb    

usb_storage            33920  0 

scsi_mod              78140  2 ide_scsi,usb_storage

Here's what I have in my fstab for the thumbdrive

Code:

root@floods[box]:/home/floods# cat /etc/fstab | grep sda

/dev/sda          /mnt/usbstick        vfat            user,noauto,umask=0              0  0

Here's lsusb -vvv, only the part about the lexar drive though (to save space)

Code:

Bus 003 Device 007: ID 05dc:0080 Lexar Media, Inc. 

Device Descriptor:

  bLength                18

  bDescriptorType        1

  bcdUSB              1.10

  bDeviceClass            0 (Defined at Interface level)

  bDeviceSubClass        0 

  bDeviceProtocol        0 

  bMaxPacketSize0        8

  idVendor          0x05dc Lexar Media, Inc.

  idProduct          0x0080 

  bcdDevice            0.01

  iManufacturer          1 LEXAR MEDIA  

  iProduct                2 JUMPDRIVE    

  iSerial                3 F259192121020

  bNumConfigurations      1

  Configuration Descriptor:

    bLength                9

    bDescriptorType        2

    wTotalLength          32

    bNumInterfaces          1

    bConfigurationValue    1

    iConfiguration          0 

    bmAttributes        0x80

    MaxPower              90mA

    Interface Descriptor:

      bLength                9

      bDescriptorType        4

      bInterfaceNumber        0

      bAlternateSetting      0

      bNumEndpoints          2

      bInterfaceClass        8 Mass Storage

      bInterfaceSubClass      6 SCSI

      bInterfaceProtocol    80 Bulk (Zip)

      iInterface              0 

      Endpoint Descriptor:

        bLength                7

        bDescriptorType        5

        bEndpointAddress    0x82  EP 2 IN

        bmAttributes            2

          Transfer Type            Bulk

          Synch Type              None

          Usage Type              Data

        wMaxPacketSize    0x0040  bytes 64 once

        bInterval              0

      Endpoint Descriptor:

        bLength                7

        bDescriptorType        5

        bEndpointAddress    0x03  EP 3 OUT

        bmAttributes            2

          Transfer Type            Bulk

          Synch Type              None

          Usage Type              Data

        wMaxPacketSize    0x0040  bytes 64 once

        bInterval              0

Here's tail -s 3 -f /var/log/messages when I plug the drive in

Code:

Jul 31 00:36:00 floods[box] kernel: usb 3-2: USB disconnect, address 6

Jul 31 00:36:02 floods[box] kernel: usb 3-2: new full speed USB device using address 7

Jul 31 00:36:02 floods[box] kernel: scsi5 : SCSI emulation for USB Mass Storage devices

Jul 31 00:36:02 floods[box] scsi.agent[9269]: bogus sysfs DEVPATH=/devices/pci0000:00/0000:00:10.1/usb3/3-2/3-2:1.0/host5/5:0:0:0

Jul 31 00:36:02 floods[box] kernel:  Vendor: LEXAR    Model: JUMPDRIVE        Rev: 1.20

Jul 31 00:36:02 floods[box] kernel:  Type:  Direct-Access                      ANSI SCSI revision: 02

Jul 31 00:36:03 floods[box] usbmgr[7475]: vendor:0x5dc product:0x80

Jul 31 00:36:03 floods[box] usbmgr[7475]: class:0x8 subclass:0x6 protocol:0x50

Jul 31 00:36:03 floods[box] usbmgr[7475]: USB device isn't matched the configuration

Now what bugs me about that part is the "bogus sysfs" portion, and the DEVPATH=/ is what I believed would be /dev/sda, but I'm not sure since I've yet to find anyone else post with that same message in /var/log/messages
It's not even directing it to /dev/sd*, which everything else I've read said it would list /dev/sd* somewhere in my /var/log/messages.

I think the usbmgr parts are from something I downloaded to try and get it working and just uninstalled, but it's still showing up. Not my problem right now though :)

I'm just lost on where to start!
Any pointers?
Much appreciated. especially if you even read all this :) and if you need any more information I'm willing to give it of course.
Thanks in advance!

normally you could watch /var/log/messages as you plug it in, you should see the name shown.

I guess your using devfs which is going to change things a bit.

Maybe try linking to something in this path

/devices/pci0000:00/0000:00:10.1/usb3/3-2/3-2:1.0/host5/5:0:0:0

I did watch /var/log/messages/ and never found *anything* relating to sd*
and I'm not using devfs.

Code:

root@floods[box]:/home/floods# cd /usr/src/linux

root@floods[box]:/usr/src/linux# cat .config | grep DEVFS

# CONFIG_DEVFS_FS is not set

should I be to get this to work? I've never tampered with devfs becuase I simply didn't know it's purpose and had no real reason to.

going to try with devfs on and see what it gives, but haven't yet. will edit this post once I do.. mainly a bump :(

edit: tried devfs, nothing sd* was listed in /dev then, which was what I was afraid of. I've messed with my kernel a little more (took devfs off again, other things) and now I see this in dmesg..

Code:

scsi0 : SCSI emulation for USB Mass Storage devices

  Vendor: LEXAR    Model: JUMPDRIVE        Rev: 1.20

  Type:  Direct-Access                      ANSI SCSI revision: 02

USB Mass Storage device found at 2

usbcore: registered new driver usb-storage

Try mounting it as /dev/sda1. You need to mount the partition, not the device itself. I had similar problems with my flash reader when I tried to get it working last week.

See this page too: http://www.cs.sfu.ca/%7Eggbaker/personal/cf-linux

There really needs to be a sticky thread about USB devices here.

hm, now it's getting really irritating.
I have tried mounting it as /dev/sda1, and I just read that link.

Once I got past all the kernel stuff and got sg_utils, sgcan -i gives this

Code:

root@floods[box]:/home/floods/Downloads# sg_scan -i 

/dev/sg0: scsi0 channel=0 id=0 lun=0 [em]  type=0

    LEXAR    JUMPDRIVE        1.20  [wide=0 sync=0 cmdq=0 sftre=0 pq=0x0]

which looks pretty normal.. then sg_map gives this

Code:

root@floods[box]:/home/floods/Downloads# sg_map 

/dev/sg0

it's not linked to anything?! I tried mounting /dev/sg0 but it said it's not a valid block device. ack :(

anyone? heh. hate to feel like I bought this thing for nothing. :/

How about sg1

linux:/proc/scsi # ls -l /dev/sg0 /dev/sg1
crw-r----- 1 root disk 21, 0 Oct 2 2003 /dev/sg0
crw-r----- 1 root disk 21, 1 Oct 2 2003 /dev/sg1

ls-l /dev/sda /dev/sda1
brw-rw---- 1 root disk 8, 0 Oct 2 2003 /dev/sda
brw-rw---- 1 root disk 8, 1 Oct 2 2003 /dev/sda1

If the drive has more that one partition as the secure version does then you may need multilun enabled in the kernel to use the drive.

I usually run fdisk like this to see mine..

fdisk -l
Disk /dev/sdc: 255 MB, 255852544 bytes
16 heads, 32 sectors/track, 976 cylinders
Units = cylinders of 512 * 512 = 262144 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 1 976 249840 83 Linux

Disk /dev/sdd: 129 MB, 129990656 bytes
16 heads, 16 sectors/track, 991 cylinders
Units = cylinders of 256 * 512 = 131072 bytes

Device Boot Start End Blocks Id System
/dev/sdd1 * 1 990 126703+ 6 FAT16

Disk /dev/hda: 60.0 GB, 60011642880 bytes
255 heads, 63 sectors/track, 7296 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 1 3825 30724281 83 Linux
/dev/hda2 * 3826 7296 27880272 82 Linux swap

Code:

[root@floodsbox:/home/floods]ls -l /dev/sg0 /dev/sg1

crw-------  1 root root 21, 0 Apr 13  1999 /dev/sg0

crw-------  1 root root 21, 1 Apr 13  1999 /dev/sg1

nothing important there, right?

btw, I do have multilun enabled in my kernel, which I did *just* in case this were the problem :(

fdisk -l gives me no options, still. do I need to format this thing on my windows box maybe? I think I'll try that in a few.

Code:

[root@floodsbox:/home/floods]fdisk -l



Disk /dev/hda: 13.0 GB, 13020069888 bytes

255 heads, 63 sectors/track, 1582 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes



  Device Boot      Start        End      Blocks  Id  System

/dev/hda1  *          1        132    1060258+  82  Linux swap

/dev/hda2            133        1582    11647125    5  Extended

/dev/hda5            133        1582    11647093+  83  Linux

only portion on there I'm curious about is /dev/hda2, I know it's not the usb device but I don't know what it actually is.

This is a long shot, but worth a try:

Try some other USB mass storage device, like a USB Hard disk. Mount that using the "-t auto" option on mount. If you can access this device, then remove it and connect your thumb-drive and try accessing it just like you did for the other USB storage device.

Note: If you are using a USB hard drive - make sure you have the proper kernel modules for the particular file system.

vxc

Well, I finally had some real free time and asked a friend. he repointed me in the direction of the scsi drivers in the kernel, which I had as modules. I changed them from modules and compiled them in and it worked like a charm.
Why is it that it wouldn't work as a module?
Anyways, it works now, so I'm happy. :)

Thanks for all your help, it's muchly appreciated

It would work as a module. You just need to load them.

Basically the devices I posted were to show the device nodes in the event that you had to create them for some reason.

Well, even after they were loaded I couldn't get it up.

I've had quite a few issues with modules not working on my newer 2.6 kernels, but with all the 2.4 kernels I rolled they worked fine.

I've moved on to FTP and IP masquerading, so now I have newer and bigger things to learn. :) Just need a router, but that may be for another post another day.

Thanks for all the help David