USB 2 drives making system hang...

MonkeyBumps · 08-28-2003, 11:42 PM

I have two different usb 2 drives, one is an ntfs drive and the other is vfat. now the system picks them up fine. when i plug them in dmesg see them and they are assigned to sda1 (if only one is connected). then i can do an "fdisk -l /dev/sda" and it shows the correct info for that drive. now if i try and mount the drives with the following command:
"mount -r -t ntfs /dev/sda1 /mnt/usb_drive"
"mount -t vfat /dev/sda1 /mnt/usb_drive"

the system just hangs.... keyboard locks up and system is down for the count. (i guess it could just be the usb hanging cause both my mouse and keyb are usb aswell)

i have read a few post here about mounting usb drives but nothing about the system hanging after you try and mount the dev. any ideas on what would cause something like this?

================================================
= here is some of the kernel log.... this should tell something
================================================
Aug 28 21:24:25 [kernel] Initializing USB Mass Storage driver...
Aug 28 21:24:25 [kernel] scsi0 : SCSI emulation for USB Mass Storage devices
Aug 28 21:24:25 [kernel] Vendor: WDC WD80 Model: 0BB-00CAA1 Rev: 17.0
Aug 28 21:24:25 [kernel] Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Aug 28 21:24:25 [kernel] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
Aug 28 21:45:35 [kernel] usb.c: USB disconnect on device 00:10.3-4 address 2
Aug 28 21:45:40 [kernel] Device 08:01 not ready.
Aug 28 21:45:40 [kernel] NTFS: Read/write error.
Aug 28 21:46:32 [kernel] hub.c: new USB device 00:10.3-4, assigned address 3
Aug 28 21:46:43 [kernel] usb_control/bulk_msg: timeout
Aug 28 21:46:43 [kernel] scsi1 : SCSI emulation for USB Mass Storage devices
Aug 28 21:46:48 [kernel] Vendor: QUANTUM Model: FIREBALL ST2 Rev: A0F.
Aug 28 21:46:48 [kernel] Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
Aug 28 21:46:48 [kernel] SCSI device sdb: 5008752 512-byte hdwr sectors (2564 MB)
Aug 28 21:47:05 [kernel] Device 08:00 not ready.
Aug 28 21:47:05 [kernel] Device 08:01 not ready.
Aug 28 21:47:07 [kernel] Device 08:00 not ready.
Aug 28 21:47:07 [kernel] Device 08:01 not ready.
Aug 28 21:47:08 [kernel] Device 08:00 not ready.
Aug 28 21:47:08 [kernel] Device 08:01 not ready.
Aug 28 21:47:09 [kernel] Device 08:00 not ready.
Aug 28 21:47:09 [kernel] Device 08:01 not ready.
Aug 28 21:47:09 [kernel] Device 08:00 not ready.
Aug 28 21:47:09 [kernel] Device 08:01 not ready.
Aug 28 21:47:09 [kernel] Device 08:00 not ready.
Aug 28 21:47:09 [kernel] Device 08:01 not ready.
Aug 28 21:47:09 [kernel] Device 08:00 not ready.
Aug 28 21:47:09 [kernel] Device 08:01 not ready.
Aug 28 21:47:10 [kernel] Device 08:00 not ready.
Aug 28 21:47:10 [kernel] Device 08:01 not ready.
Aug 28 21:47:10 [kernel] Device 08:00 not ready.
Aug 28 21:47:10 [kernel] Device 08:01 not ready.

===============================================

* also drives work on all other systems i have tried.

thanks for the help,
-mb

==============================================
my system is running :
gentoo
kernel -> 2.4.20 (gamming-source)
all other usb hardware works. but these are the only usb 2 devices in the system.
==============================================

faheyd · 08-29-2003, 01:14 AM

Try this:
1. Boot with no USB drives
2. Plug in the vfat usb2 drive
In terminal console (you may have to be root to do some of this)
3. mkdir /mnt/usb1
4. mkdir /mnt/usb2
5. type: "mount -t vfat -o ro /dev/sda1 /mnt/usb1"
6. ls -al /mnt/usb1 (assuming there are files on vfat)
success, go have coffee
7. Plug in the ntfs usb2 drive
8. type: "mount -t ntfs -o ro /dev/sdb1 /mnt/usb2"
9. ls -al /mnt/usb2 (assuming there are files on ntfs)
success, go buy me a coffee
10. Read other links on this site as to 'fstab' files, permissions to use files on the drive, etc.
go have more coffee!

Any problems, post the offending drive /var/log/messages when you plug 'just' that drive in. Maybe you should plug the drives directly into the usb2 ports on the motherboard, if you are not already doing that? On a side note, you should see something similar to usb "High bandwidth mode enabled" in your 'dmesg' output somewhere. Don't forget "/sbin/lsusb" and "uname -r" are your friends when you post about usb problems.

michaelk · 08-29-2003, 06:37 AM

With USB the first drive that is connected will be assigned /dev/sda, the second will be /dev/sdb etc etc.

You can't mount the drives to the same directory.

What I am wondering is why didn't you get a message to say that sda1 was already mounted.

MonkeyBumps · 08-29-2003, 07:20 AM

Michaelk..... i'm not mounting the two drives into the same dir. that was just my example.

faheyd,
when you say go have coffeedo you mean that its going to take awhile? if so how long? i waited for over ten mins to see if it would ever do anything.... but no.

also there are no messages about "High bandwidth mode enabled" in dmesg. maybe usb 2 is messed up? but usb 1 devices work fine...... out of the same ports.

is there any info that would be useful to anyone for helping me solve this? i really need the data on those drives, plus i'd like to use them. =)

lsusb see the drives, and my kernel is 2.4.20 (gaming-r5) on a gentoo system.

faheyd · 08-29-2003, 01:36 PM

Try this, since my sense of humor got the best of me.
1. Boot with no USB drives
2. In a terminal window/console, type tail -f /var/log/messages, move window to the side, open new terminal window, and do the following.
3. Plug in the vfat usb2 drive
4. type: "mkdir /mnt/usb1" (if already done, skip)
5. type: "mount -t vfat -o ro /dev/sda1 /mnt/usb1"
6. type: "ls -al /mnt/usb1" (assuming there are files on vfat)

If no success, (/var/log/messages is the current state of your system, and in seconds shows the usb/scsi storage systems coming online), copy/paste the output of your /var/log/messages here.

Show us the output of lsusb command, after trying the above.

I would also like to see your output of 'dmesg' concerning any lines concerning your usb system.

Confirm/show the following:
Your motherboard (M/B) make/model, bios version.
M/B is USB2 capable? yes/no
USB chip on M/B: See output dmesg or M/B manual
Custom kernel or package (stock)?

go have coffee, while I or someone else gets back to you. I'll be back online tonight, anyone else want to pick up the ball, feel free.

MonkeyBumps · 08-29-2003, 03:09 PM

this the info on my current system.... if you need other info please ask... i just dont understand way it locks when i mount the drive.....
thanks for your help!
-mb

dmesg after plugin in the vfat usb2 drive:

Code:

hub.c: new USB device 00:10.3-4, assigned address 2
usb_control/bulk_msg: timeout
scsi1 : SCSI emulation for USB Mass Storage devices
  Vendor: QUANTUM   Model: FIREBALL ST2      Rev: A0F.
  Type:   Direct-Access                      ANSI SCSI revision: 02
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
SCSI device sda: 5008752 512-byte hdwr sectors (2564 MB)
 /dev/scsi/host1/bus0/target0/lun0: p1
WARNING: USB Mass Storage data integrity not assured

==
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
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 hid
usb.c: registered new driver usb-storage
input0: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb4:2.0
input1: USB HID v1.10 Pointer [Logitech Logitech USB Keyboard] on usb4:2.1
input2: USB HID v1.10 Mouse [B16_b_02 USB-PS/2 Optical Mouse] on usb4:3.0
usb.c: USB device 3 (vend/prod 0x46d/0x870) is not claimed by any active driver.
usb_control/bulk_msg: timeout

lsusb after plugin the vfat drive:

Code:

bash-2.05b# lsusb
Bus 004 Device 001: ID 0000:0000
Bus 004 Device 002: ID 046d:c30a Logitech, Inc.
Bus 004 Device 003: ID 046d:c025 Logitech, Inc. MX500 Optical Mouse
Bus 003 Device 001: ID 0000:0000
Bus 003 Device 002: ID 04cc:1122 Philips Semiconductors Hub
Bus 003 Device 003: ID 046d:0870 Logitech, Inc. QuickCam Express
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 001 Device 003: ID 0c0b:b001 Dura Micro, Inc. (Acomdata)

fdisk -l /dev/sda

Code:

Disk /dev/sda: 2564 MB, 2564481024 bytes
128 heads, 63 sectors/track, 621 cylinders
Units = cylinders of 8064 * 512 = 4128768 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/sda1             1       621   2503840+   b  Win95 FAT32

lsmod:

Code:

Module                  Size  Used by    Tainted: PF
ide-scsi                7600   0
floppy                 47004   0  (autoclean)
nls_iso8859-1           2780   1  (autoclean)
nls_cp437               4316   1  (autoclean)
vfat                    9324   1  (autoclean)
fat                    29816   0  (autoclean) [vfat]
nvidia               1626624  11
8139too                14152   1
mii                     2128   0  [8139too]
usb-storage            55608   0
hid                    12468   0  (unused)
uhci                   23008   0  (unused)
ehci-hcd               13056   0  (unused)
usbcore                55456   1  [usb-storage hid uhci ehci-hcd]

/proc/bus/usb/devices

Code:

S:  Manufacturer=Linux 2.4.20-gaming-r5 ehci-hcd
S:  Product=VIA Technologies, Inc. USB 2.0
S:  SerialNumber=00:10.3
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=   2 Ivl=256ms
T:  Bus=01 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#=  3 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=0c0b ProdID=b001 Rev=11.10
S:  Manufacturer=DMI
S:  Product=USB 2.0 Storage Adaptor
S:  SerialNumber=0B02011C0420E34C
C:* #Ifs= 1 Cfg#= 2 Atr=c0 MxPwr= 98mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=125us
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=83(I) Atr=03(Int.) MxPS=   2 Ivl=32ms

cat /proc/scsi/usb-storage-0/1

Code:

   Host scsi1: usb-storage
       Vendor: DMI
      Product: USB 2.0 Storage Adaptor
Serial Number: 0B02011C0420E34C
     Protocol: Transparent SCSI
    Transport: Bulk
         GUID: 0c0bb0010b02011c0420e34c
     Attached: Yes

cat /proc/scsi/scsi

Code:

Attached devices:
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: QUANTUM  Model: FIREBALL ST2     Rev: A0F.
  Type:   Direct-Access                    ANSI SCSI revision: 02

Computer spec:

Code:

mb       -> MSI KT3 Ultra2-R  (via kt333 chipset)
cpu      -> AMD 1800+
USB      -> VIA (VT8235)    (is a usb 2.0 chipset)
OS       -> Gentoo 1.4
Kernel   -> 2.4.20 (gaming-source-r5)

MonkeyBumps · 08-31-2003, 05:56 PM

is there a patch for 2.4.20 kernel that will fix this? where would i look to see if there was a patch? thanks again.

MonkeyBumps · 09-01-2003, 10:35 AM

anyone???

Brian1 · 09-01-2003, 11:14 AM

Are you running the Redhat 9 distro?

If so try this:

Boot up system without the USB drives attached. Go into a terminal screen and enter this command ' service kudzu stop ' press enter. Now plug in your USB drive that is vfat. Default Redhat 9 or any update from them or Synaptic does not have NTFS support in the kernel.

Make sure you have a valid mount point /mnt/usb_drive
' mount /dev/sda1 /mnt/usb_drive '
Does it lock up?

If all works fine then you and issue ' chkconfig --level 345 kudzu off ' to turn off kudzu from startup.

If it does lock up try this: (This may corrupt your system make sure you have a backup or don't mind to reinstall)
Disable kudzu from startup ' chkconfig --level 345 kudzu off ' . Kudzu does not work with the latest hotplug.
Download the latest HotPlug from http://sourceforge.net/project/showf...group_id=17679

Get these two files
http://prdownloads.sourceforge.net/l...h.rpm?download
http://prdownloads.sourceforge.net/l...h.rpm?download

Install from a terminal screen ' rpm -Uvh hotplug*.rpm
Reboot leaving the drives off again. plug the vfat drive in and try mounting it.

Let me know how this works for you.

For ntfs support you will need to recompile the kernel I would do the following. I would download the kernel-2.4.21 and patch to patch-2.4.22-rc2. Kernel 2.4.22 has some bugs in it. Then copy your config-2.4.20-8 from /boot to /usr/src/linux-2.4. Load this config file in your ' make xconfig ' , then go under filesystems and click y for ntfs read, and ' save and exit '. Compile and add to your grub file.

Hope this helps.
Brian

MonkeyBumps · 09-01-2003, 10:11 PM

thanks for the help but i'm running Gentoo 1.4 with kernel 2.4.20 . I dont have kudzu running, but perhaps your onto something about the version of hotplug i'm running? also i have been looking into the idea that perhaps its the device and the way it "wants" to do the handshake.... if it were this then it would need to be added to the devices in the unusable_dev.h. in fact i have tried this idea of adding to the unusual devices, but have not had any luck so far. back to the idea of the hotplug version... are there patches for this and how would one find out what version of hotplug they are using?

do you know where one would look to see if linux supports a certain usb drive? i have done some searching but have not had anyluck... the drive is a "WDC WD80" thats a USB2.0 device. the strange thing is that it seems to id it fine when i first plug it in, but it then hangs aafter a random amount of time... the longest being about 30-45sec.

if you have anyother ideas please let me know... i would really like to get this thing working.

ps, i have turned on "long wait for slow devices" under the usb support and i also i have ntfs support compiled in.

thanks for your help
mb

faheyd · 09-02-2003, 01:49 AM

MB,
1. Never got an answer if you tried pluggin the vfat drive directly into the motherboard usb2 port.
2. Darn, I wish I knew about gentoo, but I don't.
3. I have the VT8235 chipset and am using the 2.4.21 kernel, and this how my /var/log/messages show the boot:

Aug 29 00:41:01 localhost kernel: usb.c: registered new driver usbdevfs
Aug 29 00:41:01 localhost kernel: usb.c: registered new driver hub
Aug 29 00:41:01 localhost kernel: usb-uhci.c: $Revision: 1.275 $ time 15:05:31 Mar 14 2003
Aug 29 00:41:01 localhost kernel: usb-uhci.c: High bandwidth mode enabled
Aug 29 00:41:01 localhost kernel: usb-uhci.c: USB UHCI at I/O 0xdc00, IRQ 21
Aug 29 00:41:01 localhost kernel: usb-uhci.c: Detected 2 ports
Aug 29 00:41:01 localhost kernel: usb.c: new USB bus registered, assigned bus number 1
Aug 29 00:41:01 localhost kernel: hub.c: USB hub found
Aug 29 00:41:01 localhost kernel: hub.c: 2 ports detected
Aug 29 00:41:01 localhost kernel: usb-uhci.c: USB UHCI at I/O 0xe000, IRQ 21
Aug 29 00:41:01 localhost kernel: usb-uhci.c: Detected 2 ports
Aug 29 00:41:01 localhost kernel: usb.c: new USB bus registered, assigned bus number 2
Aug 29 00:41:01 localhost kernel: hub.c: USB hub found
Aug 29 00:41:01 localhost kernel: hub.c: 2 ports detected
Aug 29 00:41:01 localhost kernel: usb-uhci.c: USB UHCI at I/O 0xe400, IRQ 21
Aug 29 00:41:01 localhost kernel: usb-uhci.c: Detected 2 ports
Aug 29 00:41:01 localhost kernel: usb.c: new USB bus registered, assigned bus number 3
Aug 29 00:41:01 localhost kernel: hub.c: USB hub found
Aug 29 00:41:01 localhost kernel: hub.c: 2 ports detected
Aug 29 00:41:01 localhost kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
Aug 29 00:41:01 localhost kernel: usb.c: USB device 4 (vend/prod 0x5dc/0x200) is not claimed by any active driver.
Aug 29 00:41:01 localhost kernel: SCSI subsystem driver Revision: 1.00
Aug 29 00:41:01 localhost kernel: Initializing USB Mass Storage driver...
Aug 29 00:41:01 localhost kernel: usb.c: registered new driver usb-storage
Aug 29 00:41:01 localhost kernel: usb-uhci.c: interrupt, status 2, frame# 1471
Aug 29 00:41:01 localhost kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Aug 29 00:41:01 localhost kernel: Vendor: LEXAR Model: JUMPDRIVE PRO Rev: 0
Aug 29 00:41:01 localhost kernel: Type: Direct-Access ANSI SCSI revision: 02
Aug 29 00:41:01 localhost kernel: USB Mass Storage support registered.
Aug 29 00:41:01 localhost kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Aug 29 00:41:01 localhost kernel: SCSI device sda: 503808 512-byte hdwr sectors (258 MB)
Aug 29 00:41:01 localhost kernel: sda: Write Protect is off
Aug 29 00:41:01 localhost kernel: /dev/scsi/host0/bus0/target0/lun0: p1 p2

I would say that (another wild ass guess), that something didn't get detected/configured correctly on the kernel build, I am really confused that the via site says it's a ehci, but my boot above is uhci, strange! If you try all the suggestions and nothing helps, upgrading the kernel is always a safe bet, although a large leap if you haven't done it before, but there are plenty of HOWTO's to make that safe for ya.
I wish I had better news, but I don't see any reason 'why' your hard drive is not working.

faheyd · 09-02-2003, 01:53 AM

Could this be a 'related' problem??? Hardware, ie disconnects?
http://www.qbik.ch/usb/devices/showdev.php?id=2078

faheyd · 09-02-2003, 02:10 AM

And last but not least, try only plugging in the USB devices you need, unplug un-needed ones, try borrowing a PS2 keyboard and mouse, and then try pluggin in 'only' the USB vfat drive. You may have unreliable usb hardware (or too many usb devices), and that may be affecting the usb BUS, thus causing the loss of connectivity with the drive.

That's all I can think of.

MonkeyBumps · 09-02-2003, 08:53 AM

Faheyd,
i tried what that link said and it didnt work =(
yes i have tried plugging in just the vfat drive, but it too hangs the system. I'm starting to think that the usb2.0 support for harddisks is not so good in the 2.4.20 build. I'm going to try installing the 2.6 kernel, perhaps that will fix my problems
(or just cause other ones.... like nvidia drivers).

wish me luck.

thanks for all the help and i will post my result of the kernel upgrade.

mb

faheyd · 09-02-2003, 01:55 PM

Good Luck!!! and yes, please post whether the kernel upgrade fixed it, as that will help the 'next' person that has the same problem. Ouch on the NV drivers, you should have no problem with them....(cross our fingers).