From owner-freebsd-current@freebsd.org Thu Sep 19 15:57: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 7F14D127157 for ; Thu, 19 Sep 2019 15:57:18 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46Z1gx40ytz3QDH for ; Thu, 19 Sep 2019 15:57:17 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.92.2 (FreeBSD)) (envelope-from ) id 1iAynx-000FEh-68; Thu, 19 Sep 2019 17:57:13 +0200 Date: Thu, 19 Sep 2019 17:57:13 +0200 From: Kurt Jaeger To: Toomas Soome Cc: freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <20190919155713.GG2863@home.opsec.eu> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> X-Rspamd-Queue-Id: 46Z1gx40ytz3QDH X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of lists@opsec.eu designates 2001:14f8:200::1 as permitted sender) smtp.mailfrom=lists@opsec.eu X-Spamd-Result: default: False [-4.80 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx:c]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[opsec.eu]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_TO(0.00)[me.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-3.50)[ip: (-9.14), ipnet: 2001:14f8::/32(-4.65), asn: 12502(-3.72), country: DE(-0.01)] 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 15:57:18 -0000 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 -- pi@opsec.eu +49 171 3101372 One year to go !