Date: Thu, 19 Sep 2019 18:18:37 +0300 From: Toomas Soome <tsoome@me.com> To: Kurt Jaeger <lists@opsec.eu> Cc: freebsd-current@freebsd.org Subject: Re: Lockdown adaX numbers to allow booting ? Message-ID: <7E0AE025-596C-457E-BC40-41217857A3CD@me.com> In-Reply-To: <20190919140219.GE2863@home.opsec.eu> References: <20190919140219.GE2863@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 19 Sep 2019, at 17:02, Kurt Jaeger <lists@opsec.eu> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7E0AE025-596C-457E-BC40-41217857A3CD>