Re: Lockdown adaX numbers to allow booting ?

On Thu, Sep 19, 2019 at 06:04:54PM +0200, Michael Gmelin wrote:

> 
> 
> > On 19. Sep 2019, at 17:57, Kurt Jaeger <lists_at_opsec.eu> wrote:
> > 
> > Hi!
> > 
> >>> We have a system with 10 SATA disks. 2 disks are for the system,
> >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes:
> >>> 
> >>> bck    72.8T  38.7T  34.1T        -         -     1%    53%  1.00x  ONLINE  -
> > 
> >>> The problem is that if all 10 disks are connected, the system
> >>> looses track from where it should boot and fails to boot (serial boot log):
> > 
> >> Why this order does change?  One would expect disks 0 and 1 to be OS disks and the rest for data???
> > 
> > 0+1 are 2.5", and the initial setup was:
> > - we installed system disks as zroot 
> > - shipped the box to the housing facility
> > - booted and added the drives
> > 
> > At that time we did not do additional tests about the disk/boot sequence
> > etc.
> > 
> >> 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.
> > 
> >> disk4 becomes adaX? why it matters, are you using ufs on boot disks?
> > 
> > No, zpool only.
> > 
> > I've made a few more details available here:
> > 
> > https://people.freebsd.org/~pi/host/dmesg.txt
> > https://people.freebsd.org/~pi/host/devlist.txt
> > https://people.freebsd.org/~pi/host/gpart.txt
> > https://people.freebsd.org/~pi/host/pciconf.txt
> > https://people.freebsd.org/~pi/host/zpool.txt
> 
> What about gpart output of the pool drives?
> 
> In general you would create zpools using gptids or gpt labels, not the devices, so you’re independent of device numbering. The boot loader should only be installed on drives that contain the boot pool (maybe you have old boot loaders on data drives?).

ZFS work w/ ZFS labels, not w/ device names/gptids/gpt labels.
You don't worry about changed device names aroud reboots.