@Bigredcherokee I have seen people in the past “think” they can use this account for system administration, they install FOG and the installer takes over this account and gives it a new password. The admin then resets the password on the fog account that’s where things usually go sideways. FOG will throw a similar error to what you last posted when this happens.

You will also see a similar error when you try to capture an image. Right at the end of the capture it will fail with an error about unable to update the fog database. That is an indication that the fog service account’s password has changed.

@Xibeaga actually, no. There’s been very few this past year.

Found the problem! Hurrah!

Managed to find this page on other DHCP Settings for routers which listed instructions for Cisco: https://wiki.fogproject.org/wiki/index.php?title=Other_DHCP_Configurations

We initially used:

Option 66 [Server IP] Option 67 ascii undionly.kpxe

What actually worked

next-server <Server IP> bootfile undionly.kpxe

Thanks for the help @Sebastian-Roth @george1421

@Sebastian-Roth -465.7 GB

@dbrilliant -It’s all good. Working fantastic!

That’s it thanks guys. I used sudo add-apt-repository universe, and there were about 20 packages out there. Now, if I can remember how to finish this project off. It’s been 7 years since I built a fog server. lol

@osandag said in no such device or address:

Hi, Was this issue resolved?
I have a same or similar issue where the host status is green for about the first ten minutes till i register the host image it, but after a while fog says ‘no such device or address’

Given the age of the issue, has it been fixed or I have to follow the SQL edit procedure?

I just had the same issue that you are describing. The way I fixed it was to ensure that my interfaces file (Ubuntu server) was configured correctly. In my case, I was using search [domain] instead of dns-search [domain]. Once I fixed that, all was well.

@george1421

Reading the Parted Magic Frugal install instruction did get me some valuable information :

https://partedmagic.com/frugal-install/

Simply put, the boot process for Parted Magic will seek the Squashfs in removable devices, which do not exist in a “sanboot” :

root=/dev/sdXX

Starting with PartedMagic 6.2 the search for the pmagic-.sqfs file will begin with the removable devices, unless a device/partition (root=/dev/sdXX), label (label=XXXXXXXX) or partial uuid (uuid=XXXXXX) is stated. Without such a kernel boot parameter a 10 seconds delay will occur.*

Furthermore, the boot must be set to “boot=/boot” :

directory=/boot

Previous versions of this document said to copy the “pmagic” folder to ”/”. This carried the risk of a subsequent run of PartedMagic from a CD or a USB stick to find the pmagic-.sqfs file on the disk instead of the on the media – something you would not want in the majority of cases.
Starting with PartedMagic 6.2 the risk is inverted: a subsequent run of PartedMagic from the disk might find the pmagic-.sqfs file on the media.
The solution in both cases is to “hide” the “pmagic” folder on the disk in e.g. the ”/boot” folder.

@aborn said in Images are created with 777 (world writable file rights) and owner root on CentOS 7:

I inserted the proposed new line now in the fog.postinit script

This is at the wrong point in time. We can use a postinit script to fix things before things happen. Current a postdeploy script will handle actions after an image is install on the target computer. What we need is a postcapture script to handle things after the image has been captured but before the image is moved from /images/dev to /images. Once the image has been captured we will use a postcapture script to reset the permissions and file ownership of the captured directory so that the FTP process can move it as fog. I can see the process in my head clearly. We just need to patch the fog.capture (guessing at name) script to make the call to a postcapture script. We should be able to mimic what is done for a postdeploy script. It shouldn’t be that hard to do, then we’ll use a postinit script to copy the patch fog.capture script to FOS before it starts doing its thing.

@abulhol Fixed in working branch, will be in the next release. Let’s see if we are able to get this out in time so people upgrading their servers from 16.04 to 18.04 won’t run into the same issue as you did.

@lucycle
I used to have an issue with some Realtek cards behaving weird and throwing errors in IPXE and later in the boot process, but it’s been a while. With these two HP models and an integrated Realtek card I had to use a different boot firmware, long shot but maybe you can try that?

HP210 Legacy Test

pxe-service=tag:HP210,X86PC, “HP-210 Working”, realtek.kpxe

HP430 UEFI Test

pxe-service=tag:HP430,X86-64_EFI, “HP 430”, realtek.efi

@lucycle said in NFS over TCP not available from x.x.x.x:

In my case the driver in question was dm9601.ko and I also compiled it into my initrd.img which did not fix the issue and behavior persists.

I’ve added another USB dongle, this time a Lenovo 2.0 Ethernet Adapter based on the asix driver, however it didn’t work, then I checked with modinfo and noticed I was missing a dependency (usbnet.ko)

modinfo asix .... depends: mii,usbnet modinfo usbnet filename: /lib/modules/4.15.0-34-generic/kernel/drivers/net/usb/usbnet.ko

Just to be sure, you said initrd.img, I added it to initrd.lz

That’s about all I’ve got to suggest at this point

@george1421
Thanks george1421,
I have no issues with mine but thank you 🙂

@Boyan-Biandov yes, but I prefer to use the working branch because it uses Ubuntu’s PHP7.2, which makes it more compatible with other software.

@geardog Sorry for the long delay. Will be ready fairly soon. Are you still interested, I hope?!

I added it yesterday but also had to put in some major work to fix issues in our kernel build environment… https://github.com/FOGProject/fos/pull/12

@abulhol Fixed in working branch.

Hello Sebastian!
Just realized my response stayed as a draft for this long.
Thank you so much for this very useful pieces of advice. I will look into that.
To be honnest, scripting was on my list of skills to develop and improve on a short term scale and that is the perfect occasion to do so!
I shall get back to you when I have moved forward enough.
Regards.

You have to set a (very strong) mysql password first, topic:

https://forums.fogproject.org/topic/12445/please-help-ubuntu-updates-screwed-up-my-mysql-root-password/7

@george1421 Great you’ve been helping out so much here and figured it all out.

@mstumpo Marking this solved as I think the initial question(s) is/are solved. Please feel free to open new topics as you run into new issues. Good to keep topics clean so other people can find this and profit from the answers as well (details not lost in a 5 page topic).

First let me say that FOG will not work as you have it defined. FOG will only image using a single IP address on the FOG server. Your FOG server can have more than one network interface but will only image using a single IP address.

I know I’m mixing what I’m saying. FOG does support network bonding (using two or more physical network interfaces to add additional lanes of bandwidth). But those bonded interfaces MUST have a single IP address assigned. And typically the bonded interfaces go to a single network switch.

Your drawing appears you want a multi-homed FOG server (multi-homed means multiple network interfaces each with their own IP address). That is not supported for FOG imaging.

@jtyler Have you had a look into the mentioned error_logs? Let us know what you get.