From owner-freebsd-stable@FreeBSD.ORG Fri May 13 22:26:55 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EACD016A4CE for ; Fri, 13 May 2005 22:26:55 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6D9B43D60 for ; Fri, 13 May 2005 22:26:55 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id CF9D172DD4; Fri, 13 May 2005 15:26:55 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id CAA0872DCB; Fri, 13 May 2005 15:26:55 -0700 (PDT) Date: Fri, 13 May 2005 15:26:55 -0700 (PDT) From: Doug White To: Rainer Duffner In-Reply-To: <4283862D.1060401@ip-tech.ch> Message-ID: <20050513152513.Y30976@carver.gumbysoft.com> References: <4283862D.1060401@ip-tech.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: Problem booting 5.4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2005 22:26:56 -0000 On Thu, 12 May 2005, Rainer Duffner wrote: > Hi, > > I installed FreeBSD5.4 on a server with a 3ware 7006-2 controller and > two 120GB disks as RAID1 > I cannot boot this install. (I get some kind of panic or endless loop, > but the display is re-painted so fast I cannot read it). > What I *can* do is insert my SuSE9.2-pro cd1, boot from that and at the > grub-menu say "boot from harddisk". > That boots FreeBSD. > > On advice from IRC, I tried: > # boot0cfg -B twed0 > > -which leads to this output > > boot0cfg: write_mbr: /dev/twed0: No such file or directory This is a erroneous message. The actual problem is: 484 boot0cfg NAMI "/dev/twed0" 484 boot0cfg RET open -1 errno 1 Operation not permitted This is a known problem with certain MBR layouts. To work around this problem, set: sysctl kern.geom.debugflags=16 then try your boot0cfg. There's a protection mechanism that sometimes gets confused by certain partition table layouts. Flag 16 disables that protection. I don't recommend running this unless you are explicitly trying to updating something in a partition table-like area; its very easy to destroy your system with the flag set! -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org