From owner-freebsd-stable@FreeBSD.ORG Tue Jun 15 16:17:48 2004 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 8562816A4CE for ; Tue, 15 Jun 2004 16:17:48 +0000 (GMT) Received: from mail.datausa.com (mail.datausa.com [216.150.220.134]) by mx1.FreeBSD.org (Postfix) with SMTP id 22AD343D41 for ; Tue, 15 Jun 2004 16:17:48 +0000 (GMT) (envelope-from freebsd@wcubed.net) Received: (qmail 49959 invoked from network); 15 Jun 2004 16:16:09 -0000 Received: from web.datausa.com (HELO webmail.wcubed.net) (216.150.220.132) by mail.datausa.com with SMTP; 15 Jun 2004 16:16:09 -0000 Received: from 24.9.172.8 (SquirrelMail authenticated user freebsd@wcubed.net) by webmail.wcubed.net with HTTP; Tue, 15 Jun 2004 10:15:43 -0600 (MDT) Message-ID: <2398.24.9.172.8.1087316143.squirrel@webmail.wcubed.net> Date: Tue, 15 Jun 2004 10:15:43 -0600 (MDT) From: "Brad Waite" To: freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.4.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Subject: 4.10-STABLE boot issues 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: Tue, 15 Jun 2004 16:17:48 -0000 Hi all. I just installed 4.10 (and upgraded to 4.10-STABLE) on a 2 x 9GB SCSI disk AMI MegaRAID array (RAID0). I set up slices as I have previously with 30GB+ IDE drives: 1GB swap 29GB / Fdisk, label and the rest of install went fine, as did the update, but on all reboots (even before the update) I got the following error: Disk error 0x1 (lba=0x21fc09f) No /boot/loader >>> FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: If I hit enter, it spit out this error: WARNING: loader(8) metadata is missing! and continued the boot process. After finding all the devices, including the RAID controller (amr0) and the logical drive (amrd0), it displayed a 'mountroot>' prompt. If I gave it the logical drive slice a: (ufs:/dev/amrd0s1a) it finished the boot. I got around the problem by doing two things: 1. Created a /boot.config containing "0:da(0,a)/kernel" After doing this, the boot2 stopped complaining about a missing /boot/loader, which makes sense because I'm telling it to load /kernel instead of /boot/loader. 2. Built a new kernel and defined ROOTDEVNAME=\"ufs:amrd0s1a\" Now I'm no longer prompted to specify the root slice. So things are good. My machine boots w/out interaction. But I'm still perplexed as to why it didn't before. If boot2 can find /kernel, why can't it find /boot/loader? To further investigate, I copied /boot/loader to / and changed /boot.config to '0:da(0,a)/loader' and whaddya know? It now runs the BTX loader properly. So what's going on? Can anyone answer this stumper? Thanks, Brad