Date: Thu, 7 Oct 2021 08:10:34 +0800 From: Erich Dollansky <freebsd.ed.lists@sumeritec.com> To: "Justin O'Connor" <oconnor@crystal.harvard.edu> Cc: freebsd-questions@freebsd.org Subject: Re: not getting to bootloader screen Message-ID: <20211007001034.055b41e5.freebsd.ed.lists@sumeritec.com> In-Reply-To: <CAKHthbWWZ12w=CoxKrfYOGc%2BAr4-cAGaLJx2hjDP46zKE=Q3uw@mail.gmail.com> References: <CAKHthbWWZ12w=CoxKrfYOGc%2BAr4-cAGaLJx2hjDP46zKE=Q3uw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Wed, 6 Oct 2021 11:56:19 -0400 "Justin O'Connor" <oconnor@crystal.harvard.edu> wrote: > Hi list, > > We have a system that will enumerate a list of disks and stops at > "can not get information about disk unit" then it will be disk like > 0xaa. The boot loader screen never comes up. > > An example - > ... > ... > BIOS drive n: is disk43 > BIOS drive 0: is disk44 > BIOS drive p: is disk45 > BIOS drive q: is disk46 > can not get information about disk unit 0xaf > / > \ from distance it looks like that you have not written the master boot record (MBR) to the disk. Erich > We are trying to upgrade a server and opted to install on OS some > alternate SSD's and swap the disks to minimize downtime. System boot > with 11.x OS disks installed. In the system there is an 3108 raid > card with many disks, a few nvme's, then the boot disks are a pair of > sata disks on a gmirror. Changing around loader.conf options for > mfi/mrsas have no effect. We have an alternate mfsbsd netboot with > 13.0-RELEASE and the same issue netbooting. We have a replica system > (with minor differences in sas settings) that boots fine with the > same netboot image. > > Looking at the system booted 11.x system and not finding any logs that > might indicate a hardware issue. > > Ideas? > > Justin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20211007001034.055b41e5.freebsd.ed.lists>