OT: Weird Hardware Problem

[Tim Daneliuk]

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 at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at 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

-- 
----------------------------------------------------------------------------
Tim Daneliuk     tundra at tundraware.com
PGP Key:         http://www.tundraware.com/PGP/