Posts made by Sebastian M.

When uploading an image we have a speed from about 600MB/min.
With image size space in use 43GB we need over one hour to complete one upload task.
For me it’s slower than the FOG versions in the past. Is there any reason for this speed?
FOG is the actual version out of SVN, running on VMware ESXi 5.5, Ubuntu 14.04 LTS, two cores, four v-cores and 2048MB RAM. The newest VMware Tools are installed and running.
Sebastian

After a new installation I got the error messages als following:

File not found.
TFTP error - File not found

Looking into /tftpboot there is ony a pxelinux.0.old but no pxelinux.0

System is Ubuntu 14.04 LTS with FOG 0.33b SVN/RC build.

Hey,

what do I have to change at the named files do make it working?

I found them but I cannot find the desired error message “Unable to move…” or something like that.

Sebastian

If you would read the post and he did not edited the post after your questions you could read: “After some searches, i could resolve the issue by restarting the nfs service… The portmapper caused troubles for me as well, so i include it here :”

Hannover, Germany

Which version of FOG are you using?

Yes, right Thank you for you effort!

I will try.

Happend on the systems where we tried to directly link to the NAS.

At FOG Configuration -> FOG Settings I only find the information about TFTP server, there is the entry 192.168.86.105

Hello,

we have a problem with imaging our PC. We are trying to image to a Synology DS212+ NAS.

this is the error message:
[IMG]http://s14.directupload.net/images/130829/el5enpvp.jpg[/IMG]

Settings of the storage node:

[IMG]http://s14.directupload.net/images/130829/5bm4th2x.png[/IMG]
the settings for the path at the synology:
[IMG]http://s14.directupload.net/images/130829/e8xvg26p.png[/IMG]

At the synology FTP and NFS are enabled, the user FOG was added with the password “password”

We added the two .mntcheck files at /images and at /images/dev

It creates the files with the owner fog but is unable to move it:
[IMG]http://s14.directupload.net/images/130829/leoh3bsi.png[/IMG]

I followed [url]http://www.fogproject.org/wiki/index.php/Images_Directory_Permissions[/url] and set the permissions as root user at the Synology over SSH.

[IMG]http://s1.directupload.net/images/130829/mjwcctmg.png[/IMG]

Hello everybody.

Tom Elliott did the trick: [url]http://fogproject.org/forum/threads/kernel-cannot-open-proc-partitions.5487/#post-14450[/url]

Thank you very very much, it works like a charm!

Did both steps auto.register.php and init.gz.

The error message appears again with the ioctl but the registering is done without problems.

Yes, the current 899 revision of 0.33 Beta.

I only followed the tutorial how to build a custom kernel and after doing all things mentioned I got the named error.

Hello,

not actually a problem but the question if it is possible to find out the revision of my installed FOG.

I know that the actual revision is 899 for 0.33B but I have an older install and would like to check if it is the same build.

I used the one mentioned in the tutorial: [FONT=monospace][COLOR=#000000]cp /opt/fog-setup/fog_0.29/kernel/kitchensink.config /usr/src/linux-2.6.35.3/.config[/COLOR][/FONT]

[FONT=monospace][COLOR=#000000]But the file from the 0.33B installation instead, from the system the FOG is running on.[/COLOR][/FONT]

[FONT=monospace][COLOR=#000000]Yes, I used the [/COLOR][/FONT]ARCH=i386 menuconfig and make ARCH=i386 bzImage!

If I use another kernel it works but with my self compiled one I got the error, so I think I have done something wrong while compiling the kernel by myself. I also think that the guide on how to compile it is not complete at all (I mean I read it at another place here at the forum) or not working for me with this tut.

Hey, as written in the PM the bin address is the correct local one and not 127.0.0.1.

I tested the configuration out of the setup package like it is mentioned at [url]http://www.fogproject.org/wiki/index.php/Building_a_Custom_Kernel[/url]

Now I think this was the wrong way

But for me the problem here is always the same and appears with all kernels including yours I have tested before: [url]http://fogproject.org/forum/threads/host-registration-hdparm-ioctl-0x304-failed-inappropriate-ioctl-for-device.4494/[/url]

Hello,

after compiling my custom kernel I got this error messages when starting a FOG registration:

[B]cat: can’t open ‘/proc/partitions’ : No such file or directory[/B]

[B]cannot open /proc/partitions[/B]

[B]hard disk not found![/B]

I followed [url]http://www.fogproject.org/wiki/index.php/Building_a_Custom_Kernel[/url] using

make ARCH=i386 menuconfig
make ARCH=i386 bzImage

for building a x86 kernel.

I tried kernel [url]https://www.kernel.org/pub/linux/kernel/v3.0/linux-3.10.tar.gz[/url] and [url]https://www.kernel.org/pub/linux/kernel/v3.0/linux-3.5.tar.gz[/url]

Are these the wrong kernel or do I have to pay attention to special settings in menuconfig to be able to run the HDD?

Not at the same time, I shut down the one server and started the other one.