f



Memorex USB Flash Drive Won't Mount -- "/dev/sda1 is not a valid block device"

I'm having no success mounting my Memorex USB 2.0 flash drive on my
Toshiba 1905-S277 running Redhat 9.0. I've tried nearly all of what I
read in the posts. I've added the line
/dev/sda1 		/mnt/thumbdrive		vfat user,noauto,umask=0   0 0 
to /etc/fstab, and created the /mnt/thumbdrive directory. When I try
mounting it, I get the message "/dev/sda1 is not a valid block
device."

I believe that the necessary modules are installed. The output from
lsmod is as follows:

/sbin/lsmod
Module                  Size  Used by    Not tainted
sd_mod                 13516   0  (autoclean) (unused)
vfat                   13004   0  (autoclean)
fat                    38808   0  (autoclean) [vfat]
usb-storage            69332   0 
parport_pc             19076   1  (autoclean)
lp                      8996   0  (autoclean)
parport                37056   1  (autoclean) [parport_pc lp]
autofs                 13268   0  (autoclean) (unused)
ds                      8680   4 
yenta_socket           13472   2 
pcmcia_core            57216   0  [ds yenta_socket]
e100                   60644   1 
ipt_REJECT              3928   6  (autoclean)
iptable_filter          2412   1  (autoclean)
ip_tables              15096   2  [ipt_REJECT iptable_filter]
sg                     36524   0  (autoclean)
sr_mod                 18136   0  (autoclean)
ide-scsi               12208   0 
scsi_mod              107160   6  [sd_mod usb-storage sg sr_mod
ide-scsi]
ide-cd                 35708   0 
cdrom                  33728   0  [sr_mod ide-cd]
keybdev                 2944   0  (unused)
mousedev                5492   1 
hid                    22148   0  (unused)
input                   5856   0  [keybdev mousedev hid]
usb-uhci               26348   0  (unused)
usbcore                78784   1  [usb-storage hid usb-uhci]
ext3                   70784   1 
jbd                    51892   1  [ext3]

The output of /sbin/lsusb is as follows:

Bus 002 Device 001: ID 0000:0000  
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x0000 
  idProduct          0x0000 
  bcdDevice            0.00
  iManufacturer           0 
  iProduct                2 USB UHCI Root Hub
  iSerial                 1 1840
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x40
      Self Powered
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               none
        wMaxPacketSize          8
        bInterval             255
  Language IDs: (length=4)
     0000 (null)((null))

Bus 001 Device 001: ID 0000:0000  
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x0000 
  idProduct          0x0000 
  bcdDevice            0.00
  iManufacturer           0 
  iProduct                2 USB UHCI Root Hub
  iSerial                 1 1820
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x40
      Self Powered
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               none
        wMaxPacketSize          8
        bInterval             255
  Language IDs: (length=4)
     0000 (null)((null))

Bus 001 Device 004: ID 08ec:0008 M-Systems 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 Interface
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x08ec M-Systems
  idProduct          0x0008 
  bcdDevice            1.00
  iManufacturer           1 Memorex
  iProduct                2 TD 2C
  iSerial                 3 2830B840F301
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
    MaxPower              128mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk (Zip)
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               none
        wMaxPacketSize         64
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               none
        wMaxPacketSize         64
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               none
        wMaxPacketSize         64
        bInterval               1
  Language IDs: (length=4)
     0409 English(US)

The output of /proc/bus/usb/devices is as follows:
T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 1.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 0.00
S:  Product=USB UHCI Root Hub
S:  SerialNumber=1840
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=255ms
T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 1.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 0.00
S:  Product=USB UHCI Root Hub
S:  SerialNumber=1820
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=255ms
T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  4 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=08ec ProdID=0008 Rev= 1.00
S:  Manufacturer=Memorex
S:  Product=TD 2C
S:  SerialNumber=2830B840F301
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=128mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=06 Prot=50
Driver=usb-storage
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=83(I) Atr=03(Int.) MxPS=  64 Ivl=1ms

The contents of /proc/scsi are as follows:
ide-scsi
scsi
sg
usb-storage-0

The contents of /proc/scsi/usb-storage-0/1 are as follows:

   Host scsi1: usb-storage
       Vendor: Memorex
      Product: TD 2C
Serial Number: 2830B840F301
     Protocol: Transparent SCSI
    Transport: Bulk
         GUID: 08ec000800002830b840f301
     Attached: Yes

tail -f /var/log/messages:
Nov 13 13:35:29 localhost kernel: hub.c: new USB device 00:1f.2-2,
assigned address 7
Nov 13 13:35:32 localhost /etc/hotplug/usb.agent: Setup usb-storage
for USB product 8ec/8/100
Nov 13 13:35:32 localhost devlabel: devlabel service started/restarted


Any help would be greatly appreciated.

--Rob Siegel
Please cc mail directly to robbysiege@aol.com
0
11/13/2004 7:50:52 PM
comp.os.linux.misc 33599 articles. 1 followers. amosa69 (78) is leader. Post Follow

7 Replies
491 Views

Similar Articles

[PageSpeed] 3

On Sat, 13 Nov 2004 22:57:40 +0000, Andy Axnot wrote:

> On Sat, 13 Nov 2004 21:04:59 +0000, Dances With Crows wrote:
> 
>> ["Followup-To:" header set to comp.os.linux.hardware.] On Sat, 13 Nov
>> 2004 20:46:55 GMT, Andy Axnot staggered into the Black Sun and said:
>>> On Sat, 13 Nov 2004 11:50:52 -0800, Rob Siegel wrote:
>>>> /dev/sda1  /mnt/thumbdrive  vfat user,noauto,umask=0   0 0
>>> Some of us who have had this problem have dealt with it by changing the
>>> line you added in fstab, changing sda1 to just sda, no 1. Don't ask me
>>> to explain this, I can't
>> 
>> Obviously, some USB storage devices are partitioned, and some aren't.
>> The vast majority of USB storage devices have one partition of type 0x7
>> or 0x8 (FAT32, non-LBA (< 8G) or LBA (> 8G)) covering the entire device.
>> 
> Well, I don't know how obvious it is, but it makes sense.  If it is
> actually obvious to someone knowledgeable, it's just amazing that no one
> pointed this out before.  I posted several requests for help on the Mepis
> Linux forum and other places over a period of... a month?  more?  Most of
> the replies were of the "works OK for me" sort.
> 
> I stumbled on to the "sda" by trying variations on "sda1" until I didn't
> get an error.  At least one poster at Mepis told me that such an
> unmodified descriptor (I don't know the proper term) should never be
> necessary.
> 
>>> I keep hoping someone will point me to a tutorial on all this sda,
>>> sda1, sdax, sdb, etc., stuff.  So far no one has.
>> 
>> Tutorial?  Huh?  It's simple; sda is the first SCSI disk, sda1..sda15
>> are the 1st through 15th partitions on the disk.  sdb is the second SCSI
>> disk, sdc is the third... sddx is the 128th.  Most SCSI disks are
>> partitioned.  Some (MO disks, some USB storage devices) aren't.  You can
>> use "fdisk -l" on any block device to find out whether a partition table
>> is present and which partitions exist (if any).  HTH,
> 
> It does, indeed, help.  Thank you.
> 
> Andy

I've found that /dev/sda is necessary on an up to date system if you're
trying to mount a USB floppy - reason: floppies are not generally
considered to be partitionable!


0
ray65 (5421)
11/12/2004 11:16:52 PM
On Sat, 13 Nov 2004 11:50:52 -0800, Rob Siegel wrote:

> I'm having no success mounting my Memorex USB 2.0 flash drive on my
> Toshiba 1905-S277 running Redhat 9.0. I've tried nearly all of what I
> read in the posts. I've added the line
> /dev/sda1 		/mnt/thumbdrive		vfat user,noauto,umask=0   0 0 
> to /etc/fstab, and created the /mnt/thumbdrive directory. When I try
> mounting it, I get the message "/dev/sda1 is not a valid block
> device."
> 

Some of us who have had this problem have dealt with it by changing the
line you added in fstab, changing sda1 to just sda, no 1.

Don't ask me to explain this, I can't, but it works for me and some
others.  I keep hoping someone will point me to a tutorial on all this
sda, sda1, sdax, sdb, etc., stuff.  So far no one has.

Andy

0
Andy4315 (13)
11/13/2004 8:46:55 PM
["Followup-To:" header set to comp.os.linux.hardware.]
On 13 Nov 2004 11:50:52 -0800, Rob Siegel staggered into the Black Sun
and said:
> I'm having no success mounting my Memorex USB 2.0 flash drive on my
> Toshiba 1905-S277 running Redhat 9.0.

It's highly probable that your kernel's too old, so the USB ID of this
device isn't in the list the usb-storage module recognizes.

> /dev/sda1  /mnt/thumbdrive  vfat user,noauto,umask=0   0 0 

That's appropriate, but read on.

> sd_mod                 13516   0  (autoclean) (unused)
> usb-storage            69332   0 
> scsi_mod              107160   6
> usb-uhci               26348   0  (unused)

Why isn't ehci-hcd loaded?  Unless you modprobe that, you're limited
to USB 1 speeds.  USB 2 devices are supposed to downgrade to USB 1 if
that's all that's available, but who wants to settle for 1M/s speed?

> localhost kernel: hub.c: new USB device 00:1f.2-2, assigned address 7

Give your machine a real hostname; "localhost" can cause confusion since
localhost is supposed to be aliased to 127.0.0.N.

> /etc/hotplug/usb.agent: Setup usb-storage for USB product 8ec/8/100
> devlabel: devlabel service started/restarted

What's the output of "uname -a"?  The first thing to try is to get the
latest stable kernel.  Remember that Redhat 9 is EOLed, so you're going
to want to upgrade to something newer soon anyway.  I hear Mandrake 10
is nice, but for ease of maintenance, you can't beat Gentoo/Debian.

-- 
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /    mail: TRAP + SPAN don't belong
http://www.brainbench.com     /                Hire me! 
-----------------------------/ http://crow202.dyndns.org/~mhgraham/resume
0
11/13/2004 8:58:30 PM
["Followup-To:" header set to comp.os.linux.hardware.]
On Sat, 13 Nov 2004 20:46:55 GMT, Andy Axnot staggered into the Black
Sun and said:
> On Sat, 13 Nov 2004 11:50:52 -0800, Rob Siegel wrote:
>> /dev/sda1  /mnt/thumbdrive  vfat user,noauto,umask=0   0 0 
> Some of us who have had this problem have dealt with it by changing
> the line you added in fstab, changing sda1 to just sda, no 1.
> Don't ask me to explain this, I can't

Obviously, some USB storage devices are partitioned, and some aren't.
The vast majority of USB storage devices have one partition of type 0x7
or 0x8 (FAT32, non-LBA (< 8G) or LBA (> 8G)) covering the entire device.

> I keep hoping someone will point me to a tutorial on all this sda,
> sda1, sdax, sdb, etc., stuff.  So far no one has.

Tutorial?  Huh?  It's simple; sda is the first SCSI disk, sda1..sda15
are the 1st through 15th partitions on the disk.  sdb is the second SCSI
disk, sdc is the third... sddx is the 128th.  Most SCSI disks are
partitioned.  Some (MO disks, some USB storage devices) aren't.  You can
use "fdisk -l" on any block device to find out whether a partition table
is present and which partitions exist (if any).  HTH,

-- 
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /    mail: TRAP + SPAN don't belong
http://www.brainbench.com     /                Hire me! 
-----------------------------/ http://crow202.dyndns.org/~mhgraham/resume
0
11/13/2004 9:04:59 PM
On Sat, 13 Nov 2004 21:04:59 +0000, Dances With Crows wrote:

> ["Followup-To:" header set to comp.os.linux.hardware.] On Sat, 13 Nov
> 2004 20:46:55 GMT, Andy Axnot staggered into the Black Sun and said:
>> On Sat, 13 Nov 2004 11:50:52 -0800, Rob Siegel wrote:
>>> /dev/sda1  /mnt/thumbdrive  vfat user,noauto,umask=0   0 0
>> Some of us who have had this problem have dealt with it by changing the
>> line you added in fstab, changing sda1 to just sda, no 1. Don't ask me
>> to explain this, I can't
> 
> Obviously, some USB storage devices are partitioned, and some aren't.
> The vast majority of USB storage devices have one partition of type 0x7
> or 0x8 (FAT32, non-LBA (< 8G) or LBA (> 8G)) covering the entire device.
> 
Well, I don't know how obvious it is, but it makes sense.  If it is
actually obvious to someone knowledgeable, it's just amazing that no one
pointed this out before.  I posted several requests for help on the Mepis
Linux forum and other places over a period of... a month?  more?  Most of
the replies were of the "works OK for me" sort.

I stumbled on to the "sda" by trying variations on "sda1" until I didn't
get an error.  At least one poster at Mepis told me that such an
unmodified descriptor (I don't know the proper term) should never be
necessary.

>> I keep hoping someone will point me to a tutorial on all this sda,
>> sda1, sdax, sdb, etc., stuff.  So far no one has.
> 
> Tutorial?  Huh?  It's simple; sda is the first SCSI disk, sda1..sda15
> are the 1st through 15th partitions on the disk.  sdb is the second SCSI
> disk, sdc is the third... sddx is the 128th.  Most SCSI disks are
> partitioned.  Some (MO disks, some USB storage devices) aren't.  You can
> use "fdisk -l" on any block device to find out whether a partition table
> is present and which partitions exist (if any).  HTH,

It does, indeed, help.  Thank you.

Andy
0
Andy4315 (13)
11/13/2004 10:57:40 PM
Thanks to all for the advice. I still don't have it working. Below is
the latest output from \var\log\messages after plugging in the Flash
drive:

hub.c: new USB device 00:1f.2-2, assigned address 2
usb.c: USB device 2 (vend/prod 0x8ec/0x8) is not claimed by any active
driver.
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
usb-uhci.c: interrupt, status 2, frame# 1428
scsi1 : SCSI emulation for USB Mass Storage devices
hub.c: already running port 2 disabled by hub (EMI?), re-enabling...
usb.c: USB disconnect on device 00:1f.2-2 address 2
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
hub.c: Cannot enable port 2 of hub 1, disabling port.
hub.c: Maybe the USB cable is bad?

> Why isn't ehci-hcd loaded?  Unless you modprobe that, you're limited
> to USB 1 speeds.  USB 2 devices are supposed to downgrade to USB 1 if
> that's all that's available, but who wants to settle for 1M/s speed?
> 

modprobe ehci-hcd fails, as follows:
/lib/modules/2.4.20-8/kernel/drivers/usb/hcd/ehci-hcd.o: init_module:
No such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters.
      You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-8/kernel/drivers/usb/hcd/ehci-hcd.o: insmod
/lib/modules/2.4.20-8/kernel/drivers/usb/hcd/ehci-hcd.o failed
/lib/modules/2.4.20-8/kernel/drivers/usb/hcd/ehci-hcd.o: insmod
ehci-hcd failed
[root@localhost stols]#

> What's the output of "uname -a"?  

Linux localhost.localdomain 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003
i686 i686 i386 GNU/Linux

> The first thing to try is to get the
> latest stable kernel.  Remember that Redhat 9 is EOLed, so you're going
> to want to upgrade to something newer soon anyway.  I hear Mandrake 10
> is nice, but for ease of maintenance, you can't beat Gentoo/Debian.

Forgive the neophyte question, but when you say "get the latest stable
kernel," do you mean a full from-scratch install of another Linux? I'd
prefer to avoid that if possible; if it means falling back to an older
USB 1.1 flash drive, that's fine.
0
11/14/2004 4:43:27 PM
["Followup-To:" header set to comp.os.linux.hardware.]

See that?  That means you should reply in col.hardware, and *only* in
col.hardware, because this is a hardware question.  groups.google
doesn't grok the Followup-To: header, so change the Newsgroups: line
manually, or get a Real Newsreader.

On 14 Nov 2004 08:43:27 -0800, Rob Siegel staggered into the Black Sun
and said:
> hub.c: new USB device 00:1f.2-2, assigned address 2
> usb.c: USB device 2 (vend/prod 0x8ec/0x8) is not claimed by any active
> driver.

That's usually not a good sign.  It looks like you're running hotplug
though, so usb-storage gets modprobed later.

> USB Mass Storage device found at 2
> USB Mass Storage support registered.

This is usually a good sign.

> hub.c: Cannot enable port 2 of hub 1, disabling port.
> hub.c: Maybe the USB cable is bad?

This isn't.  Read on for a possible solution.

>> Why isn't ehci-hcd loaded?
> /lib/modules/2.4.20-8/kernel/drivers/usb/hcd/ehci-hcd.o: init_module:
> No such device

Does an EHCI device show up when you do "lspci -vv"?  If not, then your
machine doesn't have an EHCI chipset, and you will be limited to USB 1
speeds.

> Linux localhost.localdomain 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003

See, this kernel is 1.5 years old.  That's positively ancient in
software terms.

>> The first thing to try is to get the latest stable kernel.  Remember
>> that Redhat 9 is EOLed, so you're going to want to upgrade to
>> something newer soon anyway.
> Forgive the neophyte question, but when you say "get the latest stable
> kernel," do you mean a full from-scratch install of another Linux?

No, I mean "get the redhat9-2.4.26-x86-kernel.rpm (or whatever it's
called) and rpm -Uvh it, then reboot."  You *will* want to install
another distro soon, because Redhat 9 is EOLed, but you can just upgrade
the kernel on this machine.  Your USB device might work then.

The kernel is the master process that runs everything else.  Device
drivers in Linux are typically kernel modules, little pieces of code
that are loaded with "modprobe".  You can find out more than you ever
wanted to know about the kernel by looking in /usr/share/doc/howto/ for
the Kernel-Upgrade HOWTO, or /usr/src/linux/Documentation/ if you
installed the kernel sources.

-- 
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /    mail: TRAP + SPAN don't belong
http://www.brainbench.com     /                Hire me! 
-----------------------------/ http://crow202.dyndns.org/~mhgraham/resume
0
11/14/2004 5:49:08 PM
Reply: