Re: Lockdown adaX numbers to allow booting ?

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

Re: Lockdown adaX numbers to allow booting ?

On Sun, October 13, 2019 13:47, Kurt Jaeger wrote: > Hi! > >> > You're probably looking for this: >> > https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html >> >> Would glabel solve it? > > The disks are not gpart-formatted, they are used raw. mine neither: root@x:~ # gpart show

Re: Lockdown adaX numbers to allow booting ?

> On 14 Oct 2019, at 19:08, Kurt Jaeger wrote: > > Hi! > > You're probably looking for this: > https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html Would glabel solve it? >>> >>> The disks are not gpart-formatted, they are used raw. >> >> What file

Re: Lockdown adaX numbers to allow booting ?

Hi! > >>> You're probably looking for this: > >>> https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html > >> > >> Would glabel solve it? > > > > The disks are not gpart-formatted, they are used raw. > > What file system are they formatted with? ZFS, see

Re: Lockdown adaX numbers to allow booting ?

> On 21 Sep 2019, at 02:36, Garrett Wollman > wrote: > > In article <20190920155304.gn3...@zxy.spb.ru>, s...@zxy.spb.ru writes: > >> Location of device in multi-chassis storage system is different story. >> I am don't know how to field engineer insert disks in chassis. >> For me simple is

Re: Lockdown adaX numbers to allow booting ?

> On 14 Oct 2019, at 03:17, Kurt Jaeger wrote: >>> You're probably looking for this: >>> https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html >> >> Would glabel solve it? > > The disks are not gpart-formatted, they are used raw. What file system are they formatted with? UFS

Re: Lockdown adaX numbers to allow booting ?

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-( -- p...@opsec.eu

Re: Lockdown adaX numbers to allow booting ?

Hi! > > You're probably looking for this: > > https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html > > Would glabel solve it? The disks are not gpart-formatted, they are used raw. -- p...@opsec.eu+49 171 3101372One year to go !

Re: Lockdown adaX numbers to allow booting ?

On Thu, September 19, 2019 17:10, Daniel Engberg wrote: > Hi Kurt! > > You're probably looking for this: > https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html Would glabel solve it? I have almost as much disks and some zpools and it runs fine. matheus

Re: Lockdown adaX numbers to allow booting ?

In article <20190920155304.gn3...@zxy.spb.ru>, s...@zxy.spb.ru writes: >Location of device in multi-chassis storage system is different story. >I am don't know how to field engineer insert disks in chassis. >For me simple is find in /var/run/dmesg.boot S/N <=> daXY mapping and >turn ON led by

Re: Lockdown adaX numbers to allow booting ?

On Fri, Sep 20, 2019 at 01:06:29PM -0400, Garrett Wollman wrote: > In article <20190920155304.gn3...@zxy.spb.ru>, s...@zxy.spb.ru writes: > > >Location of device in multi-chassis storage system is different story. > >I am don't know how to field engineer insert disks in chassis. > >For me simple

Re: Lockdown adaX numbers to allow booting ?

On Fri, Sep 20, 2019 at 08:29:08AM -0700, Freddie Cash wrote: > On Fri, Sep 20, 2019 at 7:35 AM Slawa Olhovchenkov wrote: > > > On Thu, Sep 19, 2019 at 06:04:54PM +0200, Michael Gmelin wrote: > > > What about gpart output of the pool drives? > > > > > > In general you would create zpools using

Re: Lockdown adaX numbers to allow booting ?

On Fri, Sep 20, 2019 at 7:35 AM Slawa Olhovchenkov wrote: > On Thu, Sep 19, 2019 at 06:04:54PM +0200, Michael Gmelin wrote: > > What about gpart output of the pool drives? > > > > In general you would create zpools using gptids or gpt labels, not the > devices, so you’re independent of device

Re: Lockdown adaX numbers to allow booting ?

Kurt Jaeger writes: The problem is that if all 10 disks are connected, the system looses track from where it should boot and fails to boot (serial boot log): Consoles: internal video/keyboard serial port BTX loader 1.00 BTX version is 1.02 Consoles: internal video/keyboard serial port

Re: Lockdown adaX numbers to allow booting ?

On Thu, Sep 19, 2019 at 06:04:54PM +0200, Michael Gmelin wrote: > > > > On 19. Sep 2019, at 17:57, Kurt Jaeger wrote: > > > > Hi! > > > >>> We have a system with 10 SATA disks. 2 disks are for the system, > >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup > >>>

Re: Lockdown adaX numbers to allow booting ?

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. -- p...@opsec.eu+49 171 3101372One

Re: Lockdown adaX numbers to allow booting ?

On Thu, Sep 19, 2019 at 12:01 PM Andreas Nilsson wrote: > 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. > >

Re: Lockdown adaX numbers to allow booting ?

Hi Kurt! You're probably looking for this: https://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html Best regards, Daniel ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To

Re: Lockdown adaX numbers to allow booting ?

> On 19 Sep 2019, at 21:48, Kurt Jaeger wrote: > > Hi! > Also the question is, what you mean with ???system looses track > >>> I interpret the hang during boot as 'it looses track'. So I guess >>> it tries to read the kernel from the wrong drives. > >> no, loader does probe disks

Re: Lockdown adaX numbers to allow booting ?

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

Re: Lockdown adaX numbers to allow booting ?

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

Re: Lockdown adaX numbers to allow booting ?

Hi! > >> Also the question is, what you mean with ???system looses track > > I interpret the hang during boot as 'it looses track'. So I guess > > it tries to read the kernel from the wrong drives. > no, loader does probe disks to see which devices make up the pool and hung > system is not

Re: Lockdown adaX numbers to allow booting ?

> > 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

Re: Lockdown adaX numbers to allow booting ?

On 19/09/19 18:54, Freddie Cash wrote: > On Thu, Sep 19, 2019 at 9:47 AM Guido Falsi > wrote: > > On 19/09/19 18:04, Michael Gmelin wrote: > > > > What about gpart output of the pool drives? > > > > In general you would create zpools using gptids or

Re: Lockdown adaX numbers to allow booting ?

On Thu, 19 Sep 2019 18:04:54 +0200 Michael Gmelin wrote: > > On 19. Sep 2019, at 17:57, Kurt Jaeger wrote: > > > > Hi! > > > >>> We have a system with 10 SATA disks. 2 disks are for the system, > >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup > >>> purposes: > >>> >

Re: Lockdown adaX numbers to allow booting ?

On Thu, Sep 19, 2019 at 9:47 AM Guido Falsi wrote: > On 19/09/19 18:04, Michael Gmelin wrote: > > > > What about gpart output of the pool 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

Re: Lockdown adaX numbers to allow booting ?

On 19/09/19 18:04, Michael Gmelin wrote: > > What about gpart output of the pool 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

Re: Lockdown adaX numbers to allow booting ?

> On 19 Sep 2019, at 18:57, Kurt Jaeger wrote: > > Hi! > >>> We have a system with 10 SATA disks. 2 disks are for the system, >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: >>> >>> bck72.8T 38.7T 34.1T- - 1%53% 1.00x ONLINE

Re: Lockdown adaX numbers to allow booting ?

> On 19. Sep 2019, at 17:57, Kurt Jaeger wrote: > > Hi! > >>> We have a system with 10 SATA disks. 2 disks are for the system, >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: >>> >>> bck72.8T 38.7T 34.1T- - 1%53% 1.00x ONLINE

Re: Lockdown adaX numbers to allow booting ?

Hi! > > We have a system with 10 SATA disks. 2 disks are for the system, > > 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: > > > > bck72.8T 38.7T 34.1T- - 1%53% 1.00x ONLINE > > - > > The problem is that if all 10 disks are

Re: Lockdown adaX numbers to allow booting ?

> On 19 Sep 2019, at 17:02, Kurt Jaeger wrote: > > Hi! > > We have a system with 10 SATA disks. 2 disks are for the system, > 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: > > bck72.8T 38.7T 34.1T- - 1%53% 1.00x ONLINE - > > The

Lockdown adaX numbers to allow booting ?

Hi! We have a system with 10 SATA disks. 2 disks are for the system, 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: bck72.8T 38.7T 34.1T- - 1%53% 1.00x ONLINE - The problem is that if all 10 disks are connected, the system looses