From owner-freebsd-stable@FreeBSD.ORG Sat Mar 3 19:52:07 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 71E9A1065674 for ; Sat, 3 Mar 2012 19:52:07 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id D976A8FC13 for ; Sat, 3 Mar 2012 19:52:06 +0000 (UTC) Received: by bkcjc3 with SMTP id jc3so3083430bkc.13 for ; Sat, 03 Mar 2012 11:52:05 -0800 (PST) Received-SPF: pass (google.com: domain of mavbsd@gmail.com designates 10.204.173.11 as permitted sender) client-ip=10.204.173.11; Authentication-Results: mr.google.com; spf=pass (google.com: domain of mavbsd@gmail.com designates 10.204.173.11 as permitted sender) smtp.mail=mavbsd@gmail.com; dkim=pass header.i=mavbsd@gmail.com Received: from mr.google.com ([10.204.173.11]) by 10.204.173.11 with SMTP id n11mr7717215bkz.120.1330804325719 (num_hops = 1); Sat, 03 Mar 2012 11:52:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=N5qNLevz6dKQSpX7iXnoP2RhK2xVCKhW3mucEsktcIU=; b=oeNdnKBAkZfapqdVKmMLzIPZyI83iyKb83hVmN1BA5E0b4WaWlx3LcD2wd7k+TwN+m 9+wRRe3myiC/WvXyI13cfiegyXONLbOSgQ5p9JcSkwk77e7DWUmiIYV2yIPZVaEK2va1 vpWujYUcyz5FeGHG3vKaOHXQPPYzM8eR3WVP5areFCYM/7E4h8VEVilnVCT7xQRgaSnh 0ZvOQ/g4Q42Kj+JcYhh5Vu6DRaLx3tD+UjgxblEqJYTtHZGKsQlLIqBQzkmkp/ybG3sp HivhpyptdHIYUB38qAKMqMgWsDw0xYztqqNAW/ZXiMGEfl0nmvQduXvbW0qUwC5bz8ji GKbA== Received: by 10.204.173.11 with SMTP id n11mr6159350bkz.120.1330804325640; Sat, 03 Mar 2012 11:52:05 -0800 (PST) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua. [212.86.226.226]) by mx.google.com with ESMTPS id y9sm16033158bkw.5.2012.03.03.11.52.04 (version=SSLv3 cipher=OTHER); Sat, 03 Mar 2012 11:52:04 -0800 (PST) Sender: Alexander Motin Message-ID: <4F527659.5030001@FreeBSD.org> Date: Sat, 03 Mar 2012 21:51:53 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120116 Thunderbird/9.0 MIME-Version: 1.0 To: Jeff Blank References: In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: missing disk device under 9-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2012 19:52:07 -0000 Hi. On 03.03.2012 21:08, Jeff Blank wrote: > I attempted an upgrade last night from an old 8-STABLE (25 Apr 2011) > to 9-STABLE and ran into a problem where a disk apparently wasn't > detected. I'm of course aware of the ATA/CAM changes, but I haven't > found anything that quite explains what's happening here. I've > attached dmesg output from the 8-STABLE and 9-STABLE kernels as well > as the results of 'ls -l /dev/ad*' and 'zpool status' under both > kernels. > > ZFS seems to have figured out what to do about its ad4p3 member > (switching to a gptid device), but since only ada0 is detected during > boot, it can't complete the pool. The weird thing is, though, that > the other disk was actually detected on one reboot to the 9.0 kernel, > ZFS was happy, etc. I haven't been able to reproduce it, though. > > Due to these problems, I haven't upgraded userland yet and am of > course sticking with the 8-STABLE kernel, but I can boot into the > 9-STABLE kernel at will if anyone needs more information. This looks like cause of the missing disk: ahcich1: Timeout on slot 0 port 0 ahcich1: is 00000002 cs 00000000 ss 00000000 rs 00000001 tfd 50 serr 00000000 cmd 00006017 ahcich1: Timeout on slot 0 port 0 ahcich1: is 00000002 cs 00000000 ss 00000000 rs 00000001 tfd 50 serr 00000000 cmd 00006017 It tells that controller signals interrupt, but driver haven't got it. That is even more strange after the disk on first SATA port is working fine. You may try to add to your /boot/loader.conf line: hint.ahci.0.msi=0 , or just set it via loader prompt. -- Alexander Motin