Very slow cloning speed on specific model

[wuenschz]

@sebastian-roth Hello again, I just wanted to update you on this issue. I have launched the task in debug mode and entered nvme set-feature -f 0x0c -v=0 /dev/nvme0. I am now able to get past the “Restoring partition Tables (GPT)” portion of the cloning, however it still gets hung up at the partclone screen. I did look at the partition information and it said that “Disk /dev/nvme0n1: 256GB” Do I have to change the command to reflect nvme0n1 instead of the /dev/nvme0?

Also, I saw that it says “Write caching not supported” but does support the drive and sees the drive.

I have also tried adding the nvme_core.default_ps_max_latency_us=0 kernal arguments to to the host in FOG and that did not fix anything.

[Sebastian Roth]

@wuenschz said in Very slow cloning speed on specific model:

Do I have to change the command to reflect nvme0n1 instead of the /dev/nvme0?

I don’t have any of these disks myself to test, so I am not sure. Give it a try with /dev/nvme0n1 and let us know.

[wuenschz]

@sebastian-roth Good morning,
Yesterday I tried changing the command to nvme0n1, however that did not make a difference. Today I am going to try rolling the Kernel back a version and see if that makes a difference. It is weird that it is transmitting data, just extremely slowly. The 7090 Ultras are transferring at 70-200MB per minute and our other devices transfer anywhere from 4-10GB per minute.

[herman]

@Middle said in Very slow cloning speed on specific model:

init_partclone.xz

Link down of Drive Google…!!!
Have another place or link?

[Sebastian Roth]

@herman said in Very slow cloning speed on specific model:

Link down of Drive Google…!!!

Well, this link is more than two years old and was probably meant as a temporary one…

What exactly so you hope to get from an old init.xz? I suggest you open a fresh new topic here in the forums and describe the exact issue you have, mention the FOG version and OS version used.