LaCie Biggest F800GB USB2 drive won't connect to RHEL4 kernel 2.6.9
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)
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 Reading the web, looks like other people are having similar problems. Does anyone have a solution? Or perhaps a suggestion? Wes |
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. |
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 |
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:
Any suggestions from here? |
Further diagnostics
Here is the output from lsmod:
Code:
# lsmod Here is the output from lspci: Code:
# lspci Code:
# lsusb |
When I powercycled my LaCie drive, this was because it wasn't being recognized as a usb drive. I think that yours is.
Quote:
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" |
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? |
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! |
Quote:
|
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?
|
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. |
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 |
So you are removing the ehci_hcd module, eh?
I'll try that. What lead you to give that a try? W. |
same problem here:
http://www.linuxquestions.org/questi...09#post2906709 |
All times are GMT -5. The time now is 06:32 AM. |