From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219773] External USB disk drive and SSD corruption while connected to USB 3 ports.
Date: Sat, 15 Feb 2025 12:38:42 +0000 [thread overview]
Message-ID: <bug-219773-208809-A98zmxJBwl@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219773-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219773
Michał Pecio (michal.pecio@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michal.pecio@gmail.com
--- Comment #5 from Michał Pecio (michal.pecio@gmail.com) ---
Hi,
1. According to your dmesg snippet UAS was already disabled back then.
2. AFAIK usb-storage uses device reset to recover from various errors, maybe
this is simply a matter of poor USB link quality. Try:
echo 'func handle_tx_event +p' >/proc/dynamic_debug/control
3. Corruption sounds bad. Is it reproducible, i.e. you write more data and more
problems show up? Are things still broken when the disk is read by other
machines?
4. Does the same disk work any better on other machines?
5. FYI, some buggy USB SATA bridges report smaller than actual capacity, which
can cause problems with reading GPT tables at the end of the disk.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-02-15 12:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 21:51 [Bug 219773] New: External USB disk drive and SSD corruption bugzilla-daemon
2025-02-11 21:52 ` [Bug 219773] " bugzilla-daemon
2025-02-12 18:27 ` [Bug 219773] External USB disk drive and SSD corruption while connected to USB 3 ports bugzilla-daemon
2025-02-12 18:28 ` bugzilla-daemon
2025-02-14 10:00 ` bugzilla-daemon
2025-02-15 12:38 ` bugzilla-daemon [this message]
2025-02-15 15:09 ` bugzilla-daemon
2025-02-15 15:09 ` bugzilla-daemon
2025-02-15 15:58 ` bugzilla-daemon
2025-02-15 16:51 ` bugzilla-daemon
2025-02-15 18:41 ` bugzilla-daemon
2025-02-15 18:45 ` bugzilla-daemon
2025-02-15 20:08 ` bugzilla-daemon
2025-02-15 20:25 ` bugzilla-daemon
2025-02-16 16:24 ` bugzilla-daemon
2025-02-17 14:36 ` bugzilla-daemon
2025-02-17 15:53 ` bugzilla-daemon
2025-02-17 17:48 ` bugzilla-daemon
2025-02-20 9:32 ` bugzilla-daemon
2025-02-20 9:34 ` bugzilla-daemon
2025-02-27 13:21 ` bugzilla-daemon
2025-02-27 13:22 ` bugzilla-daemon
2025-02-27 13:25 ` bugzilla-daemon
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=bug-219773-208809-A98zmxJBwl@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@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