Linux XFS filesystem development
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 220669] Drive issues cause system and coredump and reboot
Date: Thu, 16 Oct 2025 08:09:11 +0000	[thread overview]
Message-ID: <bug-220669-201763-hV0yeIVPrj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220669-201763@https.bugzilla.kernel.org/>

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

--- Comment #4 from Artem S. Tashkinov (aros@gmx.com) ---
> [  998.356008] sd 0:0:21:0: [sdv] tag#415 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE cmd_age=3s
> [  998.365528] sd 0:0:21:0: [sdv] tag#415 Sense Key : Medium Error [current]
> [descriptor]
> [  998.373544] sd 0:0:21:0: [sdv] tag#415 Add. Sense: Unrecovered read error
> [  998.380347] sd 0:0:21:0: [sdv] tag#415 CDB: Read(16) 88 00 00 00 00 05 01
> 1f 6d 90 00 00 00 08 00 00
> [  998.389524] blk_update_request: critical medium error, dev sdv, sector
> 21493673360 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0

You may need to replace your failing hardware first.

-- 
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-10-16  8:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16  0:10 [Bug 220669] New: Drive issues cause system and coredump and reboot bugzilla-daemon
2025-10-16  0:19 ` [Bug 220669] " bugzilla-daemon
2025-10-16  4:38 ` [Bug 220669] New: " Dave Chinner
2025-10-16  4:38 ` [Bug 220669] " bugzilla-daemon
2025-10-16  8:05 ` bugzilla-daemon
2025-10-16  8:09 ` bugzilla-daemon [this message]
2025-10-16 11:10 ` 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-220669-201763-hV0yeIVPrj@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-xfs@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