From owner-freebsd-current@FreeBSD.ORG Sun Jun 28 12:46:56 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27D23106564A for ; Sun, 28 Jun 2009 12:46:56 +0000 (UTC) (envelope-from ken@tydfam.jp) Received: from tydfam.jp (ns.tydfam.jp [61.197.228.42]) by mx1.freebsd.org (Postfix) with ESMTP id C94B78FC15 for ; Sun, 28 Jun 2009 12:46:55 +0000 (UTC) (envelope-from ken@tydfam.jp) Received: from localhost (tyd3.sub.tydfam.jp [192.168.1.3]) by tydfam.jp (8.14.2/8.14.2) with ESMTP id n5SCksjK061751; Sun, 28 Jun 2009 21:46:55 +0900 (JST) (envelope-from ken@tydfam.jp) Date: Sun, 28 Jun 2009 21:44:17 +0900 (JST) Message-Id: <20090628.214417.598552788769548331.ken@tydfam.jp> To: doconnor@gsoft.com.au From: ken In-Reply-To: <200906252320.32544.doconnor@gsoft.com.au> References: <200906252011.42597.doconnor@gsoft.com.au> <20090625.202617.598552788702437664.ken@tydfam.jp> <200906252320.32544.doconnor@gsoft.com.au> X-Mailer: Mew version 6.2 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=9.5 tests=ALL_TRUSTED autolearn=failed version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on daemon.sub.tydfam.jp Cc: freebsd-current@freebsd.org, admin@kkip.pl Subject: Re: 8.0-current cannot find disk!! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jun 2009 12:46:56 -0000 From: "Daniel O'Connor" > From what I can see it finds ad10 (Hitachi 100Gb on ata5) and ad12 (WD > 100Gb on ata6) disks.. > > ata5 & ata6 are on the JMicron JMB363. > > The question is why sysinstall thinks there are no disks :( > > What happens if you open a Fixit emergency holographic shell and run > echo /dev/ad* I took a little different approach because it looks to be not only sysinstall problem; a) create 7.2R and update src to -current. b) make buildworld && make installworld && make buildkernel && make installkernel c) reboot d) See what happens..... The result is at http://www.tydfam.jp/experimental/boot_photo2/. They are photos ordered by the sequence. And the last one showes 'db > where' result that says something is wrong at malloc_init!! I'll try what you are suggesting tomorrow..