Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Aug 2014 14:25:29 -0400
From:      Allan Jude <allanjude@freebsd.org>
To:        freebsd-current@freebsd.org
Subject:   Re: Booting a SuperMicro Superserver
Message-ID:  <53EA5C19.4060604@freebsd.org>
In-Reply-To: <1407866979.73449.YahooMailNeo@web121604.mail.ne1.yahoo.com>
References:  <1407861156.35826.YahooMailNeo@web121606.mail.ne1.yahoo.com> <0D393AB7-4632-4BF8-95A3-D8AF25D53E60@jnielsen.net> <1407866979.73449.YahooMailNeo@web121604.mail.ne1.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--mmdOR6ibOUdCuFk9jr6dTROp2tJ6rV5VN
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2014-08-12 14:09, Barney Cordoba wrote:
> The bios only gives you one choice for "HDD". You can't select one of t=
he 4 drives to boot from. You can specify USB or CD or HDD, but Not HDD2 =
or HDD3.
>=20
> BC
>=20
>=20
> On Tuesday, August 12, 2014 1:16 PM, John Nielsen <lists@jnielsen.net> =
wrote:
> =20
>=20
>=20
> On Aug 12, 2014, at 10:32 AM, Barney Cordoba <barney_cordoba@yahoo.com>=
 wrote:
>=20
>=20
>> A continuing issue (with 9.1 previously and now 10) is that FreeBSD oc=
casionally (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 b=
ios
>> guys are hard to work with and fairly arrogant if you don't specifical=
ly isolate something.
>>
>> The scenario occurs when ada0 is upgraded and has an incompatible kern=
el 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 modu=
les.
>>
>> The problem is resolved by popping the 2nd drive. So there is nothing =
wrong with ada0 to cause it to bounce to ada1.
>>
>> My question: What would cause the system to boot from ada1 instead of =
ada0? Bios or Bootcode?
>=20
> BIOS, most likely. If the disk controller in question is onboard you sh=
ould 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 a=
nd in what order. I have recent experience with a SuperMicro box and an L=
SI controller; the latter allows you to specify a (b)oot drive and an (a)=
lternate. Yes, b comes before a. :)
>=20
> JN
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o=
rg"
>=20

There is usually a second menu after you select 'HDD' in the boot order
menu, something like 'HDD Boot Priority' that lets you select the
correct disk to boot from

http://s1121.photobucket.com/user/SleeperPro/media/BIOSBoot.jpg.html

So after you select 'HDD" in the 'boot device priority' menu, go to the
'hard disk drives' menu and set the order of the drives.

--=20
Allan Jude


--mmdOR6ibOUdCuFk9jr6dTROp2tJ6rV5VN
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJT6lwcAAoJEJrBFpNRJZKf9yYP/0hRvTXLrQV48YhDnK2tLYdo
18cGPvMKWOs1bySEqkJViUHFnCd5vhCC/whme5sPhcuUnJuT02lA/rUPfB0LN+BA
eK20y9tRHDDm3b0DGSDAymC+CsP8UhkBtPlZsZuhdjdskmPbHBPEUKZmmGPJJ9LN
bTeXU+SbPZxoAjYUcZYifOpwJaNua0vIkQfEHOxDP3jPETyXyG4gkObpxGPa8ZtD
2+kjog36peXqEaV1l5hzLM6RuzLbIIXYbJTUF2TNN/H71wpBfcqJIxMVV6OUWfUK
ybsA98qSkUNMepvK0QJnITLyffQj/7nyxDF3UNUKkU8kJtipvEmsuFhH4zKN7Pf3
TxjrW/AIQML/CFeGAjmP7+MY+INkXgM4xxgxHLD9cBAhKanLXJkCsUQwbYzXpDnr
XPvIT5MeVwOkOwG7IbNtkPNxFUSI6MYnj/O6YLYJYwb70Avq60mApscsG5XMXZmH
xYKJPAosHBWS58dikX1ajoU7070CVksGoR+szkPlGgLrgpX1Ad7hQpGQWFc60RFs
0TIZVfZHsfAV4OuZQH8A3BXuiL1Ho8nGIu7vjg6u0pNJY8eOlKyEZLDnBmcd55Ma
cLTqscGikueuaAYG96HP1KQMsfaOhB9DLB80nxU61i6n6CLkZQ6BOlU6Z9FGDFoZ
Li+Pa/LW8f+c8XVvZme+
=efU2
-----END PGP SIGNATURE-----

--mmdOR6ibOUdCuFk9jr6dTROp2tJ6rV5VN--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53EA5C19.4060604>