Very Slow
-
@Sebastian-Roth
Found it ! soory
KERNEL ARGS -
@Jimbohello After you are able to image the machine, could you provide feedback on if the kernel args works for you or you had to go the debug route and enter the instructions directly into the console? We are trying to collect information on which solution works the best for resolving these issues with these specific nvme drives.
In short these two commands (applied differently) keep the drive from going into low power mode during imaging. The developers are working towards a solution where the imaging engine will adapt these commands without intervention.
-
@Sebastian-Roth
After analysing the situation, here are my conclusion
i did add your code : nothing change
same slow ridiculous speed
maybe your not looking at the right place for the bug ! of slowness
we use FOG for more than 3 years, alway the same SSD and Same Machine, closely.
so conclusion, has nothing to do with nvme_core.default_ps_max_latency_us=0
nothing has change in our environnement except we upgrade fog every 1-2 mounth.thank’s
-
@Jimbohello Something had to have changed. And if this were a bug in the code, chances are highly likely that we’d have a lot more posts regarding the issue (as it would impact everybody.)
Something changed. I don’t understand why you update fog every 1-3 months. Last official release was 1.5.7 (July 2019). Are you running a dev-branch version? When you say you upgrade fog, do you mean the OS components (e.g. apt-get)?
Have you looked at BIOS upgrades that may be happening? Pictures of the issue would be handy too. (Yes we want to see the blue partclone screen).
I still think this is in your environment. I don’t know where or what, and the fact that things worked okay, then started getting slow, without knowing more this is very " you guys did this now you fix it " and we don’t know how to help.
-
@Jimbohello Have you tried the other suggestion yet??
Schedule a task in debug mode and before you start the job run this command in the command shell on the host PC:
nvme set-feature -f 0x0c -v=0 /dev/nvme0 -
@Sebastian-Roth He’ll need newer inits that include the NVME package since it wasn’t included in the 1.5.7 package iirc.
-
@Tom-Elliott
Agree with you !
i’ll get back to you very fast
but for now, i’ve created a samba share and i get full speed of what a gigabit nic can give so arround 112-120 mb/s
with acronis.FOG 1.5.7.99
-
@Jimbohello said in Very Slow:
but for now, i’ve created a samba share and i get full speed of what a gigabit nic can give so arround 112-120 mb/s
with acronisWe did have reports of another user who had fast speeds with acronis as well. Turns out Acronis is using a fairly old kernel which doesn’t seem to have the issue. If you are keen to give an older kernel a try:
https://fogproject.org/kernels/bzImage-4.9.51
fogproject.org/inits/init-4.9.x.xz -
@george1421
obviously i’m not sure i did the right hoses
but i haded
KERNEL ARGS nvme_core.default_ps_max_latency_us=0
and haded postinit.script in the image section = nvme set-feature -f 0x0c -v=0 /dev/nvme0i’ll try tomorrow the all process debug mode
thank’s
-
just to let you know that the issue was solve this week buy updating the latest version of fog
seem that you finaly found the problemthank’s
