From owner-freebsd-stable@FreeBSD.ORG Wed Apr 18 07:14:12 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 687D7106564A for ; Wed, 18 Apr 2012 07:14:12 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id B9BE08FC0A for ; Wed, 18 Apr 2012 07:14:11 +0000 (UTC) Received: from ur.gsoft.com.au (Ur.gsoft.com.au [203.31.81.55]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id q3I6iOLL001094 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 18 Apr 2012 16:14:29 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=us-ascii From: "Daniel O'Connor" In-Reply-To: <20120417175405.X89206@shell.xecu.net> Date: Wed, 18 Apr 2012 16:14:23 +0930 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20120417175405.X89206@shell.xecu.net> To: Andy Dills X-Mailer: Apple Mail (2.1257) X-Spam-Score: -2.51 () ALL_TRUSTED,BAYES_00,T_RP_MATCHES_RCVD X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: FreeBSD Stable Mailing List 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 07:14:12 -0000 On 18/04/2012, at 7:32, Andy Dills wrote: > I've got a new supermicro server I'm trying to get FreeBSD on. It uses = the=20 > Intel c602 chipset, and it's my understanding that support for that=20 > chipset (c60X) was recently added via the isci driver. Ok, great, that=20= > explains why 8.2-R and 9.0-R didn't see the drives. >=20 > So, I grabbed the memstick image of 8.3-RELEASE that is on the ftp = server,=20 > booted it up, and sure enough, as the dmesg scrolls I see it now = properly=20 > recognizes da0 and da1, as it should (the memstick is da2). It sees = the=20 > disks fine at this point, everything looks good. >=20 > However, once the system finishes booting and loads into sysinstall, = and I=20 > go to partition the drives, I get "No disks found! Please verify that = your=20 > disk controller is being properly loaded at boot time". >=20 > Any suggestions for avenues to troubleshoot this? I have pictures to=20= > document if it helps. >=20 > Seems very odd. I confirmed the behavior with the SATA set to IDE, = AHCI,=20 > and RAID modes. (The drives were recognized as da0 and da1 during = bootup=20 > in all three modes, but not by sysinstall.) That does seem very odd - if they appear as daX then sysinstall should = see them. Can you go into the holographic shell (or livecd if you have it) and = run.. echo /dev/da* echo >/dev/da0 echo >/dev/da1 (this will trash the first sector of da0 and da1 but I assume that's OK = since you're installing on those). If you could obtain a KLD for isci built for 9.0 you could load it in = the loader and see if that installer sees it, you might not have the = facilities for that though.. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C