From owner-freebsd-stable@FreeBSD.ORG Fri Dec 10 17:01:27 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DC05106566B for ; Fri, 10 Dec 2010 17:01:27 +0000 (UTC) (envelope-from aw1@swelter.hanley.stade.co.uk) Received: from outbound-queue-1.mail.thdo.gradwell.net (outbound-queue-1.mail.thdo.gradwell.net [212.11.70.34]) by mx1.freebsd.org (Postfix) with ESMTP id F2ADF8FC15 for ; Fri, 10 Dec 2010 17:01:26 +0000 (UTC) Received: from outbound-edge-1.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-1.mail.thdo.gradwell.net (Postfix) with ESMTP id 1C0FB223B5; Fri, 10 Dec 2010 16:50:46 +0000 (GMT) Received: from 93-97-22-18.zone5.bethere.co.uk (HELO swelter.hanley.stade.co.uk) (93.97.22.18) (smtp-auth username postmaster%pop3.stade.co.uk, mechanism cram-md5) by outbound-edge-1.mail.thdo.gradwell.net (qpsmtpd/0.83) with (AES256-SHA encrypted) ESMTPSA; Fri, 10 Dec 2010 16:50:45 +0000 Received: from swelter.hanley.stade.co.uk (localhost [127.0.0.1]) by swelter.hanley.stade.co.uk (8.14.4/8.14.4) with ESMTP id oBAGojUe031940; Fri, 10 Dec 2010 16:50:45 GMT (envelope-from aw1@swelter.hanley.stade.co.uk) Received: (from aw1@localhost) by swelter.hanley.stade.co.uk (8.14.4/8.14.4/Submit) id oBAGojqN031939; Fri, 10 Dec 2010 16:50:45 GMT (envelope-from aw1) Date: Fri, 10 Dec 2010 16:50:45 +0000 From: Adrian Wontroba To: Paul Mather Message-ID: <20101210165044.GA31790@swelter.hanley.stade.co.uk> Mail-Followup-To: Adrian Wontroba , Paul Mather , Jeremy Chadwick , freebsd-stable@freebsd.org References: <20101209213556.GA3322@pollux.local.net> <20101209221108.GA13256@icarus.home.lan> <8591B0F0-82B2-433C-AE0C-0D454B12E41B@gromit.dlib.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8591B0F0-82B2-433C-AE0C-0D454B12E41B@gromit.dlib.vt.edu> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.2-PRERELEASE Organization: Oh dear, I've joined one again. X-Virus-Scanned: clamav-milter 0.95.3 at swelter.hanley.stade.co.uk X-Virus-Status: Clean X-Gradwell-MongoId: 4d025a65.167cb-357d-1 X-Gradwell-Auth-Method: mailbox X-Gradwell-Auth-Credentials: postmaster@pop3.stade.co.uk Cc: freebsd-stable@freebsd.org, Jeremy Chadwick Subject: Re: umass: AutoSense failed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: aw1@stade.co.uk List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2010 17:01:27 -0000 On Fri, Dec 10, 2010 at 09:40:05AM -0500, Paul Mather wrote: (reformatted) > I get something similar to this happening on 8.2-PRERELEASE. In my > case, it's not during boot probing or device attachment. Instead, it > happens occasionally after boot. The devices concerned are Maxtor > OneTouch external USB hard drives. Every now and then, I will get > something akin to the following crop up in the console log: > > (da1:umass-sim1:1:0:0): AutoSense failed > > I have three of these Maxtor OneTouch drives attached to the system as > part of a ZFS pool. When I get an "AutoSense failed" message, it is > usually accompanied by the ZFS pool being marked as faulted. > > The Maxtor OneTouch drives are wont to spin down and go into a > deep sleep after a period of inactivity and appear very slow to > wake up again when I/O occurs. I have always assumed that the > "AutoSense failed" is associated with this---that there is some kind > of timeout in the FreeBSD stack that this device is exceeding. In > fact, sometimes the devices fail to probe properly during boot when > they are asleep. > > This is what the OneTouch normally probes as: > > da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 : > da0Fixed Direct Access SCSI-4 device : 40.000MB/s transfers : 953869MB > da0(1953525168 512 byte sectors: 255H 63S/T 121601C) > > > Cheers, > > Paul. I had this happen while backing up to two successive previously reliable UFS USB external disk drives. Plugging the USB cable into a motherboard USB socket at the back of the computer rather than a front panel socket made the problem go away. This might cure the OP's problem too. -- Adrian Wontroba If it weren't for the opinion polls we'd never know what people are undecided about.