From: Martin Steigerwald <martin@lichtvoll.de>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev,
linux-usb@vger.kernel.org,
"Holger Hoffstätte" <holger@applied-asynchrony.com>,
linux-bcachefs@vger.kernel.org
Subject: Re: I/O errors while writing to external Transcend XS-2000 4TB SSD
Date: Fri, 15 Mar 2024 10:08:10 +0100 [thread overview]
Message-ID: <4894644.GXAFRqVoOG@lichtvoll.de> (raw)
In-Reply-To: <mqlu3q3npll5wxq5cfuxejcxtdituyydkjdz3pxnpqqmpbs2cl@tox3ulilhaq2>
Hi!
Kent Overstreet - 11.02.24, 19:51:32 CET:
> He only got errors after an hour or so, or 10 minutes with UAS disabled;
> we send flushes once a second. Sounds like a screwy device.
Kingston support intends to RMA the XS-2000 4 TB SSD with a variant with a
newer firmware version, in case they have it available, while they work on
a newer firmware version for the device variant the error happened on.
So it appears the device has a bug. I will keep you posted, once I either
receive that other variant or a firmware upgrade for the existing one.
I am happy with Kingston support so far. It takes quite a while, but they
are taking the issue for real instead of writing use Windows instead of
Linux or something like that :) - like I read before in other occasions
with hardware from other suppliers. Thanks!
Best,
--
Martin
prev parent reply other threads:[~2024-03-15 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 15:42 I/O errors while writing to external Transcend XS-2000 4TB SSD Martin Steigerwald
2024-02-11 16:02 ` Holger Hoffstätte
2024-02-11 17:06 ` Martin Steigerwald
2024-02-11 18:51 ` Kent Overstreet
2024-02-12 15:52 ` Martin Steigerwald
2024-02-12 20:42 ` Kent Overstreet
2024-02-15 11:09 ` Martin Steigerwald
2024-02-15 15:19 ` Alan Stern
2024-02-15 15:36 ` Martin Steigerwald
2024-03-15 9:08 ` Martin Steigerwald [this message]
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=4894644.GXAFRqVoOG@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=holger@applied-asynchrony.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).