After upgrade from 6.4-5 to 6.4-6 hypervisor lost fc luns

[BadSimon]

Hi all!

Subject. After reboot don't determines luns on fc filer.

Make rescan-scsi-bus, and nothing. But hypervisor determines hba adapter.

Everything worked before the update.

How can i fix that?

Thx.

 

[BadSimon]

Nobody can help me?

 

[aaron]

Was a new kernel installed as well? You could try to reboot and select an older kernel to see if it works with that. In general a bit more infos would be needed. E.g. what kind of FC cards do you have? Anything in the system logs / dmesg output that indicates a problem?

 

[BadSimon]

Thx a lot! I was do and all good again!

Kernels 5.4.44-2 and 5.4.106-1 work fine.

Srv's - Dell R710, Supermicro.
FC Filer - Netapp FAS2020.
FC HBA - Qlogic 2462.

I do not looking for any errors with HBA.

If i can help with more information or action from my side just write about it.

 

[tell]

Hi @BadSimon @aaron,
I wonder if you have any more insight on this issue.
I just installed the current 6.4 updates which included an kernel update
from 5.4.106-1-pve
to 5.4.128-1-pve
and I don't see my FC attached LUNs any longer as well.

Rebooting to kernel 5.4.106-1 everything is back to normal.

FC HBA used is Qlogic QLE2462
The storage server is DataCore SANsymphony.
FC connectivity gets established and the server (port) appears as online on the storage server.
Looking at dmesg the HBA also seems to get initialized properly:

[ 8560.448729] scsi host1: qla2xxx
[ 8560.450189] qla2xxx [0000:09:00.0]-00fb:1: QLogic QLE2462 - PCI-Express Dual Channel 4Gb Fibre Channel HBA.
[ 8560.450197] qla2xxx [0000:09:00.0]-00fc:1: ISP2432: PCIe (2.5GT/s x4) @ 0000:09:00.0 hdma- host#=1 fw=8.07.00 (9496).
[ 8560.450461] qla2xxx [0000:09:00.1]-001d: : Found an ISP2432 irq 62 iobase 0x00000000ac81fc19.
[ 8560.796508] qla2xxx [0000:09:00.0]-500a:1: LOOP UP detected (4 Gbps).

Still no disk does appear using kernel 5.4.128-1-pve.
rmmod/insmod of qla2xxx does not help either.

Is there anything else I can try?

Thanks

 

[tell]

Short update:
- same issue with kernel 5.4.128-2-pve
- Upgrade to Proxmox 7 with kernel 5.11.22-3-pve -> disk is visible again

So a possible solution or workaround appears to be upgrading to Proxmox 7.