From owner-freebsd-current Wed Mar 22 18:16:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from Kharma.Nextshift.Net (kharma.nextshift.net [216.200.15.16]) by hub.freebsd.org (Postfix) with ESMTP id 205F337B582; Wed, 22 Mar 2000 18:16:25 -0800 (PST) (envelope-from eric@clickrebates.com) Received: from clickrebates.com (adsl-63-197-30-140.dsl.snfc21.pacbell.net [63.197.30.140]) by Kharma.Nextshift.Net (8.9.3/8.9.0) with ESMTP id SAA13033; Wed, 22 Mar 2000 18:16:22 -0800 (PST) Message-ID: <38D97E76.BAD2FCF6@clickrebates.com> Date: Wed, 22 Mar 2000 18:16:22 -0800 From: Eric Sabban X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Forrest Aldrich Cc: freebsd-current@freebsd.org, freebsd-questions@freebsd.org Subject: Re: 4.0 sysinstall fails to recognize disks References: <4.3.1.2.20000322144026.00bb1c40@216.67.12.69> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try low-levelling the drives. The behavior sounds similar to what I had a long time ago, low level formatting them fixed the problem. -eric Forrest Aldrich wrote: > Since this is a fairly current issue, I'm posting this appropriately. > > I have a DELL server that has hooked up to it a PowerVault, with 8 36gb 10krpm LVD drives. The system has recognized these previously and dmesg shows them present; however, /stand/sysinstall says that I don't have ANY disks installed when using Label or Fdisk. > > Is this a known bug? I've done a buildworld/installworld yesterday after a cvsup. > > TIA. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message