From owner-freebsd-questions@FreeBSD.ORG Sat Mar 26 19:30:25 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2DEF16A4CE for ; Sat, 26 Mar 2005 19:30:24 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9676C43D3F for ; Sat, 26 Mar 2005 19:30:24 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j2QJUNtI019325 for freebsd-questions@freebsd.org; Sat, 26 Mar 2005 13:30:23 -0600 (CST) (envelope-from dan) Date: Sat, 26 Mar 2005 13:30:23 -0600 From: Dan Nelson To: freebsd-questions@freebsd.org Message-ID: <20050326193022.GD12481@dan.emsphone.com> References: <239528826.20050326182122@wanadoo.fr> <42459AD8.90802@makeworld.com> <11929402.20050326195054@wanadoo.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <11929402.20050326195054@wanadoo.fr> X-OS: FreeBSD 5.4-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.8i Subject: Re: Updated on SATA drive problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Mar 2005 19:30:25 -0000 In the last episode (Mar 26), Anthony Atkielski said: > Chris writes: > > That's good news - I'm glad to hear that you are progressing with > > your issues. Once you have these items under control - you ought to > > have a more enjoyable experiance with whatever OS you wish to use. > > Now if I could just fine the problem FreeBSD has with my SCSI drives > on my test machine. I noticed that the pages and pages of error > messages I get sometimes when doing I/O to the disks are also > generated even by something as simple as "smartctl -a" which > presumably does not do any physical I/O to the platters. This would > seem to rule out any hardware problems involving the media, > actuators, etc. smartctl sends raw SCSI requests to the disk, and I think a recent change in either smartmontools or the scsi code is ending up with the wrong timeout value, so the request times out immediately. This happens to me when I launch smartd on all my machines, but it's intermittent and doesn't seem to affect anything (I get periodic temerature notifications after that with no timeout errors). See PR misc/73833 . -- Dan Nelson dnelson@allantgroup.com