From owner-freebsd-current@freebsd.org Thu Sep 19 14:02:31 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 3DFB412440D for ; Thu, 19 Sep 2019 14:02:31 +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 46Yz7V189Rz3HN0 for ; Thu, 19 Sep 2019 14:02:29 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.92.2 (FreeBSD)) (envelope-from ) id 1iAx0l-000Enm-Gb; Thu, 19 Sep 2019 16:02:19 +0200 Date: Thu, 19 Sep 2019 16:02:19 +0200 From: Kurt Jaeger To: freebsd-current@freebsd.org Subject: Lockdown adaX numbers to allow booting ? Message-ID: <20190919140219.GE2863@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: 46Yz7V189Rz3HN0 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.85 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[opsec.eu]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(-3.55)[ip: (-9.31), ipnet: 2001:14f8::/32(-4.69), asn: 12502(-3.75), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2] 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 14:02:31 -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): -------------------- /boot/config: -Dh -S115200 Consoles: internal video/keyboard serial port BTX loader 1.00 BTX version is 1.02 Consoles: internal video/keyboard serial port BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS drive E: is disk2 BIOS drive F: is disk3 BIOS drive G: is disk4 BIOS drive H: is disk5 BIOS drive I: is disk6 BIOS drive J: is disk7 BIOS drive K: is disk8 BIOS drive L: is disk9 // / -------------------- The system disks are detected as ada4 and ada5, when all disks are plugged in. The solution right now is this to unplug all disks of the 'bck' pool, reboot, and re-insert the data disks after the boot is finished. I looked into the output to kenv(1), but did not find inspiration on how to fix this. Now my questions: - Shuffeling around SATA cables seems the wrong approach to fix this. - Can we somehow lock down the disk numbering so that the system disks are detected as ada0 and ada1 ? - Would rootdev="disk4s1a" in /boot/loader.conf work or is that the wrong approach ? - How could we configure two drivers as root devices in loader.conf ? -- pi@opsec.eu +49 171 3101372 One year to go !