Guys, he solved his issue, this is an old topic. We are just playing Necromancy.

Thanks Tom! I’ll just stick with 6.5 then.

yes the exports files is ok.
now the task start but when display " … prepare device … " , waiting…
when i press “enter” , dispay " invalid partition data" and reboot

. i setting “other windows image not resizable” because if setting “windows 7 system” fog return when start-up , boot sector not found !

[quote=“Tom Elliott, post: 40087, member: 7271”]Try this:

[code]update-rc.d isc-dhcp-server disable[/code]

Then edit the file:

Add before the exit 0 line:

[code]sleep 30 && start isc-dhcp-server[/code]

Restart and hopefully all things will work.[/quote][/quote]

Thank you for your help. The syslog still reads the same interface error. I looked into previous syslog files, and at one point, it read out:
[CODE]Withdrawing address record for [IP address] on eth0
Leaving mDNS multicast group on interface eth0
Interface eht0 IPv4 no longer relevant for mDNS[/CODE]

Could any of this have to do with the error?

Yes, it is very true with Ubuntu . I am using Ubuntu and have faced the same problem while setup of internet connection,as this issue got resolved from the experts on [URL=‘http://www.libertybts.com’]site web[/URL] in my new office.

Hi [URL=‘http://fogproject.org/forum/members/junkhacker.21583/’]Junkhacker[/URL],

After creating a image with “Single disk” “Resizable” it’s allright.
The whole disk space is allocated.

Super!

Thanks for the tip!

Kr,

Joeri

Adding authorized_keys will do the job, but I’m not going to add it. Mostly because of the security involvements. If I create a copied authorized keys, it’d be done using methods that would be extremely insecure as it would always have to be the same key.

in what way is it not working?

DNSMasq takes less than 5 minutes to configure and can save you a mountain of time troubleshooting. There could be a number of reasons you are experiencing this error. Do you have access to manage/edit the DHCP scope?

DNSMasq alleviates the need to make changes to the entire scope of the DHCP, I would recommend trying DNSMasq as it has helped many others in the past. DNSMasq involves the installation from apt-get, and a single configuration file, and we already created the template for you in the wiki, you copy and paste and change the ip address information to match that of your location.

Continuing any further without permission of your Network engineer/manager is NOT recommended. You MUST edit the settings at the DHCP server in order for your server to be seen by your network properly.

[url]https://github.com/mastacontrola/fogproject/issues/1[/url]

It’s very possible, I haven’t even tried that route due to lack of time over the summer when I just had to put the legacy/UEFI boot file issue to rest.

The fog system you’re running does not have a mount point labeled as:

/mnt/USB

You need to, in the debug, run:
[code]mkdir /mnt/USB
mount /dev/<usbdevicehere> /mnt/USB
[/code]

All should work then.

[FONT=Arial][COLOR=#333333]I believe I found the issue. I had one DHCP scope in which I had missed updating option 67 to undionly.kpxe. It was still set to pxelinux.0 Once I changed that, it seemed to fix the issue.[/COLOR][/FONT]

Fixed issues mentioned in previous post.

changes made to:
lib/common/input.sh
Due to: “ifconfig and route commands, which were used in older versions of Linux. They are now deprecated in Arch Linux; you should use ip instead.”

See: [url]https://bitbucket.org/david_fear/fog-project/commits/43dfbe784022f04002249ee3491f0ea3d35de77e[/url]

First, lvm is not supported as it controls the volume and formats of those volumes under its control.

You’re sure the second partition is EXT4, or the LVM that, for all purposes, is the second partition is formatted as EXT4?

sorry for the late respond but i not trying to boot from PXE any more.
i try to make it the first boot device and nothing change.

only two things that work is to create an offline repository and then run the boot - repair process
or
[SIZE=14px][FONT=UbuntuRegular][COLOR=#333333]copy GRUB from [/COLOR][/FONT][/SIZE][COLOR=#222222][FONT=Ubuntu Mono][SIZE=14px]EFI/ubuntu/grubx64.efi[/SIZE][/FONT][/COLOR][SIZE=14px][FONT=UbuntuRegular][COLOR=#333333] to [/COLOR][/FONT][/SIZE][COLOR=#222222][FONT=Ubuntu Mono][SIZE=14px]EFI/BOOT/bootx64.efi [as published in [URL=‘http://askubuntu.com/questions/380447/uefi-boot-fails-when-cloning-image-to-new-machine]’]here[/URL]] [/SIZE][/FONT][/COLOR]
but it will only boot from UEFI and not when i try to repair on legacy,

what i need and want to try is to install fresh copy on legacy and then upload it with FOG, then i will try to deploy it on another computer and see…

thanks Cadyfish and Tom

hope that this post will help others

Nir

I’m currently working a different system to this.

I have built a clamav system from source.

Stored the source in /opt/fog/clamav.

Gave it 777 permissions throughout.

Added it to nfs mounts.

Making the mount point happen at boot, along with a checkin to let the system know it’s in progress.

Use those binaries to load the data. Freshclam can be run, and it will update the database files on the fog server as well.

Hopefully this will help us out. If you need the files right away, you can update the freshclam from the fog server using:
[code]/opt/fog/clamav/bin/freshclam[/code]

This is in testing and there may be bugs to work out, but for right now I’m hoping this will help.

It has the added benefit that the init can be that much smaller as it won’t require building the init with clamav built into it. So when clamav updates, you can update on the fog server. I’ll see about building a "zip’ to keep this updated autonomously, but that can wait. I hope this will help everybody out.