Unable to mount USB memstick in RHL9
 

Hi,

I am unable to mount usb memstick in RH 9 server, even after I did the following.
1. Created a new directory /dev/memstick
2. Edited /etc/fstab and edited the line /dev/sda1 to
/dev/sda1 /mnt/memstick vfat noauto,owner,kudzu 0 0
3. Restarted the machine, and tried to mount the device using the follwing commands
mount /dev/sda1
mount /mnt/memstick
mount -t vfat /dev/sda1 /mnt/memstick
but still no luck...I am getting the following error message
mount: /dev/sda1 is not a valid block device

fdisk -l Output:
Disk /dev/sda: 125 MB, 125829120 bytes
4 heads, 60 sectors/track, 1024 cylinders
Units = cylinders of 240 * 512 = 122880 bytes

Device Boot Start End Blocks Id System

Disk /dev/hda: 40.0 GB, 40060403712 bytes
255 heads, 63 sectors/track, 4870 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 4822 38628292+ 83 Linux
/dev/hda3 4823 4870 385560 82 Linux swap

dmesg output:
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 18:11:21 Apr 13 2004
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 11 for device 00:1f.2
PCI: Setting latency timer of device 00:1f.2 to 64
usb-uhci.c: USB UHCI at I/O 0xeec0, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
hub.c: new USB device 00:1f.2-1, assigned address 2
hub.c: USB hub found
hub.c: 4 ports detected
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,2), internal journal
Adding Swap: 385552k swap-space (priority -1)
hub.c: new USB device 00:1f.2-1.1, assigned address 3
usb_control/bulk_msg: timeout
usb.c: USB device not accepting new address=3 (error=-110)
hub.c: new USB device 00:1f.2-1.1, assigned address 4
usb.c: USB device 4 (vend/prod 0x1011/0x1) is not claimed by any active driver.
hub.c: new USB device 00:1f.2-1.2, assigned address 5
input0: USB HID v1.00 Mouse [Logitech] on usb1:5.0
hub.c: new USB device 00:1f.2-1.4, assigned address 6
input1: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb1:6.0
input2: USB HID v1.10 Pointer [Logitech Logitech USB Keyboard] on usb1:6.1
SCSI subsystem driver Revision: 1.00
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: AccFast Model: USB-MSC Disk IN Rev: T
Type: Direct-Access ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 4
USB Mass Storage support registered.
usb-uhci.c: ENXIO 84000680, flags 0, urb caab9780, burb caab9680
usbdevfs: USBDEVFS_CONTROL failed dev 6 rqt 128 rq 6 len 59 ret -6
usb-uhci.c: ENXIO 84000680, flags 0, urb caab9680, burb caab9780
usbdevfs: USBDEVFS_CONTROL failed dev 6 rqt 128 rq 6 len 59 ret -6
usb-uhci.c: ENXIO 84000680, flags 0, urb caab9780, burb caab9680
usbdevfs: USBDEVFS_CONTROL failed dev 6 rqt 128 rq 6 len 59 ret -6

It would be great if anyone could help me out in this regard.

cd into /dev/ and then list all sda* devices; in terminal, give this command:

cd /dev
ls sda* | less

depending on what you get, try and mount these devices (sda1 seems not to be your stick, because you get errors):

mount /dev/sda4 /mnt/memstick
mount /dev/sda3 /mnt/memstick
etc...

so try and mount each sdaX-device (where X is a number) you get when you do the ls -sda* in /dev as above. this is, after you plug your stick in. if sda1 doesn't work, my guess would be that it's sda4, altough it can be what ever.

when you get the stick mounted (no errors come after mount command) just edit your fstab file to correspond the right device.

when I did ls sda* | less, after plugging in the memstick,
I am able to see sda followed by sda1. Moreover, when I tried to mount using
GNOME menu (using rt click in desktop, disks then memstick) the system throws
the follwing message
"Nautilus was unable to mount the volume. There is probably no media in the device."
when I clicked the details button, it shows the message
"mount: /dev/sda1 is not a valid block device."

Hence it should be sda1.

I tried mounting the memstick with sda1, sda2, sda3, sda4....
But still, without luck.

I then tried mounting the device with sda and it worked.
I am able to mount the device.

But still I am wondering, why the OS showed it as /dev/sda1 instead
of using /dev/sda?

Anyway, thanks for helping me out!!!

Hello,

I've got a similar issue. I found, that's why linux don't find VendorID. Without VendorID Linux does't know what to do with the device.
Now my question - how and where to add the VendorID manualy ?
I can find the ID by booting the system with pluged in stick - that works.

Let me know if you found something