Date: Thu, 19 Sep 2019 18:04:54 +0200 From: Michael Gmelin <grembo@freebsd.org> To: Kurt Jaeger <lists@opsec.eu> Cc: Toomas Soome <tsoome@me.com>, freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> In-Reply-To: <20190919155713.GG2863@home.opsec.eu> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 19. Sep 2019, at 17:57, Kurt Jaeger <lists@opsec.eu> wrote: >=20 > Hi! >=20 >>> 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 purpos= es: >>>=20 >>> bck 72.8T 38.7T 34.1T - - 1% 53% 1.00x ONLI= NE - >=20 >>> 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 lo= g): >=20 >> Why this order does change? One would expect disks 0 and 1 to be OS disk= s and the rest for data??? >=20 > 0+1 are 2.5", and the initial setup was: > - we installed system disks as zroot=20 > - shipped the box to the housing facility > - booted and added the drives >=20 > At that time we did not do additional tests about the disk/boot sequence > etc. >=20 >> Also the question is, what you mean with ???system looses track???? >=20 > I interpret the hang during boot as 'it looses track'. So I guess > it tries to read the kernel from the wrong drives. >=20 >> disk4 becomes adaX? why it matters, are you using ufs on boot disks? >=20 > No, zpool only. >=20 > I've made a few more details available here: >=20 > 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 devic= es, so you=E2=80=99re independent of device numbering. The boot loader shoul= d only be installed on drives that contain the boot pool (maybe you have old= boot loaders on data drives?). -m > --=20 > pi@opsec.eu +49 171 3101372 One year to go != > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C855A39-BF79-4430-98CB-CB9174768E11>