From owner-freebsd-fs@FreeBSD.ORG Mon May 17 18:41:34 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A48CC106564A for ; Mon, 17 May 2010 18:41:34 +0000 (UTC) (envelope-from tsw5@duke.edu) Received: from smtp.duke.edu (smtp-01.oit.duke.edu [152.3.174.14]) by mx1.freebsd.org (Postfix) with ESMTP id 679FB8FC0A for ; Mon, 17 May 2010 18:41:34 +0000 (UTC) Received: from smtp.duke.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id B0CE8309025; Mon, 17 May 2010 14:41:33 -0400 (EDT) Received: from [152.3.137.189] (k.cs.duke.edu [152.3.137.189]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.duke.edu (Postfix) with ESMTP id 8EA2B309047; Mon, 17 May 2010 14:41:33 -0400 (EDT) Message-ID: <4BF18DEA.7030405@duke.edu> Date: Mon, 17 May 2010 14:41:46 -0400 From: Todd Wasson User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Thunderbird/3.0.4 MIME-Version: 1.0 To: Jeremy Chadwick References: <0B97967D-1057-4414-BBD4-4F1AA2659A5D@duke.edu> <4BF0F231.9000706@mapper.nl> <53F15A8B-77DA-4CEF-A790-2902BEC91002@duke.edu> <20100517182411.GA14251@icarus.home.lan> In-Reply-To: <20100517182411.GA14251@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.4.2.338381, Antispam-Engine: 2.6.0.325393, Antispam-Data: 2010.5.17.183021 Cc: freebsd-fs@freebsd.org Subject: Re: zfs drive replacement issues X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2010 18:41:34 -0000 > Can you provide some details about the controller you have these disks > attached to? "dmesg | egrep -i 'ata|ahci'" should be sufficient at this > point. Hi Jeremy, sure. As the problem has been resolved, I suppose this is just for curiosity's sake, but here's the dmesg|egrep output: atapci0: port 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f irq 16 at device 0.0 on pci2 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] atapci1: port 0x9c00-0x9c07,0x9880-0x9883,0x9800-0x9807,0x9480-0x9483,0x9400-0x940f,0x9080-0x908f irq 22 at device 31.2 on pci0 atapci1: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] ata4: on atapci1 ata4: [ITHREAD] atapci2: port 0xac00-0xac07,0xa880-0xa883,0xa800-0xa807,0xa480-0xa483,0xa400-0xa40f,0xa080-0xa08f irq 22 at device 31.5 on pci0 atapci2: [ITHREAD] ata5: on atapci2 ata5: [ITHREAD] ata6: on atapci2 ata6: [ITHREAD] ad4: 152627MB at ata2-master UDMA100 ad6: 476940MB at ata3-master SATA300 ad8: 381554MB at ata4-master SATA300 ad10: 476940MB at ata5-master SATA300 ad12: 476940MB at ata6-master SATA300 The motherboard in question is an ASUS P5K-VM, with an Intel ICH9 SATA controller. > SMART statistics for the drive(s) you feel might be bad would also help. > I can try my best to describe the conditions of the disk(s) based on > output from "smartctl -a /dev/adX". You can install smartmontools from > ports/sysutils/smartmontools. The problematic drive is physically disconnected from the machine at the moment, but if you think it would be helpful, I can take the new drive back out, reconnect the old one, and run smartctl on it later this evening. Thanks again. Todd