sponitz Posted June 3, 2022 Share Posted June 3, 2022 Hello, all! Today, I installed some new hard drives into my R720XD which is running my UnRaid Server. However, now my NICs aren't getting detected. I went into the BIOS and made sure that they were all configured and detecting, which they were. I am seriously stumped. Nothing else was changed to my knowledge. I did recently upgrade to the latest firmware from 6.9.2, but today the server was running completely fine until I installed some new drives. I am able to go into the GUI on the server and initialize the drives and do all my normal functions, however, my 4 NICs, that I use 2 of are not getting detected. I disabled my 802.1D bonding. Put everything back to "default." I would send a diag file but I am unsure how to download it if I cannot access the device via another computer. Hoping someone can help me get this back up and running. Thank you in advance. Quote Link to comment
Solution sponitz Posted June 3, 2022 Author Solution Share Posted June 3, 2022 Update, I disabled Virtualization Technology in the BIOS which is needed ya know for VMs and all four NICs were detected. Seems like a bug? Quote Link to comment
itimpi Posted June 3, 2022 Share Posted June 3, 2022 3 hours ago, sponitz said: Update, I disabled Virtualization Technology in the BIOS which is needed ya know for VMs and all four NICs were detected. Seems like a bug? Sounds like you have are encountering the issues described in the 6.10.2 release notes which can result in the NIC being (temporarily) blacklisted due to potential data corruption issue. If you need VMs and your system is not one that is affected by the data corruption issue you can take the steps laid out there to enable virtualisation support. Quote Link to comment
sponitz Posted June 4, 2022 Author Share Posted June 4, 2022 Thanks again! You always seem to find a solution. Which firmware would be safe to downgrade to? 21 hours ago, itimpi said: Sounds like you have are encountering the issues described in the 6.10.2 release notes which can result in the NIC being (temporarily) blacklisted due to potential data corruption issue. If you need VMs and your system is not one that is affected by the data corruption issue you can take the steps laid out there to enable virtualisation support. Quote Link to comment
itimpi Posted June 4, 2022 Share Posted June 4, 2022 1 hour ago, sponitz said: Thanks again! You always seem to find a solution. Which firmware would be safe to downgrade to? I am not sure which of the steps identify in the 6.10.2 release notes to work around the NIC being blacklisted you have tried to actually determine if you really need to downgrade. You mentioned disabling virtualisation completely in your BIOS so far but there are other options detailed there. If you need to downgrade then the release to downgrade to is probably the 6.9.2 release. If you can get diagnostics then posting those will allow you to get informed feedback as to whether (and how) you could get the 6.10.2 release working reliably on your hardware. Failing that you should probably wait for a future 6.10.x release where the root cause for the issues described in the 6.10.2 release has been firmly identified and a fix developed. Quote Link to comment
JorgeB Posted June 4, 2022 Share Posted June 4, 2022 So far no Dell server has been to be affected by the corruption issue, should be pretty safe to use it even with vt-d enabled if needed, but if you don't need it leave it disabled. Quote Link to comment
sponitz Posted June 4, 2022 Author Share Posted June 4, 2022 I would attach my diag file but it's taking about an hour to download for some reason. 10 hours ago, itimpi said: I am not sure which of the steps identify in the 6.10.2 release notes to work around the NIC being blacklisted you have tried to actually determine if you really need to downgrade. You mentioned disabling virtualisation completely in your BIOS so far but there are other options detailed there. If you need to downgrade then the release to downgrade to is probably the 6.9.2 release. If you can get diagnostics then posting those will allow you to get informed feedback as to whether (and how) you could get the 6.10.2 release working reliably on your hardware. Failing that you should probably wait for a future 6.10.x release where the root cause for the issues described in the 6.10.2 release has been firmly identified and a fix developed. While you guys are looking can you tell me why my Docker won't start now? Quote Link to comment
JorgeB Posted June 5, 2022 Share Posted June 5, 2022 Try rebooting and post new diags if it still doesn't start, if you can't get the full diags get the syslog. Quote Link to comment
sponitz Posted June 11, 2022 Author Share Posted June 11, 2022 On 6/5/2022 at 2:41 AM, JorgeB said: Try rebooting and post new diags if it still doesn't start, if you can't get the full diags get the syslog. Here is the diag file with virtualization disabled. Do you want one with it enabled? jarvis-diagnostics-20220610-2324.zip Quote Link to comment
JorgeB Posted June 11, 2022 Share Posted June 11, 2022 Nothing really jumps out, please reboot and post new diags after array start. Quote Link to comment
sponitz Posted June 11, 2022 Author Share Posted June 11, 2022 6 hours ago, JorgeB said: Nothing really jumps out, please reboot and post new diags after array start. The NICs work fine when virtualization is off, but when it’s on, none are detected on this R720XD. So you want another diag with it turned off? Quote Link to comment
JorgeB Posted June 11, 2022 Share Posted June 11, 2022 22 minutes ago, sponitz said: The NICs work fine when virtualization is off, but when it’s on, none are detected on this R720XD. Ahh, sorry, missed that part, update to v6.10.3-rc1 and you can have VT-d and the NICs. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.