Topics created by vemoya

@george1421 Thanks for the information on this. Also, what is the process for updating the kernel? I know it is on the GUI side of FOG but not sure if the is a specific process to avoid any unexpected errors. I have 2 storage servers and not sure if this would affect the connection or settings.

Another thing is that I have already set up Windows 10 on this Dell 3410 laptop using the RAID settings on the BIOS. So how can I fix Windows 10 since when changing to AHCI I get a blue screen?

Any tips or suggestions would be greatly appreciated.

Thanks

@JJ-Fullmer Just stumbled upon this again. Added a hint in the web UI (ref).

You might also add this to the documentation. Although when I looked into adding the hint to working-1.6 as well I saw that with the new web UI you actually have a checkbox for file deletion on deletemulti as well as single delete. So it’s only for FOG 1.5.x.

@george1421 The command work for me. Thanks for the help.

@vemoya We have seen hosts go pending but that seemed to have been cause by the PowerShell module API calls.

We shall try to figure out if you have entries in the DB that are obviously not correct:

shell> mysql -u fogmaster -p Password: ... mysql> use fog; ... mysql> SELECT hostID,hostName,hostPending FROM hosts WHERE hostID NOT IN (SELECT hmHostID FROM hostMAC); ... mysql> SELECT hostID,hostName,hostPending FROM hosts WHERE hostID NOT IN (SELECT hmHostID FROM hostMAC WHERE hmPrimary = '1'); ... mysql> SELECT hostID,hostName,hostPending FROM hosts WHERE hostPending = '1'; ... mysql> SELECT * FROM tasks WHERE taskStateID IN ('1','2','3'); ....

You find the password for the “fogmaster” database user in /var/www/html/fog/lib/fog/config.class.php. Please run the queries and try to copy&paste all the results here in the forums. Use PuTTy or some other SSH tool to connect to your server so you can copy&paste text.

@vemoya All I can say you get what you’re paying for.

Create a new iPXE menu that looks similar to this.

Menu Item: os.chainwdsimaging
Description: Boot WDS Imaging Solution
Parameters:
cpuid --ext 29 && set warch x64 || set warch wx86
iseq ${platform} pcbios && set bootfname wdsnbp.com ||
iseq ${platform} efi && set bootfname wdsmgfw.efi ||
chain -ar tftp://10.254.0.155\\boot\\${warch}\\${bootfname}
boot || goto MENU
Menu Show with: All Hosts

The script parameters looks a bit complicated but it basically checks to see if the target is x86 or x64 and uefi or bios to pick the right location and file name to boot.

Understand that for pxe booting there is two methods and it appears you are using both in your setup.

There is the static mode where you define dhcp options 66 and 67 listing statically the boot server and file name to use. In your case your dhcp server looks like you have policies defined to switch between uefi and bios boot files this is good.

The second method you are using is called proxy dhcp this is where you add your pxe boot server (WDS or FOG running dnsmasq) to the last host in your dhcp-helper service on your router. Both WDS and FOG running dnsmasq will respond with the proper boot file when it hears a dhcp discover from the target computer (this is why you have it listed in the dhcp helper service). The proxydhcp server (WDS or dnsmasq) will only provide the pxe boot information leaving your main dhcp server to provide the rest of the boot information. If you have a proxydhcp server configured its settings will override the static settings you have defined in dhcp options 66 and 67.

The reason why I’m telling you this, if you don’t stop the proxydhcp service on WDS it could respond to proxy boot requests giving you a random boot experience. Its ok to have static and dynamic assigned boot files, just know that proxydhcp will override static settings, when you can’t figure out why things are working as intended.

Be aware I did not test the script above only wrote it on the fly without much thought. YMMV

@vemoya said in Cannot find disk on system:

develop something to remedy this issue with RAID BIOS configs

This is beyond the capabilities of the FOG Project. The FOG Project relies on the linux kernel developers to interface with the hardware. Intel will not release the drivers for their RST Raid controller. In tern the linux kernel developers can’t create a driver to see the disks behind the intel raid controller. This is an issue that impacts the entire linux community. The trifecta is uefi + intel RST Raid-On + linux. If you change any one of the elements FOG will be able to see the disks behind the controller.

@Sebastian-Roth Thanks for the TIP. I did make the change on the storage nodes as well. The time on the reports is now correct.

Thanks for the reply.

@vemoya Well 3 GB/s is on the bottom edge of acceptable (in my book). There may be some tuning needed to do in your infrastructure. Its not horrible just a bit slower than expected.

Just be aware with 3 ongoing unicast images you will saturate a 1 GbE link (125MB/s or 7.5GB/min theoretical max) This isn’t a fog issue specifically but a limitation of 1GbE ethernet. You can supplement this by adding additional network cards in your FOG server and then creating LAG links between your network switch and the FOG server. Even if you create these LAG links between the FOG server and switch, if your switch to switch links are 1GbE links that will become your next bottleneck. Again this isn’t a FOG issue, but a byproduct of using a FAST imaging solution. Also if you are imaging more than 2 computers at a time, its best to have an SSD or RAID array in your FOG server and not try to serve multiple unicast streams with a single spindle HDD. That single HDD will not be able to feed the data fast enough to the network adapter.

You mentioned multicasts. This is a great solution to push out one image to many computers, but it also has its drawbacks. You need to ensure your network is capable of multicast imaging (again not a fog issue). If your target computers are on the same subnet as the FOG server that is the easiest solution. You just need to turn on IGMP Snooping on your network switches and then multicast away. Just remember the slowest computer in your multicast group sets the pace for the group. But if properly setup you can multicast 30 computers in about the time it takes to image 2 computers (serially) using unicast imaging.