On Thu, Sep 19, 2019, 20:56 Michael Gmelin <gre...@freebsd.org> wrote:

>
>
> On 19. Sep 2019, at 19:15, Kurt Jaeger <li...@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’s not optimal that way. I made it a habit to use GPT on all pools
> and label partitions with the enclosure slots they’re in (makes it easier
> to not make mistakes in case of emergency). I also leave a bit of space at
> the beginning and end of the drive (allows adding in a boot partition later
> or more flexibility when replacing the drive).
>
> Anyway, I’m curious what the exact problem will turn out to be.
>
> Cheers,
> Michael
>
> >
> > --
> > p...@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-unsubscr...@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

>
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to