@greichelt On your fog server itself, there is a config file /etc/resolv.conf that file should list your name servers (DNS servers) used for the fog server to do name lookups. A quick google-fu will show you the parameters needed for that file. Typically on ubuntu that file is managed by the network manager application. Just be aware of that because it may overwrite any settings you add. For the network manager application that is typically an application on the tool tray that deals with network configuration (sorry I’m a rhel guy, so I can’t give exact instructions for ubuntu).

@weite Start here: https://forums.fogproject.org/post/129262

@george1421
The only reason I can see it continuing to work is because microsoft isn’t primarily a hardware company. They need their OS to be available on many different standard x86_64 hardware. Now if they stop selling OEM installers and only using somesort of pre-baked internet recovery I would be more nervous.

@Sebastian-Roth said in All disk capture unable to deployed to two larger disks:

The old patch was removed some time ago (ref) and I guess this was a hickup in your build environment.

Yes I found out a bit after that post, I just over laid the new files over the existing path because I’m building the inits using a different method than the build script. Sorry that was my mistake.

@Sebastian-Roth So, in the end, I have entirely switched to a bridged network solution, and everything is working fine now. It seems that the problem was, in fact, as you mentioned, about the issue in the installer script with network adapter enumeration. But that also means it is some type of bug - all captures of an image were successful, only failed at the very end trying to update the database.

The difference that I noticed between bridged and internal NAT configuration is that in the latter one, the FOG installer script at the very beginning complains that net-tools is not installed. When it asked about the network adapters, it couldn’t get an IP at first because it tried to use a network adapter enp0s3 enp0s8 (NAT adapter for internet connection and internal NAT adapter), at which point I had to specify to use enp0s8 adapter manually.

@UWPVIOLATOR Did you get to test the script?

Meanwhile we have released a new version of the fog-client which should print out a text instead of the hash when it catches the unhandled exception.

Either you can update to the latest dev-branch version to get the new fog-client or you can switch over manually: Download SmartInstaller and MSI and put those in /var/www/html/fog/client/ (rename the old binaries to be sure you have a backup copy in case). Then edit /var/www/html/fog/lib/fog/system.class.php and change the line where you see the client version from 0.11.16 to 0.11.17. Be aware that all your hosts with running fog-client will download the SmartInstaller from your FOG server and attempt to auto update!

@jhumpf We need more information to be able to help!

@mikmatcr Did you get your disk setup or do you still need help with this?

good call, I will talk better with the MS people.

Cheers!

Good holidays!

@Sebastian-Roth

Ohh thank you ! It works now ! 🙂

I didn’t know if I had to log on and then reboot manually to join the domain.

I noticed that I have to wait 3-4 minutes after the first boot for the automatically reboot and then the PC is in the domain !

Thanks a lot for the help, the problem is now solved !

@Sebastian-Roth the installer will not run without internet connectivity. It hangs on the line adding repository, I think. I’ve left it for 30 minutes with no change.

This behavior is new, because I’ve always deleted the .fogsettings file and rerun the installer to change the ip.

Outside the settings in the web ui I had to manually change the ip set in the tftpboot folder.

@dinagaran7007 Please open a new topic and post all your details there: FOG version, install error log, …

@Sebastian-Roth There were still some duplicated MACs on my network removed then from the database and it worked, this issue was caused by myself, there were some pending macs to aprove and I didn’t paid attention to then and approved then all, but lots of them were from Virtual machines.

@IdahoTech said in Updated Ubuntu and now cannot get to fog gui:

So let me ask this to all who answered do you have a password on your sql? Seems to be a problem with ‘no password’ mysql installations…

Just as an FYI, this issue is being addressed in the soon to be released FOG version 1.5.8. In 1.5.8 there will be tighter controls on the database side. The downside is that the FOG admin will need to remember the root password for mysql since it won’t be recorded anywhere in FOG. FOG shouldn’t need the root user’s password for mysql except the first time FOG is installed, it need’s root’s password to setup the FOG database. After that there is a foguser created that interacts with the FOG database even during upgrades.

@FuriousGamer065 You probably should run through the tutorial to ensure that all of the bits are in the right spot and then rerun the fog installer.

Understand this will only address the ftp issue. There still may be the issue related to unable to find the storage node. That’s on the NFS site of the image upload.

@george1421 thanks for the info I’ll get that done Monday and I’ll left you know what we find

@Schuede said in Xps15 Fail to deploy image - Ipxe / Uefi:

listen-address=127.0.0.1

Sebastian, good point I skipped right over that. In this case that command is telling dnsmasq to bind to the loopback interface. So only DHCP DISCOVERS on the loopback interface would get a response. Probably not what the OP wants. While that’s not the issue in the picture it would be the cause of the other issues reported.

@DeRo93

I’m curious, what drives are inside your HP 840 G6s? We currently have the same laptop at my company, but our drives included in our G6 are Western Digital PC SN520 NVMe SSD. I know there is a configuration with OPAL drives (so they are already encrypted by default)

Hi,

Thanks george1421. The second storage node was running 1.5.6. As it is still in a test environment, I completely rebuilt it from scratch. All working fine now.

Yes, the remote storage node is a full FOG server, so I will export / import the metadata.

Thanks again 🙂