From owner-freebsd-current@freebsd.org Thu Sep 19 16:27:39 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 0EC60127BA5 for ; Thu, 19 Sep 2019 16:27:39 +0000 (UTC) (envelope-from tsoome@me.com) Received: from mr85p00im-ztdg06011901.me.com (mr85p00im-ztdg06011901.me.com [17.58.23.198]) (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 46Z2Ly18QCz3xTt for ; Thu, 19 Sep 2019 16:27:37 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by mr85p00im-ztdg06011901.me.com (Postfix) with ESMTPSA id BAC2BA60A03; Thu, 19 Sep 2019 16:27:34 +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: <20190919155713.GG2863@home.opsec.eu> Date: Thu, 19 Sep 2019 19:27:31 +0300 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20190919140219.GE2863@home.opsec.eu> <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> <20190919155713.GG2863@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-1909190146 X-Rspamd-Queue-Id: 46Z2Ly18QCz3xTt 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)[198.23.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.16.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: (-7.11), ipnet: 17.58.16.0/20(-2.39), 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 16:27:39 -0000 > On 19 Sep 2019, at 18:57, Kurt Jaeger wrote: >=20 > Hi! >=20 >>> 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: >>>=20 >>> bck 72.8T 38.7T 34.1T - - 1% 53% 1.00x = ONLINE - >=20 >>> 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): >=20 >> Why this order does change? One would expect disks 0 and 1 to be OS = disks and the rest for data??? >=20 > 0+1 are 2.5", and the initial setup was: > - we installed system disks as zroot=20 > - shipped the box to the housing facility > - booted and added the drives >=20 > At that time we did not do additional tests about the disk/boot = sequence > etc. >=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. 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? Since the raidz seems to be created = partitionless, what version of freebsd are you using? BIOS up to date? = can you test pool visibility in loader with latest current usb/cd start = - like press esc in menu and check lasdev -v (assuming you get to = menu)=E2=80=A6 the same with uefi? rgds, toomas >=20 >> disk4 becomes adaX? why it matters, are you using ufs on boot disks? >=20 > No, zpool only. >=20 > I've made a few more details available here: >=20 > 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 >=20 > --=20 > pi@opsec.eu +49 171 3101372 One year to = go ! > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org"