From owner-freebsd-questions@FreeBSD.ORG Sat Aug 7 05:11:35 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 2876416A4CE for ; Sat, 7 Aug 2004 05:11:35 +0000 (GMT) Received: from ns1.tiadon.com (SMTP.tiadon.com [69.27.132.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id D62E043D5A for ; Sat, 7 Aug 2004 05:11:34 +0000 (GMT) (envelope-from kdk@daleco.biz) Received: from [69.27.131.0] ([69.27.131.0]) by ns1.tiadon.com with Microsoft SMTPSVC(6.0.3790.0); Sat, 7 Aug 2004 00:07:58 -0500 Message-ID: <41146483.8050908@daleco.biz> Date: Sat, 07 Aug 2004 00:11:31 -0500 From: "Kevin D. Kinsey, DaleCo, S.P." User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040712 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Spumonti References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 07 Aug 2004 05:07:59.0099 (UTC) FILETIME=[81CFFCB0:01C47C3C] cc: freebsd-questions@freebsd.org Subject: Re: installation of FreeBSD 4.10 on Dell PowerEdge 650 fails after reboot with mountroot 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: Sat, 07 Aug 2004 05:11:35 -0000 Spumonti wrote: >The disk is a Seagate 120GB and it's actually ad4, not ad0. If I >interrupt the boot process at: > > > >>>FreeBSD/i386 BOOT >>> >>> >Default: 0:ad(0,a)/kernel >boot: > >and enter: > > > >>>FreeBSD/i386 BOOT >>> >>> >Default: 0:ad(0,a)/kernel >boot: 0:ad(4,a)/kernel > >the machine will boot properly. I've tried two things I found while >checking on this: > >1. Adding to loader.conf: >rootdev="disk4s1a" >root_disk_unit=0" > >2. Rebuilding the kernel and adding: >options ROOTDEVNAME=\"ufs:ad4s1a\" > > >Neither of which worked. Is there something I'm missing while doing >the installation? If I look in /dev the devices are there ad4, >ad4s1, ad4s1a, ad4s1b, etc. > >About at wit's end ... any help would be great. > > Is this the only disk in the box? Why is it ad4 instead of ad0? That's at issue, but maybe it's not as bad as pulling out your hair... It might be possible to "fix it" without changing disk numbers by adding the following to /boot/loader.conf: set root_disk_unit=4 boot /kernel See loader(8) for details. That said, I'm no expert on loader(8) et al. But that's what the docs say, anyway. HTH, Kevin Kinsey DaleCo, S.P.