Detection of Lacie USB2 harddrive fails

[pointwood]

I have debugged this based on the guide found here:
https://wiki.ubuntu.com/DebuggingRemovableDevices

Martin Pitt stated that I got a "pretty low-level problem" and asked me to file
this to a bug report here:

=== Cut ===
[4295495.033000] usb 5-2.3: new high speed USB device using ehci_hcd and address 11
> [4295495.090000] scsi0 : SCSI emulation for USB Mass Storage devices
> [4295495.091000] usb-storage: device found at 11
> [4295495.091000] usb-storage: waiting for device to settle before scanning
> [4295500.091000] Vendor: WDC WD25 Model: 00JB-00EVA0 Rev: 15.0
> [4295500.091000] Type: Direct-Access ANSI SCSI
revision: 04
> [4295576.127000] usb 5-2.3: reset high speed USB device using ehci_hcd and
address 11
> [4295579.160000] usb 5-2.3: device descriptor read/64, error -110
> [4295594.294000] usb 5-2.3: device descriptor read/64, error -110
> [4295594.428000] usb 5-2.3: reset high speed USB device using ehci_hcd and
address 11
> [4295597.461000] usb 5-2.3: device descriptor read/64, error -110
=== Cut ===

The drive has 2 partitions: a NTFS partition and a FAT32 partition. I have of
course kept all the debugging info in case more is needed.

[Matt Zimmerman (mdz)]

Try some of the suggestions at https://wiki.ubuntu.com/DebuggingIRQProblems and
attach complete dmesg output

[pointwood (jramskov)]

Created an attachment (id=4437)
Full dmesg log

[Sean Fitzgibbon (sean-fitzgibbon)]

Created an attachment (id=4812)
output of dmesg on amd64

[Sean Fitzgibbon (sean-fitzgibbon)]

Created an attachment (id=4813)
output of dmesg on i386

Sorry about lack of comment on my last attachment but this is my first time
using bugzilla.

I have a similar proble with a lacie bigger disk (F800) on my AMD64
(2.6.12-9-amd64-k8-smp) breezy box.

When I connect via USB2 I get the error messages in dmesg in my previous
attachment.

I have also tried an x86 live cd of Breezy (ubuntu 2.6.12-9-386) with the same
errors (this attachment).

At first I thought I had a broken disk but it works fine under windows xp and
knoppix 3.9 (Knoppix 2.6.11 #2 SMP). It seems unusal to me that it works with a
2.6.11 kernel and not 2.6.12???

[Ben Collins (ben-collins)]

If possible, please upgrade to Dapper's 2.6.15-7 kernel. If you do not want to
upgrade to Dapper, then you can also wait for the Dapper Flight 2 CD's, which
are due out within the next few days.

Let me know if this bug still exists with this kernel.

[pointwood (jramskov)]

(In reply to comment #5)
> If possible, please upgrade to Dapper's 2.6.15-7 kernel. If you do not want to
> upgrade to Dapper, then you can also wait for the Dapper Flight 2 CD's, which
> are due out within the next few days.
>
> Let me know if this bug still exists with this kernel.

I've just tested with the Dapper Flight 2 live CD and it looks like the bug
still exists.

I've added dmesg and lspci logs.

[pointwood (jramskov)]

Created an attachment (id=5581)
dapper flight 2 dmesg output

[pointwood (jramskov)]

Created an attachment (id=5582)
dapper flight 2 lspci output

[Ben Collins (ben-collins)]

(In reply to comment #6)
> (In reply to comment #5)
> > If possible, please upgrade to Dapper's 2.6.15-7 kernel. If you do not want to
> > upgrade to Dapper, then you can also wait for the Dapper Flight 2 CD's, which
> > are due out within the next few days.
> >
> > Let me know if this bug still exists with this kernel.
>
> I've just tested with the Dapper Flight 2 live CD and it looks like the bug
> still exists.

Dapper is showing a completely different problem for you (oopses)

Try disabling the ehci_hcd by doing:

echo blacklist ehci_hcd > /etc/modprobe.d/blacklist.ehci
update-initramfs -u

Then reboot. The drive will be slower, but it should work.

[pointwood (jramskov)]

Hrm...will that work when I'm using the live CD?

[Ben Collins (ben-collins)]

(In reply to comment #10)
> Hrm...will that work when I'm using the live CD?

No, it will only work for installed system.

[pointwood (jramskov)]

I thought so :(

I'm not sure I want to upgrade my install to dapper since it is my only system,
I would like to keep it in a resonable working stage :)

OTOH, I might get an second older machine soon which I might be able to test it on.

[Kent Tenney (ktenney)]

I've found that removing the jumper from the drive (MA, SL, CS)
corrects the problem

This is confirmed on 3 drives which failed with the jumper in
any position, and succeeded with the jumper removed.

Thanks,
Kent

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Martin Kalén (martin-kalen)]

For the record; I can confirm that the solution posted by Kent Tenney also works for me in Hardy Heron 8.04.

I have a generic no-name external USB case for ATA drives.

When trying to mount an IBM DeskStar 40GB disk (IC35L040 AVER07-0) I first got the following messages in /var/log/messages:

 [ 1155.095613] usb 3-1.3: new high speed USB device using ehci_hcd and address 11
 [ 1155.216151] usb 3-1.3: configuration #1 chosen from 1 choice
 [ 1155.229398] scsi4 : SCSI emulation for USB Mass Storage devices
 [ 1165.750265] scsi 4:0:0:0: Device offlined - not ready after error recovery
 [ 1165.750989] usb 3-1.3: USB disconnect, address 11

The adapter was not visible through lsusb and the drive could not be mounted.

Switching the drive jumpers from CS/Cable Select to drive 0 primary master made auto-mounting work with the following output:

 [ 1929.136861] usb 3-4: new high speed USB device using ehci_hcd and address 13
 [ 1929.281381] usb 3-4: configuration #1 chosen from 1 choice
 [ 1929.297936] scsi6 : SCSI emulation for USB Mass Storage devices
 [ 1934.303006] scsi 6:0:0:0: Direct-Access IC35L040 AVER07-0 0811 PQ: 0 ANSI: 0
 [ 1934.318784] sd 6:0:0:0: [sdc] 80418240 512-byte hardware sectors (41174 MB)
 [ 1934.320664] sd 6:0:0:0: [sdc] Test WP failed, assume Write Enabled
 [ 1934.322581] sd 6:0:0:0: [sdc] 80418240 512-byte hardware sectors (41174 MB)
 [ 1934.326566] sd 6:0:0:0: [sdc] Test WP failed, assume Write Enabled
 [ 1934.326585] sdc: sdc1
 [ 1934.347731] sd 6:0:0:0: [sdc] Attached SCSI disk
 [ 1934.347873] sd 6:0:0:0: Attached scsi generic sg3 type 0

The adapter now appears correctly as a USB device:

 $ lsusb
 Bus 003 Device 013: ID 05e3:0702 Genesys Logic, Inc. USB 2.0 IDE Adapter

[kernel-janitor (kernel-janitor)]

This bug report was marked as Confirmed a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Ramaddan (ramaddan)]

I started to have this problem after I upgraded to Jaunty from Intrepid.

It was working fine in Intrepid.

I have an external Lacie 500GB drive.

this is what I get in dmesg:

[14058.524564] usb 2-1: new full speed USB device using ohci_hcd and address 12
[14073.700589] usb 2-1: device descriptor read/64, error -110
[14088.980545] usb 2-1: device descriptor read/64, error -110
[14089.248045] usb 2-1: new full speed USB device using ohci_hcd and address 13
[14104.412435] usb 2-1: device descriptor read/64, error -110
[14119.693880] usb 2-1: device descriptor read/64, error -110
[14119.972566] usb 2-1: new full speed USB device using ohci_hcd and address 14
[14124.993906] usb 2-1: device descriptor read/8, error -110
[14130.112896] usb 2-1: device descriptor read/8, error -110
[14130.392382] usb 2-1: new full speed USB device using ohci_hcd and address 15
[14135.412883] usb 2-1: device descriptor read/8, error -110
[14140.532866] usb 2-1: device descriptor read/8, error -110
[14140.636558] hub 2-0:1.0: unable to enumerate USB device on port 1

And sometimes it shows up in lsusb, and sometimes not, but never works.

Please tell me if you need more info.

[Ramaddan (ramaddan)]

Related info follows

[Martin Pitt (pitti)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

In Ubuntu 9.10 (Karmic) we have a new tool to debug storage related problems. Please run "ubuntu-bug", select "storage problem", and walk through the steps. This will create a new bug report, please send the new bug number here, so that I get to know it quickly.

Thank you!

[Martin Pitt (pitti)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Martin Pitt (pitti)]

For the "device descriptor read/64, error -110" thingies:

  - Do you still get this problem in Ubuntu 9.10 final?

  - If so, please try this:

    sudo mv /lib/udev/devkit-disks-probe-ata-smart{,.disabled}

    Does this help? If not, please move it back with

    sudo mv /lib/udev/devkit-disks-probe-ata-smart{.disabled,}

[Ramaddan (ramaddan)]

Well, I had to access my information, so I had to get a new hardisk enclosure.

I do not know anymore if it was just a hardware issue or a firmware one.

So unfortunately I cannot really give more info for it.

I removed the hardisk from the enclosure, and tried it directly on my PC, and it worked fine, so I got a new enclosure.

With the new enclosure, everything is working great.

Thanks for taking the time.

[Martin Pitt (pitti)]

Closing then. Thanks for reporting back!