Date: Mon, 15 May 2023 07:17:50 -0600 From: Rebecca Cran <rebecca@bsdio.com> To: =?UTF-8?B?Sm9zw6kgUMOpcmV6?= <fbl@aoek.com> Cc: Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: 20230504 -CURRENT snapshot panics during install at zfs probing Message-ID: <5c4bad0f-1e38-4bd4-60ce-a515198d65b1@bsdio.com> In-Reply-To: <56da7c27b99ae6bc0ff3880f3cff5733@mail.yourbox.net> References: <e0a0420b-98a7-7fe5-b213-012ec1200d30@bsdio.com> <d63557f6-cc54-6c3f-49dd-4f732dee58b0@bsdio.com> <56da7c27b99ae6bc0ff3880f3cff5733@mail.yourbox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/15/23 07:09, José Pérez wrote: > > I recall exepriencing a similar issue with a SuperMicro server and I > think I worked this around by adding hw.mfi.mrsas_enable="1" to > /boot/device.hints in order to have FreeBSD booting from the SAS disks. > > Unfortunately I do not have access to that hardware anymore (it is > running AnotherOS and cannot be taken out of production). > > I still recommend you do open a bug with the details you have so far, > having FreeBSD on server with SAS disks is not a sin ;) and software > causing memory corruption shall be fixed anyways. Thanks. I wanted to boot FreeBSD from the BOSS-1 drive (NVMe) so I worked around it by disabling the mrsas controller during install then re-enabling it later. I'll open a bug report so the details don't get lost. -- Rebecca Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5c4bad0f-1e38-4bd4-60ce-a515198d65b1>