From owner-freebsd-current@freebsd.org Fri Sep 20 14:35:44 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 0765AFEB3B for ; Fri, 20 Sep 2019 14:35:44 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46ZbqM5tqPz4GJL; Fri, 20 Sep 2019 14:35:43 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1iBK0R-0002BF-Qf; Fri, 20 Sep 2019 17:35:31 +0300 Date: Fri, 20 Sep 2019 17:35:31 +0300 From: Slawa Olhovchenkov To: Michael Gmelin Cc: Kurt Jaeger , Toomas Soome , freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <20190920143531.GB38096@zxy.spb.ru> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3C855A39-BF79-4430-98CB-CB9174768E11@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-Rspamd-Queue-Id: 46ZbqM5tqPz4GJL X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-5.99 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.993,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] 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: Fri, 20 Sep 2019 14:35:44 -0000 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 purposes: > >>> > >>> bck 72.8T 38.7T 34.1T - - 1% 53% 1.00x ONLINE - > > > >>> 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): > > > >> Why this order does change? One would expect disks 0 and 1 to be OS disks and the rest for data??? > > > > 0+1 are 2.5", and the initial setup was: > > - we installed system disks as zroot > > - shipped the box to the housing facility > > - booted and added the drives > > > > At that time we did not do additional tests about the disk/boot sequence > > etc. > > > >> 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. > > > >> disk4 becomes adaX? why it matters, are you using ufs on boot disks? > > > > No, zpool only. > > > > I've made a few more details available here: > > > > https://people.freebsd.org/~pi/host/dmesg.txt > > https://people.freebsd.org/~pi/host/devlist.txt > > https://people.freebsd.org/~pi/host/gpart.txt > > https://people.freebsd.org/~pi/host/pciconf.txt > > https://people.freebsd.org/~pi/host/zpool.txt > > 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 pool (maybe you have old boot loaders on data drives?). ZFS work w/ ZFS labels, not w/ device names/gptids/gpt labels. You don't worry about changed device names aroud reboots.