From owner-freebsd-current@freebsd.org Thu Sep 19 15:18:44 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 AD1C1126160 for ; Thu, 19 Sep 2019 15:18:44 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-zteg10021301.me.com (pv50p00im-zteg10021301.me.com [17.58.6.46]) (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 46Z0qQ6zttz3N26 for ; Thu, 19 Sep 2019 15:18:42 +0000 (UTC) (envelope-from tsoome@me.com) Received: from nazgul.lan (148-52-235-80.sta.estpak.ee [80.235.52.148]) by pv50p00im-zteg10021301.me.com (Postfix) with ESMTPSA id 33D00580F53; Thu, 19 Sep 2019 15:18:40 +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: <20190919140219.GE2863@home.opsec.eu> Date: Thu, 19 Sep 2019 18:18:37 +0300 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> References: <20190919140219.GE2863@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=1011 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1909190143 X-Rspamd-Queue-Id: 46Z0qQ6zttz3N26 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.20 / 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)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; RCVD_IN_DNSWL_MED(-0.20)[46.6.58.17.list.dnswl.org : 127.0.5.2]; DKIM_TRACE(0.00)[me.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[me.com,quarantine]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; 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)[]; 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]; IP_SCORE(0.00)[ip: (-5.25), ipnet: 17.58.0.0/20(-3.39), asn: 714(-2.92), country: US(-0.05)]; 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)[]; 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 15:18:44 -0000 > On 19 Sep 2019, at 17:02, 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 > -------------------- > /boot/config: -Dh -S115200 >=20 > 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 > // > / > -------------------- >=20 > The system disks are detected as ada4 and ada5, when all disks are > plugged in. >=20 > 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. >=20 > I looked into the output to kenv(1), but did not find inspiration > on how to fix this. >=20 > Now my questions: >=20 > - 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 ? Why this order does change? One would expect disks 0 and 1 to be OS = disks and the rest for data=E2=80=A6 Also the question is, what you mean with =E2=80=9Csystem looses = track=E2=80=9D? disk4 becomes adaX? why it matters, are you using ufs on = boot disks? rgds, toomas > - Would > rootdev=3D"disk4s1a" > in /boot/loader.conf work or is that the wrong approach ? > - How could we configure two drivers as root devices in loader.conf ? >=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"