Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Sep 2019 21:01:06 +0200
From:      Andreas Nilsson <andrnils@gmail.com>
To:        Michael Gmelin <grembo@freebsd.org>
Cc:        Kurt Jaeger <lists@opsec.eu>, Current FreeBSD <freebsd-current@freebsd.org>
Subject:   Re: Lockdown adaX numbers to allow booting ?
Message-ID:  <CAPS9%2BSttVfV-E0U68Y3SHxxswRsLM07OrL5r3LjUVKiuimY%2BbA@mail.gmail.com>
In-Reply-To: <AA25F90D-5603-4602-B17E-DFFF333D8299@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> <20190919171529.GH2863@home.opsec.eu> <AA25F90D-5603-4602-B17E-DFFF333D8299@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 19, 2019, 20:56 Michael Gmelin <grembo@freebsd.org> wrote:

>
>
> On 19. Sep 2019, at 19:15, Kurt Jaeger <lists@opsec.eu> 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

>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPS9%2BSttVfV-E0U68Y3SHxxswRsLM07OrL5r3LjUVKiuimY%2BbA>