From owner-freebsd-fs@FreeBSD.ORG Sun Apr 14 20:35:54 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 33968776 for ; Sun, 14 Apr 2013 20:35:54 +0000 (UTC) (envelope-from radiomlodychbandytow@o2.pl) Received: from moh3-ve1.go2.pl (moh3-ve2.go2.pl [193.17.41.86]) by mx1.freebsd.org (Postfix) with ESMTP id A481C12C for ; Sun, 14 Apr 2013 20:35:53 +0000 (UTC) Received: from moh3-ve1.go2.pl (unknown [10.0.0.157]) by moh3-ve1.go2.pl (Postfix) with ESMTP id 4C40AAF696B for ; Sun, 14 Apr 2013 22:35:52 +0200 (CEST) Received: from unknown (unknown [10.0.0.108]) by moh3-ve1.go2.pl (Postfix) with SMTP for ; Sun, 14 Apr 2013 22:35:52 +0200 (CEST) Received: from unknown [93.175.66.185] by poczta.o2.pl with ESMTP id nEdjtI; Sun, 14 Apr 2013 22:35:44 +0200 Message-ID: <516B1315.8060408@o2.pl> Date: Sun, 14 Apr 2013 22:35:33 +0200 From: =?UTF-8?B?UmFkaW8gbcWCb2R5Y2ggYmFuZHl0w7N3?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130407 Thunderbird/17.0.5 MIME-Version: 1.0 To: Jeremy Chadwick Subject: Re: A failed drive causes system to hang 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> <20130414195211.GA39201@icarus.home.lan> In-Reply-To: <20130414195211.GA39201@icarus.home.lan> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-O2-Trust: 1, 30 X-O2-SPF: neutral 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 20:35:54 -0000 On 14/04/2013 21:52, Jeremy Chadwick wrote: > {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? No. > > 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. > I looked into BIOS and it can be controlled. 6 ports are divided into 2 triples and I can switch mode of each triple independently. One drive is connected to one and two to the other. Looks like there's a bug because both triples are set to ATA. I left them like that for now. Anyway, I got the hang again, so I can provide dmesg. I was not at the computer when it happened, so there's only the last screen though... pastebin.com/bjYtzPgs -- Twoje radio