From owner-freebsd-current@freebsd.org Thu Sep 19 18:56:17 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9612C12B9D9 for ; Thu, 19 Sep 2019 18:56:17 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.evolve.de (mail.evolve.de [213.239.217.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.evolve.de", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Z5fS5FDdz48HR; Thu, 19 Sep 2019 18:56:16 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: by mail.evolve.de (OpenSMTPD) with ESMTP id 7f131086; Thu, 19 Sep 2019 18:56:13 +0000 (UTC) Received: by mail.evolve.de (OpenSMTPD) with ESMTPSA id d1c99d3a TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 19 Sep 2019 18:56:11 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: Lockdown adaX numbers to allow booting ? From: Michael Gmelin X-Mailer: iPhone Mail (16G102) In-Reply-To: <20190919171529.GH2863@home.opsec.eu> Date: Thu, 19 Sep 2019 20:56:10 +0200 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: 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> <20190919171529.GH2863@home.opsec.eu> To: Kurt Jaeger X-Rspamd-Queue-Id: 46Z5fS5FDdz48HR X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-2.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:24940, ipnet:213.239.192.0/18, country:DE] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Sep 2019 18:56:17 -0000 On 19. Sep 2019, at 19:15, Kurt Jaeger wrote: >>> I've made a few more details available here: >=20 >>> https://people.freebsd.org/~pi/host/gpart.txt >=20 >> What about gpart output of the pool drives? >=20 > No gpart on the bck pool, raw drives. >=20 >> In general you would create zpools using gptids or gpt labels, not the de= vices, so you???re independent of device numbering. The boot loader should o= nly be installed on drives that contain the boot pool (maybe you have old bo= ot loaders on data drives?). >=20 > I think not, because they are used as raw drives. >=20 > Maybe that decision was an error in hindsight. Yeah, it=E2=80=99s not optimal that way. I made it a habit to use GPT on all= pools and label partitions with the enclosure slots they=E2=80=99re in (mak= es it easier to not make mistakes in case of emergency). I also leave a bit o= f space at the beginning and end of the drive (allows adding in a boot parti= tion later or more flexibility when replacing the drive). Anyway, I=E2=80=99m curious what the exact problem will turn out to be. Cheers, Michael >=20 > --=20 > pi@opsec.eu +49 171 3101372 One year to go !=