Posts made by RobTitian16

@Quazz Thanks for replying. It does have a physical disk and I’ve tried chkdsk /r but it seemed to run through it within minutes… it was the same with chkdsk /f.
I’ve just had a look with CrystalDiskInfo as well, and that’s come back saying it’s fine.
Would a defrag help it at all?

Hi all,

I currently have a computer with an image I want to upload, but I can’t get it to upload to the FOG server. It seems to fail on the hard drive check and says: “Cluster accounting failed… extra cluster in $Bitmap”
I’ve run chkdsk /f multiple times and restarted multiple times as it has suggested to no avail. I have at least 15GB free on the C drive and have successfully uploaded images in the past. I do currently have the trunk version of FOG installed on my Ubuntu 14.04 server and the image I’m trying to upload is a Windows 8.1 image.

Any help with this would be greatly appreciated!

@Wayne-Workman That’s solved it! Thanks a lot for your help

@ITSolutions I upgraded the server from 1.2. I can confirm I’m now running build 7971. However, I’m still experiencing the same issue.

@ITSolutions Sorry, it’s an old version that was released last week that I’m currently using. I’ll update to the latest and let you know how I get on.

@ITSolutions I can confirm both folders are there and there is a symlink between the two.

@ITSolutions Ubuntu 14.04… Perhaps it’s time to upgrade?

@ITSolutions I’ve tried with IE and Edge. I’ll have to download Firefox if you think it’s worth trying on there as well. I still get the same issue. It’s as if 10.1.0.102 goes directly to the right log-in page, whilst the fog-server/fog/management/ goes to an old database or something… like a remnant of the upgrade.

Another thing to note (which is also a bit of an issue but I’m not too bothered about it) is that I edited the Apache settings before upgrading to trunk so that fog-server/ would go directly to the fog-server/fog/management/ page. Since updating to trunk, that’s stopped working.

@ITSolutions Windows 10 Pro with Google Chrome. I’ve already attempted to clear my browser history, cookies, etc. to no avail.
The server is Windows 2008 R2.
I do get the correct IP when I ping Fog-server.

Another thing to note is that when I go to the ‘wrong’ login page, I can’t login using any of my credentials. It keeps saying username/password is incorrect.

@Wolfbane8653 Yes - Fog-Server points to 10.1.0.102.

Hi all,

I recently upgraded to trunk (as of last week) and I’ve since had a problem when trying to log into fog/management. The problem is, whenever I type in the DNS name - i.e. FOG-Server/fog/management, I’m taken through to a log-in page with 1.2.0 showing in the cloud picture on the left. However, when I type in the IP address: x.x.x.x/fog/management, I get taken through to a log-in page showing the correct version of FOG in the cloud picture.
I’ve tried flushing the DNS on both the server and my PC to no avail. I’ve also checked the DNS records on the server running DNS and that points to the correct IP address. Has anyone else experienced this issue before? Or does anyone know how I would be able to resolve it?

Any help with this would be greatly appreciated as always

@george1421 Upgrading to trunk has resolved this issue - thank you!

@Quazz Thanks! I’ve already done that (as per my initial message) so I should be good to go. I’ll update to trunk later this morning and then see how the booting into the hard drive from the fog menu issue goes.

No - not discouraged at all! Thanks for the help!

I’m currently using dnsmasq so I guess it’s a simple solution of going into that config file and ensuring that undionly.kpxe is the boot file (which I’m pretty sure it is anyway)? How would I go about unlinking undionly.kpxe to undionly.0? Or is it a case of redownloading undionly.kpxe and overwriting the one in the tftpboot folder?

I’ll upgrade to Trunk later today if I can and see how it goes.

Hi everyone,

I’ve just installed FOG 1.2.0 on an Ubuntu 14.04 VM. It’s working great so far - I’ve already registered a host which is a lot further than what I was able to do yesterday. However, I have an issue where the systems won’t boot from the hard drive if nothing is pressed - it just says ‘Press a key to reboot’. I’ve done some research into this and I believe it’s something to do with the chainloader (you’ll have to forgive me - I am new to this).
I’ve linked unidonly.kpxe to undionly.0 using:
sudo ln -s -r undionly.kpxe undionly.0

I’ve created the pxelinux.cfg folder:
mkdir /tftpboot/pxelinux.cfg

and the file /tftpboot/pxelinux.cfg/default, with:
vi /tftpboot/pxelinux.cfg/default

I’ve then written in the default file the following:

DEFAULT vesamenu.c32
MENU TITLE Fog Reimage Menu
MENU COLOR TITLE 1;36;44 #ffffffff #00000000 std
LABEL iPXE Boot
MENU DEFAULT
KERNEL ipxe.krn
APPEND dhcp && chain http://10.1.0.102/fog/service/ipxe/boot.php?mac=${net0/mac}
PROMPT 0
TIMEOUT 3000

Interestingly, I thought the timeout setting would cause the menu to not cancel out so fast (going by a Google result), but it hasn’t changed anything, which makes me think that FOG isn’t reading the pxelinux.cfg/default file for some reason.

The only way to boot from the hard drive is to either press F12 at the beginning of the system booting and select the hard drive from the boot menu, or to press F8 whilst it’s loading from the network and then tell it to boot from the hard drive. I’ve read this: https://wiki.fogproject.org/wiki/index.php/Boot_looping_and_Chainloading and have tried adding the last section mentioned into my cfg/default file to no avail. Maybe I can’t just add it on and it needs to go somewhere specific? I’m not entirely sure.

Any help with this would be greatly appreciated