@foguser9856 said in X1 Yoga Black screen after init.xz:

Is that something I can change?

Unfortunately that is one of the caveats of booting this way. You loose the dynamics that iPXE provides.

But booting FOS via USB does tell us that there is nothing wrong with the kernel or the inits. It appears to be the handoff between iPXE and FOS, or you have flaky firmware on that yoga.

Has the firmware been updated to the latest release on the yoga?

@quazz

So I tried re-capturing the image from my VM and it finally finished but took forever. I left a ping running on the host and the server and never had any lost packets. I had some higher ping times going to the VM were average with one very high number. But never any packet loss.

I decided to try and capture the image to a brand new image and not one I had used previously. I noticed my transfer rate was higher and it ultimately finished capturing the image.

Could the delay simply be the difference between imaging a Windows 10 machine versus a Windows 7 Machine? This is the first image I have created of a Windows 10 machine.

Let me know if you have any thoughts on this.

Thanks again for making me think more about it. 🙂

Cheers!

@fmaster007 the … translates to the path of your fog installer, not the path on Linux of /lib

You can use a dns name and create a split horizion dns where you make fogserv.domain.com at each school point locally to the local fog server.

The issue is as Wayne said, Once the client touches a fog server it becomes tattooed to that fog server. Now if you know that ahead of time you can synchronize (i.e. copy the ssl certificate from your master FOG servers to the other remote fog servers) then have the clients reach out via dns name. If you have any clients that have touched one of the older non master fog server, you will have to reinstall the fog client on the target computer.

Can one of the @developers or @moderators or @testers check to see if this bug exists in 1.5.2 please? I’m not able to do it at the moment.

I found out that the error was caused because the fog account was not recreated when we upgraded. All is well now except for name changing and getting them on the domain automatically. I think that is also a password issue.

@ddavis
If rebooting the server does not fix the problem it could be an apache problem, you could run a

tail -f /var/log/apache2/error.log``````

let this run and see what you get when you try modifying your changes.

@wayne-workman

Going from 1.5.0 to 1.5.2 resolved the issue.

Glad that helped. The beauty of an active forum where ones struggle becomes others solution. Pretty cool.

@andythemayor Lol, my bad. I thought you were OP. I didn’t read…

Also, changing the memory to 256 resolved the issue, thanks for the help!

I am having this issue with 1.5.2

Just throwing this out there, might absolutely not be related and me just missunderstanding whats actually happening here.

I had problems Imaging a computer at point when switching from a hdd machine as image-source to an ssd.

I had to change the host primary disk to the correct one - I think from sda to sda2 or something along those lines - for this to work.

Rereading again I suppose this is in another direction, but just in case.

A pending host is a host with the FOG Client installed that is not registered in your FOG Server.
That FOG Client is calling home to your FOG Server and is added as a pending host - because it is unknown and therefore untrusted until you (the admin) claim it. Claiming is basically saying ‘Yes, that’s one of ours, trust it’

This was made aware a while ago and has been addressed in the github working branch which will become 1.5.3.

@wayne-workman
That worked!

Legend - exactly what I needed.
Nodes are visible and I can continue the project 😄

Where do I mark this as solved and buy you a virtual beer!

@george1421 I had downloaded the 6077 again and not 6078 🙂
END USER ERROR 🙂

@julianh said in Ubuntu upgrade to 16.04.4 LTS kills Fog:

I have a dedicated fog Server that was somewhat expensive with its SSD arrays, so I can’t migrate to a new box, I can’t afford it.

You could migrate to a VM first - then from the VM back to the nice hardware. Keep the VM as a spare - but first use the VM and ensure everything is correct and working - and imaging.