linux-kernel - Re: WD Red SN700 4000GB, F/W: 11C120WD (Device not ready; aborting reset, CSTS=0x1)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8d03ba23-6677-4002-82cd-21502c42821a@sotapeli.fi>
Date: Wed, 26 Nov 2025 00:37:06 +0200
From: Jani Partanen <jiipee@...apeli.fi>
To: Dragan Milivojević <galileo@...-inc.com>,
 Justin Piszcz <jpiszcz@...idpixels.com>
Cc: LKML <linux-kernel@...r.kernel.org>, linux-nvme@...ts.infradead.org,
 linux-raid@...r.kernel.org
Subject: Re: WD Red SN700 4000GB, F/W: 11C120WD (Device not ready; aborting
 reset, CSTS=0x1)

On 25/11/2025 17.19, Dragan Milivojević 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.

I dont know if this WD issue is same issue that I had with WD_BLACK 
SN770 2TB drive, but I share what I know anyway.

That drive cannot handle 4K LBA. It works fine with 512k LBA, but with 
4K it will die sooner or later, usually when you hit it with heavy IO.

WD has know this for years and havent done anything. So I think it is 
safe to say that its hardware issue what cannot be fixed with firmware, 
other than disabling ability to even switch to 4K LBA but they havent 
done that. What it turns tell me how much they care. Good thing is that 
there is other brands.

Lot of talk about that issue here: 
https://github.com/openzfs/zfs/discussions/14793

I think there was also some other WD drives suffering this same issue.

And this is nothing to do with linux or zfs, its purely WD drive issue 
because I originally got it in windows, then switched drive to linux to 
test it out and same happened with linux.

// Jani