Yes.
Tasked Successfully
Task Wake-Up Successfully created!
Created Tasks For
“hostname”

@Sebastian-Roth Ok, it sounds good that things are looking normal, and I can wait on doing an update. I see your reasoning and agree with that philosophy, on step at a time. I’m also three days away from the semester start so have limited time to troubleshoot and communicate here. I have run a few test images and may have figured something out, I need to complete my testing and will let you know. Thanks again, this has all been so helpful!

@Tom-Elliott said in db_root: cannot open: /etc/target:

@kboutelle There’s the problem.

You have /images and /images2 mounting to the same File system ID. I believe nfs will use the 1st instance (in your case it’s mounting /images rather than your new share /images2.

Edit the /etc/exports file.

For your /images and /images/dev lines, prepend them with a # symbol. This will comment those lines.

That, or change the fsid of the /images2 and /images2/dev to have 2 and 3 respectively.

Then restart the nfs service, systemctl restart nfsd

I can’t believe I missed that. Edited, going to try again.

Deployment is proceeding as it should.

Thank you all for taking the time to help.

@Rhywden said in Error while installing FOG on Ubuntu 18.04:

I tried it on both Debian 8 and Ubuntu 18.04

We have automatic daily installer test running and there is no general issue with Debian or Ubuntu I can assure you.

Make sure that interface is up and has an IP! Run ip a s before running the installer and post output here.

Basically I want to set it up thus that it’s able to connect to an existing network over Wifi.

Ok then you need to configure both interfaces. First WLAN, get an IP and make sure you have internet access through that (ping -c ix.de). Then configure enp6s0 with a static IP and make sure the interface is UP!

ip a s
…
2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
…

@Tom-Elliott @Sebastian-Roth Understood, thanks again guys!

@MoonDancer Check out this wiki pages: https://wiki.fogproject.org/wiki/index.php/.fogsettings, https://wiki.fogproject.org/wiki/index.php/Password_Central and https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

Well if I reread your post through a different lens…

When you pxe boot through the fog iPXE boot menu and let the default “Boot to hard drive” menu happen, when windows starts the iPXE dhcp name is still in place and windows is happy to just use that lease. If this is the case then iPXE might not be releasing the dhcp lease when it boots from the hard drive. In this case its not clear who is at fault (iPXE or Windows for just reusing what was there)?

Hi @quinniedid ,

In this post you can find info about how works and how create rules in this plugin.

https://forums.fogproject.org/topic/9624/control-access-plugin/14

With this plugin you can restrict the access to the menus and submenus but not to specific host and groups. To do this maybe you can use the Site plugin but, unfortunately, this plugin doesn’t work with the 1.5.5 version. I am working to fix the bugs.

@george1421 Oh, my apologies. Thank you very much for your help. You’re truly a wizard as your profile picture shows. 😉 Thank you again!

@Sebastian-Roth I’m not seeing image definition. If you mean under Image General after opening an image and changing one of the properties to any of the settings then that did not work either.

I was able to export the images and import them to the new server after I RSYNC’d the images.

I’m good now.

After @Tom-Elliott’s 1 on 1 assistance, the server is updated and running smoothly again. Thanks everyone for your suggestions and help.

Ok @Sebastian-Roth, if it goes wrong again I will tell.
Thanks

@Technolust FWIW, since you have a Windows 2012 DHCP server you might want to look over this wiki page if you need to support both uefi and bios systems in your environment: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

thx! I try this way.

@Andrew-Seals The standards for the ipxe boot loaders are:
BIOS: undionly.kpxe (kkpxe only if you have problems with kpxe.
UEFI: ipxe.efi (or sndonly.efi if you have problems iwht ipxe.efi)

If your environment has to support both uefi and bios systems and you have a Windows 2012 or newer dhcp server or a linux dhcp server you can setup dynamic boot file assignment by following here: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence

@mstrolo Good thing we have a wiki article addressing this exact issue: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Repair_broken_database

@arnaudrigole I am glad you found a solution that worked for you, though I’m still interested in trying to at least guess at why the other partition scheme gave problems.

Was there a difference in disk size in the SATA vs nVME SSDs?

Perhaps the nVME SSD is smaller and the OEM partitition at the end of the disk was out of range, though we’d expect a different error for that.

@Troye-Johnson I’d wait for 1.5.6 as we have improved things like client communication in the dev-branch a fair bit. Not sure when we get to the next release though.

@Sebastian-Roth thank you for pointing me at the DHCP! I found the problem! All files are fine, but our company DHCP was not! After trying it in a seperated VMware Network it worked like a charm! So all the effort was in vain - i am sorry

We have an old fog running 1.4.4 in our DHCP config for managing the PXE Menu because we are running multiple (i)PXE Services in one subnet. I created a new boot menu item to forward the pxe boot to the new fog server.

like this:

iseq ${net0/mac} a0:36:9f:bd:XX:XX && goto testing || :testing set pxeserver:ipv4 FOG-IP set next-server ${pxeserver} chain tftp://FOG-IP/default.ipxe exit

Got it from here in 2017: https://forums.fogproject.org/topic/9648/add-a-second-pxe-boot-option

Worked fine, until now … And by now, i understand why no certification cmds were availibe because it got stuck in the old fog enviroment. Need sth. to reload the enviroment i think. I will take a look into it to find a way. Maybe i will open a new topic here!

Thank you @Sebastian-Roth for taking the time! Your scrips are fine - it was my fault …

@Sebastian-Roth Awesome, thank you!