059f:104b LaCie USB 3.0 External HDD fails to detect

[Lixin Chin]

Ubuntu 11.04, kernel version 2.6.38-10-generic. 64-bit arch.

Drive is a Lacie 1TB USB3.0 / Firewire 800 2.5" external harddrive:
http://www.lacie.com/au/products/product.htm?id=10553

Plugging the drive into the usb3 port just results in xhci_hcd errors, and the drive is never properly detected.

/dev/sd* doesn't show the drive, or any partitions.

I tried plugging the same drive into my usb 2 port and a similar issue occurs. A slew of errors in dmesg, and the partition table isn't detected properly.

When I tried it on the same computer under Windows 7 everything worked, so the hardware would appear to be functioning.

WORKAROUND: Add:
blacklist uas

to:
/etc/modprobe.d/blacklist-usb.conf

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-10-generic 2.6.38-10.46
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd6600000 irq 52'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,104313d3,00100004'
   Controls : 12
   Simple ctrls : 8
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xd0040000 irq 53'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Thu Aug 18 10:31:39 2011
HibernationDevice: RESUME=UUID=a1004e3d-fe83-40ad-afb1-5f58dd605e06
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: ASUSTeK Computer Inc. N61Ja
ProcEnviron:
 LANGUAGE=
 LANG=en_AU.UTF-8
 SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic root=UUID=4337590f-82ea-4029-9342-00d9074286c4 ro splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-10-generic N/A
 linux-backports-modules-2.6.38-10-generic N/A
 linux-firmware 1.52
SourcePackage: linux
UpgradeStatus: Upgraded to natty on 2011-05-11 (98 days ago)
dmi.bios.date: 01/08/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N61Ja.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N61Ja
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN61Ja.206:bd01/08/2010:svnASUSTeKComputerInc.:pnN61Ja:pvr1.0:rvnASUSTeKComputerInc.:rnN61Ja:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: N61Ja
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Lixin Chin (wstfgl)]

Attaching dmesg output.

[Lixin Chin (wstfgl)]

Oops, previous dmesg missed a few lines from the scsi driver which are output a few seconds after the xhci_hcd failures.

[Lixin Chin (wstfgl)]

Attached the dmesg output when plugging the same drive into a usb2.0 port on the same computer.

Although it says its attached the disk to sdb,

sudo fdisk -l /dev/sdb

just returns with no output.

[Lixin Chin (wstfgl)]

It appears to be related to this:
https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=717633

error in Fedora 15, and to this:
http://ubuntuforums.org/showthread.php?p=11142776

posting on the ubuntu forums.

[Lixin Chin (wstfgl)]

Confirming that the bug still exists in the latest Ubuntu kernel, 2.6.38-11-generic (64-bit).

[Lixin Chin (wstfgl)]

Another search of the ubuntu forums turned up this user who seems to have the identical problem with the same model of HDD:
http://ubuntuforums.org/showthread.php?t=1815922

[Lixin Chin (wstfgl)]

Tested in oneiric 11.10, and the bug is still present.

[Lixin Chin (wstfgl)]

Tested in oneiric 11.10 with linux-image-3.0.0-13-generic and the bug is still present.

[Lixin Chin (wstfgl)]

sudo fdisk -l; echo; sudo parted -l;

----------------------------------------------------------

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x76692ca8

   Device Boot Start End Blocks Id System
/dev/sda1 2048 30716279 15357116 1c Hidden W95 FAT32 (LBA)
/dev/sda2 * 30717952 135575551 52428800 7 HPFS/NTFS/exFAT
/dev/sda3 135588600 240428789 52420095 83 Linux
/dev/sda4 240428790 976768064 368169637+ 5 Extended
/dev/sda5 240429056 964202495 361886720 7 HPFS/NTFS/exFAT
/dev/sda6 964205298 976768064 6281383+ 82 Linux swap / Solaris

Model: ATA ST9500325AS (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
 1 1049kB 15.7GB 15.7GB primary fat32 hidden, lba
 2 15.7GB 69.4GB 53.7GB primary ntfs boot
 3 69.4GB 123GB 53.7GB primary ext4
 4 123GB 500GB 377GB extended
 5 123GB 494GB 371GB logical ntfs
 6 494GB 500GB 6432MB logical linux-swap(v1)

----------------------------------------------------------

So the drive isn't detectable via fdisk or parted.

[Martin Backhaus (salemaleikum)]

The drive is not completely detected on my laptop, too.
Ubuntu 11.10, Kernel 3.0.0-13-generic, 32bit
With the "Disk Utility 3.0.2" Tool I am able to discover the drive, but I get error messages, whenever I try to format it:

Error formatting drive
An error occurred while performing an operation on "Hard Disk" (LaCie Rugged FW USB3): The operation failed
Details: Error creating partition table: helper exited with exit code 1: cannot open /dev/sdb: No such device or address.

I can open the drive with Windows 7 (it automatically mounts).
The application "Start.exe" on the drive can reformat the drive with a FAT and NTFS partition, where the FAT partition is labeled with "Linux". I will try this later, so a workaround could be to reformat the drive within Windows.

[Martin Backhaus (salemaleikum)]

No, after reformatting the drive with Windows it is not recognized at all.

[Martin Backhaus (salemaleikum)]

Putting "blacklist uas" into the file /etc/modprobe.d/blacklist.conf solved the problem for now...

[Lixin Chin (wstfgl)]

I can confirm that adding the line "blacklist uas" into /etc/modprobe.d/blacklist.conf (or /etc/modprobe.d/blacklist-usb.conf in my case) solves the bug.

The harddrive seems to work perfectly over USB3.0 once this is done, even without adding a FAT32 partition.

Oddly in kubuntu, plugging in the drive doesn't pop up the mount drive dialog box as usual, although the partitions still appear in dolphin and can be mounted and unmounted from there as usual.

[Nan (4-null-nan)]

Adding the above line (blacklist uas) to either files didn't solve my problem.

Linux vy-MXG071 2.6.38-13-generic #55-Ubuntu SMP Tue Jan 24 15:34:24 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Please see the attached log.

The drive case is:

Rocketfish Rf-hd3025 USB 3.0 2.5" Sata Hard Drive Enclosure

The internal real hard drive is Intel 320 SSD 160 GB.

Intel® SSD 320 Series (160GB, 2.5in SATA 3Gb/s, 25nm, MLC)

This drive works okay inside Linux as internal hard drive. Also works in Windows 7, NTFS formatted.

[Nan (4-null-nan)]

Also tested on both USB 2.0 and USB 3.0, and both failed. Disk utility see the drive, but cannot format. gparted doesn't see the drive at all.

[Nan (4-null-nan)]

After adding the blacklist uas and restarted, I also did this:

 sudo rmmod uas

I then plug it in, and a dialog popped on on Ubuntu saying cannot mount the device. However, I can see it in the Disk Utility.
I try to mount there with a same error. However, after I reformat the drive, and then create a partition, formatted as NTFS, and it now works.

[Henning Mortensen (k-henning)]

After adding the blacklist uas and restarted it works: It has confused me a bit that it took 10-20 seconds before the drive (Lacie Rugged USB 3.0) was actually recognized. So first I thought it had not worked, (did not show up in "df") . But suddenly Nautilus blinked, and there it was! Then also shown by "df". Also a problem with "lsusb" hanging after removal of the drive (only a problem in USB 3.0 ports) disappeared after the "blacklisting".

[penalvch (penalvch)]

Lixin Chin, thank you for reporting this bug and helping make Ubuntu better. Could you please attach all relevant information noted in: https://wiki.ubuntu.com/DebuggingHardwareDetection ?

[Lixin Chin (wstfgl)]

Attached files *with* uas blacklisted:

[Lixin Chin (wstfgl)]

Attached files *with* uas blacklisted:

[Lixin Chin (wstfgl)]

dmesg.log *without* blacklisting uas (only dmesg and lspci outputs differ in this case)

[Lixin Chin (wstfgl)]

lspci-vvnn.log *without* blacklisting uas (only dmesg and lspci outputs differ in this case)

[penalvch (penalvch)]

Lixin Chin, if you could also please temporarily remove the workaround and test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Lixin Chin (wstfgl)]

Tested using the v3.3-rc7-precise kernel image from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc7-precise/

And it works!

The uas module is unblacklisted:

> etc/modprobe.d% grep -r uas *
blacklist-usb.conf:# blacklist uas

But it doesn't load anyway:
> lsmod | grep uas
[1] 2704 done lsmod |
       2705 exit 1 grep --color=auto uas

(/proc/version_signature doesn't seem to exist with this kernel version,
so that's been left off the attachments).

[Lixin Chin (wstfgl)]

And with the 2012-03-25 mainline kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/

It likewise works, and doesn't load the uas module:

> lsmod | grep -i uas
[1] 2717 done lsmod |
       2718 exit 1 grep --color=auto -i uas

Once again, no /proc/version_signature.

[penalvch (penalvch)]

Marking Triaged as mainline tested.

[Po-Hsu Lin (cypressyew)]

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!