Posts made by Baessens

Hi there

FOG version: 1.5.9-RC2

I’m getting the “failed to update database…” error at the very end of capturing an image.
This problem occurs when I am trying to capture a Windows 10 UEFI (V2004) image. (see attach. below)

I use Virtualbox and set my DHCP option 67 to undionly.kpxe to capture, as capturing doesn’t work when i put it on ipxe.efi. (I did this before and never had a problem)

Weird thing is I don’t have this problem when i capture an image in “legacy mode” on our hyper-v server.

I keep seeing the username “fogproject” in there, but i don’t have a user by that name tho…

Any help would be appreciated.

@george1421

Works:

Doesn’t work;

The total is different and the rights on default.ipxe (3th row) different user aswell.

Do you spot anything that’s obviously wrong?

Thanks

@george1421
Fog that’s working

Fog that’s not working

I do see some differences but i have no idea if they matter. i’ll try and copy the files tomrrow, thanks for the help already!

I have one FOG server; when i boot from network(legacy nic) on a Hyper-v server, i can’t seem to get past the “initialising devices…” screen.

I have another FOG server in a different location that works fine on hyper-v, the difference being:

• the version of FOG (fog1: 1.5.7 vs fog2: 1.5.5)
• DHCP server is Unifi USG router(fog1), the other one uses Windows DHCP(fog2)

On both DHCP servers i use undionly.kpxe as the boot file name.

EDIT: when i set the fog1 as boot server in dhcp option on my first location, it works just fine, so it would seem it has something to do with the VM on my other hyperv, so far the only difference is that the configuration version is 9.0, the other one is 8.0 … hm

Any suggestions on how to troubleshoot this?

Thanks in advance

@george1421 As always, thanks for the quick reply. Another reason i don’t want to use a storage node with location plugin, is that I then have to register my host first, before i can deploy an image. Unless this is incorrect?

I have two standalone fog nodes, each on a different site. I want to automatically sync images from node A to B. What is the best way to do this? Do i need the location plugin for this?

I understand I have to export/import the Images list.
I will only be creating images on node A.

The reason i’m not using a storage node, is cause I want to be able to use fast deploy from both nodes.

EDIT: i don’t want to have to register my hosts

Thanks in advance !

@george1421 Ah, i see. I was doing it with rsync in a cron job at the moment. I’ll try out your suggestion. Thanks for the info.

@george1421 Oh, so FOG will automatically replicate between fog standalone servers as well? i don’t need to do it manually?

@george1421 Thanks for your reply. i’ll look into a clonezilla and/or a mobile Fog server.

Although people have recommended me to use a standalone fog server for each location and sync the images manual(with rsync,…). As i can’t “fast deploy” with a storage node without registering the devices.

Hi everyone

I was wondering if there was a way to turn an image i capturedwith FOG into an ISO or something. To create a bootable usb-stick from later?

I want this because not all my sites have a server.

Thanks in advance

@Baessens Maybe i need to change the UID of my FOG installation? ?
Edit: changed the UDPCAST INTERFACE to eth0, still same problem.

Also, Is this wrong?

ict@fogserver:/images$ ls
dev         postdownloadscripts  Priminfowin10pro
lost+found  postinitscripts      priminfowin10pronewofficekey
ict@fogserver:/images$ cd dev
ict@fogserver:/images/dev$ ls
dev  postdownloadscripts

EDIT: re-running the installer seemed to fix the issue.

@Quazz
I think it’s quick deploy, i just boot a PC to network, login on the FOG server and chose ‘deploy image’.
Also my fog server doesn’t have DHCP server, we use a windows DHCP.

I migrated a FOG server(physical) to another FOG server(VM).

I used the following tutorial: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

I migrated the DB aswell. However the new fog server has a larger disk then the first one.
At first the dashboard showed me the older disk size en usage (in the pie chart).
Now i fixed that by changed the IP adres. (still had the old one)

The problem i’m now having is that when i try to deploy one of those images, i get the error invalid mac adres when checking mounted file system… (see picture below)

https://imgur.com/JwkZtS6

Few things i tried then:

• Changed the interface name to ‘eth0’ it was something else on the old server. (on the fog webportal under settings)
• Changed NFS ETH MONITOR to ‘eth0’ as well
• UDPCAST INTERFACE to eth0
  Any ideas here?

Thanks in advance

EDIT: re-running the installer seemed to fix the issue.

@george1421 I didn’t know that storage nodes were deploy only. Thank for the info.

@george1421 Thanks for the quick reply. This helped me out, thank you !
So you wouldn’t recommend me setting up a Fog storage node?

Hi people

I installed my FOG server in a VM on a 60GB SSD disk, that i made.
Now i would like to add a secondary Disk of about 300-500GB HDD to that same ubuntu instance to store the images.

Is there a way i can change the /image folder to that second disk?

Or should i not bother and install a second FOG server just as a storage node?

Thanks in advance

@Sebastian-Roth @Quazz

I captured a new image of one of the physical machines (not VM). This is a resizable image.
I CAN deploy this image to the other machines without the recovery screen error…

This machine has been setup by one of my colleagues using windows media creation tool.
It’s also a Win 10 pro 64 bit.
The Disk management looks a little different tho; (name of OEM partition)

Seems like something must be wrong with the VM i set up ?

Thanks

@Sebastian-Roth @Quazz

Make sure you disable fast boot and shutdown the machine using shutdown -s -t 0 -f in Windows command line.
I used the shutdown command. I’ll try disabling fast boot and reimaging.

Is it possible you’re deploying an MBR (legacy/old BIOS) (assuming, based on your partitions) to a system that’s trying to boot in GPT (new/UEFI) mode?
It’s possible the VM i made uses MBR. But i’ve enabled Legacy boot on the BIOS and disabled secure boot. Also with the other image(not resizable) i made i have no problems deploying.

Does d1.mbr exist in your image folder?
Yes, it does.

The thing i don’t understand is how i don’t have any problems deploying the other image i made. Which is Not Resizable. I’m deploying on the exact same machine.

I do have the option legacy boot enabled in the BIOS, and secure boot disabled. I’ve tried using uefi boot but that doesn’t work at all.

Maybe i have to add some kind of option or parameter in the host options on the FOG UI?

@Quazz
I do not use any unattend.xml file.
All I do is install from a win 10 pro 64 bit iso, on my hyper-v which is Windows server 2016.

Version: Windows 10 Professional, version 1803 (june 2018) - Dutch

I manually go through the installation process, install office and some other small things (with Ninite); and capture the machine with FOG.
I do add a legacy network card to be able to boot from network on hyperv. and i use generation 1 as my VM type.

If i do not chose for the resizable disk, it deploys just fine.

Thanks for all of the help already!

@Sebastian-Roth Thanks for the reply.
d1.fixed_size_partitions:
This is an empty file.

d1.partitions:

d1.minimum.partitions:

Disk management of the machine i captured;