Posts made by madeyem

Definitely no semicolon at the beginning of the line.

[quote=“Tom Elliott, post: 36665, member: 7271”]Berlin is +2 hours from GMT?[/quote]

Yes.

The time zones in both ini files are set correctly (in my case to Europe/Berlin). The time shown on FOG is still wrong.

My system time (what I get after typing date) was wrong, although it is also set to Europe/Berlin. After typing “[SIZE=14px][FONT=Ubuntu Mono][COLOR=#222222]sudo ntpdate ntp.ubuntu.com[/COLOR][/FONT][/SIZE]”, system time is correct now. However, “FOG time” is still wrong (2 hours behind).

I’m on FOG 0.32 and I have never been able to make the web interface show the correct time (e.g. in the bandwidth/transmit graph on the dashboard), although I put my time zone in every php.ini file I could find including apache restarts. I eventually gave up on that matter.

Hm dann bin ich überfragt. Ich kann den aktuellen Stand mal auf Englisch übersetzen, damit dir evtl. andere helfen können.

---

Hi everyone,
here is an update on the threadstarter’s problem:

He installed DNSmasq on his FOG server (192.168.115.20), which now handles the IP range 192.168.115.21 - 35 as a DHCP. He has another DHCP (Fritzbox, home router), which handles the IP range 192.168.115.150 - 199.

He can PXE-boot a Windows XP client and has already uploaded an image using the debug-mode. When he tries to PXE-boot a Windows 7 client, he gets an error, which you can see in the screenshot in post #11. PXE-boot is enabled on that client. The threadstartet hasn’t changed anything in pxelinux.cfg/default.

Can someone help?

Hi,
es ist seltsam, dass es mit einem Windows XP-Client geht und mit einem Windows 7-Client nicht. Denn der PXE-Boot hat mit dem installierten Betriebssystem in der Regel nichts zu tun. Der Netzwerkboot läuft ja, bevor das Betriebssystem überhaupt angefasst wird.

Ich würde also zunächst überprüfen, ob im BIOS des Windows 7-Clients der PXE-Boot korrekt aktiviert ist. Ansonsten scheint was in der Datei pxelinux.cfg/default falsch zu sein. Hast du dort was verstellt?

Hi,
es ist wichtig die Optionen 66 und 67 in [I][U]dem[/U][/I] DHCP einzutragen, der auch die IPs verteilt, in deinem Fall also offensichtlich die Fritzbox. Du müsstest hier erstmal recherchieren, ob man dort diese Optionen überhaupt eintragen kann. Bei jedem “normalen” DHCP geht das, aber Fritzbox ist ja eher was für Heimanwender und evtl. kann der das gar nicht.

Ich würde erstmal das, was du im letzten Post gemacht hast, rückgängig machen, d.h. die Fritzbox als next-server wieder austragen.

Du kannst den FOG auch als DHCP nutzen und dort die Optionen 66 und 67 konfigurieren. Allerdings kann es natürlich sein, dass sich die beiden DHCPs dann in die Quere kommen. Man sollte jedenfalls nur einen DHCP in einem Netzwerk nutzen. Als weitere Alternative gibt es noch DNSmasq. Da müsstest du dich erstmal einlesen und das einfach ausprobieren. Ich habe damit noch keine Erfahrungen gemacht. Hier für den Anfang:

[url]http://wiki.ubuntuusers.de/Dnsmasq[/url]
vor allem siehe Abschnitt: [url]http://wiki.ubuntuusers.de/Dnsmasq#PXE-Server[/url]

[CODE]dhcp-boot=/pxelinux.0,zeus,192.168.1.11[/CODE]

“zeus” ersetzt du durch den Namen deines Fogservers und die IP durch die IP deines Fogservers.

[url]http://wiki.ip-phone-forum.de/software:ds-mod:pakete:dnsmasq[/url]

Hi,
ich glaube dein Problem ist, dass dein aktiver DHCP den Clients nicht mitteilt, wo sie das PXE-Bootfile des Fogservers finden. Dafür gibt es im DHCP die Optionen 66 (IP des Fogservers) und 67 (Name des Bootfiles, im Falle von FOG “pxelinux.0”). Diese beiden Optionen musst du im DHCP eintragen, sonst wissen deine Clients nicht, wo sie das Bootfile finden.

Im Client selbst muss die PXE-Bootoption aktiviert sein im BIOS. Normalerweise kannst du mit F12 den Netzwerkboot einleiten auf dem Client. Darüber kannst du erstmal testen, ob dein Client das Bootfile von FOG lädt. Dies erkennst du an dem Erscheinen des FOG-Menüs. Wenn das erfolgreich gelaufen ist, würde ich erst einen Task anstarten.

Ok. Thanks for the info!

Ok. Currently, I’m completely fine with using 0.32. But when there is a stable 0.33, I would consider updating.
However, whenever 0.33 stable is released, I would appreciate a short HowTo, which points out what to look out for while updating from 0.32 to 0.33 in order to keep all the settings, hosts, images etc… In case 0.33 is a complete rewrite, as I read here and there, it might not be possible to update from 0.32 at all.

Maybe Tom can enlighten me, whether or not it will be possible to update from 0.32 to 0.33. Thanks!

Tom,
will your FOG 0.33b at some point in the future emerge to an official and stable FOG 0.33 or will that remain an unofficial side project?

Yes, thanks. I will use parted now. Apparently using cfdisk to create partitions is not good for me.

Sorry, my fault. I thought I had created one partition for the whole array, but apparently the system only created a 1,1 TB partition and left the rest unpartitioned.

Hi James,

thanks, but the path in freespace.php was already correct. In my case the folder is “/images”. The permissions on /images, /dev and .mntcheck are all set to 777.

Hi everyone,

I use FOG 0.32 on Ubuntu Server 10.04 LTS.

The RAID 5EE on my FOG server failed, I replaced 3 disks and created a new RAID 6. After partitioning (with cfdisk) and formatting (ext4) my array, the web interface doesn’t show the right storage size under “Disk information”. It should be about 9985 GB, but it only shows 1035 GB.
If I check the partition size in Ubuntu terminal (fdisk -l), it shows the correct size, so it has to be something with FOG. The settings for FOG haven’t changed. If I remember correctly, someone had a similar problem, but unfortunately I wasn’t able to find the thread.

Can someone help?
Thanks in advance!

Tom,

I installed the laptop manually and already handed it over to an employee. I don’t have a second laptop of that kind (Thinkpad x240), so hopefully Chris can test it.

Thanks, but unfortunately it gets stuck at the same point. Waited over 10 minutes this time, but nothing happened.

Could the SSD be the trouble maker, what do you think? Usually I image computers with HDDs, so I’m thinking maybe the SSD is the problem in this case.

Tom,

first of all thanks for all the efforts you put into FOG!

Yes, I’m quite sure, that it is stuck, because the computer doesn’t react to anything except complete shutdown via power button. I think I waited at least 5 minutes every time before shutting the computer down. You might be right with your assumption. The x240 is a relatively new model, so probably the chipset or whatever driver is missing, causes the problem. The model I have here is the following:

[url]http://www.campuspoint.de/lenovo-thinkpad-university-x240-20ams05e00.html[/url]

The website is German, but you should be able to see the hardware components inside.

Thanks again!

Hi everyone,

I have a brandnew Thinkpad x240 laptop (SSD included) and I want to deploy an image to it. I’m able to boot to Fog, but whatever task I choose from the menu (e.g. Quick host registration) the computer gets stuck and has to be turned off by pressing the power button.

When I try to register, it gets stuck at:

Error Unknown unclaimed register before writing to c5100
Error Timed out waiting for DP idle patterns
Error Unknown unclaimed register before writing to 64040

I registered the laptop manually and tried to deploy and debug-deploy, but it gets stuck as well:

acpi_walk_namespace failed

I use FOG 0.32 with Kernel 3.8.8 on Ubuntu Server 10.04 LTS.

I already tried Tom Elliott’s kernel, but that doesn’t work either. The laptop’s ethernet interface seems to be from “LCFC(HeFei) Electronics Technology”. The first numbers from the MAC are 28:d2:44. Maybe the correct drivers are not included in the kernels. Can anyone help? Maybe Tom?

Thanks in advance!

Maybe this solves your problem:

[url]http://fogproject.org/forum/threads/win-7-image-upload-no-partitions-found.1130/#post-5714[/url]