Small local disk and the rest unallocated

[jemerson93]

Hi all,

Finding a new issue and unsure where to even start. This issue is random with which workstation it affects. The issue is once I deploy an image, the local disk will be 12GB-13GB and the rest of the drive will be unallocated. Other times when deploying that same image to a different workstation, everything is fine. Issue seems to be apparent since I have upgraded to 1.5.6 as I never had this issue under 1.5.4.

FOG Version: 1.5.6
bzImage Version: 4.19.36
bzImage32 Version: 4.19.36

[jemerson93]

Just wanted to bump this and see if anyone had any insight. Still running into this issue.

[Sebastian Roth]

@jemerson93 Thanks for bumping this topic. Must have gone unseen in the last busy week, sorry.

Is it one particular image that you see this “random” issue with? Please post the contents of the text files p1.partitions, p1.minimum.partitions and p1.fixed_size_partitions of that image here in the forums.

[jemerson93]

@Sebastian-Roth said in Small local disk and the rest unallocated:

@jemerson93 Thanks for bumping this topic. Must have gone unseen in the last busy week, sorry.

Is it one particular image that you see this “random” issue with? Please post the contents of the text files p1.partitions, p1.minimum.partitions and p1.fixed_size_partitions of that image here in the forums.

Hi Sebastian,

It is not a particular image but I think I’ve found it only to happen with desktops (laptops are not affected).

I’ll get the information for you and update this post.

[Sebastian Roth]

@jemerson93 I’ve found a bug in the resize scripts just two days ago. It only effects machines with NVMe drives…

Download the latest init files here: https://dev.fogproject.org/blue/organizations/jenkins/fos/detail/master/88/artifacts/ (init.xz and init_32.xz)

Put those in /var/www/html/fog/service/ipxe/ - rename the original ones to have a backup copy of those. As well go to the FOG web UI -> FOG Configuration -> FOG Settings -> FTP Server and increase KERNEL RAMDISK SIZE from 127000 to 275000.

[marcolefo]

Hi

We face the same problem.
I have installed the new init files and modified the ramdisk size but nothing change.

Here is Gparted after cloning

[Sebastian Roth]

@marcolefo May I ask you to open a new topic because I am fairly sure you have a special partition layout if the new inits don’t work for you. We need to analyze that in detail. Please post the contents of d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions in the new topic.

[jemerson93]

@Sebastian-Roth said in Small local disk and the rest unallocated:

@jemerson93 I’ve found a bug in the resize scripts just two days ago. It only effects machines with NVMe drives…

Download the latest init files here: https://dev.fogproject.org/blue/organizations/jenkins/fos/detail/master/88/artifacts/ (init.xz and init_32.xz)

Put those in /var/www/html/fog/service/ipxe/ - rename the original ones to have a backup copy of those. As well go to the FOG web UI -> FOG Configuration -> FOG Settings -> FTP Server and increase KERNEL RAMDISK SIZE from 127000 to 275000.

Hi Sebastian,

I copied over the latest init files and I’m receiving an error upon deployment now.

windows could not finish configuring the system. to attempt to resume configuration, restart the computer

Any idea?

[Sebastian Roth]

@jemerson93 said in Small local disk and the rest unallocated:

windows could not finish configuring the system. to attempt to resume configuration, restart the computer

Are you sure this image deployed without an issue before? I am not exactly sure but this sounds like some kind of sysprep issue to me.

[jemerson93]

@Sebastian-Roth said in Small local disk and the rest unallocated:

@jemerson93 said in Small local disk and the rest unallocated:

windows could not finish configuring the system. to attempt to resume configuration, restart the computer

Are you sure this image deployed without an issue before? I am not exactly sure but this sounds like some kind of sysprep issue to me.

Hey Sebastian,

Sorry for the late response. You are right, as before I did have an issue with nvme drives not expanding, other issues were unrelated and were an issue with my unattend.xml. I spent some time on Thursday and Friday and manually re-created it, and re-created the image and so far I have had no issues with expanding or errors.

Those inits definitely fixed the nvme drives not expanding correctly.

This is resolved, thank you for all of the assistance!

[marcolefo]

@Sebastian-Roth ok done
https://forums.fogproject.org/topic/13329/1-5-6-small-local-disk-and-the-rest-unallocated