Topics created by AndrewC

@AndrewC said in Dev branch fails install:

Changing or removing completely the password field from .fogsettings does not appear to affect this at all.

Just a quick info on that. The installer not only looks for an existing password in .fogsettings but also in .../fog/lib/fog/config.class.php. This has been in the code for some time but had a smaller issue because of the password being defined in the PHP file over multiple lines. Which working on the password stuff I also fixed this. Please let us know if you think we should only ever read an existing password from .fogsettings?!

The latest parted magic iso image I can find (free) is 2013. So I looked through that iso and based on what I see I have an observation.

The error message mentions unable to mount the squashed file system file.

I don’t see where you are transferring that file system via iPXE? I do see that file on the iso in /pmagic/pmodules directory.

I would be interested in reviewing the following files from the 2018 iso image.

/boot/syslinux/syslinux.cfg /boot/pxelinux/sample_pxelinux.cfg

Lastly are you trying to iPXE boot this image on a uefi or bios based image?

No updates of the system have been performed, and FOG is the only software in use on this system. I’ve had zero issues upgrading all along from 1.3 through various RC releases as they come out and onward to this final 1.4.0 release. This is the first time I’ve seen a failed message during an upgrade.

Specifically the error log shows:
“update-rc.d: error: cannot find a LSB script for FOGMulticastManager”

I was able to bypass the issue by grabbing the init.d scripts out of the packages folder, and manually placing them into /etc/init.d following with a chmod +x. Once those scripts were copied into init.d the foginstaller script moved along nicely.

@Tom-Elliott said:

@AndrewC I’m not seeing the problem, but I would imagine you are seeing this in particular with EFI style systems?

Yes. It was an issue with the particular test machine. Did not have a problem with any others BIOS or EFI. Worry not.

@AndrewC The menu entries look perfectly sound to me.

I would ask you to try this exact configuration on any machine you can get your hands on that is capable of UEFI mode (not mixed mode, turn that off). If it flat-fails across the board (which I doubt), that’s one thing. But if it works on any at all, then it’s likely something to do with the hardware or with the boot ROM ipxe.efi.

That error from your first post “Could not boot: Result too large” really sounds like it’s boot ROM related, or a hardware issue.

It could be resolved as simply as trying different .efi files. Your options to try are on your FOG server in /tftpboot. Just change your DHCP UEFI policy’s option 067 to a different file name, try them one at a time. Do a complete power-off on the computer you’re trying to boot with for each try.