@Strahd Have you been able to make progress?

@Tom-Elliott Tom, looks like everything has been resolved after going from 2144 to 1.5.10.2218! No errors and I was able to capture no problem. Thanks

FOG 1.6 is great, but I ultimately had to roll back to version 1.5.10 because I ran into an issue I couldn’t resolve, and the deadline for deploying a large batch of computers is fast approaching.
​All my images are stored on a Synology NAS. On the older version, I had multiple storage groupe and nodes configured on the multiple Synology NAS, and everything (capture/deploy) worked fast without any issues.
​In version 1.6, however, I’m hitting a roadblock. It seems there is a check during task creation that verifies if the primary storage node (in storage group) is online. Since it’s a Synology NAS, this check naturally fails, and FOG won’t allow me to create any capture tasks. I also tried mounting a share directly inside the /image, but it wasn’t fast at all (capture/deploy).

​I tried the sanboot, and it really helped—it works well, especially on some HP machines.

​I kept version 1.6 in a VM for testing purposes. Maybe a feature to disable the online node check will be added in the future—or perhaps it’s already there and I didn’t find it—or maybe direct NAS support will be introduced eventually.

Working 👍

@JJ-Fullmer This was it, thank you!!

Everything I read kept telling me this machine was x86 based and there is no hint in the BIOS or the serial number lookup tool, of it running an ARM processor(other then “Elite”). We are going to return these machines to the vendor, so problem solved for us.

Would be interested in hearing about future support for ARM in FOG because I’m sure this isn’t the last time we will cross paths with it.

@Tom-Elliott Hi! I updated my FOG server to latest beta-branch version: 1.6.0-beta.3197. I also updated my storage node to 1.6.0-beta.3197. This fixed the invalid path issue I was having. Thank you for the help!

1a0e5491-b776-49fe-9fbf-d2bc40087f78-image.png

@Tom-Elliott

Thanks so much for your help with this. Happy to feed back any info I can so please do let me know if there’s anything else you need me to test. Will be on annual leave for a couple of weeks after this and have no access to the systems but I think this confirms your suspicion. Please see results below from a Dell OptiPlex 3070:

Addresses on this machine:

NIC: 01:00.0 (Realtek RTL8168h)
Root port: 00:1c.0

UEFI mode:

setpci -s 01:00.0 CAP_EXP+10.w = 0142 (last digit 2 = L1 enabled)
setpci -s 00:1c.0 CAP_EXP+10.w = 0c42 (last digit 2 = L1 enabled)

Legacy/CSM mode:

setpci -s 01:00.0 CAP_EXP+10.w = 0040 (last digit 0 = ASPM off)
setpci -s 00:1c.0 CAP_EXP+10.w = 0c40 (last digit 0 = ASPM off)

Dell’s UEFI firmware enables L1 on both the NIC and root port. The Legacy/CSM path leaves both off. The only difference between the two readings is those two ASPM bits. Everything else in the register is identical.

Thanks for the nudge to run these. Anything else needs testing please do let me know. We love using FOG and it’s invaluable in our set of schools that we work in at least so please do keep up the great work!

@toschulz So I suspect the problem is due to a divergence of db schema between dev-branch/stable + working-1.6

If you can update yoru Mysql directly:

sudo mariadb -u root fog (if no root password of course - if you have a root password add -p

UPDATE schemaVersion SET vVersion=0;

Then refresh your screen, click the install/update, and hopefully the error will go away.

The way the schema is configured is it will attempt (idempotently) to rerun every single SQL query in the schema chain.

This should fix the problem you’re seeing.

I believe there’s a column on the login history piece being requested that may just simply be missing which would cause the issue with datatables.

@DiegoP I believe mdadm will still be allowed to work, but I think you’re supossed to use “mdraid=true” for a kernel argument. If this is not set, FOG won’t know to build the array. This would help explain why the disk couldn’t find a partition layout as well since it’s expecting to be part of an array (which then looks/acts as the disk you’re truly working with.

As for “partclone to partimage” I’m not sure I understand.

Fog moved FROM partimage -> partclone way back in the 1.0.0 days as partimage has been obsolete for quite some time now.

@Tom-Elliott Hi, Yes with the proposed fix, it works now.

@Tom-Elliott
The fix worked perfectly! The menu issue is now resolved.

Thanks for the support!

@Tom-Elliott Hello Tom yes I have installed the compatible Fog client from the Fog server on the reference machine, sys prepped and captured the image and now I am deploying.

@Tom-Elliott
Updated to latest dev-branch and snapins are working now
Thansk for help.

What version of FOG are you running?

@Valer I think we need to understand what this plugin is doing.

CSS isn’t something we’ve allowed to be injectable though it could be.

You can still use your own CSS but that’s more at the FOG Configuration -> FOG Setting -> FOG_THEME, but you would need to put it on your server in a location you type the path too here.

https://docs.fogproject.org/en/latest/development/plugin-development

This is a good toolkit for understanding how to build your own plugin.

@rpycroft Please attempt to update to 2231.

I have figured out the issue. I was looking in the wrong place in BIOS for the secure boot setting which was on. Turning off secure boot fixed the process which runs perfectly now.

So, somehow this slipped by my radar, but this guide is now largely obsolete! Pretty much everything done here now seems to be automatically handled by FOG after the transition to iPXE 2.0. FOG will now generate it’s own signing keys and seemingly sign the kernels for you, and provides a dedicated boot menu entry to enroll keys via MOK! I’ve yet to test this myself so happy to be corrected if I’m missing anything here.

Additionally, it looks like you can pretty easily migrate existing keys into this setup with some install parameters. I’ll be updating my ansible role to acomodate these changes soon!

@JasonNaughton

Hi, I noticed that this was unresolved after so long. Wonder if you have solved it?
I recently stumbled across the man page for dhcpcd.conf. In there is a denyinterfaces (pattern) should solve the issue for you. It tells dhcpd to ignore the nic interfaces listed in pattern. Just was wondering if you found the fix otherwise hope this helps.

** WARNING: /etc/exports still exports with no_root_squash.
** Captures land as root, so moving the image out of
** /images/dev fails with ‘550 Rename failed’.
** Replace the /images/dev export options with:
** all_squash,anonuid=1002,anongid=1002

Fixed problem