From owner-freebsd-questions Fri Dec 15 12: 5:36 2000 From owner-freebsd-questions@FreeBSD.ORG Fri Dec 15 12:05:33 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from fremont.bolingbroke.com (adsl-216-102-90-210.dsl.snfc21.pacbell.net [216.102.90.210]) by hub.freebsd.org (Postfix) with ESMTP id A35F737B402 for ; Fri, 15 Dec 2000 12:05:32 -0800 (PST) Received: from fremont.bolingbroke.com (fremont.bolingbroke.com [216.102.90.210]) by fremont.bolingbroke.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id eBFK50A61557; Fri, 15 Dec 2000 12:05:00 -0800 (PST) Date: Fri, 15 Dec 2000 12:05:00 -0800 (PST) From: Ken Bolingbroke To: Slade Edmonds Cc: questions@FreeBSD.ORG Subject: Re: No disks found! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 15 Dec 2000, Slade Edmonds wrote: > When using sysinstall to label a disk that has been recognized by the > system (verified via dmesg) I get the message "No Disks Found!" I > have done some reading and folks have found this to be a problem after > upgrading a machine and being left with an old sysinstall. Their fix > was to simply upgrade the sysinstall program. This machine is a fresh > install of 4.1.1. I went ahead and recompiled to get the sysinstall > binary anyway but of course it didn't work. Any ideas what is going > on? I had this problem after an upgrade in which the disk naming scheme went from wdX to adX. In my case, upgrading sysinstall fixed the problem. I don't have any idea why that doesn't work for you, but the root problem is probably that sysinstall isn't looking for the same type of disks as your kernel is configured for--sysinstall looking for wd0, when the kernel is using ad0, or vice versa. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message