From owner-freebsd-questions Tue Apr 10 1:32: 4 2001 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id B8C5A37B422 for ; Tue, 10 Apr 2001 01:32:01 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id f3A8Vos73019; Tue, 10 Apr 2001 01:31:50 -0700 (PDT) Date: Tue, 10 Apr 2001 01:31:50 -0700 (PDT) From: Doug White To: Greg Lehey Cc: Danny Howard , FreeBSD Questions Subject: Re: fdisk & disklabel dont work! In-Reply-To: <20010410113808.K64481@wantadilla.lemis.com> Message-ID: X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Apr 2001, Greg Lehey wrote: > > This is great, except the system will then refuse to boot. PXE boot > > crashes and SCSI boot hangs, and the explanation I can find is that > > the Adaptec controller is pissed off about the dangerously dedicated > > mode and ends up diving by zero. > > That's maybe the explanation you can find, but I doubt it's correct. > I have lots of dedicated installations running with Adaptec host > adaptors, and it works fine. But there are other Adaptec controllers (eg, those built on the Intel L440GX+ motherboard) that do _not_ work in a dedicated situation. My advice is to play it safe and put a proper slice table on. fdisk -I is quite handy for this, assuming there's nothing on the disk you care about. :) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message