No "read error corrected" message even after read error occurred twice on the same sector.

Solution Verified - Updated -

Issue

  • No "read error corrected" message even after read error occurred twice on the same sector.

expected behavior

[Sun Mar 15 18:58:12 2020] blk_update_request: critical medium error, dev sdb, sector 8386963088
[Sun Mar 15 18:58:14 2020] blk_update_request: critical medium error, dev sdb, sector 8386963088
[Sun Mar 15 18:58:14 2020] md/raid:md127: read error corrected (8 sectors at 8386961040 on sdb1) - # 2048 difference as sdb1 partition

no read error corrected messages

[Sun Mar 15 18:58:17 2020] blk_update_request: critical medium error, dev sdb, sector 8386965680
[Sun Mar 15 18:58:19 2020] blk_update_request: critical medium error, dev sdb, sector 8386965680

Environment

  • Red Hat Enterprise Linux 7
    • 3.10.0-1062.9.1.el7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content