Posts made by abos_systemax

Ah! I see where my issue comes from…
the “&& goto proxycheck” part is booting towards WDS. because this is a proxy.

Guess I’ll have to build my own ipxe files then

@Tom-Elliott Thnx!

This was the exact answer I was looking for. I was really confused as to where the default.ipxe came from; now I know.

Is this thcase for both the undionly.kpxe and ipxe.efi?

Hello FOG,

I am trying to find out how I can replace the default PXE server from FOG with one of my own.
It is not that I do not like the default PXE server; but I really need WDS to handle the initial requests in order to support SecureBoot enabled devices.

My situation is as follows:

1. The Client boots to network, either UEFI or Legacy
2. The DHCP request is fetched by the WDS Proxy
3. The DefaultBootProgram in WDS is (currently) set to (I have tested several)
   …a. undionly.kpxe
   …b. ipxe.efi
   …c. pxelinux.0

I receive several results;
ipxe.efi just loads and reboots
pxelinux.0 loads a pxelinux menu with a FOG entry (which I edited to chain any of the IPXE files/boot.php’s)
undionly.kpxe works, but not on UEFI devices.

What I am noticing is, when the device boots towards IPXE: it performs a new DHCP request; This is where my issue begins because the WDS DHCP proxy interferes here and somehow I receive default.ipxe as a boot option (I do, in none of my configs, have default.ipxe set as a boot option).

Is this a inbuilt ipxe script; or am I overlooking something?

Love to hear,

@Wayne-Workman I will. I did not pay much attention to it because I assumed that I installed 1.3… but during our Q&A, i slowly realized that there might be an issue with my initial install, especially when I noticed that the FOG client that loaded was 1.2, not 1.3 (but that skips so darn fast that I noticed only after 3 reboots…)

@Tom-Elliott Thanks Tom for the quick help;
For the others in this topic: Thanks as well,
The issue has been resolved. Apparently there was a misconfiguration ‘somewhere’ in the server setup.
I installed FOG 1.2.0 and immediately upgraded to 1.3.1, then configured the SDB harddisk and the images (which were copied from another server), chown-ed and grpch-ed the folders, reconfigured the node and MySQL …

somewhere some setting went wrong;

I’ve reinstalled the server and started from scratch with Fog 1.3.1, now everything works as intended.

@Tom-Elliott
they were indeed! I was wondering where that issue arose from

@Wayne-Workman
The reason why I am using another disk is because we want the images and the server to be separated for replication/backup/restore possibilities.
That is why SDA is only 30GB, and the SDB is 1.2TB

Right now I am reïnstalling the server to see why my FOG install seems to be weird; the password etc don’t match, and the FOG client appears to be 1.2.0 instead of 1.3.0 (dunno if that is what it should be). Upgrading the Kernel doesn’t work.

I did first install FOG 1.2.0 by accident; after which I upgraded to 1.3.1, but there might be some configuration issues?

Will post results asap

@Quazz

root@NLBDGASS-X03:/# ls -lah /images
total 56K
drwxr-xr-x 11 fog  root 4.0K Jan  9 13:40 .
drwxr-xr-x 25 root root 4.0K Jan  8 17:03 ..
drwxr-xr-x  2 fog  root 4.0K Dec 23 14:08 M900_v1
drwxrwxrwx  2 fog  root 4.0K Jan  8 16:15 dev
drwxr-xr-x  2 fog  root  16K Jan  8 15:44 lost+found
-rwxrwxrwx  1 fog  root    0 Jan  9 09:36 .mntcheck
drwxr-xr-x  2 fog  root 4.0K Jan  8 16:15 postdownloadscripts

root@NLBDGASS-X03:/# ls -lah /images/dev
total 8.0K
drwxrwxrwx  2 fog root 4.0K Jan  8 16:15 .
drwxr-xr-x 11 fog root 4.0K Jan  9 13:40 ..
-rwxrwxrwx  1 fog root    0 Jan  9 09:37 .mntcheck

IPTables has been removed (apt-get remove --purge iptables) and the server has been rebooted, but no change

@Quazz changing the root path did not solve the issue.

that is the case.
could it be an issue that the images themselves are in /images/FOGImages (which is also configured in the FOG Setup btw)

@Quazz no, is not enabled. iptables have been flushed.

What is the group that fog belongs to by default that needs ownership of the folder?
Right now the ownership is: fog.root root

Export list for NLBDGASS-X03:
/images/dev *
/images *

/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

Server

• FOG Version: 1.3.1
• OS: Debian Jessy

Hello Foggers,

I am sure that I am not the first one that has this problem, but I’m stuck using the conventional methods.

I have the following setup:

FOG is installed on SDA, SDB (which is a ext4 partition) is mounted to /images
I chmod’ded the /images folder, and did chown fog.root as well.
The same applies to the /images/dev

I touched the .mntcheck in both folders; but still receive an error while partclone is loading,.

The error I receive is:

Checking Mounted File System…
#######################
an error has been detected!
#######################

Fatal Error: Failed to mount NFS Volume

• If you believe the filesystem is mounted, make sure you have a file called .mntcheck
  in the directory you are mounting on the server

#################
Computer will reboot

That gives me good hopes. I’ll create a test setup and post any issues or results that I might experience.
Thanks for the quick replies!

Hello Foggers,

Are there users who tried using FOG on a XenServer installation?
Our company desires to standardize our virtualisation technology, but desires to do this in Citrix XenApp instead of KVM (which I am using right now).

Are there any issues reported lately with FOG 1.3; or things I need to consider?

@abos_systemax said in Fatclone.C: Filesystem isn't in a valid state:

@Wayne-Workman

I kind-a-fixed it by booting to Windows PE, clean the disk with diskpart, create a 100MB parititon and a ‘the rest’ partition; then restoring only partition 2 with FOG, then rebooting to Windows PE to create a bootstore… now Windows can Boot.

I now face another issue, but I’ve posted that in the Windows Issues forums (https://forums.fogproject.org/topic/9177/windows-partition-size)

— fixed that issue as well…

I solved it… I restored the partition again but now with the option ‘Single Disk - Resizeable’ … now the partition shows up as it should.

@Wayne-Workman

I kind-a-fixed it by booting to Windows PE, clean the disk with diskpart, create a 100MB parititon and a ‘the rest’ partition; then restoring only partition 2 with FOG, then rebooting to Windows PE to create a bootstore… now Windows can Boot.

I now face another issue, but I’ve posted that in the Windows Issues forums (https://forums.fogproject.org/topic/9177/windows-partition-size)