From owner-freebsd-questions Mon Sep 11 18:23:35 2000 Delivered-To: freebsd-questions@freebsd.org Received: from smtp.screaming.net (smtp.screaming.net [212.49.224.20]) by hub.freebsd.org (Postfix) with ESMTP id 85C0F37B43E for ; Mon, 11 Sep 2000 18:23:29 -0700 (PDT) Received: from lexx.my.domain (dyn214-ras26.screaming.net [212.49.249.214]) by smtp.screaming.net (8.9.3/8.9.3) with SMTP id BAA29829 for ; Tue, 12 Sep 2000 01:26:24 GMT From: John Murphy To: questions@freebsd.org Subject: Re: Need MBR/boot to use da0 instead of da1 Date: Tue, 12 Sep 2000 02:23:08 +0100 Organization: The Organisation Reply-To: bigotfo@bigfoot.com Message-ID: X-Mailer: Forte Agent 1.6/32.525 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Nicholas wrote: >Hey all- >I have 2 SCSI disks on one adaptec SCSI card on my 4.1 Release version = BSD >box. I screwed up my install and accidentally put the MBR on the second >disk. I used the FreeBSD boot manager (booteasy-- ohh yeahh). My = kernel is >on the first disk on the first slice and when the boot loader comes up = it >defaults to 1:da(1,a)/kernel >When I specify 0:da(0,a)/kernel >I get it to boot up fine. Unfortunately this is going to be located >remotely and I need it to be able to boot correctly without = intervention. > >I have tried including > rootdev=3D"disk0s1a" >in my /boot/loader.conf file and that doesn't seem to make any = difference. I've seen answers to similar questions which seem to suggest that: curdev=3D"disk0s1a" may be what you want. HTH John. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message