public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Campbell <brad@fnarfbargle.com>
To: "Justin Piszcz" <jpiszcz@lucidpixels.com>,
	"Dragan Milivojević" <galileo@pkm-inc.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-nvme@lists.infradead.org, linux-raid@vger.kernel.org
Subject: Re: WD Red SN700 4000GB, F/W: 11C120WD (Device not ready; aborting reset, CSTS=0x1)
Date: Mon, 8 Dec 2025 16:43:43 +0800	[thread overview]
Message-ID: <f6f1a5fd-814e-49f4-901e-28110feed5ee@fnarfbargle.com> (raw)
In-Reply-To: <CAO9zADx+5cNAxaz4R7SAndY5EX1z4V8i1e=rAdBbOTmxLmcopw@mail.gmail.com>

On 1/12/25 22:14, Justin Piszcz wrote:
> On Tue, Nov 25, 2025 at 10:19 AM Dragan Milivojević <galileo@pkm-inc.com> wrote:
>>
>>> Issue/Summary:
>>> 1. Usually once a month, a random WD Red SN700 4TB NVME drive will
>>> drop out of a NAS array, after power cycling the device, it rebuilds
>>> successfully.
>>>
>>
>> Seen the same, although far less frequent, with Samsung SSD 980 PRO on
>> a Dell PowerEdge R7525.
>> It's the nature of consumer grade drives, I guess.
> 
> As this affects multiple NVME manufacturers, are you aware of any
> consumer-level NVME drives that do not have this problem or is moving
> to U.2/U.3 server drives necessary to avoid drives dropping offline?
> 
> 

Late to the party, but I've got Samsung 960Pro/970evo/980Pro, Crucial P2/T500, Kingston KC2000 and SKHynix P31 nvme drives in 24/7 machines and have *never* had an issue like this. 
The 960Pro suffers from long term slowdown, and the P2 is just an awful performer, but none of them have ever suffered from connectivity issues. The Samsungs, Kingston and the T500 are all in arrays.

None of these machines get power cycled and they might get rebooted once a year (or thereabouts).

  reply	other threads:[~2025-12-08  9:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 14:42 WD Red SN700 4000GB, F/W: 11C120WD (Device not ready; aborting reset, CSTS=0x1) Justin Piszcz
2025-11-25 14:48 ` Dr. David Alan Gilbert
2025-12-01 14:09   ` Justin Piszcz
2025-11-25 14:56 ` Keith Busch
2025-12-01 14:13   ` Justin Piszcz
2025-12-02  2:47     ` Keith Busch
2025-11-25 15:19 ` Dragan Milivojević
2025-11-25 16:57   ` Paul Rolland
2025-12-08 13:37     ` Sinisa
2025-11-25 22:37   ` Jani Partanen
2025-12-01 14:14   ` Justin Piszcz
2025-12-08  8:43     ` Brad Campbell [this message]
2025-11-25 18:25 ` Wol
2025-11-26  0:15   ` David Sterba
2025-11-26 12:51     ` Roger Heflin
2025-12-01 14:16   ` Justin Piszcz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f6f1a5fd-814e-49f4-901e-28110feed5ee@fnarfbargle.com \
    --to=brad@fnarfbargle.com \
    --cc=galileo@pkm-inc.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox