From owner-freebsd-stable@FreeBSD.ORG Mon Nov 13 11:08:01 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 D5BBD16A492 for ; Mon, 13 Nov 2006 11:08:01 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D2B643D64 for ; Mon, 13 Nov 2006 11:08:01 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GjZfK-00056h-Oi for freebsd-stable@freebsd.org; Mon, 13 Nov 2006 12:07:50 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 13 Nov 2006 12:07:50 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 13 Nov 2006 12:07:50 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Mon, 13 Nov 2006 12:07:43 +0100 Lines: 39 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.4 (X11/20060625) In-Reply-To: Sender: news 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 11:08:01 -0000 Ivan Voras wrote: > - The showstopper: Sysinstall completes (though slowly), but on reboot > the loader doesn't go further than the "F1 prompt" :( This is very > curious, since when booting from install CD the loader shows it > recognizes the CD drive and drives A: and C:, so BIOS seems to be ok. If > I understand the loader correctly, after the "F1 prompt" phase, the > loader should transfer control to the boot block of the first slice? 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: - if I leave F1 to be the default, boot fails, beeping when trying to boot like before. Nothing changes when pressing F1 multiple time (it always fails and beeps). - if I leave F2 to be the default, boot fails with "invalid partition" message and escapes to the boot: prompt - if I press F1 and then F2, it beeps on F1 but after F2 is pressed it proceeds to boot from s1a! I really don't know what is going on. The disk array is supposed to be "clean", without hidden partitions (at least, fdisk doesn't see any). Is the loader re-reading the table after a failed boot (with F1), and something corrupts the data on first read? Or maybe it's a boot0 bug? Any ideas? As it stands, the machine can't boot unattended, which makes it unusable. More info: at the /boot/loader stage, lsdev shows disk0 as A:, but the floppy doesn't exist on this machine, and disk1 as C:, with normal partitions (e.g. disk1s1a, etc.)