@martial Can’t hurt to upgrade, for sure.

What FOG version are you on?

@Sebastian-Roth Yeah, I meant in FOG; spaces can be quite difficult to control correctly I think.

Spaces aren’t allowed for usernames.

Underscores do work I believe, if that’s an option for you.

@george1421 This one is auto-built by Jenkins using the github repository, the other one was the one I made for testing, but wasn’t fully complete (missing progress update patch)

Other than that they’re identical

@rocksteve69

Once you have the init.xz you can rename it to init_partclone.xz or something and then copy it to /var/www/fog/service/ipxe

Then you can change the host init in the WebGUI at host settings to init_partclone.xz or whatever you named it.

@george1421 To be honest, I never expected the partclone update to really change anything in that regard. I just figured there was a possibility that it could improve somewhat.

I’ve been confusing this thread with another one I think. I assumed he was already on those inits.

It’s worth a shot!

Can be downloaded from: https://dev.fogproject.org/blue/organizations/jenkins/fos/detail/master/95/artifacts

@rocksteve69 Can I ask which model it is specifically?

@rocksteve69 Try nvme_core.default_ps_max_latency_us=0

For the purposes of FOS, we don’t require a threshold where the drive assumes a lower power state, so we may as well try and eliminate lower power states altogether.

There may also be firmware updates for the SSDs in question

@Wolfbane8653 You can safely set this globally, unless you have even older CPUs

I’m glad those commands worked.

So this is a problem that I think was introduced in the Spectre/Meltdown patches and only affects Core 2 CPUs.

I thought it was supposed to be fixed in Kernel 4.19, but apparently not.

@Wolfbane8653 Please try kernel argument tsc=unstable

Then try kernel argument clocksource=hpet

@Wolfbane8653 A BIOS update may be required.

Other than that, trying out this kernel here might be interesting: https://drive.google.com/open?id=1ZiRWrrN3dv26bLwW8GAEdLtzGw5xkyQI

@Wolfbane8653 Can you share a picture of the result with acpi=off?

Also can you share the specifications of the system?

The original problem in that thread was solved afaik.

That said, rcu_sched can actually be caused by many different things, your case seems different.

Since it’s directly preceded by ACPI errors, disabling ACPI as George suggested is a good start.

@Middle Unfortunately, aside from the latency kernel argument there isn’t anything else we can do from our side as far as I’m aware.

Unfortunately manufacturers don’t always check how their stuff works on linux…

@Mr_Matten Ah, glad you figured it out!

@Mr_Matten Is the VM hard disk “dynamic” in size or fixed? (if it’s dynamic, try making it fixed instead, large enough to deploy the image of course)

Might also be worth going over the settings, especially CPU, since during deploy the client (the device you’re deploying to) will uncompress the image and then write which is CPU intensive.

It also needs enough RAM ofc.

Might be worthwhile to show us the VM settings altogether

@Mr_Matten Just to clear things up are you trying to capture or deploy the image when it goes wrong?

This means that it couldn’t find any partitions it can resize automatically (eg NTFS, EXT4).

If you are using different partition types that it can’t resize, then you need to change your image type to a non-resizable option in the FOG WebUI

Dual boot is tricky since you’re dealing with potentially two different OS types (eg Windows and Linux) which require different processing.

That said, I believe the best image type settings are Multipartition Single Disk with OS as “Other”.

Of course this means that deploying to devices with different disk sizes is either not possible or otherwise produces undesirable results.

But if all devices are the same anyway, then it should work fine!

Final note: resizable image type doesn’t actually reduce the size of the captured image (as far as I know), it just provides flexibility for deployment.

Empty space is still not captured under Multiple Partition capture and it will get compressed so the size should be comparable.

Only RAW capture produces larger images I believe.