Date: Wed, 20 May 2020 03:01:06 +0300 From: Mehmet Erol Sanliturk <m.e.sanliturk@gmail.com> To: Tim Daneliuk <tundra@tundraware.com> Cc: David Christensen <dpchrist@holgerdanske.com>, FreeBSD Questions Mailing List <freebsd-questions@freebsd.org> Subject: Re: OT: Weird Hardware Problem Message-ID: <CAOgwaMv023fnH371ZwivBWgkRcMw2gZs9ouwZ_MGxPLLwFMXbw@mail.gmail.com> In-Reply-To: <40b15687-e203-8f20-76d3-a408820a0763@tundraware.com> References: <0a9f810d-7b4b-f4e6-4b7c-716044a9cf69@tundraware.com> <dc56ea8c-0ee8-5115-21a4-186251958229@holgerdanske.com> <299b37be-11af-6c0a-6957-54a788d19fe5@tundraware.com> <0df1c88e-3c7b-8c4d-6b4f-95da54a46226@holgerdanske.com> <a6814843-e8a7-0754-a2a7-79533b032c73@holgerdanske.com> <40b15687-e203-8f20-76d3-a408820a0763@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 20, 2020 at 2:08 AM Tim Daneliuk <tundra@tundraware.com> wrote: > On 5/19/20 5:48 PM, David Christensen wrote: > > On 2020-05-19 11:45, David Christensen wrote: > >> On 2020-05-19 11:32, Tim Daneliuk wrote: > >>> On 5/19/20 1:23 PM, David Christensen wrote: > >>>> > >>>> I have not seen these suggestions yet: > >>>> > >>>> 1. Have you tried connecting the system drive to another port? > >>>> > >>>> 2. Have you tried replacing the SATA cable? > >>>> > >>>> 3. Have you tried replacing the system drive? > >>> > >>> > >>> 1. and 2. are next on my list of things to try. > >>> > >>> I did try 3. albeit with the same SATA cable and port - no difference. > >> > >> Another: > >> > >> 4. Have you tried installing an HBA and connecting the system drive to > that? > >> > >> 5. Have you tried resetting the CMOS settings to defaults via Setup? > Via the motherboard jumper? > > > > Another: > > > > 6. Open multiple terminals, say by booting the machine with a live > distribution with a graphical desktop or by using another machine with a > graphical desktop, opening multiple terminals, and connecting via SSH. In > one terminal, issue commands or run programs to exercise the HDD/ SSD -- > 'dd if=/dev/urandom of=foo bs=1M count=1k', 'dd if=foo of=/dev/null bs=1M', > etc.. In another terminal, watch for kernel error messages -- via dmesg(1) > or files in /var/log. (I have more practice doing this on Debian.) > > > > > > David > > > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > > > > > That's fine idea, actually. I have a nice heavyweight compile job I can > run in > parallel in docker containers and watch to see what error output looks like > > -- Another idea may be applied if you can find a thermal camera . During computer working loaded heavily , you may inspect mother board , cables , or other related parts , carefully with a thermal camera . If any point on a circuit connection line , or a circuit component , there is (are) significantly hot point(s) , it may be likely that such point(s) is ( are ) causing cracks or loose connection(s) separated to discontinue the current sufficiently long time to cause a boot ( i.e. , reset ) the computer . Mehmet Erol Sanliturk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOgwaMv023fnH371ZwivBWgkRcMw2gZs9ouwZ_MGxPLLwFMXbw>