All of lore.kernel.org
 help / color / mirror / Atom feed
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 16:51:03 +0000	[thread overview]
Message-ID: <bug-219773-208809-onsRXaprGw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219773-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=219773

--- Comment #9 from Frederic Bezies (fredbezies@gmail.com) ---
Modification done. I tried with my external USB HDD copying big files. I do not
have access of the previous USB peripheral .

Here is the output while copying 2 big tar.xz archives (6 Go each).


[11012.004194] sd 6:0:0:0: [sdb] 976773164 512-byte logical blocks: (500 GB/466
GiB)
[11012.004519] sd 6:0:0:0: [sdb] Write Protect is off
[11012.004523] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
[11012.004846] sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[11012.070815]  sdb: sdb1
[11012.070970] sd 6:0:0:0: [sdb] Attached SCSI disk
[11012.324232] xhci_hcd 0000:30:00.3: Stalled endpoint for slot 1 ep 2
[11355.077282] usb 4-1: USB disconnect, device number 2
[11355.166387] sd 6:0:0:0: [sdb] Synchronizing SCSI cache
[11355.166436] sd 6:0:0:0: [sdb] Synchronize Cache(10) failed: Result:
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK


Weird there is no other output. I'll try another external USB SSD as soon as
possible.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2025-02-15 16:51 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
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 [this message]
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-onsRXaprGw@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 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.