All data disk missing after 6.8.0 update - on two servers

HP 468406-B21 was a expander, it may not the problem source.

 

From the lspci info. (6.7.2), SAS controller load with driver "isci", what would show in 6.8 ?

 

03:00.0 Serial Attached SCSI controller [0107]: Intel Corporation C606 chipset Dual 4-Port SATA/SAS Storage Control Unit [8086:1d68] (rev 06)
    Subsystem: Super Micro Computer Inc C606 chipset Dual 4-Port SATA/SAS Storage Control Unit [15d9:0626]
    Kernel driver in use: isci
    Kernel modules: isci

Edited January 3, 2020 by Benson

1 hour ago, Benson said:

From the lspci info. (6.7.2), SAS controller load with driver "isci", what would show in 6.8 ?

That's the same driver used in v6.7.2, though likely a newer version for the newer kernel, it does look like a problem with the Intel SCU controller, first time I remember seeing this controller used with an expander, but it should work with one.

Miss that

 

"I have a 3rd system that updated fine to 6.8.0 but it has no sas controller. "

 

Does OP means have same MB in 3rd system but without expander (HP 468406-B21) and work ?

Edited January 3, 2020 by Benson

No completely different. The two systems that are effected are identical.

The expander was working with the intel SCU until ver 6.8.0. update without issue.

The issue is the Intel SCU controller, don't know if the same problem would be present without an expander, but that is kind of irrelevant here since you need to use one and it should work, as it did in the past, not sure what LT can do about it, since it's likely a kernel/driver issue, unless there's already a fix.

OK, what I find strange than is that the mother board has 2 sas ports on it. One is connected to the expander card and none of the drives show up. And the other connected to my parity drives and they do show up in 6.8.0.

Edited January 3, 2020 by josephb1701

Here is full diagnostics from 6.7.2 and 6.8.0

tower2-diagnostics-20200103-1429(6_7_2).zip tower2-diagnostics-20200103-0933(6_8_0).zip

32 minutes ago, josephb1701 said:

And the other connected to my parity drives and they do show up in 6.8.0.

OK, so that confirms the problem is only with the expander connected devices, interestingly enough the expander is detected on v6.8, just not any connected devices:

 

[1:0:20:0]   enclosu HP       HP SAS EXP Card  2.02  -          /dev/sg3

I am just afraid there isn't going to be an easy solution for your problem, especially if the controller works without an expander, and can probably work with a different expander, IMHO your best bet would be to get an LSI HBA if that's possible.

 

 

That's good confirm it is expander and OS issue.

 

If you can't wait LT for fix, you may try mask the PCIe finger pin B5 & B6 on the expander whick are same solution for HBA for booting issue.

 

From web, it confirm this expander could work without a real PCIe slot, but I just don't know which PCIe signal cause this prolem.

 

There are six LED on expander, does any difference in 6.7 and 6.8

Edited January 3, 2020 by Benson

Tried to update to 6.8.1 tonight and same problem. Still no drives are showing on the controller. checked the led they are the same ones lit and blinking when on ver 6.7.2

tower2-diagnostics-20200116-2230.zip

 

27 minutes ago, josephb1701 said:

checked the led they are the same ones lit and blinking when on ver 6.7.2

Note.

 

 

Futher check those log again, in fact, the HDDs were detect in 6.8 but with error. Why it need "lower device linkrate" but no need in 6.7 ?????

 

Jan 16 22:35:09 Tower2 kernel: ex 5001438007be0905 phy05 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate
Jan 16 22:35:09 Tower2 kernel: ex 5001438007be0905 phy05 SATA device set linkrate successfully

 

 

Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0900 phy00 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0900 phy00 SATA device set linkrate successfully
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0901 phy01 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0901 phy01 SATA device set linkrate successfully
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0902 phy02 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0902 phy02 SATA device set linkrate successfully
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0903 phy03 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0903 phy03 SATA device set linkrate successfully
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0904 phy04 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0904 phy04 SATA device set linkrate successfully
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0905 phy05 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0905 phy05 SATA device set linkrate successfully
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0906 phy06 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0906 phy06 SATA device set linkrate successfully
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0907 phy07 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0907 phy07 SATA device set linkrate successfully
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0908 phy08 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0908 phy08 SATA device set linkrate successfully
Jan  3 09:38:13 Tower2 kernel: ex 5001438007be0909 phy09 SATA device linkrate > min pathway connection rate, attempting to lower device linkrate

 

 

Jan  3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87
Jan  3 09:38:13 Tower2 kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x11)
Jan  3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87
Jan  3 09:38:13 Tower2 kernel: ata10.00: failed to IDENTIFY (I/O error, err_mask=0x11)
Jan  3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87
Jan  3 09:38:13 Tower2 kernel: ata21.00: failed to IDENTIFY (I/O error, err_mask=0x11)
Jan  3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87
Jan  3 09:38:13 Tower2 kernel: ata11.00: failed to IDENTIFY (I/O error, err_mask=0x11)
Jan  3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87
Jan  3 09:38:13 Tower2 kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x11)
Jan  3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87
Jan  3 09:38:13 Tower2 kernel: ata15.00: failed to IDENTIFY (I/O error, err_mask=0x11)
Jan  3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87
Jan  3 09:38:13 Tower2 kernel: ata13.00: failed to IDENTIFY (I/O error, err_mask=0x11)
Jan  3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87
Jan  3 09:38:13 Tower2 kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x11)
Jan  3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87
Jan  3 09:38:13 Tower2 kernel: ata14.00: failed to IDENTIFY (I/O error, err_mask=0x11)
Jan  3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87
Jan  3 09:38:13 Tower2 kernel: ata8.00: failed to IDENTIFY (I/O error, err_mask=0x11)
Jan  3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87
Jan  3 09:38:13 Tower2 kernel: ata23.00: failed to IDENTIFY (I/O error, err_mask=0x11)
Jan  3 09:38:13 Tower2 kernel: sas: sas_ata_task_done: SAS error 87
Jan  3 09:38:13 Tower2 kernel: ata18.00: failed to IDENTIFY (I/O error, err_mask=0x11)

Edited January 17, 2020 by Benson