On 7/14/19 10:05 AM, Tito wrote:
On 7/14/19 4:45 PM, Wols Lists wrote:
On 14/07/19 15:05, Tito wrote:
Hi,
I've got this email address from the MAINTAINERS file in the linux kernel
source, so I hope it is the right place to contact.
I'm running a debian/devuan system for a long time with several
md arrays on the embedded controller and on a ibm M1015 card
reflashed to LSI SAS9211-8i with all drives in passthrough mode.
My typical setup is:
You've got the right place. I can't see any mention of what disks you
have, because that could well be relevant.
Can I point you at the raid wiki for a good read ... :-)
https://raid.wiki.kernel.org/index.php/Linux_Raid
It contains a bunch of advice on troubleshooting and stuff, and it'll
hopefully help you identify anything weird so making it easier for you
to point us in the right direction and provide us with the stuff we need.
Cheers,
Wol
Hi,
thanks for your advice, read the wiki and gathered all info as requested,
hope that attaching them is ok, or do you prefer them in the body.
On 7/14/19 10:05 AM, Tito wrote:> On 7/14/19 4:45 PM, Wols Lists wrote:
>> On 14/07/19 15:05, Tito wrote:
>>> Hi,
>>> I've got this email address from the MAINTAINERS file in the linux kernel
>>> source, so I hope it is the right place to contact.
>>> I'm running a debian/devuan system for a long time with several
>>> md arrays on the embedded controller and on a ibm M1015 card
>>> reflashed to LSI SAS9211-8i with all drives in passthrough mode.
>>> My typical setup is:
>>
>> You've got the right place. I can't see any mention of what disks you
>> have, because that could well be relevant.
>>
>> Can I point you at the raid wiki for a good read ... :-)
>>
>> https://raid.wiki.kernel.org/index.php/Linux_Raid
>>
>> It contains a bunch of advice on troubleshooting and stuff, and it'll
>> hopefully help you identify anything weird so making it easier for you
>> to point us in the right direction and provide us with the stuff we need.
>>
>> Cheers,
>> Wol
>>
>
> Hi,
> thanks for your advice, read the wiki and gathered all info as requested,
> hope that attaching them is ok, or do you prefer them in the body.
To me this looks like your problem:
> Jul 14 07:54:12 debian kernel: [38809.927619] sd 2:0:6:0: [sdg] tag#580 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> Jul 14 07:54:12 debian kernel: [38809.927624] sd 2:0:6:0: [sdg] tag#580 Sense Key : Not Ready [current]
> Jul 14 07:54:12 debian kernel: [38809.927627] sd 2:0:6:0: [sdg] tag#580 Add. Sense: Logical unit not ready, cause not reportable
> Jul 14 07:54:12 debian kernel: [38809.927632] sd 2:0:6:0: [sdg] tag#580 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
FYI there's no overlap between the drives in the raid1 (sda, sdk, sdj) and the drives in the raid5 and raid6.
According to lsdrv sda, sdk, sdj, and sdl are all on the on-board SATA controller. If you've never seen an error on sdl despite it being in the raid6
then I'd pin the blame on the SAS2008 card. You should probably start by checking the firmware version and making sure it's up to date. If it is up to
date then try looking for bugs and updates related to the mpt3sas driver.
--Sarah
