Date: Thu, 19 Sep 2019 18:57:06 +0200 From: Gary Jennejohn <gljennjohn@gmail.com> To: Michael Gmelin <grembo@freebsd.org> Cc: Kurt Jaeger <lists@opsec.eu>, Toomas Soome <tsoome@me.com>, freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <20190919185706.41988cfc@ernst.home> In-Reply-To: <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 19 Sep 2019 18:04:54 +0200 Michael Gmelin <grembo@freebsd.org> wrote: > > On 19. Sep 2019, at 17:57, Kurt Jaeger <lists@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?). > Maybe the cam(4) hint settings could help in your case. -- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190919185706.41988cfc>