From owner-freebsd-current@freebsd.org Thu Sep 19 19:01:18 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 C9AB512BB87 for ; Thu, 19 Sep 2019 19:01:18 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Z5mG510yz48cX; Thu, 19 Sep 2019 19:01:18 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mail-lf1-x131.google.com with SMTP id d17so3163819lfa.7; Thu, 19 Sep 2019 12:01:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Q6ighlTD3H/CpsdNqY/gObZ3ktLq+N9XYD5CRRLdAPc=; b=GkeG6uo2+rt4yDj2WpOTrRT2OLJfid/u87ZUVvqo90GYK31YZQ5wbjtUldscRB8DYb KCyFhjcq5u8bfUyIJSCuNhJ0yXamduXFIrF+iO7AB6JpACS6wtrJK+hace0Q/G15JeTa sVTGqKkLh5U942Jl+N2knPMrFDOy0MUIyxdBYPEpXsNuNmZAET756BRH4UUVu2LGd5x+ JOsLvus1F2AWeKXv9eeSLh8FjccE7RHszCql4963zlwk9YgZ5ZFmJ9+joDFUq5X8loML 4xPwW2aNBdIr3i5ehQuk/hJwY1z8Npf8gt5zg3MqfR1nfxJfYHSGUyH6jlPooN277o0V aV8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Q6ighlTD3H/CpsdNqY/gObZ3ktLq+N9XYD5CRRLdAPc=; b=M3cQ7Nx/JliBNwFsHpkSivEMosAKPRDXhM22AqWorGZQQuYWEwMhm49gIA1aU70aoH SZjlJl2fYGYyD9ESOt5QeFSEa9hlVzCOF+HW9vG3co5h9ds6eTzVrh8nDoB6tCIo2cYr YTVMfEDJmBkpAWO2gAmpI7+gPzlomT5j6hhJR4+hLXKjkV9qBCDsE16BElwx0eybTZbO 0kJCztUqjuGdt5liXLPC64MFJCUjavy30Xjav28zKW1G8lbUJJSYXyzNcu/9hU+emum5 yptFHKjseLQGak43QMSaCZraHoBGgIsa5sZnYM0ed3q8twJvKdAXOJFqZw5dzRZOlJju 2S/A== X-Gm-Message-State: APjAAAV7NQPw91JpV83EAMT5ezOmP1xDtXEETgTgh+urXLwKVBoS6Zbf fah1C8zom2VrstqiH8hbb3JzR4zcyo7VFoMyGyesGfkx X-Google-Smtp-Source: APXvYqwTVYQdB5alcsWIObuPsyqkQ+CKcca7npE5Re1J8DHXdtmkmN3m25xhkmmEv7wW8sjBc5qDKq8WZCfzBDel848= X-Received: by 2002:a19:495b:: with SMTP id l27mr5367598lfj.45.1568919676666; Thu, 19 Sep 2019 12:01:16 -0700 (PDT) MIME-Version: 1.0 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> In-Reply-To: From: Andreas Nilsson Date: Thu, 19 Sep 2019 21:01:06 +0200 Message-ID: Subject: Re: Lockdown adaX numbers to allow booting ? To: Michael Gmelin Cc: Kurt Jaeger , Current FreeBSD X-Rspamd-Queue-Id: 46Z5mG510yz48cX X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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 19:01:18 -0000 On Thu, Sep 19, 2019, 20:56 Michael Gmelin wrote: > > > On 19. Sep 2019, at 19:15, Kurt Jaeger wrote: > > >>> I've made a few more details available here: > > > >>> https://people.freebsd.org/~pi/host/gpart.txt > > > >> What about gpart output of the pool drives? > > > > No gpart on the bck pool, raw 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?). > > > > I think not, because they are used as raw drives. > > > > 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 (makes i= t easier > to not make mistakes in case of emergency). I also leave a bit of space a= t > the beginning and end of the drive (allows adding in a boot partition lat= er > or more flexibility when replacing the drive). > > Anyway, I=E2=80=99m curious what the exact problem will turn out to be. > > Cheers, > Michael > > > > > -- > > 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= " > Seems like more of a bios enumeration issue. You should be able to set a boot order better suited for your setup there. And if that does not work, just move the sata cables around seems like the most straight forward solution. Although I think I've heard it is bad practice to use raw devices for zfs, especially if need to replace a drive, which day happens to be a different revision, with a few fewer blocks available. Then you will not be able to do the replace. Best regards Andreas >