From owner-freebsd-current@freebsd.org Thu Sep 19 19:15:45 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 B080B12C17E for ; Thu, 19 Sep 2019 19:15:45 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-ztdg10012001.me.com (pv50p00im-ztdg10012001.me.com [17.58.6.51]) (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 46Z64w5f2Mz49CF for ; Thu, 19 Sep 2019 19:15:44 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-ztdg10012001.me.com (Postfix) with ESMTPSA id 9424628123A; Thu, 19 Sep 2019 19:15:41 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Lockdown adaX numbers to allow booting ? From: Toomas Soome In-Reply-To: <20190919184803.GI2863@home.opsec.eu> Date: Thu, 19 Sep 2019 22:15:38 +0300 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <87545E27-F860-416C-8A94-B3647C476AB4@me.com> References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@home.opsec.eu> <20190919184803.GI2863@home.opsec.eu> To: Kurt Jaeger X-Mailer: Apple Mail (2.3445.104.11) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-09-19_05:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1909190161 X-Rspamd-Queue-Id: 46Z64w5f2Mz49CF X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.60 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:17.58.0.0/16]; FREEMAIL_FROM(0.00)[me.com]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[me.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; RECEIVED_SPAMHAUS_PBL(0.00)[148.52.235.80.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; RCVD_IN_DNSWL_LOW(-0.10)[51.6.58.17.list.dnswl.org : 127.0.5.1]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[me.com]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[me.com:s=1a1hai]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; IP_SCORE_FREEMAIL(0.00)[]; DWL_DNSWL_LOW(-1.00)[me.com.dwl.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(0.00)[ip: (-9.52), ipnet: 17.58.0.0/20(-3.41), asn: 714(-2.92), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] 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 19:15:45 -0000 > On 19 Sep 2019, at 21:48, Kurt Jaeger wrote: >=20 > Hi! >=20 >>>> Also the question is, what you mean with ???system looses track???? >=20 >>> I interpret the hang during boot as 'it looses track'. So I guess >>> it tries to read the kernel from the wrong drives. >=20 >> 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. >=20 >> I bet it is BIOS system? >=20 > If you mean: no UEFI boot ? Yes, it boots via BIOS, not UEFI. >=20 >> Since the raidz seems to be created partitionless, what version >> of freebsd are you using? >=20 > FreeBSD 12.0p10, amd64. >=20 >> BIOS up to date? >=20 > 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). >=20 > https://www.supermicro.com/en/products/motherboard/X10SRi-F >=20 >> 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? >=20 > I will test this when I'm at the facility. Will take some time. >=20 Those data disks are 10TB 512e, I can not recall if loader in 12.0p10 = does ignore partitionless disks in pools or not, if the bios is buggy = about large disks, that does explain the hung system=E2=80=A6 in that = case, the loader in current should be fine. rgds, toomas