Date: Tue, 19 May 2020 15:48:50 -0700 From: David Christensen <dpchrist@holgerdanske.com> To: freebsd-questions@freebsd.org Subject: Re: OT: Weird Hardware Problem Message-ID: <a6814843-e8a7-0754-a2a7-79533b032c73@holgerdanske.com> In-Reply-To: <0df1c88e-3c7b-8c4d-6b4f-95da54a46226@holgerdanske.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a6814843-e8a7-0754-a2a7-79533b032c73>