From owner-freebsd-questions@FreeBSD.ORG Sun May 16 15:51:59 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79F7716A4CF for ; Sun, 16 May 2004 15:51:59 -0700 (PDT) Received: from crestone.coronasolutions.com (crestone.coronasolutions.com [66.45.104.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 114F743D46 for ; Sun, 16 May 2004 15:51:59 -0700 (PDT) (envelope-from fbsd@drivefaster.net) Received: from localhost (localhost [127.0.0.1]) by crestone.coronasolutions.com (Postfix) with ESMTP id C69DBBF87 for ; Sun, 16 May 2004 16:50:42 -0600 (MDT) Received: from crestone.coronasolutions.com ([127.0.0.1])port 10024) with ESMTP id 13731-06 for ; Sun, 16 May 2004 16:50:42 -0600 (MDT) Received: from [192.168.1.12] (c-24-9-24-35.client.comcast.net [24.9.24.35]) by crestone.coronasolutions.com (Postfix) with ESMTP id A1B89BDD0 for ; Sun, 16 May 2004 16:50:41 -0600 (MDT) Message-ID: <40A7F08B.6000804@drivefaster.net> Date: Sun, 16 May 2004 16:51:55 -0600 From: Dan Harris User-Agent: Mozilla Thunderbird 0.6 (Macintosh/20040502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at drivefaster.net Subject: md0: Preloaded image - system hangs on install X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 May 2004 22:51:59 -0000 Like the subject says.. I'm trying to install 5.2.1-RELEASE on a Compaq Proliant 6000 (dual Xeon, 1GB RAM, Compaq SCSI RAID). When booting the CD: It gets to this message: md0: Preloaded image (/boot/mfsroot) 4423680 bytes at 0xc09e16d8 at this point the system seems to hang with no recourse other than to restart. The CD is known good (just installed fine on the box next to it, different hardware), and this box is currently running another OS without any problems. Can anyone explain why this might fail and if I can do something about it? -Dan