Date: Wed, 3 Jun 2020 10:59:58 -0600 From: Warner Losh <imp@bsdimp.com> To: Kyle Evans <kevans@freebsd.org> Cc: Budi Janto <budijanto@studiokaraoke.co.id>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: LUA ERROR: memory allocation error: block too big Message-ID: <CANCZdfpO4HPtG%2BK9tq=v6o-=uOsGgQdpLrFPTdhi_NLY-=4DOw@mail.gmail.com> In-Reply-To: <CACNAnaG%2BvNAj_tFh30-CRqg5s%2BPyj4_9=yyOoG=-f-aNp57TEg@mail.gmail.com> References: <9c5739d4-c10c-74a0-0f69-6b4cdc3e0dd7@studiokaraoke.co.id> <CACNAnaHMWf9zdhz6aOApLjuxToc6M=GkrvYpUqUQhx1bECFsWQ@mail.gmail.com> <9497bb24-39e3-0c2f-4218-aaa7643b1e7f@studiokaraoke.co.id> <CACNAnaG%2BvNAj_tFh30-CRqg5s%2BPyj4_9=yyOoG=-f-aNp57TEg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 3, 2020 at 10:12 AM Kyle Evans <kevans@freebsd.org> wrote: > On Wed, Jun 3, 2020 at 11:06 AM Budi Janto > <budijanto@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpO4HPtG%2BK9tq=v6o-=uOsGgQdpLrFPTdhi_NLY-=4DOw>