From owner-freebsd-current@freebsd.org  Mon Jan  6 10:37:50 2020
Return-Path: <owner-freebsd-current@freebsd.org>
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 1FADB1D0519
 for <freebsd-current@mailman.nyi.freebsd.org>;
 Mon,  6 Jan 2020 10:37:50 +0000 (UTC) (envelope-from pi@freebsd.org)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 47rsR15fXJz4XkQ
 for <freebsd-current@freebsd.org>; Mon,  6 Jan 2020 10:37:49 +0000 (UTC)
 (envelope-from pi@freebsd.org)
Received: from pi by home.opsec.eu with local (Exim 4.92.3 (FreeBSD))
 (envelope-from <pi@freebsd.org>) id 1ioPlZ-000DAJ-EY
 for freebsd-current@freebsd.org; Mon, 06 Jan 2020 11:37:45 +0100
Date: Mon, 6 Jan 2020 11:37:45 +0100
From: Kurt Jaeger <pi@freebsd.org>
To: freebsd-current@freebsd.org
Subject: Re: Lockdown adaX numbers to allow booting ?
Message-ID: <20200106103745.GA50553@home.opsec.eu>
References: <bb5dabdf47005047a105f935a90f4dee@pyret.net>
 <20190920052419.GJ2863@home.opsec.eu>
 <20191013164703.GC37504@home.opsec.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20191013164703.GC37504@home.opsec.eu>
X-Rspamd-Queue-Id: 47rsR15fXJz4XkQ
X-Spamd-Bar: -
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [-1.91 / 15.00];
 local_wl_from(0.00)[freebsd.org];
 NEURAL_HAM_MEDIUM(-0.93)[-0.927,0];
 NEURAL_HAM_LONG(-0.98)[-0.984,0];
 ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, 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
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2020 10:37:50 -0000

Hi!

> > > You're probably looking for this:
> > > https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html
> > 
> > Thanks, that looks like a very useful approach.
> > 
> > Will test that when I'm in the housing facility, and report back.
> 
> I tested it, no change 8-(

Update on this: I did an upgrade to 12.1p1 yesterday and the box
rebooted sucessfully without any manual intervention. The mapping
from /boot/device.hints is ignored, btw (it requested different adaX numbers).

The data pool:

        NAME        STATE     READ WRITE CKSUM
        bck         ONLINE       0     0     0
          raidz2-0  ONLINE       0     0     0
            ada0    ONLINE       0     0     0
            ada10   ONLINE       0     0     0
            ada2    ONLINE       0     0     0
            ada3    ONLINE       0     0     0
            ada13   ONLINE       0     0     0
            ada12   ONLINE       0     0     0
            ada11   ONLINE       0     0     0
            ada1    ONLINE       0     0     0

The boot pool:

        NAME        STATE     READ WRITE CKSUM
        zroot       ONLINE       0     0     0
          mirror-0  ONLINE       0     0     0
            ada5p3  ONLINE       0     0     0
            ada4p3  ONLINE       0     0     0

-- 
pi@opsec.eu            +49 171 3101372                    Now what ?