@mezan said in Unable to load into Fog server PXE:

It prompts me with service request 41 on the client.

I don’t know what that means, please take a photo of the error and upload here. Be sure to include the entire screen, well focused, with as little glare as possible so we can read what it says.

I tried using another VM instance to boot via PXE but it loops at Operating System not found.

So it imaged properly but can’t fined the OS? What did you do exactly that resulted in this?

And undionly.kpxe is a BIOS/Legacy boot ROM. Meaning this file only works with the majority of systems in BIOS mode. If the computers you’re trying to work with are in UEFI mode, then this file won’t work. Look in the computer’s firmware settings and see what it’s set to. Also, we have an article on co-existing these two modes if that’s your problem, here: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

Also, exactly what version of FOG are you running? Look in the top left of the web interface, it’ll be in/around the FOG cloud.

@Nicolas-Bricet Are you using IPv6 throughout your university?

Can you give us a YouTube video of the issue you’re seeing? Just a short smartphone video of a computer booting until it hangs would be good.

Tom has changed up a lot of things in the pre-process before partclone goes to work.

Most of the errors are usually non-impacting.

Now, it just shows them so you know what’s going on.

IMHO I say this feature can wait till FOG 2.0 is released. I really want to see 1.3.0 released soon.

Factoid about FOG 1.3.0 DHCP, it would have given the surface pro 4 the correct boot file out-of-box.

You can configure your Windows DHCP box to do the same if it’s 2012 or later.

@wwarsin said:

@Tom-Elliott Hi Tom, I just tried that and recieved the following error (I’m on SVN 5666 now)

FOGFTP: Failed to rename file. Remote Path: //var/www/html/fog/service/ipxe/bzImage/backup/bzImage_20151207_214012, Local Path: /var/www/html/fog/service/ipxe/bzImage, Error: ftp_rename(): Rename failed.

You’ll find the FTP credentials and host used for the Kernel updater here:

FOG Configuration -> FOG Settings -> TFTP Server ->

• FOG_TFTP_HOST #This is the IP that FTP uses for putting the kernel in place.
• FOG_TFTP_FTP_USERNAME #This is the username FTP uses.
• FOG_TFTP_FTP_PASSWORD #This is the password FTP uses.
• FOG_TFTP_PXE_KERNEL_DIR #This is where FTP tries to put the kernels.

Also, @Tom-Elliott I’ve recently discovered a bug. I don’t know how long it’s existed but I was able to figure it out today. On both our Administration FOG setup, and my building’s FOG setup (which is separate), the FOG_TFTP_PXE_KERNEL_DIR is missing a slash in the path:
/var/www/html/fog/service/ipxe/ The one colored red. I manually corrected it on both and it works, but we didn’t manually remove that slash. Just pointing that out to maybe help others with the issue.

inside of FOG Configuration -> FOG Settings -> Client Service

The “New client” thing must be checked for the new client to work.

Also please note that you should type in your PLAIN TEXT password into the password field, and that your fogcrypt string should go into the legacy field.

Also note that in the hosts menu, any password that you put into the AD Settings fields in there gets re-encrypted when the aforementioned “NEW CLIENT” check-box is checked. So, I’d recommend just clicking the “Clear Fields” and then click the “Join Domain” so that it simply auto-populates.

@Tom-Elliott Amazing. I’ve been wanting this for a while.

Now, if the check sums don’t match, does it re-attempt the downloads? What about checksums for the new client?

Reset the RAM in those. Also try a different hdd in them. These are the initial troubleshooting steps I would do in your situation. Results from these things determine what to do next, if anything.

Also try a dumb switch, try different network ports in the room.

@ZINGARO1972
https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk#Check_what_version_you.27re_running

files in Linux that begin with a period are hidden.

ls lists files.
-a includes hidden files.
-l shows permissions and ownership.
-R is the recursive flag.

So this command would show every single file in /images and it’s sub-directories:
[CODE]ls -laR /images[/CODE]

You could pipe that with grep, which is a powerful searching tool and just search for .mntcheck

[CODE]ls -laR /images | grep .mntcheck[/CODE]
That will only show all instances of .mntcheck inside the /images directory.

There should be two.

Please and thanks.

In plainer terms, you can update Ubuntu from an older version to a newer one - sure. But if it fails or leaves fog crippled, we don’t just “know” what went wrong. We don’t know how the old OS was setup, what was installed, how it was configured, and so on. It can be troubleshooted but how long that will take or if it’s successful or not, I can’t tell you. The Developers and Moderators and other community members are normally willing to help people - but your pace is limited to their free time.

So… Last night I wrote an article about migrating fog. For this - we know all the steps, and it’s less risky - and you can follow along with it and work at your own pace instead of relying on us.

If you’re strong with Linux and you’re Google-Foo is up to snuff, sure upgrade your OS. If you’re a newbie in a crunch don’t want risks, migrate.

@Arrowhead-IT said:

because I’m dumb when I’m sleepy.

You’re not the only one. Number 1 piece of advice I give to college kids, athletes, and just every day people is don’t sacrifice your sleep.

Short story - I was going through studying for finals in college one semester, staying up late, getting up early for work. Trying to find time to code a custom price markup management piece of software for a business that wanted to further save more paper. Basically double columns of data per page, like rows 1-80 on the left, 81 through 160 on the right, then on the back of the page, and so on…

I kept screwing it up… couldn’t get the math right. And yes, there’s algebra involved with this problem. I spent days on this. Just couldn’t get it.

Then, instead of continuing to pound at it, I realized I was really really tired, and I needed to sleep. I took a nap for 3 or 4 hours. When I woke up, I solved the problem in 5 minutes.

Sleep… so important. Sleep deprivation makes you dumb. You become mentally exhausted, just as you can physically. Physically, your body will be less strong, able to go less distance, lift less weight. Mental exhaustion means your not as clear, don’t have as good memory, not as good focus or attention to detail, and not so creative and not so good at solving problems.

People brush off sleep like it’s un-necessary. These are the people that consistently unperform, or just barely make par. Really, really value your sleep!

@Tune389 said:

@ch3i okay thanks for the info. I try now to downgrade my fog version back to 1.2 …

That’s not supported nor advised…
To “downgrade” requires either restoring a previous snapshot (via a virtual machine) or rebuilding your FOG server from scratch…

Then we need to figure out a way for any old client that reports in - to just be told to execute such-n-such to install the new client automatically. This is really important.

@maxiecool2 The Ondrej ppa is built for Debian, and thus works on Ubuntu. Quote from the page:

I’m available for some freelance work related to the packaging I do in Debian[http://qa.debian.org/developer.php?login=ondrej%40debian.org&comaint=yes] (and thus in Ubuntu)

Reference: https://launchpad.net/~ondrej

And, the fog installer has been installing this package on Debian & Ubuntu for a while. At my house, I’ve setup automated testing for the installer, I test it every day against many distributions of Linux. Results can be viewed here at the moment: http://97.85.148.83:20080/fog_distro_check/reports/

@BASURILLABAS2 In your picture below, it’s still trying to use bzimage32 with init.xz. One is 32 bit, the other is 64 bit. They can’t work together. Did you re-run the installer? What version of FOG are you using? Have you specified anything in the kernel parameters for this particular host?

@Julianh You’re missing one .mntcheck file.

You need one in both images and dev folders

[CODE]touch /images2/.mntcheck
touch /images2/dev/.mntcheck[/CODE]

After that, restart the NFS service and portmap/RPC (or reboot the machine).

Let us know what it does then.

I’d personally want to see this wait until fog-too.