Re: [dm-crypt] Help request

[Robert Nichols <rnicholsNOSPAM@comcast.net>]

On 7/7/20 3:58 PM, Michael Kjörling wrote:
> On 6 Jul 2020 03:36 +0000, from lacedaemonius1@protonmail.com (lacedaemonius):
>> [ 643.631782] print_req_error: critical target error, dev sdi, sector 11721044993
>> [ 643.631789] Buffer I/O error on dev sdi, logical block 11721044993, async page read
...
> Unfortunately, drives can fail without reporting failures in SMART
> data, and they can fail early. While the probability of either is
> _lower_, it is non-zero.

And, a single bad sector is not going to cause SMART to report a failure.
"FAILING NOW" is not reported until the drive has nearly exhausted its
supply of spare sectors.

The good news is that this LBA, right at the end of a 6TB (nominal)
drive, is a fairly unlikely location for a LUKS header, so even if
this is an actual bad sector your data should be otherwise recoverable.

The output from "smartctl -A" (or the fuller report from "-a") should
be relevant, in particular the "Current_Pending_Sector" raw value.
A non-zero value there indicates bad sectors that are visible to the
OS and will cause an I/O error when read.

-- 
Bob Nichols     "NOSPAM" is really part of my email address.
                 Do NOT delete it.