Date: Wed, 29 May 2019 13:49:15 -0600 From: Scott Long <scottl@samsco.org> To: Wallace Barrow <incin@incin.me> Cc: freebsd-scsi@freebsd.org Subject: Re: SAS3008 On FreeBSD 12 wGeli - OS Wont Boot Message-ID: <F80BA500-91BB-46D5-B630-524BA0A53364@samsco.org> In-Reply-To: <f1aa37cb-9c0f-4b5e-aa69-05307da3345d@www.fastmail.com> References: <a62c7ed3-f5f1-4a5b-83df-949a32b0d8e8@www.fastmail.com> <120DF864-06FB-4396-887B-78DA3E7DA351@samsco.org> <3A9F7544-40A8-4446-ADC8-18CE57A9F55A@samsco.org> <14e0991e-2e53-4127-baf0-dc674b6d8653@www.fastmail.com> <f1aa37cb-9c0f-4b5e-aa69-05307da3345d@www.fastmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Wallace, Sorry for the long delay in getting back to you, thanks for the update. = Is my understanding correct that the problem went away once you manually = set the chain_frames tunable during install? Thanks, Scott > On May 7, 2019, at 9:17 AM, Wallace Barrow <incin@incin.me> wrote: >=20 > Hi Scott, >=20 > I finally had some time to write back on this issue and it seems to = get more odd while I troubleshoot it. >=20 > The server I was talking about when starting this post had to be put = into production without Geli along with the 3 other Dell R640s just like = it. This cluster of 4 servers, that are exactly the same, and had no = issues installing FreeBSD 12 without Geli. >=20 > The 2nd cluster of servers consists of two Dell R640's as well. The = only difference between this group from the four above is the Intel = Silver CPU type, everything else is the same. >=20 > When trying to install FreeBSD 12 on these two servers without geli I = ran into the max_chains error constantly. I got the error in the = following ways: >=20 > When booting from the ISO I would get to the FreeBSD boot loader = screen and let it continue, hoping I would get to the install screen but = it would throw the max_chains error before that. Rebooting the server a = few more times trying to install I randomly by chance got to the FreeBSD = 12 installer and installed without issue, then on reboot, booting into = my new install I got the max_chain error. >=20 > I fixed the issue by: When booting from the ISO and on the boot menu I = set the boot value for max_chains to 4096 and got to the FreeBSD = installer. Before rebooting after the installer finished I opened the = shell and put that value in loader.conf. The server comes up cleanly = every time now, 5+ reboots so far. >=20 > To set the maximum number of DMA chains allocated for all adapters, = set > this tunable in loader.conf(5): >=20 > hw.mpr.max_chains=3DNNNN >=20 > The default max_chains value is 2048. >=20 > I had some issues with getting SOL working via SSH to get the console = output, but, I was able to screen capture some errors when we hit the = bug. >=20 > http://incin.me/bsd/chains1.png > http://incin.me/bsd/chains2.png > http://incin.me/bsd/chains3.png > http://incin.me/bsd/chains4.png >=20 > I hope the screen shots help. I also ran out of time to play with = these servers and they are needed in our environment. >=20 > Thank you! >=20 > --=20 > Wallace Barrow > incin@incin.me >=20 > On Fri, Apr 19, 2019, at 1:21 PM, Wallace Barrow wrote: >> Scott,=20 >>=20 >> You are correct. Installing onto a disk controlled by the SAS3008 = works=20 >> fine when Geli is not enabled. >>=20 >> --=20 >> Wallace Barrow >> incin@incin.me >>=20 >> On Fri, Apr 19, 2019, at 1:06 PM, Scott Long wrote: >>> =46rom the loader, set >>>=20 >>> hw.mpr.debug_level=3D0xffff >>>=20 >>> It=E2=80=99ll dump a lot of text to the console when the kernel = boots, but if=20 >>> you could send me all if it, I=E2=80=99d appreciate it. For my = understanding,=20 >>> installing onto a disk controlled by the SAS3008 works fine for you = as=20 >>> long as you don=E2=80=99t enable GELI? >>>=20 >>> Thanks, >>=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F80BA500-91BB-46D5-B630-524BA0A53364>