@sebastian-roth
Hi Sebastian,

Today I put the PC and FOG server on an even dumber switch than they were already on. (Just kidding, but this one is a 5 port un-managed Netgear switch we all know so well.)

Same behavior on the dumber switch unfortunately.

I’m about to send out my last one, the one I’ve been testing with. I don’t know if we’ll ever get this model again, lol. I really hope the next time I image with FOG it goes back to normal. I’ll have new machines in next week, so I suppose we’ll see what happens.

I appreciate the help, at this point it’s just the mystery of the thing for me. Let me know if you have any other thoughts or ideas.

@sebastian-roth

dmesg_bootup.txt
dmesg_deploy1.txt

Can’t say I know what I’m looking at, but I hope you find something cool in there.

Thank you!

@sebastian-roth

I’m having trouble ssh’ing into this thing.
I even put them on their own little network, and I can ping from the Linux session to my Windows device, but I can’t ping the PC we’re troubleshooting.

The bash shell doesn’t recognize “iptables” or “systemctl”
It feels like we’re now troubleshooting something else, so I apologize. But I’m not able to do the steps you outlined.
(Incidentally, I can ping and SSH to the FOG server from the same Windows PC.)

I’m not sure if this is just the same network driver issue we’re facing in general. Any thoughts?

@sebastian-roth

Okay, so doing a little more troubleshooting today.

Plugged the T14 into a Lenovo USB-C docking station and presto! Now we’re getting good speeds again.

I believe this would indicate some weirdness with the LAN card. Do you guys recommend any way of fixing that?

@sebastian-roth
Thank you Sebastian!

I scoured the BIOS settings and did some googling, I don’t see any VMD settings on this BIOS.

For some reason I’m having trouble uploading an image,
But here’s a link to a picture of the screen:
https://ibb.co/vV8N5Pg

Regardless, the output is:
4.0 GB copied in 2.23 s (1.9 GB/s)

(I can type out all of the output if needed, but I figured that was the key data.)

@sebastian-roth
Thank you Sebastian!

I did as you suggested.

So, it seemed to have an effect. At first it was hitting 300+MB/min and my estimate was around 2 hours. Now it dropped back down to 15MB/min with a ~30+hr estimate.

@george1421
Thank you for the response!

Ha! That is strange. I think this little black bar popped up when I did that:
“sd 0:0:0:0: [sda] No Caching mode page found”

Have given it about 5 minutes, no change in speed.

Hello!

I have been using FOG for the past 6 months with great success, thank you so much to the developers!

We just got in a new Lenovo model, the T14 Gen 2. I created my golden image and it captured with no problems. Now, however, when I go to deploy the image, I get very slow deployment speed. I have done some troubleshooting and I can’t determine the cause.
Sometimes it goes really slowly (40 hours for a 29GB image) and sometimes it hangs in various places before partclone even runs. No problem pxe booting or sending inventory to server.

1. I have the FOG server (running kernal 5.10.34, FOG version 1.5.9) on a switch that the PCs are directly connected to. I tested with this switch removed from the equation, same speed. (~10-50MB/min)
2. I tried deploying a different image to the same PC just in case my new image was causing the problem, same result.
3. I tried deploying an image to a different model PC (Lenovo T490) and it worked perfectly, usually about 5-10 minutes to deploy.
4. I have checked top on the server, and it is hardly under any load at all.

This feels like a network issue, but like I said, on another laptop it works perfectly.

Can anyone please help point me in the right direction?

Thank you!

@george1421 Scratch that. I was confused about how this works, my apologies.

The Windows 10 installation I used to create my image is using an MBR, aka Legacy boot.

Thanks again for the quick reply.

@george1421 Thank you for the reply George! I suppose that’s why I’m a bit confused.

I will try to rip the image again. (Making sure to UEFI boot to PXE)

I will post after I try deploying again.