The kernel does now have support but only basic support of raid though I’m not sure if the init has the dmraid and/or mdadm utilities.

[quote=“loosus456, post: 43874, member: 26317”]I don’t know how much of a pain in the ass it would be to implement, but could the time-zone settings be added either to the Web interface or at least the installation script? Manually editing system files just to correct the time zone seems a little much for the average user, but that’s just my opinion.[/quote]

Web interface now has this support. It will use the UTC setting if no time is set. If php.ini timezone is set, it will use this as its timezone, otherwise it will use whatever you select.

Yes.

Move /images to /home/images and create a symlink to /images from there:
[code]mkdir -pv /home/fog/images
mv /images/ /home/fog/images
ln -s /home/fog/images /images
service mysqld restart[/code]

So
I reinstalled a new machine with a clean install of fog (same OS)
If i use chain command like this:
chain [url]http://<network[/url] IP 1>/fog/service/ipxe/boot.php##params||chain [url]http://<network[/url] IP 2>/fog/service/ipxe/boot.php##params
[U]Boot on the Network IP 1:[/U]
Boot ok, menu fog appears -:)

[U]Boot from network IP 2:[/U]
TFPT…
Then
PXE-E32 : TFTP open timeout
then
TFTP…
And after 5 min , windows boots

But If I open the link [url]http://<network[/url] IP 2>/fog/service/ipxe/boot.php##params in my browser , I have :
#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
colour --rgb 0xff6600 2
cpair --foreground 7 --background 2 2
console --picture [url]http://<network[/url] IP 1>/fog/service/ipxe/bg.png --left 100 --right 80
:MENU
menu
colour --rgb 0xff0000 0
cpair --foreground 0 3

That can never work

I think the best way is open ACL (access control list) between all my network

[quote=“Tom Elliott, post: 43677, member: 7271”]You can upgrade again and that issue should go away.[/quote]

thanks a lot !
After the new upgrade, the interfaces bugs disappears.
When i launch a multicast download, in the fog log i can see the right image location.
But I’m still block after the wol, the clients stop at the image of partclone.
I suspect a network issue .
I tried the procedure udp send and udp receiver for 1 client.
[url]http://www.fogproject.org/wiki/index.php/Multicasting#Testing_1_Client[/url]

udp-send : ok
udp-receiver : no response arrive to the server.
I will search and let you know what i found.

Is it possible to do this without installing FOG as a storage node on the remote servers? I was hoping to set this up using the Samba shares already in place if possible. I could setup NFS shares as well if that would work. The servers at each location are running FreeBSD so installing FOG on them is not really an option.

I saw a “4237 aborted” … This message came up maybe 4 times, #### Aborted, #### Aborted
The last thing I read was “Image Completed”. No errors came up after this .

I have no idea what’s wrong, but obviously it’s the switch and/or router config.

Just to get things rolling for when someone begins to help, you might post your start up configuration for a random switch, and your router? You can post it as a text file, or just right in the forum using the CODE tool, feel free to XXXX out external IP addresses and other sensitive things.

Someone here will help you, just sit tight.

apparently the web gui (even though it says hostname or IP) should only have an IP entered. however the default.ipxe file will allow either name or IP.

I’ve only seen this behavior when upgrading and i forget to kill outstanding tasks or the server reboots during a host edit/add.

[quote=“Joseph Hales, post: 43676, member: 18131”]when you wiped the drive does it still have an mbr fog expects a format drive and errors on a raw blank.[/quote]

I have an ISO image of DBAN on the server to make sure that the drive is properly wiped.

I finally had a chance to look at this project again - I wiped the disk, re-installed a ‘blank’ ubuntu and re-installed FOG. Nothing special, and now it seems to work. Via dumb switch, and via smart switch.

But, thanks for all the help thus far!

[quote=“Junkhacker, post: 43718, member: 21583”]my point regarding the fact that i use a non-GUI version was simply to say that it shouldn’t be an issue.
Chris Wells may have found something that might be relevant [url]http://fogproject.org/forum/threads/not-a-problem-just-a-solution-i-found.12575/[/url][/quote]

I followed these steps and it resolved my problem. I was able to get the FOG software successfully installed, and am now able to connect to FOG manager. Thanks to all for your assistance.

Looks like this on my installation. But please be careful with this as I am not sure about what your offsite FOG nodes will do if the master is empty…

[CODE]# ls -alR /images/
/images/:
insgesamt 32
drwxrwxrwx 7 root root 4096 Feb 3 23:00 .
drwxr-xr-x 28 root root 4096 Feb 15 12:46 …
drwxrwxrwx 2 root root 4096 Mär 7 13:48 dev
-rwxrwxrwx 1 root root 0 Jan 17 10:11 .mntcheck
drwxrwxrwx 2 root root 4096 Jan 17 10:11 postdownloadscripts

/images/dev:
insgesamt 36
drwxrwxrwx 2 root root 4096 Mär 7 13:48 .
drwxrwxrwx 7 root root 4096 Feb 3 23:00 …
-rwxrwxrwx 1 root root 0 Jan 17 10:11 .mntcheck

/images/postdownloadscripts:
insgesamt 12
drwxrwxrwx 2 root root 4096 Jan 17 10:11 .
drwxrwxrwx 7 root root 4096 Feb 3 23:00 …
-rwxrwxrwx 1 root root 233 Jan 17 10:11 fog.postdownload[/CODE]

Correct, the old system didn’t always check null vaues.
The server will need to be upgraded to handle the new client. After that though, the clients can perform in-place upgrades.

It does screw with the logs. It should only need to be done after import/upgrade from 0.32 and even then, only if you’re having problems I think.

Thanks Tom! That did it!

I had database issues with the restart, though. It wanted me to update the database (as during initial installation) and when I clicked it, I received a long list of errors due to the database already being there. I followed some of the fixes on modifying the config.class.php and .fogsettings with no luck. I re-installed FOG which required me to do some dnsmasq changes as well. FOG is working again, but I’ll continue to restart and try more fixes.

Thanks again!!!

in my experience, this happens when i set up a VM as a “windows 8” computer, but not when i set it up as a “windows 7” computer in the new VM wizard. there are no settings i can find after VM creation that make it usable, but you can always install windows 8 on a “windows 7” VM

the new version 1.2.0 the old [SIZE=5][COLOR=#212121]maybe 0.32 no remember[/COLOR][/SIZE]