Re: Lockdown adaX numbers to allow booting ?

From: Kurt Jaeger <lists_at_opsec.eu>
Date: Thu, 19 Sep 2019 20:48:03 +0200
Hi!

> >> Also the question is, what you mean with ???system looses track????

> > I interpret the hang during boot as 'it looses track'. So I guess
> > it tries to read the kernel from the wrong drives.

> no, loader does probe disks to see which devices make up the pool and hung system is not about reading the kernel from wrong place.

> I bet it is BIOS system?

If you mean: no UEFI boot ? Yes, it boots via BIOS, not UEFI.

> Since the raidz seems to be created partitionless, what version
> of freebsd are you using?

FreeBSD 12.0p10, amd64.

> BIOS up to date?

The board is an X10SRi-F. dmidecode reports BIOS 3.1, supermicro
has 3.1c, but the release notes do not mention things like that
(or at least I don't understand them that way).

https://www.supermicro.com/en/products/motherboard/X10SRi-F

> can you test pool visibility in loader with latest current
> usb/cd start - like press esc in menu and check lsdev -v
> (assuming you get to menu) ? the same with uefi?

I will test this when I'm at the facility. Will take some time.

Thanks for the pointers!

-- 
pi_at_opsec.eu            +49 171 3101372                    One year to go !
Received on Thu Sep 19 2019 - 16:48:08 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:21 UTC