LinuxQuestions.org - mounting usb storage devices blues

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

- - mounting usb storage devices blues (https://www.linuxquestions.org/questions/linux-hardware-18/mounting-usb-storage-devices-blues-306878/)

mounting usb storage devices blues

Hi there,

I'm new to this forum, and I hope this is the right place to ask for help with this issue. I've been searching for a solution to this for a long time now without luck.

Background info on my system
- Quantian 0.6.9.2 hard disk installation. This is a knoppix 3.6 based distro.
- Kernel 2.6.9 with usb-storage enabled.
- Lexar Media jump drive
- Nikon Coolpix 885 digital camera

Both the camera and the jump drive are recognized fine when plugged-in prior to a CD based boot-up. That is, both work fine when the original distro runs from the CD. They do not work when running from the hard drive installation. See below.

Problem
- lsusb shows my Lexar jump drive and my camera are being recognized by the system (I use a USB hub):

Bus 002 Device 005: ID 04b0:0105 Nikon Corp.
Bus 002 Device 004: ID 05dc:a400 Lexar Media, Inc.
Bus 002 Device 003: ID 0c45:6029 Microdia Triplex i-mini PC Camera
Bus 002 Device 002: ID 058f:9254 Alcor Micro Corp. Hub

- lsmod shows:

Module Size Used by
usb_storage 100240 0
nls_iso8859_1 3968 1
nvidia 3464988 12
rfcomm 32668 0
l2cap 20996 5 rfcomm
bluetooth 40708 4 rfcomm,l2cap
deflate 2944 0
zlib_deflate 20888 1 deflate
twofish 36992 0
serpent 12672 0
aes_i586 38644 0
blowfish 9728 0
des 11520 0
sha256 9088 0
sha1 8576 0
crypto_null 2048 0
md5 3712 1
ipv6 235776 16
snd_intel8x0m 15048 0
evdev 7424 0
ide_cd 37920 0
sn9c102 54280 0
videodev 7424 1 sn9c102
ub 14620 0
8250_pci 16512 0
ehci_hcd 26116 0
snd_intel8x0 29644 4
snd_ac97_codec 67920 2 snd_intel8x0m,snd_intel8x0
snd_pcm_oss 47144 0
snd_mixer_oss 17536 2 snd_pcm_oss
snd_pcm 82696 4 snd_intel8x0m,snd_intel8x0,snd_pcm_oss
snd_timer 20996 1 snd_pcm
snd_page_alloc 7688 3 snd_intel8x0m,snd_intel8x0,snd_pcm
gameport 3712 1 snd_intel8x0
snd_mpu401_uart 6272 1 snd_intel8x0
snd_rawmidi 19876 1 snd_mpu401_uart
snd_seq_device 6536 1 snd_rawmidi
snd 46308 15 snd_intel8x0m,snd_intel8x0,snd_ac97_code c,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_ timer,snd_mpu401_uart,snd_rawmidi,snd_se q_device
soundcore 7392 2 snd
sis_agp 6020 1
dm_mod 49788 0
lp 9260 0
agpgart 27688 2 sis_agp
autofs4 16004 0
af_packet 16904 2
sis900 17284 0
crc32 4096 1 sis900
parport_pc 38340 1
parport 34632 2 lp,parport_pc
8250 18752 1 8250_pci
serial_core 19200 1 8250
sg 29088 0
ohci_hcd 18436 0
uhci_hcd 28944 0
usbcore 101348 8 usb_storage,sn9c102,ub,ehci_hcd,ohci_hcd ,uhci_hcd
thermal 10888 0
processor 15400 1 thermal
fan 3076 0
button 5136 0
battery 7940 0
ac 3588 0
ide_scsi 13956 1
rtc 7188 0

- When attempting to mount the jump drive, for instance, I get the error:

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

I've tried mounting from other sd* devices in case they were assigned to another number, but nothing changes.

I'd be very grateful for any pointers, as I'm very stuck with this problem.

Thanks in advance! and hope to see you at the next meet-up,

- sabi

let's just stop and look at what is actaully happening when each device is connected. so... unplug device. run "dmesg -c". plug in device. run "dmesg" that second output will contain everything the subsystem did to handle your device.

from your module list, i see no refernce to sd_mod or a filesystem liekly to be on the device, e.g. fat. these may have been built into your kernel though.

Thanks for responding. The output of dmesg -c after unplugging the devices is too large to post, but here are the lines at the end that seemed relevant to me:

[...]

usb 2-1.3: USB disconnect, address 5
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
UDP: bad checksum. From 213.97.110.54:5889 to 24.77.70.85:5162 ulen 27
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
usb 2-1.2: USB disconnect, address 4

Please see the next message for the dmesg after plugging back the jump drive. I'm recharging the battery of the camera now :rolleyes:

hmmm...., this "post-replugging" dmesg looks strange:

24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
24.77.68.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 24.77.71.255 on eth0
usb 2-1.2: new full speed USB device using address 6
usb 2-1.2: not running at top speed; connect to a high speed hub
uba: device 6 capacity nsec 252928 bsize 512
uba: was not changed
uba: uba1

The strange thing is that I have working webcam connected to the same hub, AND all three devices (webcam, digital camera, and jump drive) work fine when I run knoppix from the CD. Quantian (Knoppix) does a great job of recognizing everything on boot-up, but the hard disk installation is having trouble somewhere.

In anticipation, here is my /etc/fstab, which I've modified slightly after the hard disk installation (SPL entry):

# /etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
/dev/hda1 / ext3 defaults,errors=remount-ro 0 1

proc /proc proc defaults 0 0
/dev/fd0 /floppy vfat defaults,user,noauto,showexec,umask=022 0 0
usbdevfs /proc/bus/usb usbdevfs defaults 0 0
sysfs /sys sysfs defaults 0 0
/dev/cdrom /cdrom iso9660 user,unhide,defaults,ro,noexec,noauto 0 0
/dev/cdrom1 /cdrom1 iso9660 user,unhide,defaults,ro,noexec,noauto 0 0
/dev/dvd /dvd iso9660 user,unhide,defaults,ro,noexec,noauto 0 0
/dev/cdaudio /cdaudio iso9660 user,unhide,defaults,ro,noexec,noauto 0 0
# Added by SPL 17-nov-2004
/dev/hdb1 /home auto rw,auto,user,exec 0 0
# /dev/cdrom1 /mnt/auto/cdrom1 auto user,unhide,users,noauto,exec,ro 0 0
# /dev/cdrom2 /mnt/auto/cdrom2 auto users,noauto,exec,ro 0 0
# /dev/cdrom3 /mnt/auto/cdrom3 auto users,noauto,exec,ro 0 0
# /dev/cdrom4 /mnt/auto/cdrom4 auto users,noauto,exec,ro 0 0
# /dev/cdrom5 /mnt/auto/cdrom5 auto users,noauto,exec,ro 0 0
# /dev/cdrom6 /mnt/auto/cdrom6 auto users,noauto,exec,ro 0 0
# /dev/cdrom7 /mnt/auto/cdrom7 auto users,noauto,exec,ro 0 0
/dev/cdrom1 /mnt/auto/cdrom1 auto users,noauto,exec,ro 0 0
# Added by KNOPPIX
/dev/hda2 none swap defaults 0 0

Hi

Boot your computer, unplug the drive
Plug it back in and try to mount it
What happens?

Sls

For me it looks more like an issue with ub (Low-performance USB-Blockdevice), look at the ub module loaded and the output from dmesg about what happens when drive is connected:

Code:

usb 2-1.2: new full speed USB device using address 6

usb 2-1.2: not running at top speed; connect to a high speed hub

uba: device 6 capacity nsec 252928 bsize 512

uba: was not changed

uba: uba1

The important thing here is the uba: messages, but with usb-storage one whould expect something like this:

Code:

usb 1-2: new high speed USB device using ehci_hcd and address 6

hub 1-2:1.0: USB hub found

hub 1-2:1.0: 1 port detected

usb 1-2.1: new high speed USB device using ehci_hcd and address 7

scsi2 : SCSI emulation for USB Mass Storage devices

usb-storage: device found at 7

usb-storage: waiting for device to settle before scanning

Just removing it from loaded modules or /lib/modues/`uname -r`/ will not help too much because activating that module at configuration time has at least effects on usb-storage! So recompiling kernel is needed here.

bonbons seems to be right on target here, have a look at the bottom of this page:

http://www.cs.utexas.edu/users/suriy...migration.html

I'm recompiling tonight and will post a report later. Thanks to all for your help so far!

I compiled Linux kernel 2.6.11.6 last night and confirmed that enabling the option BLK_DEV_UB (Block Devices -> "Low performance USB block driver") cripples the usb-storage driver, as the help in xconfig says. I hadn't been careful reading this when compiling my previous 2.6.9 kernel!

So I was able to login with my new 2.6.11.6 kernel, but only in console mode. For some reason kdm doesn't want to start. I've tried 'su -c "kdm"', but the console goes blank for a second and returns to console mode. I don't remember having this problem last time I compiled the kernel. What could I be missing here?

Thanks