From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-nvme@lists.infradead.org, linux-raid@vger.kernel.org,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: WD Red SN700 4000GB, F/W: 11C120WD (Device not ready; aborting reset, CSTS=0x1)
Date: Tue, 25 Nov 2025 14:48:32 +0000 [thread overview]
Message-ID: <aSXBwBoBZp9t890U@gallifrey> (raw)
In-Reply-To: <CAO9zADxCYgQVOD9A1WYoS4JcLgvsNtGGr4xEZm9CMFHXsTV8ww@mail.gmail.com>
* Justin Piszcz (jpiszcz@lucidpixels.com) wrote:
> Hello,
>
> 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.
>
> Questions:
> 3. Are there any debug options that can be enabled that could help to
> pinpoint the root cause?
Have you tried using the 'nvme' command to see if the drives have
anything in their smart or error logs?
(I don't know any more than suggesting looking at those logs to see
if the drive is showing errors or what it says during the timeouts,
so I'll leave it to others to dig deeper).
Dave
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2025-11-25 14:48 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 [this message]
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
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=aSXBwBoBZp9t890U@gallifrey \
--to=linux@treblig.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-btrfs@vger.kernel.org \
--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