From owner-freebsd-current@freebsd.org Thu Sep 19 18:48:08 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 9770512B3BC for ; Thu, 19 Sep 2019 18:48:08 +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 46Z5T359bxz47d7 for ; Thu, 19 Sep 2019 18:48:07 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.92.2 (FreeBSD)) (envelope-from ) id 1iB1TH-000Fod-DY; Thu, 19 Sep 2019 20:48:03 +0200 Date: Thu, 19 Sep 2019 20:48:03 +0200 From: Kurt Jaeger To: Toomas Soome Cc: freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <20190919184803.GI2863@home.opsec.eu> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 46Z5T359bxz47d7 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.75 / 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.45)[ip: (-8.95), ipnet: 2001:14f8::/32(-4.61), asn: 12502(-3.68), 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 18:48:08 -0000 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 about reading the kernel from wrong place. > I bet it is BIOS system? If you mean: no UEFI boot ? Yes, it boots via BIOS, not UEFI. > Since the raidz seems to be created partitionless, what version > of freebsd are you using? FreeBSD 12.0p10, amd64. > BIOS up to date? The board is an X10SRi-F. dmidecode reports BIOS 3.1, supermicro has 3.1c, but the release notes do not mention things like that (or at least I don't understand them that way). https://www.supermicro.com/en/products/motherboard/X10SRi-F > can you test pool visibility in loader with latest current > usb/cd start - like press esc in menu and check lsdev -v > (assuming you get to menu) ? the same with uefi? I will test this when I'm at the facility. Will take some time. Thanks for the pointers! -- pi@opsec.eu +49 171 3101372 One year to go !