From: Wols Lists <antlists@youngman.org.uk>
To: Phil Turmel <philip@turmel.org>,
"David C. Rankin" <drankinatty@suddenlinkmail.com>,
mdraid <linux-raid@vger.kernel.org>
Subject: Re: Linux 5.5 Breaks Raid1 on Device instead of Partition, Unusable I/O
Date: Mon, 2 Mar 2020 13:32:42 +0000 [thread overview]
Message-ID: <5E5D0AFA.1030701@youngman.org.uk> (raw)
In-Reply-To: <9b1ceff4-1299-8e8a-cbc9-da717c72bba3@turmel.org>
On 02/03/20 11:44, Phil Turmel wrote:
> Hi David,
>
> On 3/2/20 4:27 AM, David C. Rankin wrote:
>> On 03/02/2020 01:08 AM, Chris Murphy wrote:
>>> smart also reports for /de/sdc
>>>
>>> 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
>>>
>>>
>>> So I'm suspicious of timeout mismatch as well.
>>> https://raid.wiki.kernel.org/index.php/Timeout_Mismatch
>>>
>>>
>>> Chris Murphy
>>>
>>
>> The strace between the virtualbox host and guess show and number of
>> I/O waits
>> that would seem to fit some timeout issue like that. But according to the
>> page, both drives in this array provide:
>>
>> SCT capabilities: (0x1085) SCT Status supported.
>
> SCT Status itself isn't sufficient. You must have ERC "Error Recovery
> Control", an optional part of SCT.
>
> smartctl -a doesn't expose that. Use smartctl -x in general, or
> smartctl -l scterc to specifically check the needed setting.
>
It's a Seagate Barracuda ... nuff said
(For David, Barracudas don't support SCT/ERC - they are not recommended
for raid. Okay for 1 but definitely not anything else. Get an Ironwolf
to replace it.)
Cheers,
Wol
next prev parent reply other threads:[~2020-03-02 13:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 1:50 Linux 5.5 Breaks Raid1 on Device instead of Partition, Unusable I/O David C. Rankin
2020-03-02 5:25 ` Roman Mamedov
2020-03-02 6:38 ` David C. Rankin
2020-03-02 6:46 ` David C. Rankin
2020-03-02 6:51 ` Roman Mamedov
2020-03-02 6:57 ` David C. Rankin
2020-03-02 7:08 ` Chris Murphy
2020-03-02 9:27 ` David C. Rankin
2020-03-02 11:44 ` Phil Turmel
2020-03-02 13:32 ` Wols Lists [this message]
2020-03-02 21:21 ` David C. Rankin
2020-03-02 21:09 ` Chris Murphy
2020-03-04 22:53 ` David C. Rankin
2020-03-05 17:18 ` Wols Lists
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=5E5D0AFA.1030701@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=drankinatty@suddenlinkmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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;
as well as URLs for NNTP newsgroup(s).