From owner-freebsd-fs@FreeBSD.ORG Sun Apr 14 19:52:14 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 486E6BA5 for ; Sun, 14 Apr 2013 19:52:14 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:32]) by mx1.freebsd.org (Postfix) with ESMTP id 2BC66F53 for ; Sun, 14 Apr 2013 19:52:14 +0000 (UTC) Received: from omta16.emeryville.ca.mail.comcast.net ([76.96.30.72]) by qmta03.emeryville.ca.mail.comcast.net with comcast id PvlN1l0061ZMdJ4A3vsEzT; Sun, 14 Apr 2013 19:52:14 +0000 Received: from koitsu.strangled.net ([67.180.84.87]) by omta16.emeryville.ca.mail.comcast.net with comcast id PvsC1l0031t3BNj8cvsCH4; Sun, 14 Apr 2013 19:52:13 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id F2A2873A33; Sun, 14 Apr 2013 12:52:11 -0700 (PDT) Date: Sun, 14 Apr 2013 12:52:11 -0700 From: Jeremy Chadwick To: Radio =?unknown-8bit?B?bcU/b2R5Y2ggYmFuZHl0w7N3?= Subject: Re: A failed drive causes system to hang Message-ID: <20130414195211.GA39201@icarus.home.lan> References: <51672164.1090908@o2.pl> <20130411212408.GA60159@icarus.home.lan> <5168821F.5020502@o2.pl> <20130412220350.GA82467@icarus.home.lan> <51688BA6.1000507@o2.pl> <20130413000731.GA84309@icarus.home.lan> <516A8646.4000101@o2.pl> <20130414192830.GA38338@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130414192830.GA38338@icarus.home.lan> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1365969134; bh=aN5pjazc8G4sxyH4/0He8A6Tw+BncOmtEMIaLNiGkiQ=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=NJs0/JFwDP1bvE9ujhC4nVuq5ZlVhLDMNH9udeuaNiYdtnBTbESW48dLVZcp509A0 X2y/5ZdOk6UlpXGgY/54P/eoO1n82zJzHWcg5IundwgRmVx5v0kJ7wWUh7YV+FCL6E MkAJm5TwOHtuRkwv5JERNg3tI4B69zYCyLOU2o13/Kl9FW0zijMtumIYFDwbyQrlCn HlOXAR1RE+aee5b+uGsCjdeKnpJahU186Yb/vaOm2TvB3+Lx6X0F6aa7wR7ERO6maT fgUKxTx2nvh0gU/HzOuAAL3VOIGEW3z8+NEQJXzXWw4KxBBKhAnaJ5q/3P9oMb8x2v yHK+Wc1rBpRow== Cc: freebsd-fs@freebsd.org, support@lists.pcbsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Apr 2013 19:52:14 -0000 {snipping lots for brevity} On Sun, Apr 14, 2013 at 12:28:30PM -0700, Jeremy Chadwick wrote: > On Sun, Apr 14, 2013 at 12:34:46PM +0200, Radio m?odych bandytw wrote: > > Sorry. I thought just the error was important. So here you are: > > dmesg.boot: > > http://pastebin.com/LFXPusMX > > Thank you. Please read everything I have written below before doing > anything. > > Based on this output, we can see the following: > > * AHCI is actively in use, and is a slowly-becoming-infamous ATI IXP700 > controller: > > ahci0: port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xf9fffc00-0xf9ffffff irq 19 at device 17.0 on pci0 > > * The system has 3 disks attached to this controller: > > ada0 at ahcich0 bus 0 scbus2 target 0 lun 0 > ada0: ATA-8 SATA 2.x device > ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada0: Command Queueing enabled > ada0: 1430799MB (2930277168 512 byte sectors: 16H 63S/T 16383C) > ada1 at ata0 bus 0 scbus6 target 0 lun 0 > ada1: ATA-8 SATA 2.x device > ada1: 150.000MB/s transfers (SATA, UDMA6, PIO 8192bytes) > ada1: 1430799MB (2930277168 512 byte sectors: 16H 63S/T 16383C) > ada2 at ata0 bus 0 scbus6 target 1 lun 0 > ada2: ATA-8 SATA 2.x device > ada2: 150.000MB/s transfers (SATA, UDMA6, PIO 8192bytes) > ada2: 610480MB (1250263728 512 byte sectors: 16H 63S/T 16383C) > > Let's talk about ada0 and ada1 first. Hold up a minute -- I just noticed some key information here (see what happens with big conflated threads?), and it sheds some light on my concerns with AHCI vs. classic ata(4): ada0 -- attached to ahcich0 ada1 -- attached to ata0 (presumably a "master" drive) ada2 -- attached to ata0 (presumably a "slave" drive) This is extremely confusing, because ata0 is a classic ATA controller (I can even tell from the classic ISA I/O port ranges): atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0 ata0: at channel 0 on atapci1 ata1: at channel 1 on atapci1 Yet the WD15EARS and ST3640323AS drives are physically SATA drives. Are you using SATA-to-IDE adapters on these two drives? If not, this seems to indicate the motherboard and/or SATA controller is actually only binding 1 disk to AHCI, while the others are bound to the same controller operating in (possibly) "SATA Enhanced" mode. This would be the first I've ever seen of this (a controller operating in both modes simultaneously), but I have a lot more experience with Intel SATA controllers than I do AMD. I don't know why a system would do this, unless all of this can be controlled via the BIOS somehow. What a mess. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |