@Sebastian-Roth

Hell yeah dude, that cleared it right up.

@Sebastian-Roth

Not sure if this has been resolved or if this helps -

I’ve created a Win 10 UEFI VM using the 2004 ISO. VMware Workstation 15 Pro 15.5.6 build-16341506. All the settings were default except I went up tp 8GB of RAM. I installed it, ran all the updates, activated it while waiting for updates, rebooted twice then captured the image with FOG dev-branch version: 1.5.9-RC2.11 running on Ubuntu 20.04 LTS

It deployed fine to a similar VM.

@george1421

I can try that later this week. If manually setting acpi=off in the host configuration kernel parameters field works then wouldn’t that mean the kernel parameter field for groups does not work?

I wish this place would get rid of those awful DC 7800’s

I mistakenly reported I was able to successfully image a DC7800 by adding the host to a group that had a kernel parameter “acpi=off”. It turns out I was mistaken. It was a DC7900.

The DC7800 can make it to the fog menu and successfully register. However, when trying to deploy or capture I get this

NO GROUP

IN GROUP with “acpi=off”

Is there another kernel parameter I need to use?

In the mean time, I had to install an older kernel in order to image it.
Tom Elliot 64
bzImage Version: 4.15.2

Thank you

It is not happening anymore. The VM is only 18GB. It takes less than 10 minutes to capture and less than 10 minutes to update FOG. Or visa versa.

The only weird thing I have since noticed is during the install process, when are asked to go to fog/management and hit update database, that page no longer shows up. It just displays the fog login screen. So I just go back to the installer and hit ENTER. It seems to work fine.

@Sebastian-Roth

Ok, I deleted my fogproject folder to make sure I got the newest stuff

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

Ran the installer/upgrader and captured an image from the VM.
All good!

Thank you

d1.partitions.txt d1.fixed_size_partitions.txt d1.minimum.partitions.txt @Sebastian-Roth

Hello,

It is possible it could be the same thing that is happening there. There weren’t any errors during the capture process.

It seems that capturing the image damages the working Windows VM. However, the image that is captured from it is fine and can be restored no problem.

I tried 3 times in a row. Setting up a rather standard Win10x64 VM . Each time I captured and image from the VM, it would not longer boot into Windows properly.
I will upload those files that were requested in the other thread.

[2_1588487227132_d1.partitions](Uploading 100%) [1_1588487227132_d1.fixed_size_partitions](Uploading 100%) [0_1588487227130_d1.minimum.partitions](Uploading 100%)

Thank you guys. I have now got the latest RC 1.3 and found a problem. I made another thread about it.

Hello,

I have noticed a problem after updating to 1.5.9-RC1.3.

After capturing an image from a Windows 10x64 VMWare Workstation 15.5, it borks the VM. It can no longer finish loading the desktop for the default user. Restarting the VM usually ends up in the Windows frowny face or a Windows repair in which it can not be repaired.

However the image it captures is good. If I deploy the newly captured image to a new VM or onto the same one everything works fine.

I was able to duplicate this 3 times in a row.
Is there more information I could provide to help determine what the cause is?

Thank you

The web interface tells me the latest dev-branch version is 1.5.8.34

@Sebastian-Roth

Hello,

Thanks everyone.

The error messages were in the links to the others posts. But it is cool now, I went in last night and tested.

Since the DC7800’s can make it to the fog menu I created a new group that adds acpi=off to the kernel parameters and add the dc7800 to that group.

EDIT: Oh woah, I see there is already a newer version of the dev branch. I’m still on 1.5.8.32

@george1421

The DC7800’s can register without any kernel parameters on the new kernels. They just can’t have an image deployed on them.

Why isn’t it a problem with the older kernels?

I have seen this posted before and my solution to make it work with the 7800’s and newer EFI network booting was to use an older FOG kernel from the web interface. I forget which one it was.

One thread mentioned using ACPI=OFF in the kernel parameters but this prevents EFI network book.

The 7800’s will make it to the fog menu but fail to deploy so I have set up a group named Legacy that uses the ACPI=OFF parameter. No way to test this yet. I am not on sight to test any of this ATM.

Like other members here there are a couple of DC5800’s those do not even make it to the boot menu but that isn’t really important.

Is there some other parameter I should use that would allow both?

Depending on which kernel I use;

I’ll see this.

https://forums.fogproject.org/topic/14317/older-dc7800-s-have-issues-with-recent-fog-kernels-how-do-i-add-a-switch?_=1587929349622

Other kernels this;

https://forums.fogproject.org/topic/12924/hp-dc7800-network-boot?_=1587929349627

And as mentioned before using an older kernel from a year or so ago, I don’t have any problems with the 7800 and can EFI network book from other workstations. But there has to be something I’m missing that is preventing me from using the latest FOG kernel.

Any ideas?

Thank you.

I love FOG

@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