From nobody Sat May 21 04:30:13 2022 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id F2AD41AE2E1C for ; Sat, 21 May 2022 04:30:20 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (jacobs.geeks.org [204.153.247.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4L4rHJ0FfWz3h63 for ; Sat, 21 May 2022 04:30:19 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (localhost [127.0.0.1]) by after-clamsmtpd.geeks.org (Postfix) with ESMTP id 50E974116F for ; Fri, 20 May 2022 23:30:13 -0500 (CDT) Received: by mail.geeks.org (Postfix, from userid 1003) id 39B004121D; Fri, 20 May 2022 23:30:13 -0500 (CDT) Date: Fri, 20 May 2022 23:30:13 -0500 From: Doug McIntyre To: freebsd-questions@freebsd.org Subject: Re: OT: Weird Hardware Problem Message-ID: References: <0a9f810d-7b4b-f4e6-4b7c-716044a9cf69@tundraware.com> <8b13e2f5-6ff4-ecc2-7036-c88cff0f5b6b@tundraware.com> <8732b894-0962-3546-4697-4c2ae0658cb8@kicp.uchicago.edu> <20200520182154.GA87305@neutralgood.org> <4287e288d0655880e1d6bb3598662eeb6a5a30e3.camel@adminart.net> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4287e288d0655880e1d6bb3598662eeb6a5a30e3.camel@adminart.net> X-Virus-Scanned: ClamAV using ClamSMTP X-Rspamd-Queue-Id: 4L4rHJ0FfWz3h63 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of merlyn@geeks.org designates 204.153.247.1 as permitted sender) smtp.mailfrom=merlyn@geeks.org X-Spamd-Result: default: False [-3.30 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[geeks.org]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-questions]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7753, ipnet:204.153.244.0/22, country:US]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Sat, May 21, 2022 at 12:14:35AM +0200, hw wrote: > In about 25 years, I have seen only two PSUs fail. One was plugged up > by dust and started smoking and might have set the place on fire if the... When you have a datacenter full of devices, you'll see alot more failures... I've gone through hundreds of fried power supplies on hardware. Sometimes its the caps drying out and popping. Sometimes the fans get clogged up and components overheat. Sometimes something fries out in switching guts. The fun ones are when one side fries itself, and feeds back into the redundant side and surges and trips out that side as well. Always something to keep you on your toes.