From owner-freebsd-net@FreeBSD.ORG Thu Jul 10 19:37:37 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 15222B96 for ; Thu, 10 Jul 2014 19:37:37 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E2BAE2C9C for ; Thu, 10 Jul 2014 19:37:36 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D684CB926; Thu, 10 Jul 2014 15:37:35 -0400 (EDT) From: John Baldwin To: freebsd-net@freebsd.org, Laurie Jennings Subject: Re: System Booting Kernel from Secondary Drive Date: Thu, 10 Jul 2014 13:16:00 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <1404396381.74461.YahooMailBasic@web125802.mail.ne1.yahoo.com> In-Reply-To: <1404396381.74461.YahooMailBasic@web125802.mail.ne1.yahoo.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201407101316.00803.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 10 Jul 2014 15:37:35 -0400 (EDT) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2014 19:37:37 -0000 On Thursday, July 03, 2014 10:06:21 am Laurie Jennings via freebsd-net wrote: > I'm having a problem with a Supermicro system running FreeBSD 9.1. Sometimes when I upgrade the kernel in my main drive (ada0), > the system boots the kernel from the 2nd drive. It only happens sometimes. ada0 is mounted. but the system is running the old kernel. > Pulling the 2nd fixed the problem. > > What can cause this to happen? Is it a supermicro problem (it's a 5017R-MTF superserver) or is it something with FreeBSD. Are you using a software RAID between the two disks? -- John Baldwin