Hi all,

Just updated to 6.10.2 and, not, my host is unreachable. After stealing a TV from another room, OS seems to boot fine but I cannot get my box to talk to the network. Upon booting, the Unraid login screen (CLI) says IPv4 Not Set and IPv6 Not Set. I checking my network.cfg and it showed DHCP, Bonding, and Bridging as "yes" with no IP, gateway, or mask set. I tried setting all three to no and setting the IP, gateway, and mask manually but was still unable to reach the box.

 

During boot, I did catch the wording: "Device 'eth0' does not exist. Cannot find device 'eth0'" (image attached). Is that because of binding/bridging?

 

I couldn't imagine the process of a reboot borking my NIC... Please let me know what I can try to fix this issue.

 

Thank you,

Wes

Post your diagnostics.

 

Also, are you running a ProLiant?

See here: (Release notes for 6.10.2):

 

 

and here:

 

Edited May 28, 20224 yr by Frank1940

4 minutes ago, Squid said:

Post your diagnostics.

 

Also, are you running a ProLiant?

The legend Squid has entered the chat

 

It is a Poweredge T420. I ran diagnostics but am not sure how to get them off the box being as how it's CLI only at this point. Simple guide for that somewhere?

5 minutes ago, Frank1940 said:

See here: (Release notes for 6.10.2):

 

 

 

Looking in to this now... this looks promising.

2 minutes ago, wes.crockett said:

The legend Squid has entered the chat

 

It is a Poweredge T420. I ran diagnostics but am not sure how to get them off the box being as how it's CLI only at this point. Simple guide for that somewhere?

 

it will be in the logs folder on the flash drive

6 minutes ago, jmztaylor said:

 

it will be in the logs folder on the flash drive

Does this mean i need to take that USB out and plug it in to another system? Or can I copy it to a new USB... i assume i would need to (learn how to) mount the new USB to do this...

1 minute ago, wes.crockett said:

Does this mean i need to take that USB out and plug it in to another system? Or can I copy it to a new USB... i assume i would need to (learn how to) mount the new USB to do this...

 

Plugging it into another computer is always the easiest

2 minutes ago, jmztaylor said:

 

Plugging it into another computer is always the easiest

Working on one of the above attempts now (disabled Intel Virtualization in BIOS). I think that is probably along the lines of the issue. I will upload logs next though for sure.

 

Thanks.

3 minutes ago, wes.crockett said:

Does this mean i need to take that USB out and plug it in to another system? Or can I copy it to a new USB... i assume i would need to (learn how to) mount the new USB to do this...

Quick push of the Power Button on the server will usually start a clean shutdown.  A Long push  (>5 seconds) will force a shutdown.

25 minutes ago, Frank1940 said:

See here: (Release notes for 6.10.2):

 

Does disabling Intel Virtualization (I can't find anything that is just VT-d) mean I cannot run VM's on this installation? I'm not anyways, just wanting to make sure I know the ramifications.

Hallelujah! Disabling Intel Virtualization did fix the NIC issue and I am able to access my UI via XXXXX.unraid.net. All docker containers up and accessible too (just validating that everything is as it should be.)

 

I have attached my diagnostics (post fix).

 

With Intel Virtualization disabled in the BIOS, I assume I cannot run VMs on this platform. Is that correct? (I'm not currently running any, but just want to make sure I know the limits currently.)

 

Is there a patch planned to fix this issue?

 

kuiper-diagnostics-20220528-1301.zip

 

7 minutes ago, wes.crockett said:

Hallelujah! Disabling Intel Virtualization did fix the NIC issue and I am able to access my UI via XXXXX.unraid.net. All docker containers up and accessible too (just validating that everything is as it should be.)

 

I have attached my diagnostics (post fix).

 

With Intel Virtualization disabled in the BIOS, I assume I cannot run VMs on this platform. Is that correct? (I'm not currently running any, but just want to make sure I know the limits currently.)

 

Is there a patch planned to fix this issue?

 

kuiper-diagnostics-20220528-1301.zip 126.22 kB · 0 downloads

 

Virtualization can be enabled but VT-d specifically needs to be disabled.  If you don't have a VT-d option like I do not then add this to the syslinux config by clicking on the flash drive under Main.

 

intel_iommu=off

 

Then reboot.

 

Screenshot shows where to put it.

Virtualization will work if you need it in the future but you will not be able to passthrough devices to the VM

Edited May 28, 20224 yr by jmztaylor

Just now, jmztaylor said:

Virtualization will work if you need it in the future but you will not be able to passthrough devices to the VM

OK. Cool. Mine did not have VT-d so I will add that to syslinux. Later, I will go back in and enable virtualization in the BIOS. I do plan to do GPU passthrough eventually, so hopefully this does get fixed in a future version.

I have a T620, same issue when updating.

51 minutes ago, THEDTM said:

I have a T620, same issue when updating.

yuuuup... makes for a fun Sunday

This just happen to me on my ML350 G6 and I was able to work around the issue by installing an HP / Intel 82571EB/82571GB Dual Port NIC I had laying around. I was just wondering if anyone knows if the corruption issue has been fixed or how to tell if your system has this corruption issue and it's safe to re-enable the TG3 driver? 

ripley-diagnostics-20220528-2218.zip

I just took out my USB drive, put in my pc, and added the empty file as stated above and I am back online. I moved from my 4 port broadcom card to the integrated intel nic as well.  I just happened to be moving my unraid to the garage, and was already on 6.10, didn't think this minor update would ruin my saturday evening....  I have had no issues with all RC updates since 6.9.2.  I think the release notes need to be updated to state a little more than "startup: blacklist tg3 by default if Intel VT-d is enabled".  I know what it means now, but who typically knows that tg3 is a broadcom nic driver?

 

Thank you all for the great help!!!

13 hours ago, wes.crockett said:

With Intel Virtualization disabled in the BIOS, I assume I cannot run VMs on this platform. Is that correct? (I'm not currently running any, but just want to make sure I know the limits currently.)

With vt-d disabled you can still run VMs, just not passtrhough any device to one.

 

FYI there are no signs of any issues with your server, also so far didn't find any on any Dell, it's been mostly HP servers and one IBM/Lenovo, so it *might* be OK to use vt-d with this NIC with a Dell, but if you can leave vt-d disabled for now just in case and until we get to the bottom of what's causing this.

4 hours ago, Gorby said:

I was just wondering if anyone knows if the corruption issue has been fixed or how to tell if your system has this corruption issue and it's safe to re-enable the TG3 driver? 

Your server also isn't showing any signs of corruptions so far, and it's a different model than the known affected ones, so it might be OK, again until we find out exactly what's causing this it's difficult to say if it's safe or not, best to be on the safe side for now.

6 hours ago, JorgeB said:

With vt-d disabled you can still run VMs, just not passtrhough any device to one.

 

FYI there are no signs of any issues with your server, also so far didn't find any on any Dell, it's been mostly HP servers and one IBM/Lenovo, so it *might* be OK to use vt-d with this NIC with a Dell, but if you can leave vt-d disabled for now just in case and until we get to the bottom of what's causing this.

Thank you for the follow up. My BIOS doesn't have a VT-d setting (just a main 'Intel Virtualization' one.) I'll leave it disabled until a future patch.

I have had the same issue as the original post after upgrading to 6.10.2. After regressing back 6.10.1, everything is working again.

 

Diagnostics attached.

 

clifford-diagnostics-20220528-1336.zip

 

NOTE: I didn't try disabling VT-d, as my BIOS doesn't have that option. I did try the empty tg3.conf file, and that didn't work for me.

2 hours ago, wes.crockett said:

My BIOS doesn't have a VT-d setting

You can also just disable vt-d by adding 'intel_iommu=off' to syslinux.cfg, see how to here.

2 hours ago, KeithRBrown said:

I have had the same issue as the original post after upgrading to 6.10.2. After regressing back 6.10.1, everything is working again.

You don't have a NIC the uses the tg3 driver, so unrelated to this, could be a network config issue.

What kind of network config issue would only come into effect after upgrading to 6.10.2?

 

Everything is working fine at 6.10.1.

 

Would the 'intel_iommu=off' workaround be worth trying?