Hello,
I have a Dell t30 server, few days ago i updated my ESXi with fresh install to v 7u3, and also my TrueNAS installation on it as a fresh one with recovering configuration (users, pools, SMB...)
My server has PERC 310 HBA card in IT mode with successful pass-trough. I can not tell if this problem was before, as i did not looked in logs of my server before, but it was running ESXi 6.7u3 and Freenas 11.2 for few years without problem.
I did bios update also few days ago.
So now all is working as should, server is booting correctly, disk on HBA card are visible, Pools are running fine, Im using SFP+ NIC on it and read speed is about 300MB/s over samba and write around 200MB/s
But inside logs i see a lot of this messages:
I search trough all internet and found only old problem here on forum, but never resolved. Now its 6 years after this happen to someone before, but i see i have this same problem now, Even if ESXi and Truenas is now in newer version then in described case:
Is there anyone who can tell me if i should be worried about this reported problem in logs?
Is there anyone who knows what else can be checked, any parameter change on ESXi host?
Is there anyone who have that same configuration like me PERC 310 + ESXi 7u3 + TrueNAS and can check on ESXi side dmesg command?
I have a Dell t30 server, few days ago i updated my ESXi with fresh install to v 7u3, and also my TrueNAS installation on it as a fresh one with recovering configuration (users, pools, SMB...)
My server has PERC 310 HBA card in IT mode with successful pass-trough. I can not tell if this problem was before, as i did not looked in logs of my server before, but it was running ESXi 6.7u3 and Freenas 11.2 for few years without problem.
I did bios update also few days ago.
So now all is working as should, server is booting correctly, disk on HBA card are visible, Pools are running fine, Im using SFP+ NIC on it and read speed is about 300MB/s over samba and write around 200MB/s
But inside logs i see a lot of this messages:
Every 5 minutes2024-01-04T16:03:59.399Z cpu2:528317)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0x4d) from (vmm0:TrueNAS)
2024-01-04T16:03:59.399Z cpu2:528317)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0x4d) from (vmm0:TrueNAS)
2024-01-04T16:03:59.416Z cpu2:528317)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0x4d) from (vmm0:TrueNAS)
2024-01-04T16:03:59.416Z cpu2:528317)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0x4d) from (vmm0:TrueNAS)
2024-01-04T16:03:59.416Z cpu2:528317)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0xb7) from (vmm0:TrueNAS)
2024-01-04T16:03:59.416Z cpu2:528317)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0x37) from (vmm0:TrueNAS)
2024-01-04T16:13:59.392Z cpu1:528317)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0x4d) from (vmm0:TrueNAS)
2024-01-04T16:13:59.393Z cpu3:528314)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0x4d) from (vmm0:TrueNAS)
2024-01-04T16:13:59.410Z cpu3:528314)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0x4d) from (vmm0:TrueNAS)
2024-01-04T16:13:59.410Z cpu3:528314)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0x4d) from (vmm0:TrueNAS)
2024-01-04T16:13:59.410Z cpu3:528314)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0xb7) from (vmm0:TrueNAS)
2024-01-04T16:13:59.410Z cpu3:528314)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0x37) from (vmm0:TrueNAS)
2024-01-04T16:18:59.399Z cpu1:528314)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0x4d) from (vmm0:TrueNAS)
2024-01-04T16:18:59.400Z cpu1:528314)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0x4d) from (vmm0:TrueNAS)
2024-01-04T16:18:59.417Z cpu3:528317)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0x4d) from (vmm0:TrueNAS)
2024-01-04T16:18:59.417Z cpu3:528317)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0x4d) from (vmm0:TrueNAS)
2024-01-04T16:18:59.417Z cpu3:528317)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0xb7) from (vmm0:TrueNAS)
2024-01-04T16:18:59.417Z cpu3:528317)VSCSIFs: 4367: handle 2269091352027138(GID:8194)(vscsi0:0):Invalid Opcode (0x37) from (vmm0:TrueNAS)
I search trough all internet and found only old problem here on forum, but never resolved. Now its 6 years after this happen to someone before, but i see i have this same problem now, Even if ESXi and Truenas is now in newer version then in described case:
Is there anyone who can tell me if i should be worried about this reported problem in logs?
Is there anyone who knows what else can be checked, any parameter change on ESXi host?
Is there anyone who have that same configuration like me PERC 310 + ESXi 7u3 + TrueNAS and can check on ESXi side dmesg command?