Posts made by michelsantana

@Tom-Elliott This is the output of the command you have requested. Now I only have access to a Virtual Machine, but I guess that the problem is the same. Here you have the captures in sequence:

@Tom-Elliott This is the output of the sgdisk command once booted with a debug deploy task with the kernel argument that you have resquested. Don’t know if is this what you are talking about.
Thank you

d1.partitions
label: dos
label-id: 0x5a45dfe4
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 1070592, type=7, bootable
/dev/sda2 : start= 1072640, size= 189747430, type=7
/dev/sda3 : start= 190852200, size= 434285145, type=7

---

d1.minimum.partitions

label: dos
label-id: 0x5a45dfe4
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 65024, type=7, bootable
/dev/sda2 : start= 1072640, size= 37683712, type=7
/dev/sda3 : start= 190852200, size= 257024, type=7

Server

• FOG Version: 1.3.5RC16
• OS: CentOS7

Client

• Service Version:
• OS:

Description

After upgrading to this version, there is a problem with the sizes of the partitions restored. For example, I captured with this version a disk with three partitions of aproximately 522 MB (System Reserved), 100 GB (C:) and 198 GB (D:) and when I deploy the captured image on the same computer the sizes of the partitions are 522MB, 295 GB(C:) and 2GB (D:)

Perhaps have something to do with using sectors instead of bytes since RC15?

This is the content of the file d1.minimum.partitions

label: dos
label-id: 0x5a45dfe4
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 65024, type=7, bootable
/dev/sda2 : start= 1072640, size= 37683712, type=7
/dev/sda3 : start= 190852200, size= 257024, type=7
Thank you

@Tom-Elliott Applied the fix and restarted and working perfect. Thank you very much!

@Tom-Elliott When I create the delay task, it only creates a “Deploy Task” in “Scheduled task”. Then when the scheduled time arrives, it creates only an “Active task” of image deployment, but no “Active snapin tasks”

Server

• FOG Version: 1.3.5-RC-14
• OS: CentOS7

Client

• Service Version:
• OS:

Description

When I launch an instant deployment to a group, it deploys the image and all the snapins to the members of the group. But when I launch a delayed deployment to the group, it only deploys the image but no snapins.
I have tried the delayed deployment with a single computer and works perfectly, deploying the image and all the snapins associated with the computer.

@Tom-Elliott Thank you very much. Updated to RC14 and working perfect.

While they fix this bug in future releases, a workaround is to edit the file fogproject/src/buildroot/package/fog/scripts/usr/share/fog/lib/partition-funcs.sh and modify this line of code

local awkArgs="-v SECTOR_SIZE=$sectorsize CHUNK_SIZE=$chunksize -v MIN_START=$minstart"

with this one:

local awkArgs="-v SECTOR_SIZE=$sectorsize -v CHUNK_SIZE=$chunksize -v MIN_START=$minstart"

And then in fogproject/src do a “make install-inits”. That will recompile the init.xz and init_32.xz in your actual installation (/var/www/fog/service/ipxe) with this fix.

I have done it with my current installation and fixed the bug.

@Frank

Seems that the problem come from the script that call the function procsfdisk. In the definition (procsfdisk.awk) you can find:

# This is where it all begins (See->BEGIN) :)
BEGIN {
    # Arguments - Use "-v var=val" when calling this script
    # CHUNK_SIZE;
    # MIN_START;

And in the script partition-funcs.sh, in the same directory, you can find that the call to the procsfdisk function:

local awkArgs="-v SECTOR_SIZE=$sectorsize CHUNK_SIZE=$chunksize -v MIN_START=$minstart"

 # process with external awk script
    /usr/share/fog/lib/procsfdisk.awk $awkArgs $data

And as you can see, there is a missing “-v”. Perhaps that’s the problem.

Hello,

Same problem here (Server on CentOS 7). I have done a capture from a computer with a small disk and three partitions (30MB, 45GB and 29,4 GB) using FOG 1.3.5RC13 and when I try to deploy it to another computer with a bigger HD, have the same error.