Date: Mon, 17 May 2010 14:41:46 -0400 From: Todd Wasson <tsw5@duke.edu> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: freebsd-fs@freebsd.org Subject: Re: zfs drive replacement issues Message-ID: <4BF18DEA.7030405@duke.edu> In-Reply-To: <20100517182411.GA14251@icarus.home.lan> References: <0B97967D-1057-4414-BBD4-4F1AA2659A5D@duke.edu> <4BF0F231.9000706@mapper.nl> <53F15A8B-77DA-4CEF-A790-2902BEC91002@duke.edu> <20100517182411.GA14251@icarus.home.lan>
index | next in thread | previous in thread | raw e-mail
> 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: <JMicron JMB368 UDMA133 controller> port 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f irq 16 at device 0.0 on pci2 atapci0: [ITHREAD] ata2: <ATA channel 0> on atapci0 ata2: [ITHREAD] atapci1: <Intel ICH9 SATA300 controller> port 0x9c00-0x9c07,0x9880-0x9883,0x9800-0x9807,0x9480-0x9483,0x9400-0x940f,0x9080-0x908f irq 22 at device 31.2 on pci0 atapci1: [ITHREAD] ata3: <ATA channel 0> on atapci1 ata3: [ITHREAD] ata4: <ATA channel 1> on atapci1 ata4: [ITHREAD] atapci2: <Intel ICH9 SATA300 controller> port 0xac00-0xac07,0xa880-0xa883,0xa800-0xa807,0xa480-0xa483,0xa400-0xa40f,0xa080-0xa08f irq 22 at device 31.5 on pci0 atapci2: [ITHREAD] ata5: <ATA channel 0> on atapci2 ata5: [ITHREAD] ata6: <ATA channel 1> on atapci2 ata6: [ITHREAD] ad4: 152627MB <Seagate ST3160815A 3.AAC> at ata2-master UDMA100 ad6: 476940MB <WDC WD5000AVVS-63M8B0 01.00A01> at ata3-master SATA300 ad8: 381554MB <WDC WD4000AAJS-00YFA0 12.01C02> at ata4-master SATA300 ad10: 476940MB <SAMSUNG HD501LJ CR100-12> at ata5-master SATA300 ad12: 476940MB <SAMSUNG HD501LJ CR100-12> 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. Toddhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BF18DEA.7030405>