Thank you for your reply.
I will try that 😉

@pkt said in Lenovo X1 Tablet hang on init.xz.... OK:

DHCP 067 Bootfile Name: ipxe.efi
Yes, secure boot is off in the BIOS on the tablet.

See here is where we keep seeing a conflict. You are saying BIOS and ipxe.efi in the same context.

The issue is the target computers need the proper ipxe kernel for the firmware mode.

For BIOS (legacy) configured systems you must use undionly.kpxe class images.

For UEFI configured systems you must use ipxe.efi class images.

@george1421 Hello George as you seen on the Database schema error log

"General error: 1819 Your password does not satisfy the current policy requirements Error Message: Error Code: “HY000”, Error Message: [“HY000”,1819,“Your password does not satisfy the current policy requirements”], "

because of mysql root password policy requirements I coulndt get update or install database schema to new one.

so I searched about error for mysql server then I understhand I dısableit Password validation on mysql

[https://dev.mysql.com/doc/refman/5.7/en/validate-password.html]

For what it’s worth: these are the manufacturers of the NICs: (You have two 00:09:0f, so I’m guessing this is a wireless card with Bluetooth?)

00:09:0F Fortinet Fortinet Inc. 98:E7:F4 HewlettP Hewlett Packard E4:A7:A0 IntelCor Intel Corporate

@sebastian-roth Hi ! the initial kernel bzimage after fresh install was 4.11.0. I attempted to update from web interface but it was tricky because of rights on directories. Finally, I did it (command line via putty) but the pxe boot resulted in an error. I worked again on it and I succeeded : the current version is now 4.13.4 and all is working great ! I had to copy this new kernel in two places : /var/www/html/fog/service/ipxe and /var/www/fog/service/ipxe to overcome an error during the pxe boot process. That said, we configured another fog server for redundancy purpose and the upgrade from web interface 4.11.0 to 4.13.4 worked perfectly this time …(?) Thanks to every body for the reactivity. The Fog server is our very useful weekly tool to restore our classrooms… Best regards.

@wayne-workman said in Images not replicating:

I have, it just shows online/offline. I created it for exactly the problem you described. In the past, this problem was fixed but I guess it just keeps cropping up. Anyways, the project is called MonitorFogStorageNodes and is located here: https://github.com/FOGProject/fog-community-scripts

I thought I saw a Fix for this issue in one of the the RCs for 1.5, but can’t find it now… I saw the referenced issue (https://forums.fogproject.org/topic/10503/images-not-replicating) and saw that it was “Solved”, so i was hoping for a confirmation that the replication issue was fixed in the upcoming release…

I will grab that plugin, thank you!

@dhruvin-t said in cant make the presented virtual disk as a storage node.:

get fog switched to the mounted share

What do you mean by ‘mounted share’ ? If this is an iSCSI block device you’re mounting, then this works fine. If it’s a regular network share, it’s not going to work. If it’s just a new local disk it’ll work but please say ‘local disk’ instead of ‘mounted share’.

@sourceminer Did you get this fixed? I am fairly sure George and Tom had the right pointer for you.

@wlainey Do you have more than one storage node defined in the Web UI?

From the username apache I see this could be a CentOS system. Any chance this is a SElinux issue? Please run sestatus and ls -alZ /opt/fog/snapins/ssl and post here.

I’ll mark this solved as it seems like the issue was fixed by disabling the other NICs.

@jmeyer I don’t seem to be able to explain this properly. I am not talking about disk size and start sectors although this might be an issue as well. But even if you get this right it still might not be able to boot in the VM as of difference in (virtual) hardware.

By the way, is your image UEFI or legacy MBR? Configure your VM accordingly.

@birvin Thanks for the update. Good to Herr it’s working now. Don’t think think it’s worth looking into this more as it seems to be a one time issue…

I always Sysprep. For me it removes any questions of there are any device independent licenses for software installed on the image.

@sebastian-roth yes the client is installed but I figured it out. I had to the reset the encryption data before doing the snapin deployment. Solved

@pberberian said in FOG is very slow to server kernel and init image:

I am using an intel addin card that gives 4x10G SFP interfaces

We need more details than that!

Sounds similar to this: https://forums.fogproject.org/topic/11157/checking-schedule-shutdown-after-task-completion-causes-the-running-task-to-hang

Moved and marked as solved.

Just a wild guess: But with Windows 10 and its Meltdown and Spectre Patches there was a massive problem with Antivirus-Programs causing Bluescreens.

Just make sure that you dont have the Windows 10 Meltdown / Spectre Patches installed and an Antivirus that isnt compatible?

@greg-plamondon The instructions were in both documents. The one I linked and one that Wayne linked. Unfortunately it happens more often then you might think. There are some documents out in the wild that recommend you setup the fog account to install the software and manage the syste (which is the wrong way).

@george1421 I’m 99% sure it was the suggestion of something I found on the forums a long time ago, but simply forgot.

Like I said, once everything calms down, I’m planning on rebuilding my FOG machine anyways, and blast away old images, especially since I can drop driver packs in now 🙂