LaCie Biggest F800GB USB2 drive won't connect to RHEL4 kernel 2.6.9

wmodes · 04-03-2007, 04:59 PM

Apparently, this is not an uncommon problem, though I haven't seen either the exact problem or a solution to it. Half of the threads in this forum are problems with USB LaCie drives. I'd use it for a boat anchor, except that a client has important data they like to shuttle back and forth on this thing.

I have a LaCie Biggest F800GB USB2 drive that won't connect to a PowerEdge 2650 running RHEL Linux 4 Release 4 (kernel 2.6.9-42.ELsmp)

USB drivers and hotplug are working -- I can connect other models of USB drive successfully to this machine
The drive itself is functional -- this LaCie drive connects successfully to a Mac OSX machine
Happens on other 2.6.9 machines -- This problem with this drive occurs on any of our servers running the same kernal

Other USB drives connect successfully to this machine. And I've connected the LaCie drive successfully to other machines.

Here are the log messages I get:

Code:

Apr  3 13:52:19 beast kernel: usb 1-3: new high speed USB device using address 14
Apr  3 13:52:24 beast kernel: usb 1-3: control timeout on ep0in
Apr  3 13:52:24 beast kernel: usb 1-3: device not accepting address 14, error -71
Apr  3 13:52:24 beast kernel: usb 1-3: new high speed USB device using address 15
Apr  3 13:52:29 beast kernel: usb 1-3: control timeout on ep0in
Apr  3 13:52:30 beast kernel: usb 1-3: device not accepting address 15, error -71

Seems the LaCie disc is not accepting the interrupt it is given.

Reading the web, looks like other people are having similar problems. Does anyone have a solution? Or perhaps a suggestion?

Wes

jschiwal · 04-03-2007, 06:10 PM

I had a problem at first with a 500GB LaCie external USB drive. It was being recognised as a TI Boot Device, whatever that is. This was happening in both windows and Linux. I power cycled the unit a few times and it kicked in.

Another problem was that mounting the drive would time out. I don't remember where I found it, but I found a config item, that allowed me to increase the time before the mount command times out. You are using a different distro so yours may be in a different place. You might try grep'ing the files in /etc/sysconfig.

Walman · 04-04-2007, 08:00 AM

Guys

I had a problem before connecting a Lacie USB Big_Disk to an IBM x336 under RHEL 3 , I noticed that it required usb-storage module installed , once that was done it did recognized it even that the LaCie is NTFSformatted disk.

Regards

wmodes · 04-04-2007, 04:07 PM

Okay, did this:

% modprobe usb-storage

but I think it was already installed.

I cycled the power on the drive (rather than what I'd been doing which was plugging and unplugging the cable).

Here's what I got:

Code:

  	
Apr  4 11:17:04 beast smbd[30821]: [2007/04/04 11:17:04, 0] lib/util_sock.c:read_socket_data(384)
Apr  4 11:17:04 beast smbd[30821]:   read_socket_data: recv failure for 4. Error = Connection reset by pee
r
Apr  4 12:16:06 beast kernel: usb 3-1: new full speed USB device using address 4
Apr  4 12:16:06 beast kernel: usb 3-1: device not accepting address 4, error -71
Apr  4 12:16:10 beast kernel: usb 1-3: new high speed USB device using address 23
Apr  4 12:16:10 beast kernel: scsi8 : SCSI emulation for USB Mass Storage devices
Apr  4 12:16:10 beast kernel:   Vendor: LaCie     Model: Biggest F800      Rev: 1.32
Apr  4 12:16:10 beast kernel:   Type:   Direct-Access                      ANSI SCSI revision: 02
Apr  4 12:16:10 beast kernel: SCSI device sde: 976790016 512-byte hdwr sectors (500116 MB)
Apr  4 12:16:10 beast kernel: sde: assuming drive cache: write through
Apr  4 12:16:10 beast kernel: SCSI device sde: 976790016 512-byte hdwr sectors (500116 MB)
Apr  4 12:16:10 beast kernel: sde: assuming drive cache: write through
Apr  4 12:16:10 beast kernel:  sde: [mac] sde1 sde2 sde3 sde4
Apr  4 12:16:10 beast kernel: Attached scsi disk sde at scsi8, channel 0, id 0, lun 0
Apr  4 12:16:10 beast kernel: Attached scsi generic sg7 at scsi8, channel 0, id 0, lun 0,  type 0
Apr  4 12:16:11 beast scsi.agent[30924]: disk at /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host8/t
arget8:0:0/8:0:0:0
Apr  4 12:17:24 beast kernel: usb 1-3: reset high speed USB device using address 23
Apr  4 12:17:29 beast kernel: usb 1-3: control timeout on ep0in
Apr  4 12:17:29 beast kernel: usb 1-3: device not accepting address 23, error -71
Apr  4 12:17:29 beast kernel: usb-storage: Bus reset ended with -19
Apr  4 12:17:29 beast kernel: usb 1-3: USB disconnect, address 23
Apr  4 12:17:29 beast kernel: scsi: Device offlined - not ready after error recovery: host 8 channel 0 id
0 lun 0
Apr  4 12:17:29 beast kernel: sd 8:0:0:0: Illegal state transition cancel->offline
Apr  4 12:17:29 beast kernel: Badness in scsi_device_set_state at drivers/scsi/scsi_lib.c:1702
Apr  4 12:17:29 beast kernel:  [<f88426d9>] scsi_device_set_state+0xd2/0xdd [scsi_mod]
Apr  4 12:17:29 beast kernel:  [<f8840903>] scsi_eh_offline_sdevs+0x49/0x5e [scsi_mod]
Apr  4 12:17:29 beast kernel:  [<f8840de9>] scsi_unjam_host+0x15a/0x16b [scsi_mod]
Apr  4 12:17:29 beast kernel:  [<f8840f0c>] scsi_error_handler+0x112/0x15a [scsi_mod]
Apr  4 12:17:29 beast kernel:  [<f8840dfa>] scsi_error_handler+0x0/0x15a [scsi_mod]
Apr  4 12:17:29 beast kernel:  [<c01041f5>] kernel_thread_helper+0x5/0xb
Apr  4 12:17:29 beast kernel: SCSI error : <8 0 0 0> return code = 0x10000
Apr  4 12:17:29 beast hald[4694]: Timed out waiting for hotplug event 633. Rebasing to 633
Apr  4 12:17:29 beast kernel: usb 1-3: new high speed USB device using address 24
Apr  4 12:17:34 beast kernel: usb 1-3: control timeout on ep0in
Apr  4 12:17:35 beast kernel: usb 1-3: device not accepting address 24, error -71
Apr  4 12:17:35 beast kernel: usb 1-3: new high speed USB device using address 25
Apr  4 12:17:40 beast kernel: usb 1-3: control timeout on ep0in
Apr  4 12:17:41 beast kernel: usb 1-3: device not accepting address 25, error -71

And that's good, as it looks like for the first time, the drive is recognized. It looks like it was on the way to being assigned a device. But then I got a whole bunch of stuff that is beyond my kin. control timeout? bus reset? device offlined? illegal state transition? Then a whole bunch of messages from scsi_mod.

Any suggestions from here?

wmodes · 04-04-2007, 04:51 PM

Here is the output from lsmod:

Code:

# lsmod
Module                  Size  Used by
vfat                   16961  0 
fat                    44001  1 vfat
ohci_hcd               23889  0 
usb_storage            62217  0 
nfsd                  213889  17 
exportfs               10049  1 nfsd
nfs_acl                 7745  1 nfsd
parport_pc             27905  0 
lp                     15405  0 
parport                37641  2 parport_pc,lp
autofs4                22725  0 
i2c_dev                14273  0 
i2c_core               25921  1 i2c_dev
lockd                  65257  2 nfsd
sunrpc                143397  12 nfsd,nfs_acl,lockd
ip_conntrack_amanda    73441  0 
ip_conntrack           45573  1 ip_conntrack_amanda
button                 10449  0 
battery                12869  0 
ac                      8773  0 
md5                     8001  1 
ipv6                  241761  28 
joydev                 14209  0 
uhci_hcd               32729  0 
ehci_hcd               32069  0 
hw_random               9557  0 
bnx2                  141605  0 
floppy                 58065  0 
ata_piix               15557  0 
libata                 67613  1 ata_piix
st                     40157  0 
sg                     38113  0 
dm_snapshot            21093  0 
dm_zero                 6337  0 
dm_mirror              31645  0 
ext3                  118729  2 
jbd                    59609  1 ext3
raid1                  19649  1 
dm_mod                 60357  8 dm_snapshot,dm_zero,dm_mirror
megaraid_mbox          37329  1 
megaraid_mm            17905  1 megaraid_mbox
mptscsih                5569  0 
mptsas                 13389  3 mptscsih
mptspi                 13261  1 mptscsih
mptfc                  12617  1 mptscsih
mptscsi                44125  3 mptsas,mptspi,mptfc
mptbase                61345  4 mptsas,mptspi,mptfc,mptscsi
aic79xx               187613  0 
sd_mod                 20545  6 
scsi_mod              117709  11 usb_storage,libata,st,sg,megaraid_mbox,mptsas,mptspi,mptfc,mptscsi,aic79xx,sd_mod

Here is the output from lspci:

Code:

# lspci
00:00.0 Host bridge: Intel Corporation 5000X Chipset Memory Controller Hub (rev 12)
00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 (rev 12)
00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev 12)
00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev 12)
00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 (rev 12)
00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 6-7 (rev 12)
00:07.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 (rev 12)
00:10.0 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 12)
00:10.1 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 12)
00:10.2 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 12)
00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 12)
00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 12)
00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 12)
00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 12)
00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09)
00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09)
00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09)
00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09)
00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)
00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09)
00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA Storage Controller IDE (rev 09)
01:00.0 PCI bridge: Intel Corporation 6702PXH PCI Express-to-PCI Bridge A (rev 09)
02:08.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068 PCI-X Fusion-MPT SAS (rev 01)
03:00.0 PCI bridge: Broadcom: Unknown device 0103 (rev c2)
04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11)
05:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01)
05:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01)
06:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01)
06:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01)
07:00.0 PCI bridge: Broadcom: Unknown device 0103 (rev c2)
08:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11)
0b:00.0 PCI bridge: Intel Corporation 80332 [Dobson] I/O processor (A-Segment Bridge) (rev 07)
0b:00.2 PCI bridge: Intel Corporation 80332 [Dobson] I/O processor (B-Segment Bridge) (rev 07)
0c:0e.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID (rev 07)
0f:00.0 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge A (rev 09)
0f:00.2 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge B (rev 09)
10:03.0 SCSI storage controller: Adaptec ASC-39320A U320 (rev 10)
10:03.1 SCSI storage controller: Adaptec ASC-39320A U320 (rev 10)
13:0d.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)

And finally, here is the output from lsusb

Code:

# lsusb
Bus 004 Device 001: ID 0000:0000  
Bus 003 Device 002: ID 09eb:0131 IM Networks, Inc. 
Bus 003 Device 001: ID 0000:0000  
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 003: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 "TetraHub"
Bus 001 Device 001: ID 0000:0000

jschiwal · 04-05-2007, 03:10 AM

When I powercycled my LaCie drive, this was because it wasn't being recognized as a usb drive. I think that yours is.

Quote:

Apr 4 12:17:29 beast hald[4694]: Timed out waiting for hotplug event 633. Rebasing to 633

This looks to me what the problem is. Look in the hotplug or had configuration for a timeout item.
There may be a timeout value in one of the UDEV rules such as for scsi devices. You might want to grep for 'ATTR{timeout}' in the rules. But something tells me that isn't the right place to look. I think that looking at hotplug would be more fruitful. Is the partition detected, but you just can't mount it?

Is the automounter used to mount it. There is an /etc/auto.master file that can contain a --timeout=<value> attribute at the end. This will be for items in the /etc/fstab file that use autofs, I believe. It the entries are commented out, then this is a dead end.

You could try running "udevmonitor" before inserting the device to see which rules are run. Also, see if you have a halmount program. If so you could try mounting it that way and see if any error messages are posted.
However, my system doesn't use hotplug for mounting external drives, so your system may not use halmount.

I did look on my system for the item I changed, but I couldn't find it. Sorry.
Comparing the udev rules for my laptop and desktop, the timeout values were the same, so that wasn't it:

Code:

/etc/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="scsi", ACTION=="add", ATTR{type}=="0|7|14", ATTR{timeout}="60"
/etc/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="scsi", ACTION=="add", ATTR{type}=="1", ATTR{timeout}="900"

wmodes · 04-05-2007, 11:10 AM

It seems not to be a mounting issue, but an issue with the USB device, driver, or system.

While dmesgs says that it is assigning device /dev/sde to the drive, and then bails on it. Afterward, there is no device node /dev/sde. Nor does fdisk -l see the drive or any partitions. So it is not merely an issue of trying to mount it. I suspect it will be easy at that point.

While it might be a timeout issue, my intuition is that it will be in the USB or hotplug system rather than the mount system.

While there is a laborious workaround for this for me (involving mounting the drive to a OSX server and transferring nearly 1TB over the LAN), I'd like to solve this problem so I can mount the drive directly.

Anyone else have any suggestions or encountered a similar problem?

jschiwal · 04-05-2007, 08:34 PM

Are you connecting a drive through a hub? Can you connect it directly. If it is connected to a usb port on a keyboard for example, there may be power problem. On a MAC at work, I can't connect a pen drive to the usb port on the keyboard. The keyboard is a USB keyboard and contains a hub to give another USB port. However, it isn't a powered hub and the USB port that the keyboard is plugged into can't power both.

If you run konqueror and enter "sysinfo:/" does the drive show up? When you had powercycled the drive, it did detect four partitions.

Also, what is with the host bridge chipset errors in the same message log?

Good Luck!

r00tb33r · 04-05-2007, 09:05 PM

Quote:

Originally Posted by jschiwal

Are you connecting a drive through a hub? Can you connect it directly. If it is connected to a usb port on a keyboard for example, there may be power problem. On a MAC at work, I can't connect a pen drive to the usb port on the keyboard. The keyboard is a USB keyboard and contains a hub to give another USB port. However, it isn't a powered hub and the USB port that the keyboard is plugged into can't power both.

If you run konqueror and enter "sysinfo:/" does the drive show up? When you had powercycled the drive, it did detect four partitions.

Also, what is with the host bridge chipset errors in the same message log?

Good Luck!

Actually some USB interfaces indeed cannot provide much power, in this case a powered USB hub is a good thing to try to disqualify power as a variable.

jschiwal · 04-05-2007, 10:40 PM

OK, I was wondering if you were on an unpowered hub such as a keyboard. Connecting to another USB port on the computer itself might still be worth a shot. What is the IM Networks device on USB Bus 3 Device 2. Could there be a problem with both devices (LaCie on 3-01) off the same hub?

wmodes · 04-09-2007, 03:45 PM

This is one of the burliest drives that LaCie sells, nearly 1 terabyte of RAID storage connected to an enterprise-class Dell server. It is powered, connected directly to a USB port on a card plugged directly into the backplane of the server, and I've tried almost every USB port the server has.

At this point, are we grasping at straws? I was hoping, looking at the logs and such, that someone might have experience that might suggest what might be happening here.

I guess, given that I have struggled with this for a little over a week, I will have to go with the unattractive choice of connecting this device to an OSX Mac and transferring a TB of data over the local LAN.

Still though, it will come up in the future, so if anyone has any suggestions, please lay them on me.

bigboss · 05-08-2007, 04:14 AM

I had a problem with a Lacie 500gb usb 2.0 external hard drive designed by porsche

messages like Timed out waiting for hotplug event 353. Rebasing to 354

and device finally not detected

i solved the problem only executing this:

modprobe -r ehci_hcd

the disk mount without problems now perhaps it can help to solve your problem

wmodes · 05-08-2007, 12:07 PM

So you are removing the ehci_hcd module, eh?

I'll try that. What lead you to give that a try?

W.

cheesus · 09-28-2007, 12:14 PM

same problem here:
http://www.linuxquestions.org/questi...09#post2906709