Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 May 2005 21:29:55 -0700 (PDT)
From:      Doug White <dwhite@gumbysoft.com>
To:        rduffner <rduffner@ip-tech.ch>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: Problem booting 5.4
Message-ID:  <20050514212943.L49081@carver.gumbysoft.com>
In-Reply-To: <20050514201952.31416.qmail@blade1-3.iptech.localdomain>
References:  <4283862D.1060401@ip-tech.ch> <20050513152513.Y30976@carver.gumbysoft.com> <20050514201952.31416.qmail@blade1-3.iptech.localdomain>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 14 May 2005, rduffner wrote:

> Doug White writes:
>
> > 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!
>
>
> I booted from CD and ran the boot0cfg "offline" - however, this worked only
> on one server. I have two more identical servers that now just beep
> endlessly at the F1-prompt.
> I was told it is a geometry problem, but what else can I do?

boot0cfg -o packet adX

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050514212943.L49081>