Re: Annoying problems with lacie external hd (JMicron 0x2339?)

[Felipe Contreras]

On Sat, Oct 3, 2009 at 6:48 PM, Sarah Sharp
<sarah.a.sharp@xxxxxxxxxxxxxxx> wrote:
> On Sat, Oct 03, 2009 at 01:35:58PM +0300, Felipe Contreras wrote:
>> Hi,
>>
>> This is with 2.6.31.1.
>>
>> I'm having a lot of problems with a lacie external hd[1]. It seems the
>> actual disk is a seagate ST375064, and the bridge is a JMicron 2339.
>>
>> In normal usage what I see is that if I don't use the disk after a
>> while hear a loud click (as if something got stuck) and then I cannot
>> use it any more; I have to turn it off and on again.
>>
>> But then I started to see some problems on one fs, so I ran badblocks
>> and I noticed a lot of strange behavior. It seems once I get a
>> read/write error then I get more of them in a row, and after a while I
>> hear another loud click, and then I only get read/write errors
>> constantly.
>>
>> I noticed in 'unusual_devs.h' there's already a quirk for another
>> JMicron product, so I tried to do the same:
>>
>> +UNUSUAL_DEV( Â0x152d, 0x2339, 0x0000, 0xffff,
>> + Â Â Â Â Â Â Â "JMicron",
>> + Â Â Â Â Â Â Â "USB to ATA/ATAPI Bridge",
>> + Â Â Â Â Â Â Â US_SC_DEVICE, US_PR_DEVICE, NULL,
>> + Â Â Â Â Â Â Â US_FL_IGNORE_RESIDUE | US_FL_SANE_SENSE ),
>>
>> This seemed to help with the consecutive errors, but not with the loud click.
>>
>> This is what I get when this click happens:
>>
>> Oct Â3 13:14:54 annwn kernel: [ Â351.099096] usb 1-1: reset high speed
>> USB device using ehci_hcd and address 3
>> Oct Â3 13:14:54 annwn kernel: [ Â351.213541] usb 1-1: device firmware changed
>> Oct Â3 13:14:54 annwn kernel: [ Â351.213588] usb 1-1: USB disconnect, address 3
>> Oct Â3 13:14:54 annwn kernel: [ Â351.213633] sd 4:0:0:0: Device
>> offlined - not ready after error recovery
>> Oct Â3 13:14:54 annwn kernel: [ Â351.213650] sd 4:0:0:0: [sdb]
>> Unhandled error code
>> Oct Â3 13:14:54 annwn kernel: [ Â351.213655] sd 4:0:0:0: [sdb] Result:
>> hostbyte=DID_ABORT driverbyte=DRIVER_OK
>> Oct Â3 13:14:54 annwn kernel: [ Â351.213663] end_request: I/O error,
>> dev sdb, sector 8596352
>> Oct Â3 13:14:54 annwn kernel: [ Â351.213774] sd 4:0:0:0: rejecting I/O
>> to offline device
>> Oct Â3 13:14:54 annwn kernel: [ Â351.213816] sd 4:0:0:0: rejecting I/O
>> to offline device
>> Oct Â3 13:14:54 annwn kernel: [ Â351.213852] sd 4:0:0:0: rejecting I/O
>> to offline device
>> Oct Â3 13:14:54 annwn kernel: [ Â351.213891] sd 4:0:0:0: rejecting I/O
>> to offline device
>> Oct Â3 13:14:54 annwn kernel: [ Â351.213927] sd 4:0:0:0: rejecting I/O
>> to offline device
>> Oct Â3 13:14:54 annwn kernel: [ Â351.213962] sd 4:0:0:0: rejecting I/O
>> to offline device
>> Oct Â3 13:14:54 annwn kernel: [ Â351.213997] sd 4:0:0:0: rejecting I/O
>> to offline device
>> Oct Â3 13:14:54 annwn kernel: [ Â351.214202] sd 4:0:0:0: rejecting I/O
>> to offline device
>> Oct Â3 13:14:55 annwn kernel: [ Â351.317278] usb 1-1: new high speed
>> USB device using ehci_hcd and address 4
>> Oct Â3 13:14:55 annwn kernel: [ Â351.432192] usb 1-1: New USB device
>> found, idVendor=152d, idProduct=2339
>> Oct Â3 13:14:55 annwn kernel: [ Â351.432196] usb 1-1: New USB device
>> strings: Mfr=1, Product=2, SerialNumber=5
>> Oct Â3 13:14:55 annwn kernel: [ Â351.432199] usb 1-1: Product: USB to
>> ATA/ATAPI Bridge
>> Oct Â3 13:14:55 annwn kernel: [ Â351.432202] usb 1-1: Manufacturer: JMicron
>> Oct Â3 13:14:55 annwn kernel: [ Â351.432204] usb 1-1: SerialNumber: 5D27FFFFFFFF
>> Oct Â3 13:14:55 annwn kernel: [ Â351.432321] usb 1-1: configuration #1
>> chosen from 1 choice
>> Oct Â3 13:14:55 annwn kernel: [ Â351.432791] scsi5 : SCSI emulation
>> for USB Mass Storage devices
>>
>> Can anyone help? This disk is important for me =/
>
> The log shows the device just disconnected from the system. ÂYou should
> post more of the logfile before the disconnect so we can see if it's an
> issue with the USB core. ÂDid it work with a previous kernel?

There was nothing special in the log. I think it was completely silent
for a while. I'll grab more logs and post them.

I'm not sure if it was working properly on previous kernels. If it
did, it was probably a long time ago. I least I can remember this
behavior since .28.

> It could be that your disk is just dying, and occasionally
> disconnecting. ÂOr you could have a bad cable or a hub that's
> introducing noise. ÂCan you try a different USB cable?

I already tried with a different cable. Another external drive I have,
worked perfectly (badblocks didn't return a single bad one) with both
cables.

Cheers.

-- 
Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/