Date: Tue, 12 Aug 2014 09:32:36 -0700 From: Barney Cordoba <barney_cordoba@yahoo.com> To: "current@freebsd.org" <current@freebsd.org> Subject: Booting a SuperMicro Superserver Message-ID: <1407861156.35826.YahooMailNeo@web121606.mail.ne1.yahoo.com>
next in thread | raw e-mail | index | archive | help
A continuing issue (with 9.1 previously and now 10) is that FreeBSD occasio= nally (or always) seems to boot from the 2nd installed drive=0Arather than = the first. I'd be happy to debug this, but I have no idea if it's bootcode = or a BIOS issue. Supermicro pleads innocent, but their bios=0Aguys are hard= to work with and fairly arrogant if you don't specifically isolate somethi= ng.=0A=0AThe scenario occurs when ada0 is upgraded and has an incompatible = kernel with other code on drive ada1. =A0(note that ada1 is a backup of the= pre-upgrade ada0,=A0so it's fstab points to ada0 for mount points). The sy= stem will boot and then modules will fail to load. It loads the kernel from= =0A=A0ada1 and then mounts partitions from ada0; old kernel and newer modul= es.=0A=0AThe problem is resolved by popping the 2nd drive. So there is noth= ing wrong with ada0 to cause it to bounce to ada1.=0A=0AMy question: What w= ould cause the system to boot from ada1 instead of ada0? Bios or Bootcode?= =0A=0AThanks.=0A=0ABC From owner-freebsd-current@FreeBSD.ORG Tue Aug 12 18:09:48 2014 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 74606152 for <current@freebsd.org>; Tue, 12 Aug 2014 18:09:48 +0000 (UTC) Received: from nm6-vm4.bullet.mail.ne1.yahoo.com (nm6-vm4.bullet.mail.ne1.yahoo.com [98.138.91.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 347EB39E4 for <current@freebsd.org>; Tue, 12 Aug 2014 18:09:47 +0000 (UTC) Received: from [98.138.100.102] by nm6.bullet.mail.ne1.yahoo.com with NNFMP; 12 Aug 2014 18:09:40 -0000 Received: from [98.138.226.164] by tm101.bullet.mail.ne1.yahoo.com with NNFMP; 12 Aug 2014 18:09:40 -0000 Received: from [127.0.0.1] by omp1065.mail.ne1.yahoo.com with NNFMP; 12 Aug 2014 18:09:40 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 227136.9082.bm@omp1065.mail.ne1.yahoo.com Received: (qmail 91670 invoked by uid 60001); 12 Aug 2014 18:09:40 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1407866980; bh=hE9luXFVTXRDYjMIQfbhUV7txZf8Q2E4waM9KXDo2aw=; h=References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=6SSpLxVvgEdQIH2XmA5nPSp43V+7lqrCDnJhUtMPaCJm5Hg4ieUG2oLttLsUa1kr1UpXhtVyjvuwbN8XQE4Rx4RoKA+C4vCwHt/iFXKg2aotRIi7E4NiG96ywc7PD+BqiMa3A5GiXj51pQZhtJEjYx6hT+W69AFZL84k1Asc7Ys= X-YMail-OSG: O_k1JSIVM1mdFWFhrhEiKVXbk3oJhUvMJ5zhHpi1pS72vNh ijHrt19HkTw8WE2bV34rgz.MtLLKk7C.na7ezjImyO2Giq3dwnSSmDpqqa3H D.73s6PsDooWnEBNa2hGlRcBSKDo5_r5V4dbKghZNu7VWBlSnK4jcw8DPP6t DuqHFwGjCNcmxl0k3mnJcEXz5FgWGMMERchUJg4dd2vVrpqxHK7SFGUyJYfn fcC74g6hDW5WKl3Gmbu1Jl._94QvDRWAxIjNRjJ.4hljZ0LizamJHp1Wbs1n o3c8cDPEVnm18Bs9yIsnddfrQPkxdlrxsYAD4ruwC3ce3AvjcLYQfcb1d2y4 IUCEl9nnLVMyOHJA5ozoLJRJnxJC7rRLrJ0BHGGNPaiG3Do4WD63X3clH3Ek 2teRWNDC1S3pT0yJxmKY_sRBhhoUMeBG7K9u0XTYzkcpapg09OSuBAMsDJwZ h2GVaIrY3NyiY7.ZWf78sGvqSZLTags9a374alM_TOXfjKtS_LHwBa3CgOzQ fDZAVC61FPcZj9pdzoNQDSzvQcp1pfx5TY7sgb7Oespc6TLqf_g7VvqmoWmH WNIg- Received: from [76.108.181.232] by web121604.mail.ne1.yahoo.com via HTTP; Tue, 12 Aug 2014 11:09:39 PDT X-Rocket-MIMEInfo: 002.001, VGhlIGJpb3Mgb25seSBnaXZlcyB5b3Ugb25lIGNob2ljZSBmb3IgIkhERCIuIFlvdSBjYW4ndCBzZWxlY3Qgb25lIG9mIHRoZSA0IGRyaXZlcyB0byBib290IGZyb20uIFlvdSBjYW4gc3BlY2lmeSBVU0Igb3IgQ0Qgb3IgSERELCBidXQgTm90IEhERDIgb3IgSEREMy4KCkJDCgoKT24gVHVlc2RheSwgQXVndXN0IDEyLCAyMDE0IDE6MTYgUE0sIEpvaG4gTmllbHNlbiA8bGlzdHNAam5pZWxzZW4ubmV0PiB3cm90ZToKIAoKCk9uIEF1ZyAxMiwgMjAxNCwgYXQgMTA6MzIgQU0sIEJhcm5leSBDb3Jkb2JhIDxiYXIBMAEBAQE- X-Mailer: YahooMailWebService/0.8.201.700 References: <1407861156.35826.YahooMailNeo@web121606.mail.ne1.yahoo.com> <0D393AB7-4632-4BF8-95A3-D8AF25D53E60@jnielsen.net> Message-ID: <1407866979.73449.YahooMailNeo@web121604.mail.ne1.yahoo.com> Date: Tue, 12 Aug 2014 11:09:39 -0700 From: Barney Cordoba <barney_cordoba@yahoo.com> Reply-To: Barney Cordoba <barney_cordoba@yahoo.com> Subject: Re: Booting a SuperMicro Superserver To: John Nielsen <lists@jnielsen.net> In-Reply-To: <0D393AB7-4632-4BF8-95A3-D8AF25D53E60@jnielsen.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "current@freebsd.org" <current@freebsd.org> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 12 Aug 2014 18:09:48 -0000 The bios only gives you one choice for "HDD". You can't select one of the 4= drives to boot from. You can specify USB or CD or HDD, but Not HDD2 or HDD= 3.=0A=0ABC=0A=0A=0AOn Tuesday, August 12, 2014 1:16 PM, John Nielsen <lists= @jnielsen.net> wrote:=0A =0A=0A=0AOn Aug 12, 2014, at 10:32 AM, Barney Cord= oba <barney_cordoba@yahoo.com> wrote:=0A=0A=0A> A continuing issue (with 9.= 1 previously and now 10) is that FreeBSD occasionally (or always) seems to = boot from the 2nd installed drive=0A> rather than the first. I'd be happy t= o debug this, but I have no idea if it's bootcode or a BIOS issue. Supermic= ro pleads innocent, but their bios=0A> guys are hard to work with and fairl= y arrogant if you don't specifically isolate something.=0A> =0A> The scenar= io occurs when ada0 is upgraded and has an incompatible kernel with other c= ode on drive ada1.=A0 (note that ada1 is a backup of the pre-upgrade ada0, = so it's fstab points to ada0 for mount points). The system will boot and th= en modules will fail to load. It loads the kernel from=0A>=A0 ada1 and then= mounts partitions from ada0; old kernel and newer modules.=0A> =0A> The pr= oblem is resolved by popping the 2nd drive. So there is nothing wrong with = ada0 to cause it to bounce to ada1.=0A> =0A> My question: What would cause = the system to boot from ada1 instead of ada0? Bios or Bootcode?=0A=0ABIOS, = most likely. If the disk controller in question is onboard you should be ab= le to specify which disk(s) and what order they will be booted from. If not= , you'll need to just say <disk controller> in the BIOS boot order then go = to the controllers BIOS to say which disk(s) to boot from and in what order= . I have recent experience with a SuperMicro box and an LSI controller; the= latter allows you to specify a (b)oot drive and an (a)lternate. Yes, b com= es before a. :)=0A=0AJN From owner-freebsd-current@FreeBSD.ORG Tue Aug 12 18:12:04 2014 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 501A3C12 for <current@freebsd.org>; Tue, 12 Aug 2014 18:12:04 +0000 (UTC) Received: from secure.freebsdsolutions.net (secure.freebsdsolutions.net [69.55.234.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AE3B42EED for <current@freebsd.org>; Tue, 12 Aug 2014 17:21:47 +0000 (UTC) Received: from [10.10.1.198] (office.betterlinux.com [199.58.199.60]) (authenticated bits=0) by secure.freebsdsolutions.net (8.14.4/8.14.4) with ESMTP id s7CHGkMl075721 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 12 Aug 2014 13:16:47 -0400 (EDT) (envelope-from lists@jnielsen.net) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Booting a SuperMicro Superserver From: John Nielsen <lists@jnielsen.net> In-Reply-To: <1407861156.35826.YahooMailNeo@web121606.mail.ne1.yahoo.com> Date: Tue, 12 Aug 2014 11:16:49 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <0D393AB7-4632-4BF8-95A3-D8AF25D53E60@jnielsen.net> References: <1407861156.35826.YahooMailNeo@web121606.mail.ne1.yahoo.com> To: Barney Cordoba <barney_cordoba@yahoo.com> X-Mailer: Apple Mail (2.1878.6) X-DCC-MGTINTERNET-Metrics: ns1.jnielsen.net 1170; Body=2 Fuz1=2 Fuz2=2 X-Virus-Scanned: clamav-milter 0.97.8 at ns1.jnielsen.net X-Virus-Status: Clean Cc: "current@freebsd.org" <current@freebsd.org> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 12 Aug 2014 18:12:04 -0000 On Aug 12, 2014, at 10:32 AM, Barney Cordoba <barney_cordoba@yahoo.com> = wrote: > A continuing issue (with 9.1 previously and now 10) is that FreeBSD = occasionally (or always) seems to boot from the 2nd installed drive > rather than the first. I'd be happy to debug this, but I have no idea = if it's bootcode or a BIOS issue. Supermicro pleads innocent, but their = bios > guys are hard to work with and fairly arrogant if you don't = specifically isolate something. >=20 > The scenario occurs when ada0 is upgraded and has an incompatible = kernel with other code on drive ada1. (note that ada1 is a backup of = the pre-upgrade ada0, so it's fstab points to ada0 for mount points). = The system will boot and then modules will fail to load. It loads the = kernel from > ada1 and then mounts partitions from ada0; old kernel and newer = modules. >=20 > The problem is resolved by popping the 2nd drive. So there is nothing = wrong with ada0 to cause it to bounce to ada1. >=20 > My question: What would cause the system to boot from ada1 instead of = ada0? Bios or Bootcode? BIOS, most likely. If the disk controller in question is onboard you = should be able to specify which disk(s) and what order they will be = booted from. If not, you'll need to just say <disk controller> in the = BIOS boot order then go to the controllers BIOS to say which disk(s) to = boot from and in what order. I have recent experience with a SuperMicro = box and an LSI controller; the latter allows you to specify a (b)oot = drive and an (a)lternate. Yes, b comes before a. :) JN
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1407861156.35826.YahooMailNeo>