LUA ERROR: memory allocation error: block too big
Warner Losh
imp at bsdimp.com
Wed Jun 3 17:00:13 UTC 2020
On Wed, Jun 3, 2020 at 10:12 AM Kyle Evans <kevans at freebsd.org> wrote:
> On Wed, Jun 3, 2020 at 11:06 AM Budi Janto
> <budijanto at studiokaraoke.co.id> wrote:
> >
> >
> >
> > On 6/3/20 6:50 PM, Kyle Evans wrote:
> > > Can you post a sample of your /boot/lodaer.conf, please? Though, the
> > > efipart_readwrite error smack dab in the middle leaves me a bit
> > > worried; status=7 looks like EFI_DEVICE_ERROR, which is a bit
> > > sinister.
> >
> > # cat /boot/loader.conf
> > autoboot_delay="5" # Delay in seconds before autobooting.
> > vfs.zfs.arc_max="5G" # Limit ZFS memory usage.
> > coretemp_load="YES" # Intel CPU temperature.
> >
>
> Thanks for confirming - this is relatively harmless, and the problem
> is indeed later.
>
> >
> > > Believe it or not, issues with underlying media can cause problems
> > > with 4thloader as well.
> >
> > Could be, I' will replace as soon as possible SSD for system (My
> > prediction SSD too old). I'am sorry, this's remote machine, so I can not
> > give you more information (I can not access that machine anymore).
> > Remote worker just send me two photo.
> >
> > First booting: https://ibb.co/NWbszqR
> > After restart: https://ibb.co/dDsH0RD
> >
>
> *nod* This isn't my domain, but I think the CAM errors after restart
> tend to support the theory of aging/dying SSD or perhaps bad cable at
> a minimum.
>
Those look like a bad sector on the disk / ssd. Rewriting it may mitigate
the issue for a while, but for long term happiness, you'll want to replace.
Warner
More information about the freebsd-stable
mailing list