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
