From: Martin Steigerwald <martin@lichtvoll.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Kent Overstreet" <kent.overstreet@linux.dev>,
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, linux-block@vger.kernel.org
Subject: Re: I/O errors while writing to external Transcend XS-2000 4TB SSD
Date: Thu, 15 Feb 2024 16:36:00 +0100 [thread overview]
Message-ID: <2140271.OBFZWjSADL@lichtvoll.de> (raw)
In-Reply-To: <eec1464d-4e9f-48b5-b619-868f0e5c1d4d@rowland.harvard.edu>
Alan Stern - 15.02.24, 16:19:54 CET:
> > First I will have a look on how to see what USB power management
> > options may be in place and how to tell Linux to keep the USB port
> > the SSD is connected to at all times.
> >
> > Let's see how this story unfolds. At least I am in no hurry about it.
>
> This may not be an issue of power management but rather one of
> insufficient power. A laptop may not provide enough power through its
> USB ports for the Transcend SSD to work properly under load.
>
> You can test this by connecting a powered UBS-3 hub between the laptop
> and the drive.
Interesting idea. Maybe the Transcend XS-2000 4TB needs more power than
the Sandisk Extreme Pro 2TB.
Not sure whether I have one at hand with USB-C here, cause my regular USB
hub only has USB-A connectors. Need to look for one with enough USB-A and
USB-C connectors as I use an USB hub as replacement for a docking station.
But I do have at least optionally powered hub with USB-C one at another
place. It does not have many ports. But for the task ahead one USB-C port
is sufficient.
I will try this as well. Thanks.
Best,
--
Martin
next prev parent reply other threads:[~2024-02-15 15:36 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 [this message]
2024-03-15 9:08 ` Martin Steigerwald
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=2140271.OBFZWjSADL@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=holger@applied-asynchrony.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.