Solved Very slow cloning speed on specific model
@DeRo93 Unfortunately there are some issues on that model with certain SSDs (though not all) that are currently resolved.
I’m unsure where to even point the finger at this point, but extensive attempts from our side have been done with no success.
Another user was using older models to deploy their images to the drive and then put those drives into the G6 model.
Does this mean there is NO other method to get my FOG Image on this Notebook model ?
@DeRo93 I think what it means is we need more details. I understand it’s the same type of machine (EliteBoot 840 G6) and all, but what things have you tried?
From what I can gather, you’ve attempted the Init.xz but did you try the nvme_core.default_ps_max_latency_us=5500 being set as a kernel argument?
Can you get us a video of the problem you’re seeing?
What is “slow” in your eyes? (For example is this on deploy or capture? Capture should be slower than deploy as it’s actually collecting the data and compressing it to store to the network.)
i tried the Init.xz and the kernel argument. I updated FOG and BIOS from the Notebook. Even tried older BIOS Versions.
With “slow” its like the rate is going to 20 kb / min … it starts with 70 MB / min and then goes lower and lower… Its a Deploy…
SSD in this Notebook is a “sk hynix bc501 hfm256gdjtng-8310a” with the newest firmware.
@DeRo93 In what Mode is the drive being read to the system? From BIOS you may find something like SATA Operation.
Can you change this to AHCI and see if this helps improve the speeds a bit? Maybe change to ATA - IDE if it’s available?
@Tom-Elliott HP UEFI does not have AHCI - IDE Options in their UEFI Setup
HP says AHCI is activated by default on newer Models.
@Tom-Elliott As far as I understand, this problem is occurring specifically on NVME SSDs
Did anyone get this working?
I have a large batch of the EliteBook 840 G6.
Some of which build and other are extremely slow.
Looks like my batch has 2 versions or firmware versions.
The one that works is “Toshiba KXG60ZNV256G 79VA215DKRVN” and the other is the same drive but an older firmware by the looks of it.
Im in contact with HP to see about getting a firmware updater…
So i swapped SSD out of a “slow” building laptop into a “working full speed” laptop.
So i thought the working laptop would now build slow, well it didnt. Building at full speed.
The other laptop with the SSD from the original full speed laptop is still building slow.
So maybe its not SSD related, but something on the motherboard?
@Duncan Are the BIOS versions the same on these laptops? Settings too?
Yes, iv updated to the latest 01.03.03 Rev.A, and my tech guys setup all the BIOS in the same way.
Im going to rip through the 2 laptops and reset BIOS, then make sure all settings are duplicated.
Going to see if i can pull some more hardware info and see if there are any differences there…
@Duncan Perhaps they are using different NVME controllers for some reason. Should be interesting to check it out at least.
@Quazz This is what im starting to think, be back with some findings soon
Running HWInfo im failing to see any differences between the 2 laptops. Even in the BIOS all settings and hardware info look the same…
@Duncan Can you schedule debug deploy task on both machines. When you get to the shell run
hdparm -i /dev/sda. Take pictures and post here.
For some reason this reminded me of some of the earliest (and most explored) reports on slow deployments on certain system drive combinations.
That user notes that if a partition is formatted and mounted on the target disk just prior to restore that it runs at expected speeds (but in FOS only if it’s not NTFS for whatever reason). Next attempt to restore will be slow again unless the same step is taken.
They then went on to try a different drive (different brand) and that one worked normally.
@Duncan Thanks for the pictures. Though I think it was such a great idea because comparing the two listings as pictures is very much error prone. I reckon both listings are identical but can’t say for sure absolutely. And even then we still don’t know if one model might have just a slightly different revision of some component.
Is it only writing to disk or also reading from disk? Even if it doesn’t make sense for you to capture from the “slow” model, can you still give it a try to see!?
Also I wonder if you could live boot some Linux CD/DVD distro and do write/read tests as well.
dd if=/dev/zero of=/dev/nvme... dd if=/dev/nvme... of=/dev/null
NOTICE: Be aware the first command will completely destroy the data on your drive!! Only do this on machines you don't have valuable data on and can re-image again.
Did you get to talk to HP about this issue? What do they say?
@Sebastian-Roth I realize we are discussion nvme drives here and only for a point of reference, but in 2017 I created a benchmark post to compare the differences in different technologies (one being disk subsystem) and its impact on imaging. https://forums.fogproject.org/topic/10459/can-you-make-fog-imaging-go-fast/6
From there I had these two commands:
… the simple disk baseline I’m using the following linux command to create a sequential 1GB file on disk and then to read it back. This process is designed to simulate the single unicast workload. The command used to write the 1GB file is this:
dd if=/dev/zero of=/tmp/test1.img bs=1G count=1 oflag=direct
The command to read it back is:
echo 3 | tee /proc/sys/vm/drop_caches && time dd if=/tmp/test1.img of=/dev/null bs=8k
The echo command is intended to disable the read cache so we get a true read back value.
root@ubuntu:/home/ubuntu# dd if=/dev/nvme0n1 of=/dev/null 500118192+0 records in 500118192+0 records out 256060514304 bytes (256 GB, 238 GiB) copied, 231.216 s, 1.1 GB/s root@ubuntu:/home/ubuntu# dd if=/dev/zero of=/dev/nvme0n1 dd: writing to '/dev/nvme0n1': No space left on device 500118193+0 records in 500118192+0 records out 256060514304 bytes (256 GB, 238 GiB) copied, 2204.34 s, 116 MB/s
I’ve emailed my guy at HP and will see what they say.
Going to upload from “slow” laptop now and see what speeds i get.
@Duncan Please replace the dots with the appropriate ending for the drive. (eg 0n1) and try again.