From owner-freebsd-usb@FreeBSD.ORG Sat Jun 23 13:43:16 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E9BD2106564A for ; Sat, 23 Jun 2012 13:43:16 +0000 (UTC) (envelope-from muxx.mailinglists@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6EFBC8FC1A for ; Sat, 23 Jun 2012 13:43:16 +0000 (UTC) Received: by lbon10 with SMTP id n10so5780965lbo.13 for ; Sat, 23 Jun 2012 06:43:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=WlH1U303E9Z0460R7lAkmCQiYVzWOcBC/AlJWiC3QzI=; b=hitJQolpdyZXaMczP73rB7TqKME8RAobdzfyC9m4NvjnOUgTu9UG359mQXZcH/G8su 947KWz2/zLxY9ZrheMWHJeidbyFvlq11lOqQ2e2JZPHvPJbASlaEb7PplL8vkOK4xDQh MvqCU2HlB/vsak52kOQO6ffKR8VrujT0h67V6RN/97dX6vhAQeUVrbah5Gr8/Oo3+c1d 1bmoYU1eHlw0sZtFDd11GTQC95F6c5Yet9Du3gF297xGZFYRz8kogEmtT5ntY0WaJYnW i3Es7eogwovrD3tu+bsSljcD7Tp2tXE4r2wCUXtXIObzADTzSzdwQnsBNA/k4XkZMGQ3 7qxg== MIME-Version: 1.0 Received: by 10.112.25.100 with SMTP id b4mr2981777lbg.55.1340458995198; Sat, 23 Jun 2012 06:43:15 -0700 (PDT) Received: by 10.112.26.163 with HTTP; Sat, 23 Jun 2012 06:43:15 -0700 (PDT) Date: Sat, 23 Jun 2012 14:43:15 +0100 Message-ID: From: maxim naumov To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Seagate FreeAgent GoFlex 1.5TB external HDD problems X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jun 2012 13:43:17 -0000 hi everyone I am having problems with a recently purchased external HDD: 0bc2:5031 Seagate RSS LLC, FreeAgent GoFlex 1.5TB USB 3.0. the HDD would work fine for a while but then the kernel would lock up and require a powercycle. after turning off soft updates on that filesystem the lock up has disappeared, but the system still reports lots of errors repeatedly like the following: Jun 22 17:05:13 xxxx kernel: (da0:umass-sim0:0:0:0): AutoSense failed Jun 22 17:05:13 xxxx kernel: g_vfs_done():da0s1d[WRITE(offset=3D406613852160, length=3D16384)]error =3D = 5 Jun 22 17:05:13 xxxx kernel: g_vfs_done():da0s1d[WRITE(offset=3D406613868544, length=3D16384)]error =3D = 5 Jun 22 17:05:13 xxxx kernel: g_vfs_done():da0s1d[WRITE(offset=3D406613884928, length=3D16384)]error =3D = 5 Jun 22 17:05:13 xxxx kernel: g_vfs_done():da0s1d[WRITE(offset=3D406613901312, length=3D16384)]error =3D = 5 Jun 22 17:05:13 xxxx kernel: g_vfs_done():da0s1d[WRITE(offset=3D406613917696, length=3D16384)]error =3D = 5 Jun 22 17:05:13 xxxx kernel: g_vfs_done():da0s1d[WRITE(offset=3D406613934080, length=3D16384)]error =3D = 5 Jun 22 17:05:13 xxxx kernel: g_vfs_done():da0s1d[WRITE(offset=3D406613950464, length=3D16384)]error =3D = 5 after getting into that state the HDD seems unresponsive. usbconfig reset/power doesn't help, you have to physically unplug the drive and plug it back in. the same FreeBSD box, same USB socket, same cable, same backup software and data, but a different USB 3.0 drive (Verbatim 1TB) shows no errors. I tried the UQ_MSC_NO_SYNC_CACHE quirk, no luck. I initially thought the drive was failing, but the long smart test detected no errors. it looks like the Seagate is getting its knickers in a twist for some reason, but after similar tests I found that it works fine in GNU/Linux 2.6.38, however, the following error is displayed from time to time during transfers: [ 5633.140506] sd 7:0:0:0: [sdb] =A0Sense Key : Recovered Error [current] [descriptor] [ 5633.140521] Descriptor sense data with sense descriptors (in hex): [ 5633.140526] =A0 =A0 =A0 =A0 72 01 04 1d 00 00 00 0e 09 0c 00 00 00 00 00= 00 [ 5633.140548] =A0 =A0 =A0 =A0 00 4f 00 c2 40 50 [ 5633.140560] sd 7:0:0:0: [sdb] =A0ASC=3D0x4 ASCQ=3D0x1d [ 5700.040026] [Hardware Error]: Machine check events logged googling shows that this is a known but benign problem: "SMART responses for SATA disks on SAS get interpreted as errors". http://forums.whirlpool.net.au/archive/1881928 https://bugzilla.kernel.org/show_bug.cgi?id=3D13594 I was wondering if the GNU/Linux error is somehow related to the problem I see with FreeBSD. perhaps it is also seen as an error but the umass code doesn't cope well with it. more info about my system: 8.2-RELEASE on i386. USB2 EHCI host controller: Intel Corporation 82801DB/DBM. it looks like it is more likely to fail when transferring large files. I use the external HDD for backups (rdiff-backup), backing up hundreds of GBs, with many files over 1GB. any ideas and requests for more data are welcome. /max