From owner-freebsd-questions@freebsd.org Tue May 19 23:08:47 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CE0BB2F77BD for ; Tue, 19 May 2020 23:08:47 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from oceanview.tundraware.com (oceanview.tundraware.com [45.55.60.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailman.tundraware.com", Issuer "mailman.tundraware.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49RWlf6xbRz4GTD for ; Tue, 19 May 2020 23:08:46 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from [192.168.0.7] (ozzie.tundraware.com [75.145.138.73]) (authenticated bits=0) by oceanview.tundraware.com (8.15.2/8.15.2) with ESMTPSA id 04JN8J4q058244 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 19 May 2020 18:08:19 -0500 (CDT) (envelope-from tundra@tundraware.com) Subject: Re: OT: Weird Hardware Problem To: David Christensen , freebsd-questions@freebsd.org References: <0a9f810d-7b4b-f4e6-4b7c-716044a9cf69@tundraware.com> <299b37be-11af-6c0a-6957-54a788d19fe5@tundraware.com> <0df1c88e-3c7b-8c4d-6b4f-95da54a46226@holgerdanske.com> From: Tim Daneliuk Message-ID: <40b15687-e203-8f20-76d3-a408820a0763@tundraware.com> Date: Tue, 19 May 2020 18:08:14 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (oceanview.tundraware.com [45.55.60.57]); Tue, 19 May 2020 18:08:20 -0500 (CDT) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: 04JN8J4q058244 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (not cached, score=-2.099, required 1, ALL_TRUSTED -1.00, AWL 0.80, BAYES_00 -1.90) X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No X-Rspamd-Queue-Id: 49RWlf6xbRz4GTD X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of tundra@tundraware.com designates 45.55.60.57 as permitted sender) smtp.mailfrom=tundra@tundraware.com X-Spamd-Result: default: False [-1.06 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[tundraware.com]; NEURAL_HAM_MEDIUM(-0.48)[-0.484]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.28)[-0.280]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:45.55.32.0/19, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2020 23:08:47 -0000 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 -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/