Massive packet loss/NIC issues with new Dell 7070 Ultra in FOG
-
@Sebastian-Roth Very true and yes I left the laptop in the exact same port/switch that I ran my live ubuntu test in.
It always seems to fail at any stage once booted to the fog menu, I typically go Deploy Image -> (Username and password) -> Select the image I want to deploy -> Sometimes it fails after I hit enter here, trying to download one of the files to move to where it clears the drive and starts partclone (I believe one is boot.php and bzimage) -> if it doesn’t fail there it typically will move to partclone and then fail while trying to copy each partition image file.
I’ve tried a handful of different kernels with no luck, but the weird thing is I was still able to image a different laptop of the exact same model and config, with the only known difference to me would be the MAC address…
-
@MHImager If it works reliably with another machine of the same model, I would start questioning the integrity of the problematic machine. Being things seem to be failing inconsistently, it might be worth it to run a memtest and run it through dell’s onboard diagnostics. While not at all common, I have received a couple of machines with dodgy RAM that have done weird things over the years.
-
@MHImager said in Massive packet loss/NIC issues with new Dell 7070 Ultra in FOG:
with the only known difference to me would be the MAC address…
Are you sure about that? Firmware version? Exact same hardware? I mean, did you buy those as a batch or several orders?
-
@Sebastian-Roth said in Massive packet loss/NIC issues with new Dell 7070 Ultra in FOG:
Are you sure about that? Firmware version? Exact same hardware? I mean, did you buy those as a batch or several orders?
Updated both laptops to BIO’s version 1.5.1, Exact same SKU, they were ordered along with 4 Optiplex 5070’s (One of those had the same issue, Had to swap the drive to image it) and 2 all in one’s which luckily imaged fine!
About a year ago we placed an order for about 35 All in one Dell PC’s (OptiPlex 5260 AIO) and one of the machines in that batch did the same thing, also in that order were about 15 laptops (Latitude 5490) again, same thing, one machine would have the same behaviour and I’d have to swap drives to image it. Should mention I was using legacy PXE boot back then too, now I’m using UEFI.
-
@MHImager If you even see such an behaviour with different models I’d think about something different causing this. Maybe it’s one switch or port or cable or??!?
-
Sorry for reviving an old thread (of mine).
Just wanted to post the solution if anyone would encounter the issue and was looking for a solution finding this thread.We solved this about the time when FOG 1.5.8 came out early spring 2020.
No matter what we did we still had the issue with ~ 7-10% of our Dell 7070 ultra PC’s after we recieved the final batch of user PC’s.
Soon after 1.5.8 rolled out i tried upgrading our FOG server to that, afterwards it all worked fine with the troublesome PC’s!
We tried lifting over the kernel and all the loaded files up until the imaging session starts as far as we know from the test environment (1.5.8) to production (1.5.7), but the issue was still there…? After a while we upgraded production FOG server to 1.5.8 and it started working there as well…Something in 1.5.7 glitches in some cases with some specific hardwares even if same models (can’t figure any difference other than perhaps some glitch depending on what MAC adresses being used if for any reason the NIC drivers misbehaves in a specific combination of MAC’s ending in some value…?). While 1.5.8. solved that - not being the Kernel itself solving this.
(if anyone would know what could cause this, i’m just curious technically to find out the reason for the errors, any developer that knows what changed other than the kernel that could solve this?)
You can close this otherwise dead thread
-
@no0NE It would be interesting to see if the linux 5.6.x or greater version of FOS Linux kernel would have also addressed this issue. You can add this kernel using the FOG Settings -> Kernel menu. You WILL need the 5.6.0 or later kernel to support the newest hardware that is out there.
FWIW: The linux kernel developers are no longer back porting new drivers to the 4.19.x series of kernels. So you will need to upgrade sooner or later.
-
@no0NE Really interesting this was solved by 1.5.8 but not the Kernel. Did you also copy over the inits to check if those would make a difference?
Anyhow, thanks for letting us know!
-
@Sebastian-Roth To my memory we replaced kernels (both 32 & 64 bit), init’s/bzimage (expanded to more and more files etc during troubleshooting to try to find the culprit) none helped other than upgrading to 1.5.8. I assume it’s something Dell specific with some weird OEM magic that messes up something somehow somewhere…
