From owner-freebsd-stable@FreeBSD.ORG Mon Nov 13 13:16:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 C093916A4D1 for ; Mon, 13 Nov 2006 13:16:46 +0000 (UTC) (envelope-from ivoras@geri.cc.fer.hr) Received: from geri.cc.fer.hr (geri.cc.fer.hr [161.53.72.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC0B843D68 for ; Mon, 13 Nov 2006 13:15:06 +0000 (GMT) (envelope-from ivoras@geri.cc.fer.hr) Received: from geri.cc.fer.hr (localhost.cc.fer.hr [127.0.0.1]) by geri.cc.fer.hr (8.13.6/8.13.6) with ESMTP id kADDErYo009782; Mon, 13 Nov 2006 14:14:53 +0100 (CET) (envelope-from ivoras@geri.cc.fer.hr) Received: from localhost (ivoras@localhost) by geri.cc.fer.hr (8.13.6/8.13.6/Submit) with ESMTP id kADDEm2f009775; Mon, 13 Nov 2006 14:14:48 +0100 (CET) (envelope-from ivoras@geri.cc.fer.hr) Date: Mon, 13 Nov 2006 14:14:48 +0100 (CET) From: Ivan Voras To: Pete French In-Reply-To: Message-ID: <20061113141033.Y9445@geri.cc.fer.hr> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Cruel and unusual problems with Proliant ML350 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 13:16:46 -0000 On Mon, 13 Nov 2006, Pete French wrote: >> There's something unusual going on and I don't know what else to try. >> Finally, after fiddling with various options, I've sort-of got it to >> work by creating two slices (s1, s2), setting root partition on s1a and >> the rest (/usr, /var, etc.) on s2. Now, the "F1 prompt" boot stage >> behaves like this: > > [snip] > > This sounds similar to a Compaq machine I used to have with a SMART RAID > in it. I had 3 drives - a SCSI, and two on the RAID. It would beep > at F1 as well. I had to press F5 3 times to cycle through all the drives, > but then when I got back to the original I could press F1 and it would now > boot fine. > > I never solved it, aand eventually changed machine (though not the > hardware). At the time it did not matter so much as the machine was > a server so when booted would just run until it manually needed to be > restarted. Hmm, it looks like it's a bug in boot0. I've replaced it with ports/sysutils/extipl and the machine boots fine now. Btw. I can confirm extipl works on amd64, so ONLY_FOR_ARCHS line can be updated now. Grub still doesn't. -- Things Mr Welch Cannot Do During An RPG: 135. I cannot demand payment in electrum, backrubs or bubblewrap.