@Sebastian-Roth

Yes.

I just want to add real quick, the DC 7800’s can boot to the menu with any kernel and without and kernel parameters. They fail when deploying.

@george1421

So… Was the fix going to 1.5.2 init? https://forums.fogproject.org/topic/12924/hp-dc7800-network-boot?_=1587922835837

I will try that and if not use one of the older Tom Elliot kernels from the web interface.

@Sebastian-Roth

Hello,

I have been able to deploy the images however the image size in the fog web interface shows 0.

I have also updated to 1.5.8.32
Another odd thing is using acpi=off in the kernel args.

We have a mix of UEFI and Legacy network boot systems. If I enable acpi=off the EFI network boot systems are able to make it to the fog menu but images can not be deployed or captured or registered it just goes to a blinking cursor unless I remove acpi=off.

I was able to get around this before by using an older FOG kernel. I do not recall which one but it was about a year or so old. I didn’t need the acpi=off switch to deploy and capture from HP dc7800s and newer EFI network boot workstations were able deploye and capture too. I am not sure if I should just keep using that older kernel.

I guess I could make a different group with that switch but it seems so odd that an older kernel just works.

Thank you for your help

Should be good.

Thanks

@Sebastian-Roth

Can I just give the images the same names and point them to the correct image path?

Actually I for got what the original names were but I made an image and pointed it to an existing image path and the size showed 0

@Sebastian-Roth

I got this

1 root root 214677 Feb 24 21:16 /home/fogDBbackups/fog_sql_1.5.8_20200224_091608.sql

@Sebastian-Roth

UPDATE.

I uninstalled PHP 7.4 and let FOG Version: 1.5.8.31 Installer/Updater install it. All good!!!

My “old” images are still in /images but I am not sure how to get FOG to see them.

@Sebastian-Roth

oops nano was only showing me a little bit

Here is the last of the log

fog_error_1.5.8.978.log

ii xinetd 1:2.3.15.3-1 amd64 replacement for inetd with many enhancements
ii zlib1g:amd64 1:1.2.11.dfsg-2ubuntu1 amd64 compression library - runtime
New password: Retype new password: passwd: password updated successfully
mysqladmin: [Warning] Using a password on the command line interface can be insecure.
Warning: Since password will be sent to server in plain text, use ssl connection to ensure password safety.
mysql: [Warning] Using a password on the command line interface can be insecure.
Failed to stop php7.3-fpm.service: Unit php7.3-fpm.service not loaded.

And last of the install.log

Please enter a new database root password to be set:

To improve the overall security the installer will create an
unpriviledged database user account for FOG’s database access.
Please provide the database root user password. Be asured
that this password will only be used while the FOG installer
is running and won’t be stored anywhere:

OK

• Backing up user reports…Done

• Stopping web service…OK

• Setting up Apache and PHP files…Failed
  ###########################################

  PHP Failed to install properly

  ###########################################

  Could not find /etc/php/7.3/fpm/php.ini!

@Sebastian-Roth

I see okay I pull from working-1.6
Version: 1.5.8.978 Installer/Updater

That is the newest one I could get. I am at a loss why can not get 1.6

Anyway, yeah, it does not like PHP 7.4

• Setting up Apache and PHP files…Failed
  ###########################################

  PHP Failed to install properly

  ###########################################

  Could not find /etc/php/7.3/fpm/php.ini!

The first FOG box I updated, I must have left php7.3 on it.

@Sebastian-Roth I tried the same upgrade on another FOG box and it failed. LOL So I have removed and reinstalled MSQL cause I forgot the root password. Now I am trying to install FOG on it but I get to

Stopping web service…Failed!

I can’t seem to get the dev branch. I can only get Version: 1.5.8.30 Installer/Updater

git clone https://github.com/FOGProject/fogproject.git /opt/fogproject
cd /opt/fogproject/
git checkout dev-branch
git pull
cd bin
./installfog.sh

SOLVED

I was on 18.04 and ran “sudo do-release-upgrade -d”, It finished, I rebooted and was able to access the FOG web interface and deploy an image. I am running the latest stable version: 1.5.8

UPDATE: I had some issues when I upgraded to 20.04 on a different FOG box. It has been resolved.

Thanks

Thank you. We have many of these hosts. I will go back to the latest kernel and try adding that switch when I go in to work next.

Is there a way to add that switch to all dc7800s when registering?

Hello,

When i installed the latest stable FOG I was unable to image older HP DC7800’s It would throw an error

I remembered this happened on the previous version of FOG stable and had to go back to an older kernel. Doing this with the latest version also solved it but maybe there is a way to use the latest kernel and add a switch? I just don’t know how.

@Sebastian-Roth

Oh. Got it. That makes sense.

@Sebastian-Roth

This is very cool. The image finished deploying and it can boots up Windows but it would not load the desktop it goes to repair. But this could be because there is a huge difference in hardware?

Perhaps a feature could be added to convert back and forth from 4k to 512 in the web interface. The one thing I was curious about is why a 250GB drive would be needed since the image is around 60GB

@Sebastian-Roth said in Unable to restore 4k cluster size NVME:
Cool! I changed d1.partitions to what you posted and it was able to deploy the image onto a VM with a 512 sector drive.

d1.partitions.txt @Sebastian-Roth said in Unable to restore 4k cluster size NVME:

I have since delete the BIGPIG image. Here is the one from TEST. This image was captured from the 4k block NVME

d1.partitions.txt

@Reuban1219

Yes you can run the DHCP server on the same FOG// Debian machine. I am new to Linux and don’t know much about setting up a DHCP server on that. I used Windows for the DHCP server.

Imaging with FOG doesn’t require the internet. The PC’s have to be on the same network and you need a DHCP server of some type that allows you to add option 66 and 67 for boot file name and boot file server.