From owner-freebsd-questions@FreeBSD.ORG Sat Jul 19 07:41:03 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4452137B401 for ; Sat, 19 Jul 2003 07:41:03 -0700 (PDT) Received: from mail.speakeasy.net (mail14.speakeasy.net [216.254.0.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95F0243F3F for ; Sat, 19 Jul 2003 07:41:02 -0700 (PDT) (envelope-from cscott@speakeasy.net) Received: (qmail 27711 invoked by uid 64014); 19 Jul 2003 14:41:02 -0000 Received: from cscott@speakeasy.net by mail14.speakeasy.net with AmikaGuardian-Server-2.0.0 (Processed in 0.984216 secs); 19 Jul 2003 14:41:02 -0000 X-AmikaGuardian-Id: mail14.speakeasy.net105862566123627708 X-AmikaGuardian-Category: AN:Urgency : 0.01 X-AmikaGuardian-Category: AN:Spam Language : 0.01 X-AmikaGuardian-Category: AN:Junk Mail : 0.01 X-AmikaGuardian-Category: AN:Spam : 0.01 X-AmikaGuardian-Action: Do Nothing() Received: from unknown (HELO nero) (cscott@[67.73.150.174]) (envelope-sender ) by mail14.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 19 Jul 2003 14:41:01 -0000 Message-ID: <002401c34e04$e5040ef0$0801a8c0@nero> From: "Casey Scott" To: Date: Sat, 19 Jul 2003 09:48:59 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: booting problem after installation of new disk controller X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 14:41:03 -0000 I recently added a new disk controller (promise ultra 133) to act as a replacement for the motherboard's controller. I also moved everything from the systems old hard drive to a new hard drive. All is well, except that I can not boot any kernel other than the one specified in /boot/defaults/loader.conf For example, if "kernel.GENERIC" is specified in /boot/defaults/loader.conf, it can boot that without a problem. However, if that entry is switched to "kernel", and I can no longer interrupt the boot, and boot kernel.GENERIC. (situation exists with any good kernel as long as its not declared in loader.conf). At the beginning of the boot of an alternate kernel, the system displays a message "WARNING: loader(8) metadata is missing!". It will continue booting until it gets to the point where it mounts root. At that point, the mount fails, and manually mounting the correct partition (ufs:/dev/ad4s1a) fails also. When booting the kernel specified, it does display what appears to be the metadata, the BTX info on the A and C partitions, etc. I have already done an fdisk -B -b, boot0cfg -B -s 1 to the new drive. The old drive, on the new controller CAN boot alternate kernels without a problem! What have I missed?? Regards, Casey