From nobody Tue Feb 13 19:56:52 2024 X-Original-To: freebsd-current@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 4TZBtY3jGRz59dRL for ; Tue, 13 Feb 2024 19:57:09 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [66.165.241.226]) (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 4TZBtX6ZlFz4K3t; Tue, 13 Feb 2024 19:57:08 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1707854209; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=GRGggJYJjz+0MeLRAeEWM2R37InBbW1RkQNT3b1Hzws=; b=Wjp8gtrUwLv8ZN8zNWRRdlu3zBYvP3VCeNpvj6/R8eoglfILYMBfUlJWZYzECTP+tMH1MR S2+Az9vtasbDDiQz0jSEXjQZjrB6RHDeLROTMTtHksFL5QzVKnhLMCGQrBx2JqSXa1O6VF NrhziPDr4z1ngichtOxEeOafewJQtj8= Received: from [192.168.1.160] ( [47.150.83.63]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id c67f3c74 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 13 Feb 2024 19:56:48 +0000 (UTC) Message-ID: <65cddfff-84ab-45e4-bcc5-84fc8f5784cb@nomadlogic.org> Date: Tue, 13 Feb 2024 11:56:52 -0800 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: nvme controller reset failures on recent -CURRENT Content-Language: en-US To: Don Lewis , Warner Losh Cc: Maxim Sobolev , FreeBSD current , John Baldwin References: From: Pete Wright In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:29802, ipnet:66.165.240.0/22, country:US] X-Rspamd-Queue-Id: 4TZBtX6ZlFz4K3t X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated >> There's a tiny chance that this could be something more exotic, >> but my money is on hardware gone bad after 2 years of service. I don't think >> this is 'wear out' of the NAND (it's only 15TB written, but it could be if >> this >> drive is really really crappy nand: first generation QLC maybe, but it seems >> too new). It might also be a connector problem that's developed over time. >> There might be a few other things too, but I don't think this is a U.2 drive >> with funky cables. > The system was probably idle the majority of those two years of power on > time. > > It's one of these: > https://www.techpowerup.com/ssd-specs/intel-660p-512-gb.d437 > I've seen comments that these generally don't need cooling. > > I just ordered a heatsink with some nice big fins, but it will take a > week or more to arrive. just wanted to add another data-point to this discussion.  i had a crucial NVME drive on my workstation that recently was showing similar problems.  after much debugging i came to the same conclusion that it was getting too hot.  i went ahead an purchased a Sabrent NVME drive that came with a heat sink.  i've also starting making much more use of my workstation (and the disk subsystem) and have had zero issues. so lessons learnt: 1. M.2 nvme really does need proper cooling, much more so than traditional SATA/SAS/SCSI drives. 2. not all vendors do a great job reporting the health of devices -pete -- Pete Wright pete@nomadlogic.org