NICs gone after upgrade

[jfrancais]

Good morning, looking for some assistance.  I upgraded top the newest release this morning and my machine came back up missing the NICS.  

 

netxtreme bcm5764m gigabit ethernet pcie

 

"lshw -class network" shows the NICs as unclaimed.  can anyone assist?  No hardware changes, just the most recent update (just a small revision jump as I was on the latest release prior to this upgrade.

[JorgeB]

Likely a NIC that uses the tg3 driver, see the release notes:

https://forums.unraid.net/topic/124108-unraid-os-version-6102-available/

 

You can also post the diagnostics so we can see the hardware and recommend the best option.

[jfrancais]

Thanks for the reply and the catch.  disabling VT-d in bios brought me back up but now I need to figure out what to do.  I have VMs running on this that I need for production so disabling VT-d leaves me non functional.  I wasn't having any issues since going to 6.10 so I'm wondering if it is safe to bypass the blacklist.

[JorgeB]

What is the server hardware?

[JorgeB]

or check this post:

https://forums.unraid.net/topic/124108-unraid-os-version-6102-available/?do=findComment&comment=1132815

 

[jfrancais]

40 minutes ago, JorgeB said:

What is the server hardware?

https://support.hp.com/ie-en/product/hp-z800-workstation/3718645/document/c01709726

[JorgeB]

It's not a known affected model, but since most affected servers have been from HP it's difficult to say more for sure, if you have been running previous v6.10.x releases with vt-d enable for a few days and didn't notice any issues or errors logged you are most likely OK, diagnostics might also give a better idea.

[jfrancais]

diagnostics attached

gobo-diagnostics-20220530-1123.zip

[JorgeB]

No corruption detected by btrfs so far, and when there's a problem it's usually quick to detect some, so if you ran other v6.10.x release for more than a day I would think it should be fine to enable vt-d, just monitor the log for the iommu error described in the post linked above, if you don't see that after a few hours use with vt-d enabled it's another indication you should be fine.

[jfrancais]

On 5/30/2022 at 11:31 AM, JorgeB said:

No corruption detected by btrfs so far, and when there's a problem it's usually quick to detect some, so if you ran other v6.10.x release for more than a day I would think it should be fine to enable vt-d, just monitor the log for the iommu error described in the post linked above, if you don't see that after a few hours use with vt-d enabled it's another indication you should be fine.

 

Been running solid since Monday with no errors thus far.