Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Oct 2019 21:43:34 +1030
From:      "O'Connor, Daniel" <darius@dons.net.au>
To:        Kurt Jaeger <pi@freebsd.org>
Cc:        freebsd-current@freebsd.org, Nenhum_de_Nos <matheus@arroway.org>
Subject:   Re: Lockdown adaX numbers to allow booting ?
Message-ID:  <C0F004AD-4158-4685-B906-3D24D0D21527@dons.net.au>
In-Reply-To: <20191014083858.GE37504@home.opsec.eu>
References:  <bb5dabdf47005047a105f935a90f4dee@pyret.net> <373a3baccca14285d433fccf20bd1a38.squirrel@net.dyn.arroway.org> <20191013164746.GD37504@home.opsec.eu> <F50C5E14-D6AF-4300-9F49-AD4DAB9E00D3@dons.net.au> <20191014083858.GE37504@home.opsec.eu>

next in thread | previous in thread | raw e-mail | index | archive | help


> On 14 Oct 2019, at 19:08, Kurt Jaeger <pi@freebsd.org> wrote:
>=20
> Hi!
>=20
>>>>> You're probably looking for this:
>>>>> =
https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html
>>>>=20
>>>> Would glabel solve it?
>>>=20
>>> The disks are not gpart-formatted, they are used raw.
>>=20
>> What file system are they formatted with?
>=20
> ZFS, see
>=20
> =
https://lists.freebsd.org/pipermail/freebsd-current/2019-September/074398.=
html

Given this:
=
https://lists.freebsd.org/pipermail/freebsd-current/2019-September/074395.=
html

I think your problem is far earlier than changing ada probe order will =
help.

It would seem more likely to be a BIOS or BTX problem :(

I would definitely try moving ada0 and ada1 to the first SATA ports to =
see if that helps.

Does anything show up on the VGA console?

--
Daniel O'Connor
"The nice thing about standards is that there
are so many of them to choose from."
 -- Andrew Tanenbaum





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C0F004AD-4158-4685-B906-3D24D0D21527>