From owner-freebsd-stable@FreeBSD.ORG Wed Apr 18 17:23:23 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F667106566B for ; Wed, 18 Apr 2012 17:23:23 +0000 (UTC) (envelope-from james.r.harris@intel.com) Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by mx1.freebsd.org (Postfix) with ESMTP id 3E15F8FC12 for ; Wed, 18 Apr 2012 17:23:23 +0000 (UTC) Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 18 Apr 2012 10:23:16 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208";a="132483765" Received: from azsmsx601.amr.corp.intel.com ([10.2.121.193]) by azsmga001.ch.intel.com with ESMTP; 18 Apr 2012 10:23:16 -0700 Received: from fmsmsx107.amr.corp.intel.com (10.19.9.54) by azsmsx601.amr.corp.intel.com (10.2.121.193) with Microsoft SMTP Server (TLS) id 8.2.255.0; Wed, 18 Apr 2012 10:23:16 -0700 Received: from fmsmsx106.amr.corp.intel.com ([169.254.6.145]) by FMSMSX107.amr.corp.intel.com ([169.254.9.62]) with mapi id 14.01.0355.002; Wed, 18 Apr 2012 10:23:16 -0700 From: "Harris, James R" To: "freebsd-stable@freebsd.org" Thread-Topic: FreeBSD 8.3-R sysinstall does not "see" disks that are recognized during boot Thread-Index: AQHNHYfwYuvp4iXoMUq/kbgSKIRNSg== Date: Wed, 18 Apr 2012 17:23:15 +0000 Message-ID: References: <20120417195749.L89206@shell.xecu.net> In-Reply-To: <20120417195749.L89206@shell.xecu.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.200.107] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: RE: FreeBSD 8.3-R sysinstall does not "see" disks that are recognized during boot 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: Wed, 18 Apr 2012 17:23:23 -0000 >---------- Forwarded message ---------- >Date: Tue, 17 Apr 2012 18:02:31 -0400 (EDT) >From: Andy Dills >To: freebsd-stable@freebsd.org >Subject: FreeBSD 8.3-R sysinstall does not "see" disks that are recognized > during boot > > >I've got a new supermicro server I'm trying to get FreeBSD on. It uses the >Intel c602 chipset, and it's my understanding that support for that >chipset (c60X) was recently added via the isci driver. Ok, great, that >explains why 8.2-R and 9.0-R didn't see the drives. > >So, I grabbed the memstick image of 8.3-RELEASE that is on the ftp server, >booted it up, and sure enough, as the dmesg scrolls I see it now properly >recognizes da0 and da1, as it should (the memstick is da2). It sees the >disks fine at this point, everything looks good. > >However, once the system finishes booting and loads into sysinstall, and I >go to partition the drives, I get "No disks found! Please verify that your >disk controller is being properly loaded at boot time". > >Any suggestions for avenues to troubleshoot this? I have pictures to >document if it helps. > >Seems very odd. I confirmed the behavior with the SATA set to IDE, AHCI, >and RAID modes. (The drives were recognized as da0 and da1 during bootup >in all three modes, but not by sysinstall.) Andy and I worked this out offline - workaround was to go to Options|Re-sca= n which caused the devices to show up in the sysinstall menu. I'm adding d= etails here for future reference. 1) C60x chipsets have the 6 traditional SATA ports, plus 4 or 8 SAS ports. = Only the latter are controlled by the isci(4) driver. 2) The IDE/AHCI/RAID modes apply only to the traditional SATA ports. 3) In Andy's case, going to Options|Re-scan Devices caused the disks to sho= w up. This problem seems to be system or platform-dependent, as I was not = able to reproduce with 8.3 memstick image on my C600 systems. 4) There was a problem with initial device scan using isci(4) on 7-STABLE, = which necessitated r233371. This was MFC'd back to 8-STABLE, but after 8.3= was released. I'm fairly convinced this is the root cause of Andy's probl= em, but don't have any easy way to verify. >Thanks, >Andy > >--- >Andy Dills >Xecunet, Inc. >www.xecu.net >301-682-9972 >---