Can't image - attempting fixparts

[Aysientor]

New to the FOG scene, and I’ve been wrestling with a machine, trying to create a master Windows 10 LTSB image.

I’ve read that some SSDs can run into problems with GPT fragments causing problems. So I attempted to run diskparts in debug mode, only to run into “command not found”

This is a brand new FOG install (downloaded and setup this tuesday) and I’ve tried updating the kernals in the web gui, with no joy.

Do I need to update the init files manually?

Any help would be greatly appreciated!

[raju_inc]

Hello,
I’m very new to FOG and i am getting the same error.

I’m running brand new Centos 7 server and FOG Version 1.5.4.

If anyone can point us in the right direction that would be much appreciated.

Thank you.

[Sebastian Roth]

@Aysientor @raju_inc Please schedule a debug capture task (like normal but hit the checkbox for debug just before submitting) when you get to the shell please run the following commands:

gdisk -l /dev/sda
...
fixparts /dev/sda
...

The later command will ask you to confirm so you go y ENTER w ENTER y ENTER. Possibly it will print out an error and quit straight away. Take a picture of the screen and post here.

[Aysientor]

@sebastian-roth

I can run gdisk, which prompts me to select MBR, Blank GPT, or GPT.

And fixparts isnt found…

[UWPVIOLATOR]

This post is deleted!

[Tom Elliott]

@aysientor Please switch to the working branch.

This issue was brought up and has since been fixed, and will be used in the 1.5.5 release. (Working only has one change, which directly relates to multicast session imaging. FOS (the thing that should contain the fixparts executable) is it’s own repository, so it was addressed separately. When a release happens, the two repos are paired, sort of, together (FOS with just the binaries generated, and the main installer you are used to seeing.)

[Tom Elliott]

@uwpviolator Close, but no. I made the fix, and have it prepared, just wanted to make sure things are okay on the working branch first.

Especially now with all the PHP-FPM hoopla going on, I have changes per @george1421 on many of the other threads which would be great to know is working properly now.

[raju_inc]

@tom-elliott
Thank you.
I have followed the instructions here: https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG and still getting the same error.
How do i check if i have successfully installed the working version?

These are the command i have run:

 git checkout working
 sudo -i
 cd /root/fogproject/bin
 ./installfog.sh

[Tom Elliott]

@raju_inc you would likely need to run git pull after the checkout otherwise working is sitting at the same point as dev, master, etc…

[Aysientor]

@tom-elliott

Copy. Just attempted to switch over to the working branch, but I to am not sure if I did it correctly.

 git checkout working
 git pull
 sudo -i
 cd /root/fogproject/bin
 ./installfog.sh

My version information is the same as what @raju_inc is showing.

[Tom Elliott]

@aysientor the version is fine, the working branch when pulled removes the implicit download of binaries zip file. When set that way, the install will download the inits individually. Of course I could’ve made a mistake and I’ll double check things.

[Aysientor]

@tom-elliott

Gotcha. I just tried another debug and fixparts wasn’t found. Thank you for the quick replies!

[Tom Elliott]

@aysientor Please manually download the latest inits. I looked and the version is still set to “full” so it’s using the predownloaded binaries.

To download the latest run as root:

wget -O /var/www/fog/service/ipxe/init.xz https://fogproject.org/inits/init.xz
wget -O /var/www/fog/service/ipxe/init_32.xz https://fogproject.org/inits/init_32.xz

[Aysientor]

@tom-elliott

Success, it’s now imaging!

Noticed one typo with /var/www/fog/service/ipxe/init.xz missing “_32”

Thank you!!

[Tom Elliott]

Thanks and fixed.