No network interface found! Kernel might not have the correct driver! Lenovo T14 Gen 2.
-
That is also what I assumed it would be. I am surprised it isn’t that causing the issue.
I installed iperf3 on the server without any errors.
With the command:sudo iperf3 -s
Resulted in:
----------------------------------------------------------- Server listening on xxxx -----------------------------------------------------------
I went to the target machine and ran:
iperf3 -c <fog_server_ip>
Target machine results:
Accepted connection from xxx.xxx.xxx.xxx, port xxxx [ 5] local xxx.xxx.xxx.xxx port xxxx connected to xxx.xxx.xxx.xxx port xxxx [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 112 MBytes 918 Mbits/sec 0 413 KBytes [ 5] 1.00-2.00 sec 110 MBytes 930 Mbits/sec 0 413 KBytes [ 5] 2.00-3.00 sec 111 MBytes 929 Mbits/sec 0 413 KBytes [ 5] 3.00-4.00 sec 111 MBytes 929 Mbits/sec 0 413 KBytes [ 5] 4.00-5.00 sec 111 MBytes 931 Mbits/sec 0 413 KBytes [ 5] 5.00-6.00 sec 111 MBytes 935 Mbits/sec 0 413 KBytes [ 5] 6.00-7.00 sec 111 MBytes 935 Mbits/sec 0 413 KBytes [ 5] 7.00-8.00 sec 111 MBytes 934 Mbits/sec 0 413 KBytes [ 5] 8.00-9.00 sec 111 MBytes 935 Mbits/sec 0 413 KBytes [ 5] 9.00-10.00 sec 112 MBytes 934 Mbits/sec 0 413 KBytes [ 5] 10.00-10.00 sec 1.12 MBytes 898 Mbits/sec 0 413 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.01 sec 1.09 GBytes 933 Mbits/sec sender [ 5] 0.00-10.01 sec 1.08 GBytes 931 Mbits/sec receiver
Results on Server:
Accepted connection from xxx.xxx.xxx.xxx, port xxxx [ 5] local xxx.xxx.xxx.xxx port xxxx connected to xxx.xxx.xxx.xxx port xxxx [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 109 MBytes 918 Mbits/sec [ 5] 1.00-2.00 sec 111 MBytes 930 Mbits/sec [ 5] 2.00-3.00 sec 111 MBytes 929 Mbits/sec [ 5] 3.00-4.00 sec 111 MBytes 929 Mbits/sec [ 5] 4.00-5.00 sec 111 MBytes 931 Mbits/sec [ 5] 5.00-6.00 sec 111 MBytes 935 Mbits/sec [ 5] 6.00-7.00 sec 111 MBytes 935 Mbits/sec [ 5] 7.00-8.00 sec 111 MBytes 934 Mbits/sec [ 5] 8.00-9.00 sec 111 MBytes 935 Mbits/sec [ 5] 9.00-10.00 sec 111 MBytes 934 Mbits/sec [ 5] 10.00-10.01 sec 1.05 MBytes 898 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.01 sec 1.08 GBytes 931 Mbits/sec receiver
-
@itsecwalrus Yes these settings are exactly what I would expect on a very healthy FOG deployment.
So you are sure that this same computer from this same network jack it was moving at 10-22MB/minute ?
I’m a bit hesitant to put you through the NFS tests because the other two were the likely trouble spots.
I want to keep this configuration on this target system, but it would be interesting to know what version of partclone your version of FOG is using. This number would be visible on the blue partclone screen. It would be a number like 0.3.13 . Maybe you could find out what version using a different computer. Its not vitally important to know now, but the underlying subsystems seem to be working as it should. The next tests are NFS file transfer and then decompression and partclone.
Does this target computer have at least 4GB of ram?
This is the same exact image as you are sending to other lenovo computers, just this model is having the speed issue consuming your standard image?
-
So you are sure that this same computer from this same network jack it was moving at 10-22MB/minute ?
Yes I have not moved it from the last time I tried to image it. We have a few others of the same model we attempted to image from different drops in different rooms. All of them had the same result.
Does this target computer have at least 4GB of ram?
Yes, I believe it has 8.
This is the same exact image as you are sending to other lenovo computers, just this model is having the speed issue consuming your standard image?
Yes we use the same image for all of our Lenovo machines because it has never given us problems to do so.
I want to keep this configuration on this target system, but it would be interesting to know what version of partclone your version of FOG is using. This number would be visible on the blue partclone screen. It would be a number like 0.3.13 . Maybe you could find out what version using a different computer. Its not vitally important to know now, but the underlying subsystems seem to be working as it should. The next tests are NFS file transfer and then decompression and partclone.
It looks like the version of Partclone being used is Partclone v0.3.13 like you said.
-
@george1421 Any update?
-
@george1421 Hello!
I wanted to check in on this post to see if there was an update.
-
@itsecwalrus I started working on this next bit here: https://forums.fogproject.org/post/146681
I still need to work out a process for testing partclone performance. I think if I grab an existing image file I can send it to the local disk. All of these steps are to help up identify where its slow. From your testing we know its not the local disk (what I initially suspected) and not the network (suspected less since other models work OK). I doubt its NFS performance but we need to test for that. It could be partclone and something recently incompatible.
In the past we’ve also seen issue with the NVMe controller putting the nvme drive in a low power state during imaging. That should have been addressed in fog 1.5.9 released. But we might look into that too. But the drive speed tests didn’t indicate that was an issue.
-
@george1421 Okay sounds good. I am checking this page frequently so if you need more from me just let me know!