From nobody Sat May 21 09:52:12 2022 X-Original-To: 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 B0AFF1B3DABD for ; Sat, 21 May 2022 09:52:21 +0000 (UTC) (envelope-from hw@adminart.net) Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [85.215.255.25]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4L4zQr43k8z4lnp for ; Sat, 21 May 2022 09:52:20 +0000 (UTC) (envelope-from hw@adminart.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1653126733; s=strato-dkim-0002; d=adminart.net; h=References:In-Reply-To:Date:To:From:Subject:Message-ID:Cc:Date:From: Subject:Sender; bh=XWhoKZtmFQJQnDgXaz5VMYIfP5TVF9TDev8z19Rge5E=; b=Khx7NOxiI9Kz8JfZhSTi8mWIA3EVRT7ns8J24kOnQP5iLCg5bTEkLdpE3zeIXxW8Mx 8PqCHSlI6/8G2ZBlvUTCf/6wo89RMR107sCAMmRNkN+VOGgXJZpAAFQG8pSIzoVZ2+0s QgEBl47hojfJZcI24GDWIH1m8z/K61rIQ4aHhD5/ubV3zn+w/+IV50V4wPrwQV4LRzrs gAs8cKuNWt9Gwo2515JhbgkBXDa6tcbn3xj8pNv+Hgm3sFFrKE0oAWpjGV9s8RzIJrQx TbqdS/kj4cJB2sPiLgIdYox03fdl5YH17H2eFOg2fsvIhn0YVAZrGkGicBtkqlhommPV Ha6Q== X-RZG-AUTH: ":O2kGeEG7b/pS1Ey9Rna9iAZFrfz26y6zbtmqiE/f0+UVPWzfkhbRoUzSCTTNnjIupuXQshKqSmqnukM53Tih9Ec7unYvBHoX7Wi69g4bwSlGyNUo" X-RZG-CLASS-ID: mo00 Received: from [IPv6:2a09:8e40:352b:d900:8a06:20b1:cf3e:1602] by smtp.strato.de (RZmta 47.45.0 AUTH) with ESMTPSA id e053e4y4L9qCIrI (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate) for ; Sat, 21 May 2022 11:52:12 +0200 (CEST) Message-ID: <101c1ce69d461c329ce028753fb60a217b7e6906.camel@adminart.net> Subject: Re: OT: Weird Hardware Problem From: hw To: questions@freebsd.org Date: Sat, 21 May 2022 11:52:12 +0200 In-Reply-To: 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> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.1 (3.44.1-1.fc36) 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 X-Rspamd-Queue-Id: 4L4zQr43k8z4lnp X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=adminart.net header.s=strato-dkim-0002 header.b=Khx7NOxi; dmarc=none; spf=none (mx1.freebsd.org: domain of hw@adminart.net has no SPF policy when checking 85.215.255.25) smtp.mailfrom=hw@adminart.net X-Spamd-Result: default: False [-3.29 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[adminart.net:s=strato-dkim-0002]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[adminart.net]; DKIM_TRACE(0.00)[adminart.net:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[85.215.255.25:from]; NEURAL_HAM_MEDIUM(-0.99)[-0.991]; MLMMJ_DEST(0.00)[questions]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6724, ipnet:85.215.255.0/24, country:DE]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Fri, 2022-05-20 at 23:30 -0500, Doug McIntyre wrote: > On Sat, May 21, 2022 at 12:14:35AM +0200, hw wrote: > > In about 25 years, I have seen only two PSUs fail.=C2=A0 One was plugge= d > > up > > by dust and started smoking and might have set the place on fire if > > the... >=20 >=20 > 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. >=20 > Sometimes its the caps drying out and popping. Sometimes the fans get > clogged up and components overheat. Sometimes something fries out in > switching guts. >=20 > 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.=20 >=20 > Always something to keep you on your toes. What would you say is the sample size and the rate of failure? I've seen only hundreds, not thousands of PSUs. BTW, this thread is 2 years old and I happened to have my mails sorted by subject instead of by date and didn't check the year, so it seemed new. If I had realised it's 2 years old, I wouldn't have answered ... But I wonder what happened to the original problem; has it ever been solved, and what caused it?