fixparts is a very powerful tool and can cause damage too. So please make sure you read about those things [B]before[/B] you proceed!! The web is full of information about it, e.g. [url]http://www.rodsbooks.com/fixparts/[/url]

Since I am still kind of new to FOG I am not absolutely sure about FOG 0.32 but I suppose there is not too much of a difference when it comes to MBR…

1. FOG (1.2.0 an newer) does save the MBR from the uploading client at least with image type mps (single disk multiple partition) and mpa (all disks multiple partitions)!
2. bcd(edit) has nothing to do with MBR! Those informations are saved in the first (100MB) partition of your disk, not in the MBR.

As FOG 0.32 is not under development I’d suggest you try setting up a test server with FOG 1.2.0 or even better current SVN version. If your issues still persist we are happy to jump in and fix things for you!

Pleas provide more information about what linux you have and possibly also you FOG version.
What do you mean by ‘DNS address’?? The address of the DNS server being used? Please read this. Might be helpful: [url]http://ubuntuforums.org/showthread.php?t=2066179[/url]

FOGWEBDIR is just a placeholder in this case. If you did not modify it when installing the system it should be like this:

[CODE]cd /var/www/fog/service/ipxe
…[/CODE]
And same again with <CURRDATE>. Just a placeholder. For example use 20150309 instead…

Alright forget about the firewall things I wrote… Switches can be so mean! :mad:
Thanks a lot for reporting back. It’s good to know, so maybe I can point to this earlier next time if someone is having a kind of similar issue!!

Looks pretty good! You were able to mount and list the NFS share. So why should other clients not be able to? Have you tried to run a FOG task again lately?
The only thing I could think of are intermediate firewalls. Looking at your IP addresses I am pretty sure there is not much in between. So maybe it’s a firewall on your FOG server?! Run this command and post the output here:
[CODE]sudo iptables -L -n -v[/CODE]

[quote=“Wayne Workman, post: 43510, member: 28155”]What else are you doing on this Linux VM? Just FOG? What’s all the things that are installed? What versions?[/quote]
Yeah, especially other PHP “apps” (other than phpmyadmin). In the end phpmyadmin might play a role too!!! But so far I don’t have any trouble and use it on most of my FOG servers…

Hmmmm. I personally don’t like reinstalling just for gods sake. Might fix it but you’ll never know why… If that’s ok with you give it a go!

But before that please check your /etc/exports again. I am very sorry to say this but I checked the code from your very fist post character by character just now. Yours looks like this (is that correct???):
[CODE]/images *(ro_sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)[/CODE]

But on my system it looks like this:
[CODE]/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure,fsid=1)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure,fsid=2)[/CODE]

See the differences?? ‘ro_sync’ should definitely be ‘ro,sync’ and I guess those ‘fsid’ parameters at the end are there for a reason too!

Sounds a bit like the file is corrupted. md5sum??
[CODE]$ md5sum Kernel.TomElliott.3.19.0.32
1c47679f256378dee6a673d20e766d31 Kernel.TomElliott.3.19.0.32[/CODE]

If you see a different md5sum you should re-download it. If you see the same it might be broken on the server (corrupt upload)…

partclone.btrfs is part of FOG and therefore already supported I reckon! Haven’t tested it myself though…

Looks pretty good! I just don’t understand why you don’t see this when connecting with NFS…

There are settings on the client (when you install the FOG client service) AND on the FOG server (service settings for this particular host)! Are you sure you set both? Maybe reinstall the client just to make sure!

The other thing that comes to my mind: Do you have SSD hard drives?? If yes you need to change the startup type of the FOG service on the client to “Automatic (delayed)”. See here: [url]http://www.coretechnologies.com/WindowsServices/FAQ.html#DelayedStart[/url]

[quote=“Shock2k15, post: 43482, member: 28829”]Kernal Panic - not syncing: VFS: Unable to Mount root fs on unkown-block(1,0)
Kernal Offset: 0x0 from 0xffffffff81000000 (relocation range: oxffffffff800000000-0xffffffff9ffffffff)
—{ end Kernal panic - not syncing: VFS: Unable to mount root fs on unkown block(1,0)[/quote]

For me this error also sounds like the initrd issue on mac os x… see here: [url]http://fogproject.org/forum/threads/mac-support.11033/page-2#post-34584[/url]

Is there a reason why you still use FOG 0.32? I am still new to this project and don’t know much about the old versions but I suppose this could be a bug in 0.32… and it won’t be fixed as we are heavily working on newer versions.

Maybe you want to setup a new test server with FOG 1.2.0 or even developers version and see if the problem is still there. Please let us know and I am sure we’ll find a way to fix it!

Upload debug is just another type of task you can schedule for a client. Select your client from the host list, click ‘Basic Tasks’ on the left, then ‘Advanced’ and there you see ‘Upload - Debug’. You’ll end up with a linux command shell. There you can run several kinds of tools like ‘fixparts’ and such…

I’ve looked through the PHP code a couple of times but it’s very hard for me to get kickstarted with this much of code that I have not worked with very much yet. I probably won’t be of much help…

But maybe I can point you to some general things I read about this sort of issues. There are a couple of good comments and tipps on debugging memory leaks within PHP code here: [url]http://stackoverflow.com/questions/849549/diagnosing-memory-leaks-allowed-memory-size-of-bytes-exhausted[/url]

Have you worked with ‘memory_get_usage’ pointed out here?? [url]http://paul-m-jones.com/archives/262[/url]

You’ll end up in an iPXE shell…
dhcp, ifstat, ipstat and ping will be helpful to debug you network connection. When it is up you can just chainload default.ipxe (chain tftp://<tftp-ip>/default.ipxe) OR run all the commands by hand (see d4rk3’s earlier post #45).

Thanks for pointing this out! I totally forgot that linux’s ‘mv’ command does not move hidden files. So either you move that file seperately (mv /images/.mntcheck /nas) or you just create it as Joseph suggested.
Concerning access rights ‘mv’ should not alter them. If they were 777 before they should be 777 after moving too! But it doesn’t hure either!

Please search the forums. Numerous people have asked on how to boot ISO files from FOG PXE menu and there are heaps of answers and code snippets on how to do this.

In short: Yes it can be done and it is easier if you use the current (unstable) development version of FOG because PXE menu can be configured within the web interface. With FOG 1.2.0 you’ll have to edit a PHP file to do this…

Right it has been done! But we also see quite some people (little linux experienced) having a lot of trouble to move the location and get it all running (NFS and such).
If you’re unsure I suppose you’re better of NOT changing the path but better mount your NAS to /images. Would be something like this (please think twice before copy paste the commands!! I won’t be liable if anything goes wrong here):
[CODE]sudo mkdir /nas
sudo mount … <nas-share> /nas
sudo move /images/* /nas
sudo umount /nas
sudo rmdir /nas
sudo mount … <nas-share> /images[/CODE]

Try if FOG is happy with this. If everything is fine you should add this NAS-share to your fstab.