From owner-freebsd-questions@FreeBSD.ORG Thu Apr 10 09:30:49 2003 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 2049137B401 for ; Thu, 10 Apr 2003 09:30:49 -0700 (PDT) Received: from scuff.cc.utexas.edu (scuff.cc.utexas.edu [128.83.135.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AE2C43F75 for ; Thu, 10 Apr 2003 09:30:48 -0700 (PDT) (envelope-from osilva@scuff.cc.utexas.edu) Received: from chepe.mail.utexas.edu (chepe.cc.utexas.edu [128.83.135.25]) by scuff.cc.utexas.edu (8.11.6/8.11.2) with ESMTP id h3AGUkE23938 for ; Thu, 10 Apr 2003 11:30:47 -0500 Message-Id: <5.1.0.14.2.20030410112027.020f0588@scuff.cc.utexas.edu> X-Sender: osilva@scuff.cc.utexas.edu X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 10 Apr 2003 11:28:40 -0500 To: questions@freebsd.org From: Oscar Ricardo Silva Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: mountroot prompt after new install of FreeBSD 4.8 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: Thu, 10 Apr 2003 16:30:49 -0000 I just installed FreeBSD 4.8 on a Dell PowerEdge 2650 with a RAID controller, 5 hard drives. After the install (which went off without a problem), I rebooted the machine and got: aac0: mem 0xf0000000-0xf7ffffff irq 16 at device 8.1 on pci4 aac0: i960RX 100MHz, 118MB cache memory, optional battery present aac0: Kernel 2.7-1, Build 3170, S/N 4441d3 acd0: CDROM at ata0-master PIO4 aacd0: on aac0 aacd0: 38912MB (79691776 sectors) aacd1: on aac0 aacd1: 30510MB (62486016 sectors) Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0s1a ? List valid disk boot devices Abort manual input mountroot> If I then type: mountroot> ufs:/dev/aacd0s1a Mounting root from ufs:/dev/aacd0s1a The machine boots fine. I've seen many questions about this same problem but no real solution. I've encountered this same problem on other machines but was able to solve it by moving the boot drive from ATA66 to ATA33 controller. Can't do that here. So what's going on here? Why do I get this prompt after a brand new install? I've tried recompiling the kernel and support for the RAID controller was built into it. I've tried creating /boot/loader.conf with the content: rootdev="aacd0s1a" # Set the root filesystem Oscar